Installation

Before you start

You need	Version
Spigot	`1.8.8`
Java	`21`
PacketEvents	`2.12.0` or later

PacketEvents is required. SomaPace reads the mining packets a client sends to know how far a block break has really got, and without it the server refuses to enable the plugin.

Install

Put the jar in place.

Drop SomaPace.jar into your server’s plugins/ folder, next to PacketEvents.
Start the server once.

SomaPace creates plugins/SomaPace/config.yml. The shipped defaults are already the ones you probably want: deny FastBreak, log every denial, no Discord webhook.
Check that it loaded.
```
/sp alerts
```
It answers that alerts are now disabled or enabled for you. That reply means the plugin enabled and the command is registered. Run it again to get back to where you were.

What it does with the defaults

Setting	Default	Effect
`cancel-breaks`	`true`	A break that arrives too early is denied and the block is put back.
`log-to-file`	`true`	Every denial is appended to `flags.log`.
`webhook.enabled`	`false`	Nothing is sent to Discord.

Staff who hold soma.pace.alerts also get a chat alert, which is on by default for them.

So a fresh install already enforces. There is nothing to configure to get protection.

Watching before enforcing

On a live server it is worth running SomaPace in observation mode for a few days first, to see what it catches before it starts denying breaks:

cancel-breaks: false

Flags are still raised, logged and alerted, but the block breaks normally. Read flags.log after a day or two, confirm that what it caught is what you think it caught, then set it back to true.

The files it creates

File	What it is
`config.yml`	Enforcement, logging and the Discord webhook.
`flags.log`	One line per denied break, when `log-to-file` is on.
`states.yml`	Which staff members turned their chat alerts off. Written by the plugin, leave it alone.

After editing config.yml, apply it with:

/sp reload