Blame (Forge)

By
telepathicgrunt

Those gosh darn crashlogs not saying which worldgen feature is crashing!

If a template pool has a weight that is super high, Blame will report that problematic pool since super high weights will actually eat up RAM very fast. And if too high, it can crash the game with an Out of Memory error!
If a mod or datapack tries to access a missing nbt file (used often for making structures), Blame will state this so you can let the modders know!
Any command that crashes when used will now print a stacktrace so modders can know why it broke easier! Typical behavior is that the command fails silently which is super bad. That's why Blame aimed to add more info here!
Ever opened a chest and found it was empty? That could be caused by the LootTable in the chest doesn't exist! Blame will detect that when the loot is attempted to be made and print out what the missing loot Table is!
Any biome with an unregistered ConfiguredFeature, ConfiguredStructure, or ConfiguredCarver will not get a Blame report that states the JSON of the thing and which biomes are affected! Look at the JSON to try and find which mod the thing came from.
Blame can detect if a ConfiguredFeature is broken like the one shown here. This one has a value that is out of the range that it accepts and it shows which ConfiguredFeature it is so it can be fixed!