All elements that used geckolib models can't compile anymore

Started by TDO on

Topic category: Help with MCreator software

Last seen on 20:10, 17. May 2024
Joined Dec 2022
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
All elements that used geckolib models can't compile anymore

Everything semmed to work perfectly for now when suddenly every element of my workspace that used geckolib now fails to compile. idk why.

I can't put the entire error message of the console but heres a part of it :

xecuting Gradle task: build
Build info: MCreator 2023.4.52316, forge-1.20.1, 64-bit, 8021 MB, Windows 11, JVM 17.0.9, JAVA_HOME: C:\Program Files\Pylo\MCreator\jdk, started on: 2024-01-28-22:14:11
Loaded APIs: geckolib

> Task :compileJava
C:\Users\onyxl\MCreatorWorkspaces\tdosmod\src\main\java\net\mcreator\tdosmod\client\model\Modelsamuraiarmor.java:6: error: cannot find symbol public class Modelsamuraiarmor<T extends Entity> extends EntityModel<T> {
^
symbol: class EntityModel
C:\Users\onyxl\MCreatorWorkspaces\tdosmod\src\main\java\net\mcreator\tdosmod\client\model\Modelsamuraiarmor.java:6: error: cannot find symbol public class Modelsamuraiarmor<T extends Entity> extends EntityModel<T> {
^
symbol: class Entity
C:\Users\onyxl\MCreatorWorkspaces\tdosmod\src\main\java\net\mcreator\tdosmod\client\model\Modelsamuraiarmor.java:9: error: cannot find symbol public static final ModelLayerLocation LAYER_LOCATION = new ModelLayerLocation(new ResourceLocation("tdosmod", "modelsamuraiarmor"), "main");
^
symbol: class ModelLayerLocation
location: class Modelsamuraiarmor<T>
where T is a type-variable:
T declared in class Modelsamuraiarmor
 

Last seen on 11:41, 17. May 2024
Joined May 2022
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • MCreator plugins:
  • Comments:
Is it possible you haven't…
Mon, 01/29/2024 - 23:50

Is it possible you haven't updated Geckolib recently? Some of the snapshot versions are kinda buggy. Also try clearing the gradle caches. If neither of these helps, it's possible there's a bigger problem.