How to Fix a "Ticking Entity" Server Crash
A "Ticking Entity" or "Ticking Block Entity" crash is a common issue on modded Minecraft servers, especially in large packs like ATM10 (All The Mods 10). This crash happens when a corrupted or bugged mob, item, or block causes the server to fail every time it tries to load the chunk it's in. Fortunately, Forge and NeoForge have a built-in tool to fix this.
This guide will show you how to safely remove the corrupted entity and get your server running again.
Step 1: Locate the Correct Config File
First, you need to find the correct server configuration file. The location depends on your version of Minecraft and its mod loader.
- For Forge (Minecraft 1.20.x and older): Navigate to
/world/serverconfig/forge-server.toml
- For NeoForge (Minecraft 1.21.x and newer): Navigate to
/config/neoforge-server.toml
You can find this file using the File Manager in your Game Panel. The world
folder may be named differently if you have changed it.
Step 2: Temporarily Enable Entity Removal
Once you have opened the correct .toml
file, you need to temporarily enable the setting that removes the problematic entity. Your crash log should tell you whether it's an "Entity" or a "BlockEntity".
- Find the line
removeErroringEntities = false
orremoveErroringBlockEntities = false
. - Change the value from false to true for the one that matches your crash report. If you are unsure, you can set both to true temporarily.
- Click Save to save your changes to the file.
WARNING :
This feature is powerful and should be used with caution. It is designed for recovery and should not be left enabled permanently
Step 3: Start the Server to Clear the Entity
Start your server. As the server loads the corrupted chunk, instead of crashing, it will now automatically delete the entity that was causing the issue. You should be able to join the server and confirm that it is no longer crashing.
Step 4: IMPORTANT - Revert the Changes
This is the most critical step. Once you have confirmed the server is working, you must undo the change you made.
- Stop the server.
- Go back and edit the same config file.
- Change the value you set to
true
back tofalse
. - Save the file and start your server again.
Your server is now fixed and back to its normal, safe operation. Leaving the removal setting on could cause unintended issues later, so it's essential to turn it off when you're done.