20% OFF Your first order with SAVE20
Background image of the page

Help Article

How To Debug and Fix Ticking Entity Errors

A step-by-step guide on how to debug and fix ticking entity errors.

Last updated on  Feb 13, 2026

Ticking entity errors can crash your Minecraft server when a corrupted entity (e.g., a mob, item, or projectile) fails during its update cycle. These are rare in vanilla, but common in modpacks.

In this guide, we'll go over the steps on how to debug and solve ticking entity errors.


Method 1: Forge Configuration

⚠️
WARNING: This can screw up everything in your server and is not recommended as a first resort, but it is the easiest.

Enabling the removeErroringBlockEntities and removeErroringEntities properties removes any ticking entity automatically.

  1. Go to your world’s /serverconfig/forge-server.toml file.
  2. Enable removeErroringBlockEntities and removeErroringEntities.
FILE: forge-server.toml

Method 2: Editing Your World

This is usually the best option to go with as this only resets one specific chunk – the chunk that is causing the problem.

  1. Navigate to the Files tab and open the crash-reports folder. Open the most recent crash-report and locate the chunk that the ticking entity is in.
  1. Use a program, such as MCASelector, to reset that specific chunk.
👉
If you're not sure on how to use MCASelector, read our guide on how to trim chunks with it.

Method 3: Restore a Backup

If you've taken a backup of your server previously, you can restore the backup's files to revert the data back to before the world was corrupted.

If you are running a server on WiseHosting, we take daily backups of our client servers, so get in touch with our support team if you'd like us to restore a backup from an earlier date.

🧑‍💻
If you still require assistance, please get in touch with our support team by opening a ticket or by joining our community Discord server.