Fixing Ticking Tile Entity Error

If you have a StickyPiston server then you can send us a Support Ticket and we will remove the Ticking Tile Entity for you.

We will also fix your world is you buy a server from us and upload your world save.

Description

What is a Ticking Tile Entity?

This is a common error on Forge servers running mods, but can also rarely occur on unmodified Minecraft. A block that has been placed in the world is causing an error during the world tick . The world tick is unable to complete and the server crashes.

How do I know it is happening?

When the error first happens, the server will crash and all the players will be kicked. The server will attempt to restart. If the Tile Entity is near the spawn area or in a chunk that is forced to load, then it will be processed during the world tick and the server will crash again. If the tile entity is elsewhere, then the server will crash when a player gets close to it, or logs in near it.

If you look at the server console when the server crashes, you will see a message in the form:

20:00:00 [SEVERE] This crash report has been saved to: /home/minecraft/multicraft/servers/server1/crash-reports/crash-2017-05-22_20.00.00-server.txt

Finding the Crash Report in the Control Panel

If you have a server with StickyPiston, you can view the most recent crash reports in the Control Panel by selecting Files>>Crash Reports from the left hand menu. You will be given a list of crash reports with the most recent at the top. Click on one to view it.

Use FTP to view or download the Crash Report

  1. Login into your server using FTP : Files > FTP Client and enter your multicraft password
  2. Click into the /crash-reports/ folder
  3. View or download the crash-###########-server.txt file and open it in a text editor like Notepad++
  4. For more info read this how-to on using FTP https://stickypiston.co/account/knowledgebase.php?action=displayarticle&id=8

Reading the Crash Report

Below is a crash report with the System Details section omitted as we won’t be needing it:

---- Minecraft Crash Report ----
// Why did you do that?

Time: 5/17/17 1:49 PM
Description: Ticking tile entity

java.lang.NullPointerException
    at com.mrcrayfish.furniture.tileentity.TileEntityOven.canSmelt(TileEntityOven.java:298)
    at com.mrcrayfish.furniture.tileentity.TileEntityOven.func_70316_g(TileEntityOven.java:259)
    at net.minecraft.world.World.func_72939_s(World.java:2209)
    at net.minecraft.world.WorldServer.func_72939_s(WorldServer.java:550)
    at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:668)
    at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:276)
    at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:587)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:484)
    at net.minecraft.server.ThreadMinecraftServer.run(SourceFile:583)


A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

-- Head --
Stacktrace:
    at com.mrcrayfish.furniture.tileentity.TileEntityOven.canSmelt(TileEntityOven.java:298)
    at com.mrcrayfish.furniture.tileentity.TileEntityOven.func_70316_g(TileEntityOven.java:259)

-- Tile entity being ticked --
Details:
    Name: cfmOven // com.mrcrayfish.furniture.tileentity.TileEntityOven
    Block type: ID #501 (tile.oven // com.mrcrayfish.furniture.blocks.BlockOven)
    Block data value: 2 / 0x2 / 0b0010
    Block location: World: (249,63,425), Chunk: (at 9,3,9 in 15,26; contains blocks 240,0,416 to 255,255,431), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)
    Actual block type: ID #501 (tile.oven // com.mrcrayfish.furniture.blocks.BlockOven)
    Actual block data value: 2 / 0x2 / 0b0010
Stacktrace:
    at net.minecraft.world.World.func_72939_s(World.java:2209)
    at net.minecraft.world.WorldServer.func_72939_s(WorldServer.java:550)

-- Affected level --
Details:
    Level name: world
    All players: 0 total; []
    Chunk stats: ServerChunkCache: 696 Drop: 0
    Level seed: -7329855476928627317
    Level generator: ID 04 - BIOMESOP, ver 0. Features enabled: true
    Level generator options: 
    Level spawn location: World: (40,64,256), Chunk: (at 8,4,0 in 2,16; contains blocks 32,0,256 to 47,255,271), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)
    Level time: 3358116 game time, 4295990 day time
    Level dimension: 0
    Level storage version: 0x04ABD - Anvil
    Level weather: Rain time: 93527 (now: false), thunder time: 32177 (now: false)
    Level game mode: Game mode: survival (ID 0). Hardcore: false. Cheats: false
Stacktrace:
    at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:668)
    at net.minecraft.server.dedicated.DedicatedServer.func_71190_q(DedicatedServer.java:276)
    at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:587)
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:484)
    at net.minecraft.server.ThreadMinecraftServer.run(SourceFile:583)

The Description on the fourth line confirms that it is a Ticking tile entity. Below it is the Java exception that is occuring, in this case a java.lang.NullPointerException followed by the stack trace leading up to the exception.

Since the crash type is a Ticking tile entity, the Crash Report contains a section called Tile entity being ticked. This contains information that will help in removing the Tile Entity. We can see it’s Name:

    Name: cfmOven // com.mrcrayfish.furniture.tileentity.TileEntityOven

But more importantly we also get the Block location:

    Block location: World: (249,63,425), Chunk: (at 9,3,9 in 15,26; contains blocks 240,0,416 to 255,255,431), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)

We can clearly see the location of the tile Entity in the <x>,<y>,<z> format : 249,63,425. We can also see the <x>,<z> coordinates for the Region: 0,0.

However, we do not know which world it is, it could be in The Nether or another world added by a mod, like the Deep Dark. For that you need to look for the Level dimension in the Affected level section.

    Level dimension: 0

0 is the main overworld. -1 is The Nether and 1 is The End. Here’s where the files for these dimensions are usually located:

DimensionNameFolder
0 Overworld world/region
-1 Nether world/DIM-1/region
1 The End world/DIM1/region
-100 Deep Dark world/DIM-100/region
7 Twilight Forest world/DIM7/region
<x> <modded world> world/DIM<x>/region

Cause

There are many causes to a Ticking Tile Entity. Here are some generalised ones:

  • An item has been placed inside a modded block. The modded block tries to do something with the item and the item is not compatible
  • Two modded blocks have been placed next to each other. One of them tries to do something with/to the other but they are incompatible
  • Modded blocks that make up a network of some kind loops back on itself. One or more of the modded blocks keep triggering each other to do something in an infinite loop
  • A modded block that interacts with entities (Players, monsters, animals, dropped items) that are near it tries to do something with/to an entity that is incompatible

How to Remove a Ticking Tile Entity

Option 1: Teleport to the Tile Entity and Destroy it

This will only work if the server is not crashing during start up. You also have a very small window of opportunity to break the block:

  1. Make sure your player is opped
  2. Join the server
  3. Use the gamemode command to put yourself into Creative mode
/gamemode creative
  1. Use the tp command to goto the exact location of the Ticking Entity
/tp <x> <y> <z>
  1. Break the block

Option 2: Remove the Ticking Tile Entity using MCEdit

This method requires you to download the world using FTP and remove the tile entity using MCEdit. We suggest using MCEdit 1.0 Unified as MCEdit 2 is still in Beta.

How to Download World Files: https://stickypiston.co/account/knowledgebase.php?action=displayarticle&id=7

Download MCEdit 1.0 Unified: http://www.mcedit-unified.net/

  1. Download your world folder
  2. Open the world in MCEdit, from the main menu:
    1. Click Open
    2. Browse to the world folder
    3. Open the level.dat file
  3. Optional: Move to the correct dimension. If the Tile Entity is in the Nether or The End:
    1. At the top of the window, look for a button labelled Overworld, click it
    2. Click on the dimension you want to move to
  4. Go to the Ticking Entity’s location
    1. Click on Menu>>Goto
    2. Enter the Tile Entity’s coordinates
    3. Click Goto
    4. Close the menu by clicking menu again
  5. You will now be in at the Tile Entity’s location. You can move around using the WASD keys. You can look around by holding down the right mouse button
  6. Move back a bit so that you can see the block
  7. Select an volume around the block using the mouse and the left mouse button. The first click selects the first corner, the next click selects the second corner. You can select just the block you want by clicking on it twice. If you mess up, you can use Deselect from the menu on the left.
  8. To remove the blocks you have selected, click Delete Blocks or press the Delete key
  9. Save your changes by Opening the Menu and choosing Save or by pressing Ctrl+S
  10. Upload your world back to your server
  11. Optional: Delete the forcedchunks.dat file for the dimension. This file keeps a track of the chunks that are force loaded. Sometimes this needs to be deleted for the the fix to work. The server will rebuild the file

Hint: You don’t have to download your entire world. You only need the level.dat file and just the region file. The region file needs to be in the correct folder relative to the level.dat for MCEdit to load it.

Option 3: Use NBT Explorer to Remove the Tile Entity

This method requires you to download the world using FTP and remove the entity using NBT Explorer. This method is also not always successful as it only removes the Tile Entity from the chunk, but does not remove it from the Block data. This can result in the TileEntity being recreated and cusing the crash again.

How To use FTP Access to Download and Upload files: https://stickypiston.co/account/knowledgebase.php?action=displayarticle&id=8

Download NBT Explorer: http://www.minecraftforum.net/topic/840677-nbtexplorer-nbt-editor-for-windows-and-mac/

This video shows you how to fix the error. https://www.youtube.com/watch?v=fWUUsdp3pJ8

  1. Download the Region File containing the Tile Entity
    The file is located in the region folder for the world that the Tile Entity is located in and has the format r.<x>.<z>.mca. e.g.:
    world/region/r.0.0.mca
  2. Open the region file using NBTExplorer
  3. Find the local chunk co-ordinates
    The region file is separated into chunks, to find the local co-ordinates:
    1. From the menu, select Search>>Chunk Finder...
    2. In the Block section, type in the X and Z co-ordinates of the block. e.g. 249 and 425
    3. Make a note of the Local Chunk X and Y values. e.g. 15 and 26
    4. Close the Chunk Finder
  4. In the list, locate the local chunk. e.g. Chunk [15,26]
  5. Click on the + symbol to expand and view the contents of the chunk
  6. Inside the chunk find and expand Level
  7. Inside that find and expand TileEntities. This will show all the Tile Entities in the chunk
  8. Find the Tile Entity that is crashing the server
    If there are only a few, expand each one and check that the x, y and z values match the Ticking Tile Entity
    If there are a lot, you can search:
    1. Click on TileEntities so that it is highlighted. This will restrict the search area
    2. From the menu, select Search>>Find...
    3. In the Name box type x
    4. In the Value, type in the x co-ordinate of the Ticking Tile Entity. e.g. 249
    5. Click Find
    6. This will find the first TileEntity with a matching x coordinate, check if all the co-ordinates match
    7. Use Search>>Find Next, or press the F3 key to find the next matching Tile Entity
  9. Once you have found the right one, click on the root node for it (It’ll be named something like x Entries) to highlight it
  10. Delete it using the Delete key or by clicking the red cross on the toolbar
  11. Save your changes with File>>Save or by clicking the Disk icon on the toolbar
  12. Upload the Region File to your server, replacing the old one
  13. Optional: Delete the forcedchunks.dat file for the dimension. This file keeps a track of the chunks that are force loaded. Sometimes this needs to be deleted for the the fix to work. The server will rebuild the file

Option 4: Delete the Region File

This is a drastic option as it will remove ALL the chunks within the region file.

The file is located in the region folder for the world that the Tile Entity is located in and has the format r.<x>.<y>.mca. e.g.:
world/region/r.0.0.mca

How To use FTP Access to Download and Upload files: https://stickypiston.co/account/knowledgebase.php?action=displayarticle&id=8

Option 5: Restoring your server from a backup

If none of the options work you can restore your server from a backup, before the server started to crash
https://stickypiston.co/account/knowledgebase.php?action=displayarticle&id=37

Was this answer helpful?

 Print this Article

Also Read

VoidLauncher Not Working / Not Installing Correct Version

The VoidLauncher can often fail to update itself correctly and this will lead to it installing...

How to install the Dynmap Mod on a modded server

Dynmap allows you to add a webbased map to see what your world looks like, it is possible to use...

Diagnosing lag issues with a Timings report

If you are running a server with many plugins it can be very difficult to diagnose performance...

Enabling Disabled mods

Some modpacks do not have all the mods enabled by default, this guide explains how to enable...

Disabling mods in your modpack

Sometimes there are mods on your server which you don't want to load, this guide explains how to...