Getting a Crash Report Link and Identifying Problem Mods with Not Enough Crashes

guide

When Minecraft runs into a problem and crashes, Not Enough Crashes shows a crash screen that helps you find the report, reach the right mod author, and keep playing where possible. This guide explains how to use that screen, how to open a mod's support website, and how to turn on extra logging for mod identification.

Reading the Crash Screen

The crash screen is titled Minecraft crashed! and its summary states that Minecraft ran into a problem and crashed.

Below that, the screen lists the mods that may be responsible. The line reads that the following mod or mods have been identified as potential causes. You are encouraged to send the report to the author of the named mod so they can fix the issue.

Because Not Enough Crashes is present, the screen also tells you that you can keep playing despite the crash. That option is not always available — see the startup case below.

If no mod could be pinned down, the screen shows No Mods. along with a note that a mod could still be indirectly causing the crash. If the identification process itself fails, the screen shows [Error identifying, report to Not Enough Crashes]. If the report could not be saved, the screen shows [Error saving report, see log]. A mod may also appear as [Failed, Report to NEC].

Getting the Report Link

A report is generated automatically when the crash screen appears, and the screen shows where it can be found, with a clickable element to open it.

To open the report in your browser, click the Get link button.

Clicking Through to a Mod's Website

The mod list on the crash screen is interactive. Click any mod in that list to go to that mod's website for support. This is the fastest route from a crash to the place where the mod's author can act on the report, so use it after you have the report link ready to share.

Startup Failures

Not every failure happens during play. If an error during startup prevented Minecraft from starting, the screen is titled Minecraft failed to start! with a summary explaining that a startup error blocked the game from launching.

The support guidance is the same: send the report to the mod's author so they can fix the issue. The difference is recovery — when the failure happens at startup, it is not possible to keep loading Minecraft.

Debug Mod Identification

Debug Mod Identification is a setting that controls extra logging. When it is true, additional information is written to the log for the mod developer. Turn it on when you need more detail about how mods were identified as crash causes, and leave it off otherwise.

These settings live under Not Enough Crashes Configuration and change how crashes are handled.

Disable Return To Main Menu — when true, the Return To Main Menu button is disabled while crashing, which means you cannot recover from the crash.
Catch Initialization Crashes — when false, the game closes normally after failing to initialize and does not show the special crash screen. This option is always disabled, even when set to true, if certain mods are present.
Catch Gameplay Crashes — when false, Not Enough Crashes does not try to stop the game from closing after a crash. This is always disabled, even when the config is set to true, if Iris is present.
Crash Limit — controls how many times Not Enough Crashes will try to prevent the game from closing within a single session.

Quick Reference

Crash report location: shown on the crash screen, with a clickable element.
Open the report: click Get link.
Reach a mod's support site: click that mod in the list.
Extra developer logging: enable Debug Mod Identification.
Keep playing after a crash: available for gameplay crashes, not for startup failures.