How to Track Damage Events with the Damage Logger

Enabling damage logging

The Damage logger records damage events as they happen, which is invaluable when you are debugging a farm, a trap, or a mob grinder and cannot tell why something is or is not dying. Find the damage logger toggle in the Carpet settings and turn it on. From that point, damage dealt in the loaded area gets reported.

What you will see

Each logged event tells you the source of the damage and the target, along with the amount. This lets you distinguish, for example, fall damage from fire damage from player hits. When tuning a farm, watch the log while you stand in the kill zone or trigger the mechanism, and confirm the damage type and magnitude match what you designed for.

Practical debugging workflow

Set up your test in a controlled area first. Trigger one damage source at a time and read the corresponding log line, so you can map each mechanic to its output. If a mob is surviving when it should die, check whether the logged damage is lower than expected — that usually means an enchantment, resistance effect, or armor is reducing it. If nothing logs at all, the damage source may not be firing, which points to a redstone or timing problem rather than a damage problem. Turn the logger off when done to keep chat readable.