This guide will explain what is a ticking entity error and will also present multiple ways to deal with it.

If your error is caused by a ticking entity, this article should help you with that!

๐Ÿ’ญ It's extremely important to read the entire article to understand the issue and to fix it so there is minimal possibility of data loss or corruption.


โ“ What Is the Ticking Entity Error โ“

This type of error can be either a ticking entity error or a ticking block entity error.

โš  GOOD TO KNOW โš :

- A tick can be referred to as the process of the game updating each creature, block, or event for every chunk of the world.
- This usually happens at a rate of 20 times per second. Even your actions with the world are processed with ticks such as placing or removing a block.
- A chunk is a zone of 16x16 blocks and its height is effectively from the lowest point of your world to the highest. 
- The gameโ€™s map is organized into chunks that need to be loaded into your memory for you to be able to interact with your world (e.g. see, move, built, etc.).


An entity can be thought of as an NPC from the Minecraft world such as mobs, villagers, etc.

โš  NOTE โš : This type of error can appear in any game type, even vanilla. However, usually, ticking entities are the result of a mod or combination of mods that change the core of the game in any way.


๐Ÿ’ Ticking Entity Error

A Ticking Entity is a mob/creature/NPC that has become corrupt in your world.

Usually, when the game is trying to load or process anything about that entity, it simply crashes due to its corrupted state and you will most likely find the following error:

java.nullpointerexeption:tickingentity


๐Ÿ’  Ticking Block Entity Error

A ticking block entity is the same as a ticking entity. The only difference is that this refers to a corrupt block rather than an NPC.

Errors like these occur with special blocks added by mods like modded crafting tables.


๐Ÿ’  How to Solve

The Ticking Entity Error and Ticking Block Entity Error can be solved using the Crash Report that is generated by the server because it will contain the type of creature/block that causes the crash, the region it is in, and also its exact coordinates (X, Y, Z).

โš  NOTE โš : For the Ticking Entity Error, you will find a section in the Crash Report titled โ€˜ Entity Being Ticked โ€™ and it contains the name, type, region, and coordinates of the Entity that caused the error.
โš  NOTE โš : All of these methods start by backing up your world folder to prevent the loss of your work. In case something gets damaged, this allows you to start over with the process. As soon as you have all the necessary details you can proceed to solve the issue.




๐Ÿ”ฐ How to Solve - General Tips ๐Ÿ”ฐ

You can use the following tips on any server to solve this type of error regardless of the server type you are running.

โš  NOTE โš : All of these methods start by backing up your world folder to prevent the loss of your work. In case something gets damaged, this allows you to start over with the process.


๐Ÿ’  Teleport to the Entity and Kill It

If your server crashes due to a ticking entity error, you should be able to access the crash report that tells you the exact X, Y, Z coordinates of the ticked Entity. Then you can note them.

โš  NOTE โš : You can also use our Crash Log Scanner to get your crash report mentioning the entity X, Y, Z coordinates.
Now you have the coordinates of the entity so you should teleport to it and kill it manually using the following command:

/tp X Y Z
(teleport you to the given X, Y, Z coordinates)

NOTE:

- This method is not effective all the time. You need to ensure you have enough time to teleport and kill the entity before the server crashes, which is a complicated task.

- You need to be able to start the server to use this method and you also need to be able to join. If your character spawns in the same chunk with the entity, the game will instantly crash without allowing you to kill it.

- We recommend changing to creative before heading to kill the entity and also to prepare a weapon that can kill the Entity from a single shot for a higher success rate.



๐Ÿ’  Use a World Editor Like MCEdit

You can use MCEditEditor to generate a view of your world and also to fly through it.

By using the MCEdit commands you can teleport to X, Y, Z coordinates into the world and you can even erase a block or entity.

NOTE:

- This method has a higher success rate for this kind of issue but it only works for worlds generated with versions up to 1.11.2.

- This method does not work on Bedrock worlds.



๐Ÿ’  Use NBT Editor:

An NBT editor is an explorer for nbt files also known as region files.
Your world is made by this kind of file that can be loaded by the editor.

The NBT editor is showing you all the data from a world in a list grouped by regions.
So when you use the NBT explorer you will find a list of data and not a generated view as in MCEdit.

We suggest being cautious when using this one as it is a hard task. So once you have the Crash Report you can take the details about the entity that is being ticked and delete it using the NBT editor which permits the search of all regions, entities, blocks by name, and coordinates into a data list, not a generated view.


What is NBT Explorer?

NBTExplorer is a graphical NBT Editor based on NBTEdit. The differences between NBTEdit and NBTExplorer are that NBTExplorer is fully compatible with Minecraft's region files, it has a dropdown directory-tree interface for ease of usage, and it offers support for the latest NBT Standard. NBTExplorer is also built on top of the Substrate.


Why and when should I use NBT Explorer?

You should use NBT Explorer when you need to attempt to solve any ticking issues without creating a new world. You would use NBT Explorer to generate a crash report. In your crash report, you will get something like this:

โš  NOTE โš : You can also use our Crash Log Scanner to get the information you need, which should make it much easier.
-- Entity being ticked --
Details:
Entity Type: null (net.minecraft.client.entity.EntityClientPlayerMP)
Entity ID: 882
Entity Name: TheObster
Entity's Exact location: -432.64, 66.62, 1002.98
Entity's Block location: World: (-433,66,1002), Chunk: (at 15,4,10 in -28,62; contains blocks -448,0,992 to -433,255,1007), Region: (-1,1; contains chunks -32,32 to -1,63, blocks -512,0,512 to -1,255,1023)
Entity's Momentum: 0.00, 0.00, 0.00
Stacktrace:
at net.minecraft.world.World.func_72939_s(World.java:2157)


If your crash report does show this, then the problem is already solved. See below for an explanation.

How to use NBTExplorer:

Step 1. Download your world folder from the FTP. (For help, use our article on How to Access Your Minecraft Server Files Via FTP)

Step 2. Download NBTExplorer from here.

Step 3. Unzip NBTExplorer and open it.

Step 4. Click on File -> Open Folder, then search for the world folder you downloaded, and open it.

Step 5. Now that you opened NBT Explorer, and your world, click on Search -> Chunk Finder. You have this part from the Crash Report "Chunk: at 15,4,10 in -28,62", and also this one " Region: -1,1". Now, the numbers that interest us are "-28,62" and "-1,1". -28 and 62 refer to the chunk the entity is in, and -1,1 refer to the region.

Step 6. In the chunk finder, put in the region X and Z the two numbers from the region, in this case, -1 and 1, and the Chunk X and Z, in this case, -28 and 62. Now click on Find Chunk.

Step 7. The chunk's folder should open. Double click on Level, and then do the same for TileEntities. You will have a list of entities. Open each one, until the X, Y, and Z coordinates match with the ones from the Entity's Exact Location, in this case, -432.64, 66.62, and 1002.98. When you find it, simply delete it, and reupload the world to your server.

โ„น Here you can find the NBT editor: https://github.com/jaquadro/NBTExplorer/releases

โš  NOTE โš : As a last resort, you can also use the NBT editor to delete the entire region where the entity is but this will cause its whole loss. However, it will surely remove the undesired entity that is being ticked and solves the issue.


๐Ÿ’  Restoring a Backup

If you have one, you can restore a backup of the world such that the server rolls back to the moment before the ticking entityโ€™s appearance.

For more information, use our guide for restoring a backup.


๐Ÿ’  Use The Entity Purge Tool

As a last resort to solve a ticking entity error, you can also use our entity purge tool which can be found in our Multicraft and which can erase all your entities from the server.

โš  NOTE โš : The entity purge tool is not killing the entities like the /kill command, but is erasing them.

Also, please note that this tool will erase ALL entities!

To use the entity purge you need to:

Log in to your Multicraft panel here and stop your server.

Click on Tools, then on Entity Purge.

Select the world you want to delete the entities for and click on Purge All Entities.

We also have a guide for using the entity purge tool here.


๐Ÿ”ฐ How to Solve - Plugins Server (Bukkit/ Spigot/ Paper) ๐Ÿ”ฐ

You can use the following tips only on a plugins server to solve this type of error.

โš  NOTE โš : All of these methods start by backing up your world folder to prevent the loss of your work. In case something gets damaged, this allows you to start over with the process. As soon as you have all the necessary details you can proceed to solving the issue.
Also, here you can find our guide explaining how to install a plugin on your server.


๐Ÿ’  Use ClearLagg Plugin

ClearLagg is a plugin that lets you erase entities from your world through console commands.
All you have to do is add the ClearLagg plugin to your server and use the following command either in-game or in the Multicraft console:

/laggclear
(it is removing configured entities)

NOTE:

- You need to be able to start the server to use this command. Also, you do not have to join the game, you can use it from the Multicraft console.

- This command removes the configured entities. If you want to make a filter for the cleared entities then you will have to open the config file for this plugin and set up this command as you like.


โ„น You can find more information on the official page of the plugin here.


๐Ÿ’  Use Plugins which Limit Entities Behavior

Another good way to prevent or solve a ticking entity error on Bukkit/Spigot/Paper servers is to use plugins that will limit entities' behavior, reducing the chance for a ticking entity error.


Farm Limiter

Farm Limiter is a plugin that will prevent players from making abnormal mob farms, limiting groups of near entities of the same type.

You can add it to your server and configure it properly to reduce the chance of a ticking entity error.

NOTE:

- You need to be able to start the server to use this plugin.


โ„น You can find more information about this on the official page of the plugin here.


Chunk Spawner Limiter

Chunk Spawner Limiter is a plugin that will limit entities in a chunk.

You can add it to your server and configure it properly to reduce the chance of a ticking entity error.

NOTE:

- You need to be able to start the server to use this plugin.


โ„น You can find more information about this on the official page of the plugin here.


๐Ÿ”ฐ How to Solve - Forge Modded Server ๐Ÿ”ฐ

You can use the following tips only on Forge modded servers to solve this type of error.

โš  NOTE โš : All of these methods start by backing up your world folder to prevent the loss of your work. In case something gets damaged, this allows you to start over with the process.
Also, here you can find our guide for installing mods on your server.


๐Ÿ’  Update the Mod Causing the Issue

If your server is crashing with a ticking entity error type, that means a crash report mentioning the exact entity will be generated.

โš  NOTE โš : You can also use our Crash Log Scanner to get your crash report mentioning the entity X, Y, Z coordinates.
If the entity/ block entity is generated by a specific mod, you should try to update it to the latest version. Just go to the official page of the mod and see if your version is the same as the latest one. If not, download and add the new version instead of the old one.


๐Ÿ’  Use CoFHCore

CoFHCore is a mod that permits erasing entities through console commands.

All you have to do is add the CoFHCore mod into your server (a lot of modpacks have this mod already installed, so check if this is the case first) and use the following command either in-game or in the Multicraft console:

/cofh killall
(erase all entities from your world)

/cofh killall creeper
(erase all creepers from your world)

NOTE:

- You will have to consult the Crash Report to find out which entity you need to erase.

- You need to be able to start the server to use this command. However, you do not have to join the game, you can use it from the Multicraft console.

- This command is not killing entities like the vanilla /kill command. Instead, it erases them so no loot will be dropped when youโ€™ve killed the mobs.

- This command takes place even in unloaded chunks.


โ„น You can find the official page of the mod as well as the download link and more info here: https://www.curseforge.com/minecraft/mc-mods/cofh-core
Thus, for modded servers, this is one of the best ways to solve a Ticking Entity error.


๐Ÿ’  Use Mods which Limit Entities Behavior

Another good way to prevent or solve a ticking entity error on Forge servers is to use mods that will limit entities' behavior, reducing the chance for a ticking entity error.


In Control!

In Control! is a mod that will give you full control over where mobs are allowed to spawn.

All you have to do is add the mod to your server and configure it to your liking as it is working on a rule system. The rule files are located in the config file of the server.

NOTE:

- You need to be able to start the server to use this mod.
- This mod is working on the Minecraft version from 1.10.2 to 1.18.


โ„น You can find more information on the official page of the mod here.


Mob Controller

Mob Controller is a mod that allows you to fully control and customize entity/ mob spawns.

All you have to do is add the mod to your server and configure it to your liking.

NOTE:

- You need to be able to start the server to use this mod.
- This mod is working only on the Minecraft 1.12.2 version.


โ„น You can find more information on the official page of the mod here.


Mob Spawner Control

Mob Spawner Control is a mod that provides ways to configure mob spawners, to discourage their use in mob farms on your server.

All you have to do is add the mod to your server and configure it to your liking. By default, this mod makes spawners break after having spawned 100 mobs, but you can customize it by editing the configuration file.

NOTE:

- You need to be able to start the server to use this mod.
- This mod works on Minecraft versions from 1.11.2 to 1.12.2.


โ„น You can find more information on the official page of the mod here.


Harder Farther

Harder Farther is a mob farm regulator for your server, but it also lets you configure mobs in various ways.

All you have to do is add the mod to your server and configure it to your liking.

NOTE:

- You need to be able to start the server to use this mod.
- This mod works on Minecraft versions from 1.16 to 1.18.


โ„น You can find more information on the official page of the mod here.


Extra Utilities

You can also use the Extra Utilities mod to kill entities.

You can do so by using the following command:
/xu_killitem

NOTE:

- You need to be able to start the server to use this mod.
- You do not have to be able to join the server to use the command. You can use it in the Multicraft console too.


โ„น You can find more information on the official page of the mod here.


๐Ÿ”ฐ How to Solve - Fabric Modded Server ๐Ÿ”ฐ

You can use the following tips only on Fabric modded servers to solve this type of error.

โš  NOTE โš : All of these methods start by backing up your world folder to prevent the loss of your work. In case something gets damaged, this allows you to start over with the process.
Also, here you can find our guide for installing mods on your server.


๐Ÿ’  Update the Mod Causing the Issue

If your server is crashing with a ticking entity error type, that means a crash report mentioning the exact entity will be generated.

โš  NOTE โš : You can also use our Crash Log Scanner to get your crash report mentioning the entity X, Y, Z coordinates.
If the entity/ block entity is generated by a specific mod, you should try to update it to the latest version. Just go to the official page of the mod and see if your version is the same as the latest one. If not, download and add the new version instead of the old one.


๐Ÿ’  Use Mods which Limit Entities Behavior

Another good way to prevent or solve a ticking entity error on Fabric modded servers is to use mods that will limit entities' behavior, reducing the chance for a ticking entity error.


Custom Spawns [Fabric]

Custom Spawns [Fabric] is a mod that allows you to configure various mob caps and persistence, as well as the spawn rate of passive mobs.

All you have to do is add the mod to your server and configure it to your liking. You can do so either through the mod menu in-game or by changing the config/customspawn.json file.

NOTE:

- You need to be able to start the server to use this mod.
- This mod works on Minecraft versions from 1.16 to 1.18.


โ„น You can find more information on the official page of the mod here.


โ“ What Is a Ticking World โ“

Ticking World errors are the ones where the server itself doesnโ€™t know where the Ticking Entity is, so as a result, the crash report will not mention any X, Y, Z coordinates or details about it.

This is the hardest to resolve from all Ticking Entity errors due to the lack of knowledge regarding the ticked entity.

โš  NOTE โš : The Crash Report will have as header Ticking Entity Crash, but no other info about the entity itself.




๐Ÿš€ How to Solve - General Tips ๐Ÿš€

You can use the following tips on any server to solve this type of error regardless of the server type you are running.


๐Ÿ’  Delete the Player Data

The Player Data is usually what generally breaks first and causes the Ticking World issue because they contain your interactions with the world. It is likely your error is caused by a ticking entity. A possible solution is removing your player data, which is what breaks first and causes this ticking problem.

The playerdata contains mostly all the playerโ€™s information. By removing this the player will need to rejoin as a new one, but it should fix the issue if the error is not too severe.

๐Ÿ€ Steps:

Log into your control panel here.
Go to your server and look at the world section. Remember the name it has then stop your server.
Connect to your server via FileZilla as our guide is telling here.
In here, open the folder named the same as the one you noted in STEP 2.
Open the playerdata folder.
Use this guide to find the UUID of the player. It will be a long string of letters and numbers.
Delete the file that has the name of the UUID. If there are other files with the player name, removing them is generally not needed.
Start your server. If the problem is still happening you might want to delete all of the players' playerdata files, including the ones with the name of the player.

Also, here you can find our guide for deleting your player data.


๐Ÿ’  Restoring a Backup

If you have one, you can restore a backup of the world so it rolls back to the moment before the ticking entityโ€™s appearance.

For more information, use our guide for restoring a backup.


๐Ÿš€ How to Solve - Forge Modded Server ๐Ÿš€

You can use the following tips only on Forge modded servers to solve this type of error.


๐Ÿ’  Use the Forge Mod Loader

We suggest using this method only if all the others did not help because it has the highest chance to damage your world. You can set forge to erase any creature or block that would cause your crash, but you give Forge permissions to erase any block or entity from your world.

We do not recommend it if you didnโ€™t try all the other alternatives.

โš  NOTE โš : This method should start with a backup of the world in case Forge damages it beyond repair/irreparably.

๐Ÿ€ To proceed, you need to:

Log into your control panel here.
Click on Files, then on FTP files access and log in.
In the config folder, find and open the file called forge.cfg.
Find removeErrorEntities and removeErroringTileEntities which will both be false.
Give the true value for the ones mentioned above depending on the error you have (Ticking Entity or Ticking Tile Entity), then save the file.
Start your server and close it immediately after it starts.
Now go back to the forge.cfg and set both of them back to false.
Start the server and join to see if the issue is fixed.

๐Ÿ’ซIt could be a completely damaged world or it could solve the issue. In most cases, it's just damaging the world. We do not recommend using this method without doing a backup before and without trying all other methods.


Sadly, if nothing above fixes the error, you will need to start a brand new world.


If you find any issues solving the ticking entity error please contact us on live chat or via the ticket system.


โ• Useful Links โ•

- Improve Your Forge Modded Server Performance
- How to Install Mods on Your Server
- How to Check Your Server Performance
Was this article helpful?
Cancel
Thank you!