Incompatible with mystcraft
Sunconure11 opened this issue · 8 comments
Tried testing mystcraft against my pack, ran into this.
Considering the number of mods with custom loot entry types, I've opted to make LootTweaker handle them as best it can. It's not perfect, but the next version will handle custom loot entry types much better. They won't cause the mutable loot system to crash; and when dumping loot tables, they'll be serialised in a best effort manner.
I've got docs to write for the new features in the next version, so hopefully I can get it out tomorrow.
0.2.0 implements the above behaviour, so the crash will no longer occur. Everything should work as expected now.
https://www.curseforge.com/minecraft/mc-mods/loottweaker/files/2988990
I'm keeping this issue open though, as a reminder to work on a guide to doing loot modification in a clean, robust manner.
It's a known issue on Mystcraft's side, #69 was the same issue, though the paste has now expired.
The error is deliberate, but it doesn't have to crash Minecraft. I'll see what I can do about that.
@TheFloydman
Mystcraft's current loot code is frankly a mess, it needs a rewrite. TreasureGenWrapper doesn't do anything.
Symbol pages are generated in Mystcraft library chests with another custom subclass of LootEntry, which could have been an item entry with a set_count loot function.
@xJon It's the same root cause. Internal changes in LootTweaker cause it to manifest differently.
Not a Mystcraft dev but am slightly familiar with the source. Could this be fixed on Mystcraft's end by extending LootEntryEmpty, LootEntryItem, or LootEntryTable instead of LootEntry directly?