# How to Fix 'Ticking Entity' Crashes on Your Minecraft Server (/docs/minecraft/fix-ticking-entity)



import { Step, Steps } from 'fumadocs-ui/components/steps';

A **"Ticking entity"** crash means a specific entity in your world (a mob, item, projectile, or even a vehicle) became corrupted, and every time the server tries to process it, it crashes. The server will crash on every restart at the same point until you delete or repair the entity.

The good news: the crash report tells you **exactly which entity** and **exactly where it is**.

Quick Diagnosis from the Crash Report [#quick-diagnosis-from-the-crash-report]

Open your latest crash report (`crash-reports/` folder) and find the **Entity being ticked** section:

```
-- Entity being ticked --
Details:
    Entity Type: minecraft:zombie (net.minecraft.world.entity.monster.Zombie)
    Entity ID: 12345
    Entity Name: Zombie
    Entity's Block location: World: (123, 65, -456), ...
    Entity's Momentum: ...
    Entity's Passengers: []
```

You now know:

* **Entity type**: `minecraft:zombie`
* **Coordinates**: `123, 65, -456`
* **Chunk**: divide x and z by 16 → chunk `(7, -29)`

Choose Your Fix Method [#choose-your-fix-method]

| Method             | When to use                                               | Difficulty |
| ------------------ | --------------------------------------------------------- | ---------- |
| **Kill command**   | Server stays up for a few seconds before crashing         | Easy       |
| **MCA Selector**   | Server crashes immediately on world load                  | Medium     |
| **NBTExplorer**    | You want surgical entity removal without losing the chunk | Hard       |
| **Restore backup** | You don't care about anything since the corruption        | Easy       |

Method 1: Kill Command (Fastest) [#method-1-kill-command-fastest]

If the server runs for **a few seconds** before crashing, you can race the crash and kill the entity.

<Steps>
  <Step>
    Get the entity type and coordinates from the crash report [#get-the-entity-type-and-coordinates-from-the-crash-report]

    From the example: `minecraft:zombie` at `(123, 65, -456)`.
  </Step>

  <Step>
    Start the server and immediately run [#start-the-server-and-immediately-run]

    In **Console** in the [XGamingServer Panel](https://panel.xgamingserver.com), as soon as the server is up:

    ```
    kill @e[type=minecraft:zombie,x=123,y=65,z=-456,distance=..10]
    ```

    Adjust `type`, `x`, `y`, `z` to match your crash report. The `distance=..10` clause kills any zombie within 10 blocks of that point.
  </Step>

  <Step>
    If it works, the server stays up [#if-it-works-the-server-stays-up]

    The crash should stop. If the entity respawns from a spawner or mod, you may need to also break the spawner or remove the chunk (Method 2).
  </Step>
</Steps>

> **Tip:** Have the kill command ready to paste *before* starting the server. You usually have 5–15 seconds before the crash hits.

Method 2: MCA Selector (Server Crashes Instantly) [#method-2-mca-selector-server-crashes-instantly]

If the server crashes before you can run any commands, edit the world offline.

<Steps>
  <Step>
    Stop the server [#stop-the-server]

    In the panel, stop the server.
  </Step>

  <Step>
    Download the world [#download-the-world]

    Click **Files**, right-click `world/` (and `world_nether/` / `world_the_end/` if relevant), **Compress** to zip, and download. See [Download World](/docs/minecraft/download-world).
  </Step>

  <Step>
    Open MCA Selector [#open-mca-selector]

    Download [MCA Selector](https://github.com/Querz/mcaselector). Open the world folder.
  </Step>

  <Step>
    Convert coordinates to chunk coordinates [#convert-coordinates-to-chunk-coordinates]

    Divide block coordinates by 16:

    * Block `123, -456` → Chunk `7, -29`

    In MCA Selector, hold **Shift** and click the chunk at `(7, -29)` to select it.
  </Step>

  <Step>
    Delete the chunk [#delete-the-chunk]

    **Selection → Delete chunks**. Confirm. The chunk and everything in it (including the corrupted entity) is removed. Minecraft will regenerate it next time someone visits.
  </Step>

  <Step>
    Re-upload the world [#re-upload-the-world]

    Compress the edited `world/` folder, upload it to the panel, and start the server.
  </Step>
</Steps>

> **Trade-off:** Deleting a chunk removes everything in it — terrain, blocks, builds, items. If players have builds in that chunk, use Method 3 instead.

Method 3: NBTExplorer (Surgical Entity Delete) [#method-3-nbtexplorer-surgical-entity-delete]

For removing a single entity without losing the chunk:

1. Download the world (as above)
2. Open the `region/` folder in [NBTExplorer](https://github.com/jaquadro/NBTExplorer)
3. Open the `.mca` region file containing your chunk
4. Navigate to `Chunk → Level → Entities`
5. Find and delete the entry matching your entity
6. Save and re-upload

This preserves all blocks and other entities in the chunk — only the corrupted one is removed.

Method 4: Restore from Backup [#method-4-restore-from-backup]

If you don't mind losing recent changes:

1. Open **Backups** in the panel
2. Restore the most recent backup from before the corruption started
3. Start the server

If a Mod Entity Is Crashing [#if-a-mod-entity-is-crashing]

The crash report sometimes names a mod entity:

```
Entity Type: somemod:weird_creature
```

In this case:

1. **Update the mod** — corruption is often a known bug fixed in a newer version
2. **Check the mod's GitHub Issues** — search for the exact `Caused by:` message
3. **Remove the mod** if no fix exists
4. **Then** delete the entity using one of the methods above

Removing the mod alone won't fix it — the corrupted entity is still in your world data and will crash the server when its chunk loads.

Common Mistakes [#common-mistakes]

| Mistake                                   | Fix                                                                               |
| ----------------------------------------- | --------------------------------------------------------------------------------- |
| Deleting `world/` to fix it               | You lose everything. Use MCA Selector or NBTExplorer instead                      |
| Killing the wrong entity type             | Match the crash report exactly — `minecraft:zombie` ≠ `minecraft:zombie_villager` |
| Wrong coordinates in the kill command     | Re-check the crash report's `Entity's Block location`                             |
| Not stopping mods that respawn the entity | Remove the spawner / mod first, then delete the entity                            |
| Forgetting Nether/End                     | If the crash is in the Nether, edit `world_nether/region/`, not `world/region/`   |

Related Guides [#related-guides]

* [Find / Read Crash Reports](/docs/minecraft/find-read-crash-reports)
* [Reset Specific Chunks](/docs/minecraft/reset-chunks)
* [Download World](/docs/minecraft/download-world)
* [Server Won't Start](/docs/minecraft/fix-server-wont-start)
* [Common Issues](/docs/minecraft/common-issues)
