Skip to main content
Where antinuke watches people who already have permissions, antiraid watches people arriving. Its main lever isn’t punishment — it’s pausing invites, which is the only thing that actually stops a raid rather than cleaning up after one. Requires Administrator to configure.

​
Start here

Every detection posts here: what triggered, who was involved, what was done about it. Without an alert channel you’ll find out about raids from your members. Aliases: alertchannel, alerts, log, logs.

​
Detection modules

Triggers when more than threshold members join inside the given timeframe. Everyone in the burst is punished, and invites are paused for the configured duration.Aliases: massjoins, mass, join, joins.
Tune the timeframe to your growth rate. A server that gets 3 joins a day should use 30s --threshold 5. A server that gets 200 a day needs something much looser or you’ll ban legitimate traffic every time you get posted somewhere.
Punishes members whose Discord account is younger than the threshold. kick is the usual choice — it keeps the account out for now without permanently blocking someone who genuinely just made an account.Aliases: new, accountage, account, age.
Requires a custom avatar to stay in the server. Crude but effective — throwaway raid accounts rarely bother setting one.Aliases: pfp, pfpcheck, nopfp, requirepfp.
This has real false positives. Plenty of normal people never set an avatar. Use kick rather than ban, and consider leaving it off unless you’re actively being raided.
Flags accounts that look automated: online via web only, never on mobile or desktop, not a booster, and joined within the last three days. That combination is very close to a signature for scripted accounts.Aliases: antispoof, spoof, browser, selfbot, alt, web.
Punishes a single member sending too many messages too quickly. Their messages are cleaned up as well.Aliases: msgspam, messagespam.
The coordinated version of spam. Triggers when several different accounts flood one channel together — the channel is locked and everyone involved is punished.Aliases: flood, massspam, floodspam, channelspam.
Counts mentions in a single message. Default threshold is 5, minimum 3.Aliases: mention, mentions, pingspam, pings.
Automod mentions does something similar but through Discord’s native AutoMod, which blocks the message before it ever appears. Antiraid’s version punishes after the fact. Running both is reasonable — automod stops the ping, antiraid handles the account.

​
Punishments

Every module takes --punishment with one of:

​
Pausing invites

When a module triggers, invites are paused automatically. Discord also blocks DMs from server members for the same window, which shuts down the DM-scam half of most raids.
duration aliases: pausefor, lockfor, freezefor. pause aliases: lock, freeze. resolve aliases: status, state, resume, unpause, unlock, unfreeze. !antiraid resolve is the “it’s over” command — it lifts the invite pause and unlocks any channels raidspam locked. Run it once you’ve cleaned up.
Discord caps invite pauses at 24 hours. Anything longer is clamped.

​
Temporarily disabling

Doing a partnered event, a bot list bump, or anything else that’ll cause a legitimate join spike:
Turns antiraid off for the duration, then re-enables it automatically. Much safer than turning modules off by hand and forgetting to turn them back on. Aliases: temp, stop, cancel.

​
Whitelisting

Exempt users are never punished by any antiraid module. Aliases: exempt, wl.

​
Reviewing the configuration

Shows every module, its state, timeframe, threshold, punishment, the alert channel, the pause duration and the whitelist.

​
Command reference

Every command requires Administrator. Group aliases: raid, warden, wd.