Server crashing at startup
Remi4001 opened this issue ยท 6 comments
When I updated astral sorcery in my custom modpack from version 1.10.12 to 1.10.13, the server was crashing during startup and when I came back to version 1.10.12 it was launching correctly.
crash-2019-04-10_19.36.25-server.txt
2019-04-10-4.log.gz
java.lang.IllegalAccessError
As can be seen on first glance, it's not a implementation problem, this happened on the JVM.
Probably due to an access level change on net.minecraft.item.crafting.Ingredient#matchingStacks - is it private/protected in newer forge versions now?
That being said, it could also be just public because some other mod in my dev environment adds that to be public. Either way, will address this in a hotfix later today (around 7-8 hours from now probably)
Temporary fix:
Include crafttweaker in your modpack for the time being.
Isn't AS crashing.
"java.lang.Error: java.lang.reflect.InvocationTargetException
at slimeknights.mantle.pulsar.internal.BusExceptionHandler.handle(BusExceptionHandler.java:34)"
This is astral sorcery, read two more into the caused by:
Caused by: java.lang.IllegalAccessError: tried to access field net.minecraft.item.crafting.Ingredient.field_193371_b from class hellfirepvp.astralsorcery.common.crafting.ItemHandle$HandleIngredient
at hellfirepvp.astralsorcery.common.crafting.ItemHandle$HandleIngredient.apply(ItemHandle.java:318)
at net.minecraftforge.common.crafting.CompoundIngredient.apply(CompoundIngredient.java:93)
at slimeknights.tconstruct.smeltery.TinkerSmeltery.registerRecipeOredictMelting(TinkerSmeltery.java:755)
at slimeknights.tconstruct.TinkerIntegration.postInit(TinkerIntegration.java:175)
... 42 more
Only reason Tinkers Construct shows up in the report is because the crash happened during one of our initialization methods, specifically a crafting registry scan.