Ticking entity or ticking block entity crash

Crash report says "Ticking entity" or "Ticking block entity".

One broken entity or block entity in the world crashes the server every time it loads; remove it.

Before you start: The coordinates from the crash report ("Entity's Exact location" or "Block location").

Step by step

1. Take a backup in the Backups tab before changing anything in the world.
2. Read the crash report for the entity type and its location.
3. Paper: in config/paper-world-defaults.yml, set remove-corrupt-tile-entities to true and fix-entity-position-desync true, then start.
4. Forge: many packs support removing erroring entities in config/forge-server.toml (removeErroringEntities / removeErroringBlockEntities = true). Turn it back off afterwards.
5. Or edit the region with an NBT tool (MCA Selector) to delete the chunk's entity.
6. If nothing else works, restore a backup from before the crash.

Check it worked: The server starts and the area loads.

Why it happens: A corrupted mob, item or block entity (often from a mod or plugin).

More guides on Crashes, startup failures, and errors:

• Find and read crash reports and logs
• Server stuck in a restart loop or will not start after an update
• Java version errors
• Failed to bind to port or unable to access jarfile
• Crash or error caused by a plugin
• Crash caused by a mod