
[1.12.2] Crash via Forge Fluid Handler at Cold Igniter
PyroFlareX opened this issue ยท 6 comments
Issue Description:
Custom Pack loads okay (check mod list in log file), but on world boot that previously worked with EnderIO, the server side shuts down.
What happens:
Forge/EnderIO error says fluid isn't registered, checked the configs and it seems to be that vapor one.
What you expected to happen:
World boots okay with Ex Nihilo: Creatio and BetterQuesting freshly added.
Steps to reproduce:
1.Load up modpack (ask if you want download, not public available yet)
2.Load Up world previously created
3.Wait + check log if forge/ world worked
...
Affected Versions (Do not use "latest"):
- EnderIO: 5.0.20
- EnderCore:0.5.18
- Minecraft: 1.12.2
- Forge:14.23.2.2653-2654
Your most recent log file where the issue was present:
Attempted deleting the configs for PE in which I tried to add EMC to infinity powder, got into the world. Thanks for the stack trace help. Also one question:
HOW DO YOU FOLLOW THIS CODE REPO?
Code organization; trying to learn how they programmed this. Kinda a java/modding newbie
The error causing your server crash is this:
Caused by: java.lang.IllegalArgumentException: Stack can not be invalid!
at net.minecraftforge.oredict.OreDictionary.getOreIDs(OreDictionary.java:493) ~[OreDictionary.class:?]
at moze_intel.projecte.events.ToolTipEvent.tTipEvent(ToolTipEvent.java:52) ~[ToolTipEvent.class:?]
at net.minecraftforge.fml.common.eventhandler.ASMEventHandler_331_ToolTipEvent_tTipEvent_ItemTooltipEvent.invoke(.dynamic) ~[?:?]
at net.minecraftforge.fml.common.eventhandler.ASMEventHandler.invoke(ASMEventHandler.java:90) ~[ASMEventHandler.class:?]
at net.minecraftforge.fml.common.eventhandler.EventBus.post(EventBus.java:179) ~[EventBus.class:?]
at net.minecraftforge.event.ForgeEventFactory.onItemTooltip(ForgeEventFactory.java:324) ~[ForgeEventFactory.class:?]
at net.minecraft.item.ItemStack.func_82840_a(ItemStack.java:889) ~[aip.class:?]
...
Which seems to be a bug in ProjectE, not EnderIO. The error following that about fluids is likely related to the now errored game state. If you still get this error without a stacktrace blaming another mod beforehand, we can reopen this issue.