☰

Ticking Block Entity (Furnace)

The server crashes while ticking a furnace block entity. One furnace has corrupted NBT data, removing or replacing that block clears the crash.

What does this error mean?
Block entities (furnaces, chests, hoppers) store extra data and tick each game tick. A 'Ticking block entity: furnace' crash means a specific furnace has invalid NBT, so it errors every tick, which can crash-loop the server on startup. 
Ticking block entity: furnace
Most Common Causes
  • Corrupted furnace NBT after an unclean shutdown.
  • An invalid item stack stored in the furnace.
  • A mod bug affecting furnace logic.
  • A partially written chunk containing the furnace.
  • Bad data from a previous crash mid-save.
How To Diagnose
  1. Read the crash report for the furnace's coordinates and dimension.
  2. Map the coordinates to the region/chunk.
  3. Note any mod in the stack trace touching furnaces.
  4. Back up the region before editing.
Recommended Fixes
  • Remove the block in MCA Selector
    Delete or replace the furnace at those coordinates to clear the bad NBT.
  • Restore from backup
    Roll the chunk back to a clean copy if the area matters.
  • Update/remove the mod
    If a mod is implicated, update or remove it.
  • Regenerate the chunk
    As a last resort, delete the chunk so it regenerates without the broken block.
Analyze My Log
Frequently Asked Questions

Only what is in that one furnace. The rest of the area is unaffected.

If the furnace is in a loaded chunk near spawn, it ticks immediately and crashes before you can reach it.

The crash report lists the exact block coordinates and dimension.