How to Keep Playing After a Minecraft Crash with Not Enough Crashes

Not Enough Crashes changes what happens when Minecraft runs into a problem, giving you options to continue playing, return to the main menu, or control how often the game is allowed to keep running instead of closing.

The Crash Screen

When something goes wrong during gameplay, a screen titled Minecraft crashed! appears. Its summary states that Minecraft ran into a problem and crashed. Below that, the screen lists the mod or mods identified as potential causes of the crash. If no mod could be singled out, it shows No Mods. along with a note that a mod could still be indirectly responsible. If the identification process itself fails, an Error identifying, report to Not Enough Crashes message appears instead.

Each mod shown in the list can be clicked to open that mod's website, where you can get support. A report is also generated, and the screen offers a Get link button that opens it in your browser. You are encouraged to send this report to the author of the responsible mod so they can fix the issue. If saving the report fails, an error message points you to the log.

Because Not Enough Crashes is present, the crash screen tells you that you can keep playing despite the crash. That is the core purpose of the mod: a crash does not have to end your session.

Startup Failures

Not everything can be recovered from. If the game fails before it finishes loading, you see a different screen titled Minecraft failed to start! It explains that an error during startup prevented Minecraft from starting. The same report and mod-identification information appears, but the screen makes clear that continuing to load is not possible after this kind of error. In this situation, your only path forward is fixing the underlying problem.

Returning to the Main Menu

The crash screen includes a Return To Main Menu button, which lets you leave the crashed session and go back to the menu rather than quitting the game entirely. This button can be turned off in the configuration. The setting Disable Return To Main Menu controls it: when enabled, the button is disabled during a crash, which means you cannot recover from that crash.

Configuration Options

The Not Enough Crashes Configuration screen holds the settings that shape this behaviour.

• Catch Gameplay Crashes — when off, the mod will not try to stop the game from closing after a crash. Note that this is always disabled when Iris is present, even if the setting is on.
• Catch Initialization Crashes — available on Fabric only. When off, the game closes normally if it fails to initialize and no special crash screen is shown. This is always disabled when certain other mods are present, regardless of the setting.
• Disable Return To Main Menu — when on, the Return To Main Menu button is unavailable during a crash, so recovery is not possible.
• Debug Mod Identification — when on, extra information is written for mod developers.
• Disabled by config — indicates a feature that has been switched off through configuration.

How Often the Game Is Kept Open

The crash limit setting decides how many times Not Enough Crashes will attempt to prevent the game from closing within a single session. Once that number is reached, the mod stops intervening. Lower it if you want the game to close sooner after repeated crashes; raise it if you would rather keep recovering and continue playing.