flags.log

When log-to-file is on, every flagged break appends one line to plugins/SomaPace/flags.log. This is where you go when you want the detail behind an alert.

[2026-09-08 21:14:03] Gatien (1.8.9, ping 42ms, DIAMOND_PICKAXE, haste 0, tracked 12.4s) FastBreak STONE -> CANCEL 61% (...)

Reading a line

Part	Means
`[2026-09-08 21:14:03]`	When it happened, server time.
`Gatien`	The player.
`1.8.9`	The client version they connect with, or `Unknown`.
`ping 42ms`	Their ping at that moment.
`DIAMOND_PICKAXE`	What they held, or `HAND`.
`haste 0`	Their haste level, 0 when they have none.
`tracked 12.4s`	How long SomaPace had been following this player when the break arrived.
`STONE`	The block.
`-> CANCEL`	The break was denied. `-> ALLOW` means `cancel-breaks` is off and the block broke anyway.
`61%`	How far the break had really got.

That last number is the one that matters. 61% means the block was only 61 percent mined when the break arrived, so 39 percent of the work was missing. The chat alert shows that missing part instead, which is why the two numbers look different for the same event.

Everything in brackets after the percentage is the internal trace of the replay. It is there for diagnosis, not for daily reading.

Using it

The context on each line is what tells a real cheat from a false positive.

A player at 300 ms ping who trips a few percent short now and then is not the same as a player at a totem that breaks the iron block 20% faster than it should.

The tracked value is worth a glance too: a very small number means the player had only just been picked up, for instance right after a join or a world change.

Housekeeping

The file is only appended to. SomaPace never rotates or truncates it, so on a busy server it grows without limit. Archive or delete it periodically, or turn log-to-file off if the chat alerts and the Discord mirror are enough for you.