What does "Description: Ticking entity" mean?

A broken entity or block crashed the world. One entity or block in the world hit a bug in a mod and crashed the server while ticking. The crash report names the entity and its position. Restore a recent backup, or ask support to remove the broken entity from the world.

How do I fix "Description: Ticking entity"?

1. Read the crash report: Find "Entity being ticked" or "Block entity being ticked". Note the entity type, its position, and the world. The stack trace above it names the mod package. 2. Remove the entity: Stand at the coordinates with the world loaded and use /kill on it if the server stays up long enough. If it crashes on load, edit the world offline with a tool such as NBTExplorer or Amulet, or delete the entity from the region file by coordinates. Back up the world first. 3. Or restore a backup: If a recent backup predates the entity, restoring it is faster and safer than editing region files. 4. Update the mod: Check whether the mod that owns the entity has a newer release; ticking crashes are exactly what mod authors fix. Report it with the crash report if not. 5. Stop it coming back: If the same entity type crashes again in a new place, the mod is broken on this version and needs removing or downgrading until fixed.

Roastd / Minecraft

critical

A broken entity or block crashed the world

What it looks like in your log

Description: Ticking entity

What causes it

One entity or block in the world hit a bug in a mod and crashed the server while ticking.

How to fix it

The crash report names the entity and its position. Restore a recent backup, or ask support to remove the broken entity from the world.

Usual suspects: complex mob mods (Alex's Mobs, Mowzie's Mobs, boss mods); tech and automation mods (Mekanism, Create, Powah); magic and ritual mods.

Why it happens

Every loaded entity and block entity is ticked once per game tick. If one of them throws inside its tick, the exception reaches the world tick and the server crashes. The crash report has a section headed "Entity being ticked" or "Block entity being ticked" with the type and the exact coordinates. The mod that owns the entity type is at fault, whether through a bug or through data the entity cannot cope with.

It repeats. The entity is saved in the world, it loads again on restart, it ticks again, it crashes again. Nothing changes until the entity is gone or the mod is fixed.

Fix it step by step

1Read the crash reportFind "Entity being ticked" or "Block entity being ticked". Note the entity type, its position, and the world. The stack trace above it names the mod package.
2Remove the entityStand at the coordinates with the world loaded and use /kill on it if the server stays up long enough. If it crashes on load, edit the world offline with a tool such as NBTExplorer or Amulet, or delete the entity from the region file by coordinates. Back up the world first.
3Or restore a backupIf a recent backup predates the entity, restoring it is faster and safer than editing region files.
4Update the modCheck whether the mod that owns the entity has a newer release; ticking crashes are exactly what mod authors fix. Report it with the crash report if not.
5Stop it coming backIf the same entity type crashes again in a new place, the mod is broken on this version and needs removing or downgrading until fixed.

If that didn't work

If the report says "Exception ticking world" with no entity section, the crash is in the world tick itself: world generation, a datapack function or a plugin task. The first non-Minecraft frame in the stack trace names it.

Not sure this is your problem? Paste your log and Roastd will tell you which of these it actually matched, and what else it found.

Check your own log