25% OFF First Invoice
Code at Checkout: NETHER
No tutorials found
Last modified on Aug 10, 2020 in Server Errors
A Ticking Entity crash will be caused when some form of data, typically a mob or block, in the world becomes corrupted. This will usually be displayed in a crash report as follows: java.lang.nullpointerexception: ticking entity
The corruption that can happen in relation to ticking entities can be so severe that anytime the game attempts to process the ticking entity it will crash. While you can see these crashes in a Vanilla world, you are more likely to come across this when playing a modded world. This is purely due to the fact that mods tend to change major aspects of minecraft and can be seen as a more unstable way to play the game.
Ticks are going to be involved with every game you may play. Ticks can be seen as loops of tasks a game does to synchronize itself. Minecraft runs its game loop at a fixed rate of 20 ticks per second. This equates to 1 tick every 0.05 seconds. One good example of ticks is the daylight cycle in Minecraft. Each day is 24,000 ticks. This means 1 day in Minecraft equals 20 minutes in real life. Anything you are doing in game will be put in the same loop to be synchronized with the rest of the world.
A Ticking Block crash is generally the same as a Ticking Entity. The difference with this crash is it is related to a block or Tile Entity specifically and not a mob or npc. This will generally be related to special blocks added from a mod.
A Ticking World crash is the most severe of them all. This will occur when the game is able to recognize that there is corruption in the world, but will not be able to give a location. The game will have no idea where the corruption occurred and in some cases this is unfixable.
Once you have become subjected to a Ticking Entity crash you will have to remove the data from your world to resolve it. Simply removing your mods will not work in this case. This is due to the corruption already being part of your world. Luckily there are multiple ways you can remove the errored entity from your world. Some fixes might work better than others and it will really depend on the specific crash you are facing.
If you discover that even after removing the errored entity the crashing keeps occurring, you may have a faulty mod. If this is the case it is important to find the specific mod/s that are causing this to be able to fix the crashes in the long run. Unfortunately there is no easy way to do this. We would recommend removing any recent additions of Mods to start. If the crashes continue you may want to start removing mods in batches until the issues stop. This will better help you narrow down which mod exactly is causing the problems.
It is very important to resolve this crash as soon as possible. If the erroring entity is not removed your server may backup your world with the errored entity included. In some cases this could remove your only option to fixing the issue.
The absolute easiest and most straightforward way to fix the Ticking Entity is by restoring a backup(https://apexminecrafthosting.com/how-to-backup-your-minecraft-server/) of your world. At Apex Hosting we will automatically set up a backup task when you purchase a server. This task will run once per day and save up to two backups on your server at a time. We have a great guide on the restoration process here.
When the server crashes due to a Ticking Entity the crash report will have very important information that can be used in the removal of the errored entity. The following information will be inside of the crash reports:
Below is an example of what you will typically see in a crash report if you experience a ticking entity crash.
---- Minecraft Crash Report ---- WARNING: coremods are present: llibrary (llibrary-core-1.0.11-1.12.2.jar) Quark Plugin (Quark-r1.6-178.jar) RandomPatches (randompatches-1.12.2-18.104.22.168.jar) OTGCorePlugin (OTG-Core.jar) Do not report to Forge! (If you haven't disabled the FoamFix coremod, try disabling it in the config! Note that this bit of text will still appear.) (foamfix-0.10.10-1.12.2.jar) IvToolkit (IvToolkit-1.3.3-1.12.jar) Contact their authors BEFORE contacting forge // This is a token for 1 free hug. Redeem at your nearest Mojangsta: [~~HUG~~] Time: 6/9/20 7:55 PM Description: Ticking entity java.lang.NoSuchMethodError: mmm.common.entities.mobs.EntityShulkerGhast.isAttacking()Z at mmm.common.entities.mobs.EntityShulkerGhast.ShootShulkerBalls(EntityShulkerGhast.java:124) at mmm.common.entities.mobs.EntityShulkerGhast.func_70071_h_(EntityShulkerGhast.java:93) at net.minecraft.world.World.func_72866_a(World.java:1996) at net.minecraft.world.WorldServer.func_72866_a(WorldServer.java:832) at net.minecraft.world.World.func_72870_g(World.java:1958) at net.minecraft.world.World.func_72939_s(World.java:1762) at net.minecraft.world.WorldServer.func_72939_s(WorldServer.java:613) at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:767) at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:397) at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:668) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:526) at java.lang.Thread.run(Thread.java:748) A detailed walkthrough of the error, its code path and all known details is as follows: ---------------------------------------------------------------------------------------
As you can see the description lets us know this is a Ticking Entity crash. If you look closely you can also see that the entity Shulker Ghast is mentioned. Upon even closer inspection you can see that this is coming from a possible mod called MMM. In this case you can do a quick google search to figure out that this entity has been added by the mod Mutated Mobs Mod.
If the description in the crash report shows Ticking World or Exception ticking world you will not be able to find exact coordinates of the errored entity. This is due to the world not knowing where the issue is thus not being able to display coordinates. In these cases, we would just recommend you restore a backup(https://apexminecrafthosting.com/restore-your-backup/) of your world.
If you take a look further down in the crash report you will be able to find the exact X, Y, Z Coordinates of the ticking entity. Below is an example of this information.
A detailed walkthrough of the error, its code path and all known details is as follows: --------------------------------------------------------------------------------------- -- Head -- Thread: Server thread Stacktrace: at mmm.common.entities.mobs.EntityShulkerGhast.ShootShulkerBalls(EntityShulkerGhast.java:124) at mmm.common.entities.mobs.EntityShulkerGhast.func_70071_h_(EntityShulkerGhast.java:93) at net.minecraft.world.World.func_72866_a(World.java:1996) at net.minecraft.world.WorldServer.func_72866_a(WorldServer.java:832) at net.minecraft.world.World.func_72870_g(World.java:1958) -- Entity being ticked -- Details: Entity Type: mmm:shulkerghast (mmm.common.entities.mobs.EntityShulkerGhast) Entity ID: 104807 Entity Name: Shulker Ghast Entity's Exact location: 183.54, 51.95, 67.90 Entity's Block location: World: (183,51,67), Chunk: (at 7,3,3 in 11,4; contains blocks 176,0,64 to 191,255,79), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511) Entity's Momentum: -0.15, 0.13, -0.07 Entity's Passengers:  Entity's Vehicle: ~~ERROR~~ NullPointerException: null Stacktrace: at net.minecraft.world.World.func_72939_s(World.java:1762) at net.minecraft.world.WorldServer.func_72939_s(WorldServer.java:613)
In the Entity being ticked section you will find all the important information regarding the errored entity. You can more easily see here that it indeed is a ShulkerGhast from the MMM mod. The exact location of the entity is going to be
183.54, 51.95, 67.90.
If you have the mod CoFH Core you will have access to the /cofh killall command. This command is an improved version of the default Minecraft kill command. You will not need to be connected to the server to run this command. However the server will need to be able to startup in order for the command to be run.
This command will have the ability to kill all creatures even in unloaded chunks on the server. This is crucial as if the chunk loads that has the ticking entity the server will end up crashing. Although CoFH Core is very common you may not have it installed. It is recommended to add this mod to your server’s mods folder to gain access to this command.
In order to remove all loaded entities of a specific type you can use the following command.
/cofh killall [type]
The [type] you will enter is going to be the name or part of the name of the entity type to remove from the server. You can also run without a type that will remove all hostile mobs from the server. If for some reason the type is not working you can force the command to remove ALL loaded entities with this command:
/cofh killall *
This would be the “low tech” way to fix the ticking entity. Using the given coordinates from the crash report you can teleport to the entity and in the split second before the crash attempt to kill it in one hit. We recommend putting yourself into creative mode with /gamemode creative and getting a weapon that could instantly kill the entity.
Once you are in creative mode and have a weapon ready you can run the /teleport command to travel to the entity and start swinging away.
/teleport X Y Z
One other way to fix the Ticking Entity would be by enabling certain features within the Forge Modloader. Forge will have two settings that will order Minecraft to remove any mobs or blocks that would cause the server to crash. This method of resolution is completely uncontrollable as forge will be given permission to remove anything and everything it deems necessary. If you have ever watched forge startup in console you will know that it will almost always give warnings or errors about one thing or another. This could cause forge to remove things you do not want it to.
WARNING: If you attempt to use this method, make a backup of your server. We cannot stress how much damage this can do to your world, and the damage cannot be fixed. The only way to undo these changes is to restore a backup made before you turned on these settings in Forge, or by restoring a saved copy of your world. Customer Support can not restore any parts of a world deleted by Forge because of these settings, unless you made a backup beforehand.
To turn on these settings, you must find the file forge.cfg, which is normally located in the config folder in the main directory. Select forge.cfg, and then click the edit button to the right of the file.
Find the word false and change it to true. It’s recommended to only turn on the setting appropriate to what you are trying to fix: If trying to correct a Ticking Entity change the one for removeErrorEntities to true, but leave the removeErroringTileEntities set to false. This will hopefully minimize the side effects.
Start the server up, let it finish running. Then immediately shut the server down, open up forge.cfg and change those settings back to false. Leaving them permanently set to true can have continuous side effects. Place a block, and it instantly disappears, because forge didn’t like it and zapped it out of existence.
Try connecting into your game, and check to make sure everything is okay. If you see entire structures and buildings gone, well, that’s the damage we were talking about. If this happened, restore the backup made before turning on the Forge settings, and try one of the other alternative methods of removing the Ticking Entity.