Permissions
SomaPace has two nodes, both defaulting to operator.
| Permission | Grants |
|---|---|
soma.pace.alerts | Chat alerts when a break is denied, and /sp alerts to toggle them. |
soma.pace.reload | /sp reload. |
What holding alerts means
Section titled “What holding alerts means”A player with soma.pace.alerts gets a chat alert every time SomaPace denies a break, unless they
turned their own alerts off with /sp alerts. Operators receive alerts as well, whether or not the
node is granted explicitly.
The alert is clickable: clicking it runs /tp <player>, which puts you next to whoever was flagged.
Hovering shows the detail behind the flag, including the tool, the haste level, the ping and how far
the break had really got.
Not a moderation permission
Section titled “Not a moderation permission”Neither node decides who is protected. SomaPace checks every player except those in creative mode, whatever permissions they hold.
Give soma.pace.alerts to the staff who watch for cheating, and soma.pace.reload to whoever
maintains the configuration.
Cutting down the noise
Section titled “Cutting down the noise”Alerts are rate limited to one per player every 2.5 seconds, so a cheater breaking a wall of blocks produces a readable stream rather than a flood.
If alerts still bother your staff during events, they can turn them off individually with
/sp alerts and read flags.log afterwards instead.