Sending flags to Discord
Chat alerts only reach staff who are online. A webhook mirrors the same flags into a Discord channel, where they stay and can be read after the fact.
Where a flag goes
Section titled “Where a flag goes”The three are independent. Turning the webhook on does not change the other two.
Set it up
Section titled “Set it up”-
In Discord, open Server Settings, then Integrations, then Webhooks, and create one on the channel you want the flags in.
-
Copy its URL.
-
Put it in
config.ymland switch the webhook on:config.yml webhook:enabled: trueurl: "https://discord.com/api/webhooks/..." -
Apply it:
/sp reload
The next flag lands in the channel. If nothing arrives, the server log will say why: SomaPace logs the failure rather than retrying silently.
What lands in the channel
Section titled “What lands in the channel”A card titled with the player name and how far off the break was, followed by a table:
| Row | Contains |
|---|---|
| Block, Tool | The block that was broken and what they held. |
| Coords, World | Where it happened. |
| Version, Ping | Their client version and ping at that moment. |
| Haste, Progress | Their haste level and how far the break had really got. |
Messages are batched over a five second window, so a burst of flags arrives as one message rather than twenty.
If you would rather not use Discord
Section titled “If you would rather not use Discord”You do not have to. flags.log holds the same information with more detail, and chat alerts cover
staff who are online. The webhook is there for teams who already live in Discord and want a record
they can scroll back through.