How to read a Minecraft crash report

Read it in this order

A crash report is long and almost all of it is irrelevant. Four things matter, and they are not at the top.

1. The last Caused by:

Not the first exception — the last Caused by:. Everything above it is wrapping. Mod Loading has failed, Failed to initialize server and Exception in server tick loop are all envelopes that tell you nothing about the actual fault.

2. The first non-vanilla jar in the trace

Forge tags every frame with its source jar in ~[...]. Skip Minecraft, Forge, the JDK and bundled libraries; the first mod jar remaining is almost always responsible. Full method in finding the mod at fault.

3. The -- being ticked -- sections

Most people never scroll this far, and it is frequently the most actionable part of the file:

-- Entity being ticked --
Entity Type: examplemod:stalker
Entity's Exact location: 412.50, 68.00, -1893.25

That is the exact thing that killed your server, with coordinates. If it is still in the world, the server will die again the moment that chunk loads.

4. System Details

Near the bottom. Confirms the Java version, the heap actually in use, and — usefully — the real Forge version:

Forge: net.minecraftforge:47.4.10

Use that line rather than the jar filename. forge-1.20.1-47.4.10-universal.jar contains two version numbers, and reading the first as the loader version is a mistake that looks completely plausible — 1.20.1 is a real version string that appears everywhere in the log.

What to ignore

• The joke line at the top. It is random.
• Mixin frames in the middle of a trace — a mixin being present does not mean it is at fault.
• Everything after the first fatal error in latest.log. Causes precede effects; a single early failure produces pages of consequences.

The whole list

Every failure mode worth recognising, with its fix: all 24 →

Doing this automatically

Forge Server Doctor performs the whole procedure above — reads the report, finds the real cause under the wrappers, skips the vanilla frames, and names the mod jar. 24 failure modes, each with its fix. The free edition covers the six most common startup failures.