Crash help

Minecraft crash report reader

Which mod crashed your game? Paste the crash report, the text that starts with ---- Minecraft Crash Report ----, or your latest.log, or drop the file here. Modkeel reads the error and names the mod that most likely caused it.

Find it in your instance folder: the newest file in crash-reports, or logs/latest.log when the game closed without a report.

How to read a Minecraft crash report

A crash report starts with ---- Minecraft Crash Report ----, then a joke line, the time and a Description such as "Mod loading failed" or "Ticking entity". The lines that matter come next: the exception (for example java.lang.NoClassDefFoundError or MixinApplyError) and the stack trace under it. Package names in that trace usually name the mod, and a mixin error names the mod's mixin config. Further down, the mod list shows each mod's version. Paste it above and Modkeel reads it for you; the crash help pages explain the common errors one by one.

Questions

Is there a mod that tells you which mod crashed Minecraft?

Yes. The Modkeel Companion, a free and open source mod for Fabric, NeoForge and Forge, does what this page does on the next start, with the mod files in front of it: it names the mod that most likely caused the crash, says how sure it is and why, and offers to turn that mod off or go back to the mods that last worked. It also copies each world before it loads with different mods.

Do I have to upload my crash log?

The text you paste is sent to api.modkeel.com, read in memory to find the mod, and dropped: it is not stored and not logged. Crash reports can hold your user name in file paths; none of it is kept.

How sure is the answer?

Each answer says Most likely, Likely or Possibly, and why: for example the loader says the mod failed to load, the error names the mod's mixin, or the mod's code is in the crash trace. When several mods are in the trace and none stands out, it says Possibly: if the first mod is not it, try the next.

Why does it name a mod that seems unrelated?

The mod named is the one whose code was running when the game crashed. Sometimes that mod is only where another mod's problem surfaced, for example a library mod called by the mod that is really out of date. Move the named mod out first; if the game still crashes, try the next one in the list.

It found no crash. What did I paste wrong?

Paste the whole crash report, from the line ---- Minecraft Crash Report ---- down, or the whole logs/latest.log. The launcher's own log or a screenshot of the error does not have the lines it needs.

What is a Caused by line?

Java errors can wrap one another: each Caused by line is the error behind the one above it. The last Caused by in a block is usually the real problem, and the package names under it usually name the mod.

What happens to your text

It goes to api.modkeel.com, is read in memory to find the mod, and is dropped: not stored, not logged. Crash reports can hold your user name in file paths; nothing of it is kept. Privacy.

Let the game tell you

The Modkeel Companion does this on the next start, with the jars in front of it, and offers to turn the mod off or go back to the mods that last worked. Free and open source, for Fabric, NeoForge and Forge.