[1.19.2] Startup crash that didn't appear before. (Part of larger modpack but crash report suspects Emendatus Enigmatica)
Closed this issue · 7 comments
Issue description
Now I've seen this specific crash report before, but I don't remember how I fixed it.
And again, it's part of a larger modpack, but the crash message went like this:
Error: java.lang.NullPointerException: Registry Object not present: emendatusenigmatica:dimensional_block
Steps to reproduce
No response
Minecraft version
1.19.2 (Latest)
Forge version
43.3.9
Emendatus Enigmatica version
2.1.x (Latest)
Other relevant versions
No response
If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)
Could you mind post the full latest.log 😅
EE Data generation, if any other mod crashes before it, gets reported as the cause, even tho EE is not at fault.
OK pastebin link of it
See line 447 of the log file. A mod zeta fails to get created, causing a ton of other mods to crash, with EE being last.
[21:48:06] [modloading-worker-0/ERROR]: Failed to create mod instance. ModID: zeta, class org.violetmoon.zetaimplforge.mod.ZetaForgeMod
java.lang.NoClassDefFoundError: net/minecraftforge/event/BuildCreativeModeTabContentsEvent
at org.violetmoon.zetaimplforge.ForgeZeta.start(ForgeZeta.java:272) ~[Zeta-1.0-16.jar%23652!/:1.0-16]
at org.violetmoon.zeta.mod.ZetaMod.start(ZetaMod.java:19) ~[Zeta-1.0-16.jar%23652!/:1.0-16]
at org.violetmoon.zetaimplforge.mod.ZetaForgeMod.<init>(ZetaForgeMod.java:30) ~[Zeta-1.0-16.jar%23652!/:1.0-16]
at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:?]
at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:77) ~[?:?]
at jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:?]
at java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:500) ~[?:?]
at java.lang.reflect.Constructor.newInstance(Constructor.java:481) ~[?:?]
at net.minecraftforge.fml.javafmlmod.FMLModContainer.constructMod(FMLModContainer.java:70) ~[javafmllanguage-1.19.2-43.3.9.jar%23655!/:?]
at net.minecraftforge.fml.ModContainer.lambda$buildTransitionHandler$4(ModContainer.java:122) ~[fmlcore-1.19.2-43.3.9.jar%23654!/:?]
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1804) [?:?]
at java.util.concurrent.CompletableFuture$AsyncRun.exec(CompletableFuture.java:1796) [?:?]
at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373) [?:?]
at java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182) [?:?]
at java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655) [?:?]
at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622) [?:?]
at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165) [?:?]
Caused by: java.lang.ClassNotFoundException: net.minecraftforge.event.BuildCreativeModeTabContentsEvent
at cpw.mods.cl.ModuleClassLoader.loadClass(ModuleClassLoader.java:141) ~[securejarhandler-2.1.4.jar:?]
at java.lang.ClassLoader.loadClass(ClassLoader.java:525) ~[?:?]
... 17 more
A fix for EE getting reported in the crash reports is on the dev branch, and when 1.21.1 port is ready, should be in the release version of the mod as well.
Well, that's good to know. Once I'm back on my laptop I'll see what I can do from here.
So removing Zeta didn't fix it, but seeing how you did what you did has let me figure out how to troubleshoot a bit by myself, and for that I GREATLY thank you for saving me so much time whenever this happens.