Leaderboard

Also, in the block models (block_drill_basic.json and block_drill_advanced.json) you need to use commas after each texture entry.

No, they aren't. According to https://jsonlint.com/ (for drill.json): Error: Parse error on line 48: ...", "y": 90 }, }} --------------------^ Expecting 'STRING', got '}' Although the actual problem is not with the 90, but a few characters later. I have to edit the tabs into 4 spaces to get the error to line up properly: Error: Parse error on line 48: "y": 90 }, }} --------------------^ Expecting 'STRING', got '}' You have an extraneous comma.

Your JSON file is broken.

Ignore it. It's deprecated because you aren't supposed to call it. Overriding is fine.

Your blockstate json file is missing.

You probably could do that. Depending on exactly how your mod works, it may be easier to simply maintain a list of block positions and search that.

It's overridden in WorldServer to call ChunkProviderServer#getNearestStructurePos, which in turn calls IChunkGenerator#getNearestStructurePos. ChunkGeneratorOverworld implements this to look for a hardcoded set of Vanilla structure types, so there's no good way for mods to hook into it. This PR aims to resolve that.

https://wiki.mcjty.eu/modding/index.php?title=Dimensions-1.12

Do it by binary halves: PIck half of the mods (alphabetically works). Doesn't need to be an exact half. Just make sure that Animania stays in each time. Remove those mods. If the problem persists, remove half of what remains. If the problem goes away, put half of the most recently removed mods back. Repeat until adding/removing a single mod causes the problem. This should take no more than 7 iterations for ~100 mods.