Minecraft anticheat guide
Configure FairPlay Discord Webhook Alerts
Set the minimum violation level, cooldown, and mention behavior for FairPlay Discord notifications.
Webhook notifications are opt-in
Webhook delivery starts disabled. The default notification settings are enabled: false, minimum-vl: 2.0, and cooldown-ms: 2000; your saved webhook.yml may contain different values.
Never publish an actual webhook URL, token, private server identifier, or unredacted player evidence. FairDiscordWebhookManager owns delivery under core/managers/webhook/.
enabled: false
minimum-vl: 2.0
cooldown-ms: 2000Threshold policy is not enforcement
The minimum-vl setting controls which notifications are eligible for webhook delivery. It does not ban a player, prove an alert is correct, or set the server's punishment tiers. Global punishments and mitigation settings have separate owners.
cooldown-ms spaces repeat notifications. It does not change check accounting.
| Setting | Default | Owns |
|---|---|---|
enabled | false | Whether any webhook delivery happens |
minimum-vl | 2.0 | Which violations are eligible for delivery; not punishment |
cooldown-ms | 2000 | How repeat notifications are spaced; not check accounting |
Diagnose non-delivery in this order
When a message never arrives, check in this order: enabled is true on the running server; the endpoint URL is valid and still belongs to the server owner; the violation met minimum-vl; a cooldown-ms window did not suppress the repeat; then network and retry behavior (connect-timeout-ms: 5000, read-timeout-ms: 5000, max-retries: 3, retry-base-delay-ms: 1000).
A configured webhook can still fail if its URL is invalid, the server cannot reach Discord, or Discord applies a rate limit. Check the saved webhook.yml keys and the server’s delivery logs.
Roll out to a private channel first
Point the first delivery at a private test destination the server owner controls, and use redacted examples when documenting the workflow. Confirm the destination before enabling delivery for staff channels.
Keep the URL private. If it is exposed, replace it through the server owner’s Discord controls.
FAQ
Does minimum-vl punish the player?
No. It only gates which violations are eligible for webhook delivery. Punishment and mitigation are owned by separate configuration.
Alerts stopped arriving but nothing changed. What first?
Confirm enabled is true, the URL is still valid, the violation met minimum-vl, and a cooldown-ms window did not suppress the repeat; then check timeout, retry, and Discord-side delivery facts.
Can I share my webhook.yml for support?
Only with the URL and any private identifiers redacted. Treat the endpoint as a secret and rotate it if it is ever exposed.