|Docs

/antiraid settings

Overview

/antiraid settings opens an interactive dashboard that detects and responds to raids, sudden bursts of new members joining with malicious intent, and filters suspicious accounts at join time.

Required Permissions

  • Administrator

Subcommands

settings

No options. Running the command opens a dashboard with five pages: Overview, Limits, Punishment, Allowlist, and Other.

Dashboard settings

The dashboard is split into five pages: Overview, Limits, Punishment, Allowlist, and Other.

Overview page

A master toggle turns anti-raid on or off.

A protection-level preset applies a bundle of related settings at once:

LevelJoin thresholdWindowMinimum account ageJoin filters
Strict6 joins8 seconds1 dayAll join filters on
Balanced10 joins10 secondsOffJoin filters off
Lenient15 joins15 secondsOffJoin filters off

Join filter toggles (each can also be adjusted individually after picking a preset):

FilterBlocks
No avatarAccounts with no profile picture
Unverified botsUnverified bot additions
Invite namesUsernames containing invite links
Suspicious accountsAccounts scoring above the suspicion threshold
Similar namesClusters of new members with near-identical names, a common raid pattern

A suspicion-factor menu controls which signals feed the suspicion score: account age, missing avatar, missing banner, numeric username, missing badges, and invite links in username, nickname, display name, or custom status.

Limits page

  • Join wave: number of joins and time window that counts as a raid (default 10 joins in 10 seconds).
  • Similar names: how many similarly-named joins within a time window counts as a raid (default 2 within 5 minutes). Setting this to 0 turns off similar-name detection.
  • Account age: a minimum age applied only during an active raid, and a global minimum account age applied to every join regardless of raid state.

Punishment page

Choose the response when a raid is detected: CAPTCHA challenge, quarantine (default), mute, kick, or ban.

  • CAPTCHA: choose a channel and role for the challenge, and a timeout (presets of 1, 2, 5, or 10 minutes, or a custom value from 10–600 seconds). BetterAntiSpam sets up the channel and verification message automatically.
  • Mute: choose a duration from presets of 5, 10, 15, 30, or 60 minutes.
  • Quarantine: choose the role to apply. BetterAntiSpam creates it automatically if it doesn't already exist.

Allowlist page

Add trusted users or roles (up to 40 each) that are never treated as part of a raid.

Other page

  • Toggle whether the server owner is DMed when a raid is detected (default on).
  • Add extra users or roles to alert, and staff roles for antiraid purposes.
  • Edit the list of raid phrases BetterAntiSpam watches for during a join wave (default: nuked by, pwned, raid by, beamed, wizzed), and the hit count and time window that trigger a response (default 5 within 60 seconds).

Behavior

  • Alert users and roles are shared with /antinuke settings. The quarantine role is shared with /antispam settings and /antinuke settings.
  • Changes only apply while anti-raid is enabled. Editing a setting while it's off prompts you to turn anti-raid on first.
  • Only the admin who opened the dashboard can interact with it.

Note: For an immediate manual lockdown independent of these settings, use /raidmode.