MC-WIKI.net
Not Enough Crashes Wiki › Guides › What Happens When Minecraft Fails to Start and How to Use Catch Initialization Crashes

What Happens When Minecraft Fails to Start and How to Use Catch Initialization Crashes

guide

When Minecraft cannot get past startup, Not Enough Crashes shows a dedicated crash screen instead of letting the game vanish silently. This screen is separate from the one you see when the game crashes during normal play, and it behaves differently in one important way.

The "Minecraft failed to start!" screen

If an error occurs while Minecraft is initializing, the game displays a screen titled Minecraft failed to start! with a summary explaining that a startup error prevented Minecraft from starting.

Below that, the screen works much like the regular crash report:

  • A line tells you which mod or mods have been identified as potential causes.
  • If no mod could be singled out, the screen says No Mods. and notes that a mod could still be indirectly causing the crash.
  • If the identification process itself ran into trouble, 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.

You are encouraged to send the report to the author of the identified mod so they can fix the issue.

The key difference from a gameplay crash: the screen states plainly that it is not possible to keep loading Minecraft because of this error. Unlike a crash during play, you cannot continue past a startup failure.

The crash screen is interactive:

  • Click any mod in the list to go to that mod's website for support.
  • A report has been generated for you, and the screen shows a clickable location where it can be found.
  • Click the Get link button to open the report in your browser.

The Catch Initialization Crashes option

Catch Initialization Crashes is a setting in the Not Enough Crashes configuration, available on Fabric only. Its behavior:

  • When enabled, a failure to initialize produces the special crash screen described above.
  • When set to false, the game closes normally on a failed initialization and no special crash screen appears.
  • The option is always treated as disabled, even when set to true, if certain mods are present.

The same configuration screen holds several other settings that affect crash handling:

  • Catch Gameplay Crashes — when false, Not Enough Crashes will not try to stop the game from closing after a crash. This is always disabled, even if set to true, when Iris is present.
  • Disable Return To Main Menu — when true, the Return To Main Menu button is disabled during a crash, which means you cannot recover from that crash.
  • Debug Mod Identification — when true, extra information is written for the mod developer.
  • Crash Limit — controls how many times Not Enough Crashes will try to keep the game from closing within a single session.
  • Disabled by config — shown when a feature is turned off through configuration.

Operating the interface

The configuration screen is titled Not Enough Crashes Configuration. Open it through the mod's own interface, then adjust each option directly. If you prefer to reach the configuration through a hotkey instead of the on-screen list, use the corresponding hotkey and set it in the controls menu.