Antiraid
Catches suspicious new joins - brand-new accounts and default-avatar accounts - and alerts, kicks, or bans them automatically, before they can do anything.
Setup
$antiraid
Also /antiraid. Opens a panel with an On/Off toggle, an alert channel picker, and one
button per detection rule below. Nothing runs until you turn it on and configure at least
one rule.
Detection rules
Each rule is configured independently - pick a threshold (if it has one) then what should happen: Alert Only, Kick, or Ban.
| Rule | What it checks |
|---|---|
| Account Age | Flags anyone whose Discord account is younger than a threshold you set (e.g. 5d, 1h 30m, 2mo) - the classic sign of a raid/bot account made minutes before joining. |
| Default Avatar | Flags anyone using Discord's default avatar (no custom avatar ever uploaded, globally or for this server) - no threshold to set, just pick the action. |
If a join matches more than one rule at once, only one action is ever taken (Ban outranks Kick, which outranks Alert) - never a double kick/ban. Whichever rules actually called for that action are listed as the reason; a rule set to Alert Only never gets folded into a different rule's kick/ban reason, since it never asked for one - it still shows up in the alert, just kept clearly separate from what actually justified the action.
What happens when someone's flagged
- If the action is Kick or Ban: they're DM'd a plain, simple explanation first (same style as any other moderation action) - capped at once per person per hour, so a raid account that keeps auto-rejoining can't spam its own DMs.
- The action is taken (or, for Alert Only, nothing happens to the member at all).
- An embed goes to the alert channel either way - who, why, what happened, and whether the DM landed.
A member removed by Antiraid never triggers a welcome or leave message, and never gets pinged by New Member Ping - there's no point announcing someone who's already gone, and it avoids spamming those channels every time a raid bot tries to rejoin.