1What the crash says
The top of the crash report, from our NeoForge test
---- Minecraft Crash Report ----
// Why did you do that?
Time: 2026-09-29 15:05:21
Description: Ticking entity
java.lang.NullPointerException: Test error: this minecart is set to fail when it ticks
Twenty times a second, the server runs every entity in the parts of the world that are active, around players and at spawn: it moves mobs and minecarts, and counts down dropped items. When the code that runs one of them throws an error, Minecraft stops the whole server and writes a crash report in the server's crash-reports folder. The line under Description is the error itself.
Ticking block entity is the same crash for a block with data and code of its own: a hopper, a furnace, a spawner, or a machine or pipe from a mod.
2Which entity, and where
Further down, the report names what failed and where it is:
The same report's entity section
-- Entity being ticked --
Details:
Entity Type: minecraft:minecart (net.minecraft.world.entity.vehicle.Minecart)
Entity ID: 2
Entity Name: Minecart
Entity's Exact location: 6.50, -60.00, 6.50
Entity's Block location: World: (6,-60,6), Section: (at 6,4,6 in 0,-4,0; chunk contains blocks 0,-64,0 to 15,319,15), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,-64,0 to 511,319,511)
- Entity Type says what it is. The part before the colon is what adds it:
minecraftfor the game, or a mod's ID. - Exact location is where it is, as x, y and z.
- in 0,-4,0 is its chunk, by the first and last numbers: x 0 and z 0. A chunk is 16 by 16 blocks, so that's the block x and z divided by 16, rounded down.
- Region: (0,0; …) names the file it's saved in:
entities/r.0.0.mca, in the world folder. A region is 32 by 32 chunks. - The lines under the error name the code that failed. In a real crash, look for a mod's or a plugin's name there; ours named the game's own minecart code, where we'd planted the error.
For a block, the section is called Block entity being ticked, and it gives the block's Name, like minecraft:hopper, and its Block location. A block's data is saved with the land around it, in region/r.0.0.mca.
3What each server did
On 29 Sep we made one minecart throw an error each time the server ran it, and one hopper the same, as a broken mod would. A small Java agent changed the game's code as it loaded, on Minecraft 1.21.1's own server, Fabric, Paper and NeoForge:
| What ran | The minecart | The hopper |
|---|---|---|
| Minecraft 1.21.1 | Stopped: Ticking entity | Stopped: Ticking block entity |
| Fabric Loader 0.19.5 on 1.21.1 | Stopped: Ticking entity | Stopped: Ticking block entity |
| Paper 1.21.1, build 133 | Logged Entity threw exception at world:6.5,-60.0,6.5, removed the minecart and kept running | Logged BlockEntity threw exception at world:10,-60,10; the hopper stayed, without the 2 diamonds in it |
| NeoForge 21.1.252 | Stopped: Ticking entity | Stopped: Ticking block entity |
| NeoForge, with its two remove settings on | Wrote the crash report into the log, removed the minecart and kept running | The same; the hopper stayed, empty |
| Fabric with Neruina 3.3.3 | Logged Neruina caught an exception, kept running and left the minecart in place, stopped | The same; the hopper kept its 2 diamonds |
Each server that stopped had saved the world first, with the entity still in it, so the crash came back:
- At spawn, Minecraft crashed in the same second it said Done, at every start.
- 2,000 blocks away, it ran normally with a player at spawn. When the player teleported next to the minecart, it crashed within a second, and the player saw Server closed.
- With nobody on, it stopped running entities shortly after it started. A broken minecart we added 10 seconds after a start crashed it at once; one added after 18 seconds did nothing until the next start.
4How to fix it
Take the first fix that fits your server. Before you change the world's files, stop the server and copy the world folder.
- Restore a backup from before the crash. The world comes back as it was then, without the broken entity; what changed since is lost.
- Paper: it's already gone. Paper removed our minecart by itself and logged its world and position. If it happens again, the lines under that log line name the code.
- Forge or NeoForge: let it remove the entity, once. Set
removeErroringEntities, orremoveErroringBlockEntitiesfor a block, totrueand start the server. NeoForge 21.1 keeps them inconfig/neoforge-server.toml, Forge 1.20.1 inworld/serverconfig/forge-server.toml; both start off. Then turn it off again: the file itself warns BE WARNED THIS COULD SCREW UP EVERYTHING, and while it's on, whatever fails next is deleted instead of stopping the server. - Fabric, Forge or NeoForge: Neruina. This mod, downloaded 9.7 million times on Modrinth, stops the entity that fails and keeps the server running.
/neruina kill @e[type=minecart,limit=1]then removed ours. It doesn't remove anything by itself: once we took Neruina off, the hopper it had stopped crashed the server again. - Otherwise, delete the entities file. With the server stopped, delete the file the Region line names. Ours then started: the blocks and a chest's diamonds stayed, and every entity in that 512 by 512 block area was gone, a cow we'd named too.
- Or only that chunk, with MCA Selector. This free world editor deleted the chunk from the report, which came back as new land: what was built in it went, and a cow one chunk over stayed. For a block, it replaced only the hopper with air, and the chest beside it kept its diamonds.
- Then the cause. If the lines under the error name a mod's code, the next entity of that kind can fail the same way: update the mod, or remove it.
# In the server's folder, with the server stopped cp -r world world-backup rm world/entities/r.0.0.mca # the numbers from the Region line # Or only chunk 0,0, with MCA Selector 2.9 java -jar mcaselector-2.9.jar --mode delete --world world --query "xPos = 0 AND zPos = 0"
# In the server's folder, with the server stopped cp -r world world-backup # Every hopper in chunk 0,0 becomes air java -jar mcaselector-2.9.jar --mode change --world world --query "xPos = 0 AND zPos = 0" --fields 'ReplaceBlocks = "minecraft:hopper=minecraft:air"'
5On a Playkeeper server
- From Playkeeper 0.4.8, the Overview names the entity and where it is. For our minecart it says The minecart at x 6, y -60, z 6 crashes it each time the game runs it, and It's in the Overworld, saved in the world, so starting again crashes again.
- Remove the minecart takes out only that one: Only it goes. Blocks, chests and other mobs stay. Playkeeper backs up the world first, so you can undo, then starts the server. For a block the button is Reset the hopper: The block stays, without what it held.
- It no longer offers to start again, which only crashes again. When it can't tell what crashed and there's no backup to restore, it offers I'll take it out myself, for the fixes above.
- It doesn't restart the server first. It knows this crash would happen again at every start, so the Overview shows what to remove right after the first crash, and the status says It would crash the same way again, so Playkeeper didn't restart it. A Discord alert says the server crashed and stays off. Crashes it doesn't recognise are still restarted, up to 3 times in 15 minutes.
Before 0.4.8, Playkeeper started the server again until it had crashed 3 times, then the Overview showed the last errors with the crash report's Description line and offered only a restart. There, as on any other server, use the fixes above: the Files tab deletes world/entities/r.0.0.mca once the server has stopped, and the World tab restores a backup, keeping the world it replaces as a rollback archive.
Questions
What does Ticking entity mean in Minecraft?
One entity, like a mob, a minecart or an item frame, threw an error while the server ran it, so Minecraft stopped the server and wrote a crash report.
What is a ticking block entity crash?
The same crash for a block with data and code of its own, like a hopper, a furnace or a mod's machine.
Why does my server crash every time it starts?
It saved the world with the broken entity in it. At spawn, that entity runs a moment after each start; elsewhere, when a player goes near it.
Will fixing it delete my world?
No. Deleting the entities file keeps every block and chest; deleting a chunk loses only what was built in it.
Can Playkeeper fix a ticking entity crash?
From 0.4.8, yes. The Overview names the entity and where it is, and Remove takes out only that one, after backing up the world.