Copper Ore crashes the game.
MagmaBro123 opened this issue ยท 18 comments
Simply start the game, and it instantly crashes.
crash-2020-06-17_22.40.06-client.txt
Forge version 31.2.20, MC 1.15.2.
This issue has been marked as stale because it has been inactive for 3 weeks. It will be closed if it remains inactive for another 3 weeks.
This issue has been closed since it has been inactive for 3 weeks since it was marked as stale.
Same crash reason different mod that caused it for me, it was Survive Combat Compat causing the copper ore crash.
Somebody also reported yesterday, that BetterPVP was causing this same error for them. Seems like a error from mod compatibility, so try removing one mod at a time. (And post back, so the devs know what to fix!)
Removing Placebo (along with FastFurnace and FastWorkbench, which it's core for) stopped the crash for me.
I removed Quark Oddities as part of working on something else, and the crash started occurring again. Adding Oddities back fixes it.
Interestingly enough, I got this crash because of another mod that needed an updated version of Java. Without Create, it would post a message saying to upgrade my Java version, but with Create enabled, it would crash with this exact exception...very strange indeed.
So could this be related to another mod crashing or another mod needing an updated version of Java? I have no idea. The only consistency seems to be another mod causing the issue, not necessarily Create itself.
I just removed Performant and the error stopped happening. Performant wasn't loading correctly without Create on either. I'm not sure if Lithium causes the same issue since they're basically the same mod. I also updated my NVIDIA drivers and Java.
2020-08-04-4.log
Here
Seems that in your particular instance, Corail Tombstone failed to load with the turkish OS locale.
As was discovered by other users, this crash seems to happen more likely when another mod interrupts the pipeline somehow.
If it's not that, it could also be caused by configs being loaded too early.
Create crashes this way when it tries to register config-driven worldgen without knowing about its own blocks.
I suppose best would be to collect more logs.