Not Enough Crashes Mod FAQ
10 questions players actually ask, answered.
How do I open the crash report after Not Enough Crashes catches a crash?
When the game drops you back to the title screen, a crash report screen appears with the log already displayed. You can read it there, copy it to your clipboard with the copy button, or find the full file in your Minecraft instance's crash-reports folder.
Why does my game go back to the main menu instead of closing when it crashes?
That's the whole point of Not Enough Crashes: it intercepts the crash before Minecraft force-quits, so instead of the window closing you land on the title screen with the report shown. This lets you keep playing or fix the issue without relaunching a heavy modpack.
Can I keep playing on my world after a crash, or do I need to restart?
You can usually return to the title screen and reload your world without restarting the game. If the crash corrupted the current session's state, though, a full restart is still the safer option.
How do I find which mod caused the crash using the Not Enough Crashes report?
Look at the list of involved mods near the top of the report and the stack trace beneath it, then check the clickable links to each mod's issue tracker. The mod whose classes appear at the top of the stack trace is usually the culprit, though a mod listed as 'involved' may just be a victim of another mod's bug.
What do the clickable mod links in the crash report do?
They open that mod's issue tracker in your browser so you can report the bug directly. This saves you from having to search for the right GitHub or CurseForge page yourself.
Why does the crash report mention mods that aren't actually broken?
Not Enough Crashes lists every mod involved in the crash, which includes mods that were merely loaded or called during the failing code path. The real cause is usually the mod at the top of the stack trace, not every mod in the list.
Does Not Enough Crashes work with other crash-handling mods like VanillaFix?
It does similar work to VanillaFix, so running both is redundant and can cause conflicts. Pick one crash-handling mod and remove the other to avoid strange behavior.
Will Not Enough Crashes fix the crash, or just show me the report?
It doesn't fix anything by itself; it only prevents the game from closing and gives you a readable report. You still need to remove, update, or reconfigure the offending mod to actually stop the crash.
Does Not Enough Crashes hurt performance or slow down my game?
It has negligible impact during normal play because it only activates when a crash occurs. The main benefit is saving time on restarts, especially with large modpacks that take a long time to load.
My game still closes on crash even with Not Enough Crashes installed. Why?
Some crashes, like out-of-memory errors or native JVM failures, happen below the level the mod can intercept, so the game still shuts down. Check your crash-reports folder for the log in those cases, since the in-game screen may not appear.