What is a Ticking Block Entity error?
The 'Ticking Block Entity' error occurs when the Minecraft server encounters a block or entity that is behaving unexpectedly during a game tick. When the server cannot process the logic for a specific block (such as a chest, furnace, or modded machine), it crashes to prevent further world corruption.
How to fix it
1. Identify the culprit
Check your server's latest.log file. Look for the stack trace associated with the crash; it will often list the coordinates (X, Y, Z) of the problematic block or the specific mod/block type causing the issue.
2. Removing the block
Once you have the coordinates, you must remove the block to stop the crash loop.
On AwakeNode: Use the File Manager in your panel to navigate to your world folder. You can use a tool like MCEdit or an external region-file editor to remove the block at the specified coordinates, or simply delete the affected chunk file if you are comfortable with world editing.
On other hosts / manually: Use an SFTP client like FileZilla to download your world folder. Use a third-party tool like Amulet Editor or Minecraft Region Fixer to identify and remove the entity at the coordinates provided in your logs. Upload the fixed region file back to your server.
3. Check for mod conflicts
If the error persists or keeps recurring, it is often caused by a faulty mod or plugin.
On AwakeNode:
Use the Files tab to remove or replace the suspect mod or plugin in the mods or plugins folder. You can set your own startup command, JVM flags included, in the Startup tab; the memory setting follows your plan.
On other hosts / manually:
Remove your mods or plugins one by one to isolate which one is causing the ticking entity. If you suspect a memory issue, ensure your startup command correctly defines your -Xmx values. If you are consistently hitting memory limits, you may need to upgrade your server plan.