Skip to content
Tickwise
ErrorWorld & chunksSIG-WO-006

An entity or block entity throws an exception while ticking (Entity/BlockEntity threw exception)

Platforms
Paper · Purpur · single server
Verified
Verified
Confidence
Confidence 85%

What it looks like in the log

Any one of these lines is enough. The agent matches them locally, on your server.

logs/latest.log
  • [ERROR] threw exception at

Symptoms

  • Entities or block contents (chests, spawners, signs) disappear in one spot
  • In the log: “Entity threw exception at <world>:x,y,z” or “BlockEntity threw exception at …”

Cause

An entity or block entity tick threw an exception. Paper does not crash; instead it removes the culprit (the entity is discarded, the block entity is removed from the chunk), so the object at those coordinates disappears.

Possible causes

  • Corrupted NBT data on the entity/block (after a version change, external editors, a dupe)
  • A plugin or datapack modifies the entity/block incorrectly (plugin frames in the trace)
  • A server/fork bug in that entity's logic

How to fixMedium risk

  1. Take the world and coordinates from the evidence, along with the exception type and the first trace frames (whether a plugin is among them).
  2. If a plugin is in the trace, update it or report it to the author; if the error keeps recurring at one spot, go there (carefully) or use /kill @e[x=..,y=..,z=..,distance=..2] for the entity.
  3. For a block entity, check the block at the coordinates; if it is corrupted, restore the region from a backup (with the server stopped).
  4. If there are many errors after a version update, check the server/fork changelog for known bugs.

Translated from the Russian original; log lines are quoted verbatim.

Sources