How to Read the Not Enough Crashes Report and Find the Culprit Mod

What the crash screen actually shows you

When a crash happens, Not Enough Crashes does not close the game. Instead you are dropped back to the title screen with a crash report window. The top section is the exception message and stack trace, with syntax highlighting so class names and line numbers stand out. Below that is the part most players care about: a list of mods the mod believes are involved in the crash. Each entry is clickable and links to that mod's issue tracker, so you can report the problem directly.

Working through the report step by step

1. Read the very first exception line before the stack trace. It usually names the failing class or method.

2. Look at the stack trace for package names that match a mod's ID rather than net.minecraft or java.

3. Check the involved-mods list. If only one mod appears, that is your prime suspect.

4. If several mods appear, the crash is often an interaction, so test by removing one at a time.

5. Use the copy button to paste the full report into a paste site when asking for help.

Practical tips

A crash on world load usually points at world-gen or entity mods, while a crash on startup points at config or mixin conflicts. The NBT data section is mainly for developers, but it can reveal which block entity or item was being processed when things broke.