☰

Ticking Entity

The server crashes while updating a specific entity. The crash report points at one mob, item, or projectile, often with its exact coordinates, so the fix is usually to remove or repair that single problem entity.

What does this error mean?
Every tick the server updates each loaded entity. A 'Ticking entity' crash means one entity threw an error mid-update, commonly from corrupted NBT data, invalid (NaN) coordinates, or a mod bug. Because it crashes on every tick, the server may crash-loop on startup. 
Ticking entity crash
Most Common Causes
  • Corrupted entity NBT data after an unclean shutdown.
  • An entity with invalid or NaN position values.
  • A mod bug in a custom entity's tick logic.
  • A duplicated or malformed entity created by an exploit or crash.
  • Broken AI/pathfinding data on a mob.
How To Diagnose
  1. Open the crash report and find the entity type, its UUID, and its block coordinates.
  2. Note the dimension so you target the right region files.
  3. Convert the coordinates to a region file (each region is 512x512 blocks).
  4. If a mod's class appears in the stack trace, suspect that mod.
Recommended Fixes
  • Delete the entity with MCA Selector
    Open the region, select the chunk at those coordinates, and remove the offending entity.
  • Remove the responsible mod
    If the stack trace blames a mod, update or remove it.
  • Use /kill if reachable
    If the server stays up long enough, target the entity by type/area with the /kill command.
  • Restore from backup
    If many entities are corrupted, roll the affected region back to a clean backup.
Analyze My Log
Frequently Asked Questions

Only that one entity. Removing a single corrupted mob or item does not affect the rest of the world.

They are printed in the crash report under the entity's details (pos / Entity's block location).

The entity is in a loaded chunk near spawn, so it ticks immediately and crashes before you can act in-game.