NPE after adding new Material
pyure opened this issue ยท 6 comments
I added "graphite" to my "metals" Material[] array. I now get a null pointer exception when I try to start up minecraft.
Crashlog: https://pastebin.com/UyCkCpxw
Script: https://pastebin.com/r0jfdvFi
acronym\saved\material_parts_contenttweaker.json: https://pastebin.com/cv7ZUmhg
acronym\saved\material_parts_contenttweaker-original.json: https://pastebin.com/b4RjBz3s
Possibly-related: I had also just uncommented the bottom loop which registers the ores. Various things went weird at that point as (presumably) orphaned ids were attempted for reuse. (Specifically: At least one "block" type transformed into an Ore in game)
Possibly-related:
- If I remove "graphite" from the list, we start fine
- If I re-add "graphite" back to the list, we seem to start fine, but the crushed-ore item is missing (others are there)
- If I restart with no further changes (hoping clean-up routines will get my crushed ore back in) we get the NPE.
Any chance this has to do with the sheer number of materials/parts I'm adding? I tried adding "graphitenew" and "graphite2", both of which also failed.
Potentially. Ive found about the time you reach 1000 parts, thinks start breaking down.
hmm I'm at 274 parts in the saved/json file right now, not even close to your observed limit.
Is there any other useful information I can provide here?
If I weren't so terrible at setting up Java environments I'd try to debug this myself :(
Not a clue then. But next release has a bit more debugging code in it so hopefully that'll work?