Kinetic Hosting Logo
Loading…

How to solve a ticking entity crash on a Minecraft server

Sorry, we don't yet have a video for this article, but we're working on it.

What is a ticking entity crash?

Sometimes an entity, block, or tile entity becomes corrupted, resulting in a bad state (such as a bug, infinite loop, corrupted NBT data, or broken mod/plugin logic). When the server tries to “tick” it, the code throws an error instead of completing.


1.18.2+

With 1.18.2+, there are tools available that can handle ticking entities, blocks, and players.
Neruina Will automatically block/kill any ticking blocks or entities that it finds. It may not always be 100% compatible with the mods that you are running.

How to use it?

Download the correct version from the CurseForge page and upload it to the server's mods folder, & Restart the server.

Other solutions

First, we will need to find the object causing the crash. This can be found in the crash reports in the file manager. You will be able to tell this is a ticking entity by its Description.

Locating the Object.

Now that we have confirmed it's a ticking entity. Locating the cause may be as simple as the server knowing the reason. If not, it will take some reading to figure out the cause.

It will also show the mods it suspects are the cause.

The highlighted area is the module that's causing the issue. Over time, you will become more adept at identifying and understanding these causes.

So this shows Type in this case, it's a player. This can be a block or any mob. This section will remain essentially unchanged for all types.

It will also show the name. In this case, as it's a player, it will show the player's name.

Entity's Location. This is where the entity in question is located.

Now that we have this information, we can look into addressing the issue.

Kill Command

Locate the entity as shown above. Teleport somewhere nearby. Ready up this command.

/kill @e[type=<entity>,distance=..30]

It's a good idea to send this command once before continuing. Once done, start walking/flying towards this location and spam the command. This will work a bit better if you are doing it via console; having someone else fly there, the distance argument in the kill command will need to be removed.

Removing the entity via files.

What is needed?

  1. Nbt explorer

  2. Chunk location

NBT Explorer will allow you to view the region data of your Minecraft world. Chunk location will be shown by entering in the block cords in the top section. The listed chunk cords & Region info is what you will need moving forward.

  1. Log in to the panel.

  2. Go to the file manager.

  3. Open world.

  4. Locate the entities folder.

  5. Open the folder.

  6. With the region info from above

  7. Use the search to locate this file.

  8. Download the file.

  9. Make a copy of the downloaded file. This one shouldn't be edited.

  10. Open Nbt exploer

  11. Drag in the region file.

  12. Use CTRL + F to locate the chunk. You will be looking for the chunk to line up here; these will be the cords of that chunk.

  13. Click the + on this chunk.

  14. Below is what you will find in that chunk. You will be looking for the ID to match the entity type.

  15. Once located, delete this entry & save.

  16. Stop the server.

  17. Delete the entity region from the panel.

  18. Upload the edited version.

  19. Start the server.

Kinetic Hosting Logo™

Our goal at Kinetic is to offer genuinely helpful, human-powered support (no bots, no AI), combined with a feature-rich panel, powerful hardware, and prices that won’t break the bank.

Registered in England & Wales • Co. No. 11439987 • ICO No. ZA841955

Kinetic Hosting and the Kinetic Hosting logo are trademarks of Dapper Fox Group LTD. All other trademarks are the property of their respective owners.

Company
Services
Clients
Legal