Reading and acting on the mod's log warning safely

Where to look

After launching a world, open the game's log file for that session. Search for the warning the mod emits in place of the vanilla exception. That line tells you a compound or list tag exceeded the normal nesting limit and that loading continued anyway.

What to do with it

1. Copy the exact warning text somewhere you can refer to it.

2. Note the timestamp so you can correlate it with what you were doing or where you were.

3. Back up the save before any inspection or edit.

4. Use an NBT editor on the copy to locate deeply nested tags, guided by any path or context in the warning.

5. Remove or correct the offending data, or identify and address the mod that produced it.

Cautions

Do not assume the warning is harmless just because the world loaded. Deeply nested NBT is abnormal and often signals a bug elsewhere. Avoid editing live save files; always work on a copy. If you cannot find the source, keep the mod installed so the world remains loadable, and monitor the log for changes in frequency or content over subsequent sessions.