I went through and added a bunch of the mods that said error in the report to a test modpack and they worked in that modpack I also kept adding until most of the world changing mods were in it and no problems. Im not sure what is the issue as I cant really understand the crash report. Does someone know whats wrong is there an incompatibility? Heres the crash report https://paste.ubuntu.com/p/P4HhDJR2Y5/
The Meaning of Life, the Universe, and Everything.
Join Date:
3/27/2016
Posts:
84
Member Details
Usually seeking out the mod's Discord or otherwise GitHub is where bugs and crashes are to be reported. For modpacks (usually asking on the official servers for the respective mod loader, if it exists, may help you solve the issue), the issue is usually an incompatible mod.
Official modpacks seem to have many issues at first, but update over time as mod's fix each other's incompatibilities.
In this specific case, your modpack crashed after pressing the world create button, then some registry is throwing an IllegalStateException. Some mod has registered something incorrectly or one of the mod's mixins is causing an issue with another mod (the render thread errored because a screen crashed). I suggest removing each mod one by one till the crash stops, and which ever mod you add causes the crash to reappear, report the issue to that mod's GitHub page, if it has one.
Note that the crash log mentions
clifftree:temperate_beach
in the error:
Unbound values in registry ResourceKey[minecraft:root / minecraft:worldgen/biome]
This means that mod didn't register their biome properly. Report it to the mod author if you can.
I went through and added a bunch of the mods that said error in the report to a test modpack and they worked in that modpack I also kept adding until most of the world changing mods were in it and no problems. Im not sure what is the issue as I cant really understand the crash report. Does someone know whats wrong is there an incompatibility? Heres the crash report https://paste.ubuntu.com/p/P4HhDJR2Y5/
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumUsually seeking out the mod's Discord or otherwise GitHub is where bugs and crashes are to be reported. For modpacks (usually asking on the official servers for the respective mod loader, if it exists, may help you solve the issue), the issue is usually an incompatible mod.
Official modpacks seem to have many issues at first, but update over time as mod's fix each other's incompatibilities.
In this specific case, your modpack crashed after pressing the world create button, then some registry is throwing an IllegalStateException. Some mod has registered something incorrectly or one of the mod's mixins is causing an issue with another mod (the render thread errored because a screen crashed). I suggest removing each mod one by one till the crash stops, and which ever mod you add causes the crash to reappear, report the issue to that mod's GitHub page, if it has one.
Note that the crash log mentions
in the error:
This means that mod didn't register their biome properly. Report it to the mod author if you can.
Hope this helps to some degree.