☰

Ticking Block Entity (Chest)

The server crashes while ticking a chest block entity. One chest holds broken NBT data, and removing it from the region file resolves the crash.

What does this error mean?
A 'Ticking block entity: chest' crash means a particular chest has invalid stored data, often a malformed item, so it throws an error each tick. Like other block-entity crashes, it can crash-loop the server at startup. 
Ticking block entity: chest
Most Common Causes
  • Corrupted chest NBT after a crash.
  • An invalid or malformed item inside the chest.
  • A mod bug affecting container logic.
  • A partially written chunk.
  • Data damage from an unclean shutdown.
How To Diagnose
  1. Get the chest coordinates and dimension from the crash report.
  2. Locate the corresponding region/chunk.
  3. Check for a mod in the stack trace.
  4. Back up the region first.
Recommended Fixes
  • Remove the chest in MCA Selector
    Delete or replace the chest at those coordinates to clear the bad data.
  • Restore the chunk from backup
    Use a clean backup to keep nearby builds and contents.
  • Address a mod cause
    Update or remove a mod implicated in the crash.
  • Regenerate the chunk
    Delete the chunk to force regeneration if nothing there must be kept.
Analyze My Log
Frequently Asked Questions

Yes, that one chest's items go. Restore from backup if they matter.

A chest in a spawn-loaded chunk ticks right away, crashing before you can intervene in-game.

MCA Selector lets you target the chunk and delete the offending block entity.