Raid protection — sliding-window detection that auto-recovers.

Detection — sliding-window join rate

Discord doesn't natively expose join-rate metrics. We track joins in a sliding window (default: 60 seconds) and compare against the trailing 24-hour average for that server. When the join rate exceeds 10× the trailing baseline AND at least 5 joins per minute (so a 50-member server doesn't false-trigger when 5 friends join), raid protection activates.

The dual threshold matters. Pure ratio false-triggers on small servers; pure absolute false-triggers on large servers (10 joins is normal in a 50k-member community). The combination works across every server size we've tested.

What auto-lockdown does

• Verification gate hardens. Account-age requirement bumps from none to 7 days (configurable). Newly-created accounts can't pass.
• Channel rate-limit increases. Members without the verified role get a 5-second slowmode in every public channel.
• Invite links pause. All invites issued in the last hour go to a held-pending state — they still work but new joins land in a quarantine role until a mod approves.
• Mods get pinged.One message in your mod-alerts channel: “Raid protection activated. Trailing 1m: 47 joins (baseline 4/min). Lockdown engaged.”

Auto-recovery — the part that matters

Most raid-protection systems lock down and stay locked until a mod manually unlocks. That works once. After the third or fourth false alarm, mods stop reacting because unlocking is annoying.

Sloth Lee's lockdown reverts itself. After 10 minutes of normal join rate (back near baseline), the verification gate softens, the slowmode releases, the held invites resume. Members in the quarantine role get reviewed in batch by mods or auto-promoted if their account passes the softer post-lockdown check.

Mods can override at any point — keep lockdown engaged longer, dismiss it early, or whitelist a specific account that joined during the window. Audit log records the activation, the reversion, and any manual overrides.

Quarantine flow

During lockdown, new joins land in a pre-configured@quarantinerole with limited permissions: can read #welcome and DM mods, can't see anything else. Mods see a queue in the dashboard with each quarantined member's account age, avatar, mutual servers (if any), and the message they sent if they've messaged us. Three actions: approve (promote to @member), kick, ban.

The drill

Dashboard → Tools → Raid drill. Spawns 100 simulated accounts in a sandboxed channel (no real Discord users). Verifies your detection threshold fires correctly, your lockdown engages, your alert posts to the right channel. Run it before a launch night, before a streamer raid-in, before a tournament. ~15 seconds total.

The configuration knobs

• Detection sensitivity — how many SD above baseline triggers. Default: 10×.
• Account-age gate — minimum during lockdown (default 7 days; can set higher for high-target servers).
• Quarantine role + channel — pre-configured in setup wizard, used during lockdown.
• Recovery window — how long of normal rate before auto-revert (default 10 min).