How to stop the "NBT depth exceeded" crash from blocking your world load

What the mod changes

Vanilla Minecraft refuses to load a save when it encounters a compound or list NBT tag nested deeper than the engine's limit. Instead of throwing the exception that aborts loading, this mod downgrades the event to a log warning and lets the game continue. If your world previously failed to open with a depth-related error, the mod should now let you in.

Steps to get back into the world

1. Back up the save folder before doing anything else.

2. Launch the game with the mod installed and attempt to load the affected world normally.

3. If it loads, play as usual — but treat the warning as a signal, not a fix.

4. Open your latest log file and search for the warning text the mod prints. Note which tag path or region it references.

5. Use an external NBT editor on a copy of the save to inspect the flagged chunk, entity, or block entity.

Why you should still investigate

A tag nested past the normal limit is abnormal data, usually caused by another mod writing malformed or runaway NBT. The mod only prevents the hard failure; it does not repair the data. Leaving it in place can cause repeated warnings, lag, or save bloat. Identify the source mod or the offending structure and remove or correct it.