Stop reporting bugs with forge 2657 it broke go away
PurpleHel opened this issue · 8 comments
Minecraft 1.12.2
Forge 14.23.3.2657
Actually Additions 1.12.2-r133
Crash occurs with no other mods enabled, is fixed by reverting to Forge 14.23.2.2654
I got another one: https://pastebin.com/2KayeD0X
Some news
- This is definitely caused by capabilities not being initialized properly. I tested with the energy cap, no mods except forge (only modification to Forge was inserting a null-check after the capability initialization).
- It only happens in a normal MC client, not a Forge dev environment (as in a environment for making Forge PR's, not an MDK. No idea whether those crash). I don't think it's because of obfuscation, the relevant classes shouldn't be obfuscated and the commits that broke it aren't obfuscation related as far as I can see. This is a bit inconvenient since making a forge build takes about 9 minutes for me.
EDIT: Probably caused by this LOC. It seems like the Forge jar was loaded/added through that call, which now only happens in dev.
MinecraftForge/MinecraftForge#4865
I guess this can be closed now, it's definitely a Forge issue.
@PurpleHel @MasterEnderman downgrade Forge to the recomended version (2654), that should fix it.
I'll keep it open to prevent duplicates being opened. I'll close it when 4865 is closed
it's not an issue with actually additions, but with forge itself. had it also happen with thermal expansion and refined storage.
Linking to BluSunrize/ImmersiveEngineering#2934 since it's probably caused by the same problem. I might try to debug this later today.
