Direct answer

Use the crash report to identify the entity type, coordinates/UUID, and the mod or plugin involved. Back up the world, fix/update the underlying content first, then recover or remove only the affected entity with a safe offline/admin method if the server cannot stay online.

What it means

Use the crash report coordinates and entity details to recover the affected area, then fix the mod, plugin, or entity setup that caused it.

Entity vs. block entity

A ticking entity crash concerns a mobile/non-block entity such as a mob, item, projectile, or modded entity. A ticking block entity crash concerns a block-attached object such as a chest, furnace, machine, or other block entity.

If you are a player

  • Note the exact world/dimension, coordinates if known, and action that triggers the problem.
  • If other players can reproduce it in the same place, tell the owner; location-specific evidence is valuable for world/chunk problems.
  • Do not repeatedly force-load a crashing area if the server is unstable. Let the owner make a backup before repair attempts.

If you run the server

  1. Stop the server and make a full backup before deleting, regenerating, downgrading, or editing world/player data.
  2. Use the crash/latest log to identify the specific player, entity/block entity, chunk/region, datapack, registry entry, or mod involved.
  3. Fix/update/restore the content that caused the bad data first; only remove the smallest affected file/entity/chunk when no safer recovery exists.
  4. Test recovery on a copy and verify the server can save/restart cleanly before putting the repaired world back into production.

Important notes

  • Recovery commands/tools differ by server software and whether the server can stay online. Use the crash coordinates/UUID and a backup; do not publish a destructive one-size-fits-all command.
Locate the entity before removing it
  1. Capture the entity type, UUID, dimension and position from the crash report or relevant log. An update bug in a modded mob can look like ordinary entity overload.
  2. Make a full backup and reproduce in a staging world with the same mods and datapacks; do not use a world-wide kill command to clear a single corrupt entity.
  3. If the responsible entity must be removed, prefer a targeted offline edit with a verified compatible tool, and keep the original region file for rollback.

References

Use the documentation for the exact software and release you run. These sources support the settings or diagnostic behavior used in this fix.

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000