Discord Alerts

Discord Alerts

ModSeeker can send selected events to a Discord webhook. Delivery is disabled by default.

Configure delivery

Create a webhook for the intended Discord channel and copy its URL into plugins/ModSeeker/config.yml:

discord:
  enabled: true
  webhookUrl: "https://discord.com/api/webhooks/YOUR_WEBHOOK_URL_HERE"
  events:
    playerJoin: true
    modListReceived: true
    blacklistViolation: true
    verificationFailed: true

Replace the entire placeholder URL with the real webhook URL, then run /modseeker reload. The plugin accepts supported Discord HTTPS webhook URLs, not arbitrary forwarding services.

What each event sends

Switch	Trigger and contents
playerJoin	When a non-bypassed player's handshake starts: player name, UUID and connection IP address. It is not a final approval notice.
modListReceived	After mod verification passes: player name, top-level mod count, mod IDs and verified status. The mod text can be truncated to fit the notification.
blacklistViolation	A normal-mode blacklist rejection: player name and blocked IDs.
verificationFailed	Selected failure paths, including unapproved hashes and count-limit rejection: player name and reason. This is not a complete audit of every disconnect.

All event switches default to true, but the top-level enabled setting and a valid URL are also required. Launcher-only mode does not produce a fresh mod-report success event. Whitelist and Floodgate bypasses do not follow the ordinary handshake/report event path.

Turn off the events you do not need. In particular, disable playerJoin if you do not want connection IP addresses included in that notification.

Access and delivery

Use a channel whose audience is appropriate for the player information above. Keep the webhook URL private: anyone holding it can use that webhook. Redact it before sharing configuration or logs.

Delivery runs in the background. Discord or network failures do not turn a rejected player into an approved one. Notifications can be dropped under load or fail without a visible success notice, so use the server console for troubleshooting rather than treating Discord as a complete audit log.

If nothing arrives, check the master switch, the relevant event switch, the full webhook URL and outbound HTTPS access. Produce a fresh event after reloading; old events are not resent.