← Back
Exception ticking world
COAL-005 · Exception ticking world
A server crash while ticking the world, usually a corrupted chunk, a broken entity, or a mod mishandling world data. How to isolate the chunk and fix it.
What it looks like in the log---- Minecraft Crash Report ---- Description: Exception ticking world java.lang.NullPointerException: Exception ticking world
What it means
The server crashed mid-tick while updating the world - blocks, entities, and block entities all update inside that tick. Because it happens during normal running rather than startup, the trigger is usually specific data in the world: one corrupted chunk, one broken entity, or one block entity a mod cannot handle.
How to fix it
- Read the crash report's "Affected level" block. It names the exact block or entity position, which tells you the chunk to deal with.
- If it crashes on join, it is where that player is standing. A player logged out inside a crashing chunk re-crashes the server on every login. Move them with an offline NBT editor, or teleport them from the console in the moment before the crash.
- Regenerate just the bad region. Tools like MCA Selector let you delete a single region file so it regenerates on next load - far less destructive than restoring the entire world.
- If it started right after a mod change, remove that mod first. Mods adding entities or machines are the usual source.
- Otherwise restore a backup from before the crashes began.
More help
Coalstack's Auto Debugger scans a Java server's log for known errors like this one and links straight to the fix. Download Coalstack to try it.