Closed MechanosG closed 1 year ago
just experienced similar thing when trying to load world list in singleplayer. took mod out and works as normal.
@Noaaan heads up there's some conflict with your custom loot condition. It looks like you are using a Vanilla loot condition type instead of creating a custom one. Thats causing my parser to fail on the condition not matching to its presumed actual class type.
I might have to find a way to make parsing by type a bit safer in parallel....
I have the same problem on my end but with different mods
@Mathead253 can you post your crash log(s)? I want to see if there is a different root cause
Version 0.6.4 should handle the problem seen on the OP here, but doesn't fix the underlying problem; using a LootCondition with a non-matching Type, so this will still fail to parse the table this condition belongs too. It should simply log errors instead of crashing.
As such I'll be leaving this issue open to track this.
Just tested 0.6.4. Confirmed not crashing now. I did notice a pretty large memory usage increase and FPS drop.. but not pointing fingers. I'll need to test further and see if it's just coincidence (lots of things it could be - fairly large modpack - but the test world I've been using has been consistent, and nothing had changed for the 0.6.4 test, so it caught my attention). Thanks for the update.
@Mathead253 can you post your crash log(s)? I want to see if there is a different root cause
Sorry for the wait but here's the crash log: crash-2023-06-25_01.24.17-client.txt
Marking this as closed now that I see Noaaan has acted on it and committed a fix.
Seems like a similar issue to this one - https://github.com/fzzyhmstrs/EMI_loot/issues/16 - except mention of Mythic Metals. After noticing the EMI Loot update and adding it to my WIP modpack, loading a singleplayer world pops up the datapack error, wanting to load the vanilla datapack or go back to menu.
Minecraft 1.19.4 Quilt 0.19.1 EMI Loot 0.6.3 EMI 1.0.4 Mythic Metals 0.18.1