[1.18.1] Mixin apply failed
LazyTechwork opened this issue · 11 comments
Hello! I have a problem with adding Immersive Engineering as a dependency. Stacktrace: https://pastebin.com/i03jvvfZ
I manually found public int getRemainingFireTicks() at net.minecraft.world.Entity, but Minecraft does not see it.
Used version of IE and JEI:
implementation fg.deobf("blusunrize.immersiveengineering:ImmersiveEngineering:1.18.1-7.1.0-145")
implementation fg.deobf("blusunrize.immersiveengineering:ImmersiveEngineering:1.18.1-7.1.0-145:datagen")
compileOnly fg.deobf("mezz.jei:jei-1.18.1:9.2.1.69:api")
runtimeOnly fg.deobf("mezz.jei:jei-1.18.1:9.2.1.69")
I can't access the paste, at a guess: You're missing these lines in your build.gradle (after you add them you need to regenerate the run configs for your IDE). If that isn't the issue, please upload the stacktrace to https://gist.github.com or try to figure out why pastebin thinks your original paste "is a private paste or is pending moderation".
Sorry, misclicked, pastebin is public now. Tried to add these lines, it doesn't help.
Can you test with ImmersiveEngineering-1.18.1-7.1.1-pre.41? That accessor Mixin wasn't even necessary any more, so I just removed it.
That time same error, but with ServerWorldMixin. Pastebin
Made my mod`s repo public here
You are missing these two lines in your build.gradle:
ImmersiveEngineering/build.gradle
Lines 111 to 112 in 064b346
They are needed to counteract the refmap in the built JARs and rename the method and field names used in the mixins back to the readable names used in your dev environment. You need to regenerate the runs after adding these lines
I just cloned your repo and set up the environment and I can't reproduce the issue with these two lines added to the build.gradle. If I remove those two lines, it crashes as expected.
Going to reiterate on this: You must reload the gradle project (IDEA shows you a button for that in the editor after modifying the build.gradle, no idea how this is done in Eclipse), then regenerate the run configs for your IDE and make sure to use those generated IDE run configs and not the run<Thing> gradle tasks.
