Skip to main content

🚨 Anti-Raid

Anti-Raid watches your server's join rate and reacts in two stages: a spike alerts your admins, and a bigger spike triggers an automatic lockdown that pauses invites, DMs, and verification until the raid passes. It's the difference between waking up to an alert and waking up to a thousand bot accounts.

Overview​

  • Tracks joins per minute and flags suspiciously new accounts
  • Two-stage response: alert first, full lockdown at a higher threshold
  • Lockdown can pause invites (including vanity), disable DMs, pause captcha, raise server verification, and DM admins
  • Lockdowns lift automatically after the configured duration and cooldown
  • A Raid Events list keeps a history of past incidents

Configuration​

To configure anti-raid protection:

  1. Open your project in the Fren One webapp.
  2. Select the Discord server you want to configure.
  3. In the sidebar under Agent Configuration, select Moderation, then the Anti-Raid tab.
  4. Toggle "Detect and respond to join raids automatically" on.

When a raid lockdown is currently active, a banner at the top of the card shows it.

When to alert and lock down​

OptionDescription
Alert ThresholdJoins per minute to trigger an alert. Minimum 1; default 10.
Lockdown ThresholdJoins per minute to trigger lockdown. Minimum 1; default 20.
Min Account Age (days)Flag accounts newer than this. Default: 7. 0 disables age screening.
Lockdown Duration (min)How long a lockdown lasts. Minimum 1; default 30.
Cooldown (min)Calm time with no join spikes before a lockdown auto-lifts. Default: 5.

What happens when a raid is detected​

Five toggles control the lockdown response:

ToggleDescription
Pause invitesDisable all server invites, including vanity.
Disable DMsStop members from DMing each other.
Pause captchaPause new-member verification while locked down.
Raise verificationSet server verification to phone-required.
DM adminsDM admins when a lockdown starts.

Alert channel​

OptionDescription
Alert channelWhere raid alerts are posted.

Raid Events​

A read-only Raid Events list shows past incidents (up to 25; empty state "No raid events").

How it works in Discord​

The agent tracks the server's join rate every minute — this check runs early in the member-join sequence, before verification and welcomes. Crossing the Alert Threshold posts an alert to the alert channel (and DMs admins if enabled); alerts are throttled to one per window, so a sustained raid doesn't flood the channel. Crossing the Lockdown Threshold starts a lockdown with whichever responses you toggled on.

Two responses deserve a closer look:

  • Pause captcha matters because raiders that complete Bot Protection verification would otherwise be auto-verified straight into your server mid-raid. Pausing it holds them at the door.
  • Raise verification sets Discord's server verification to phone-required for the duration — and the agent restores your previous verification level once the lockdown ends.

Accounts newer than Min Account Age are flagged during the raid window. After the lockdown duration passes and joins stay calm through the cooldown, the lockdown lifts automatically.

Saving your changes​

This page uses a batched save — edits stay local until you select Save in the bar that appears at the bottom of the page. Leaving the page with unsaved changes shows a warning first.

Best practices​

Calibrating raid response
  • Keep a healthy gap between the alert and lockdown thresholds — alerts should fire on "unusual", lockdowns on "unmistakable".
  • If your server runs marketing pushes or partnered events, raise both thresholds beforehand so a legitimate influx doesn't lock everyone out.
  • Enable Pause captcha if you use Bot Protection — it's the response that stops raiders from verifying themselves in.
  • Always set an Alert channel; a lockdown your admins don't know about is twice as confusing.
Troubleshooting

No alerts arrive during a spike?

  • Check the Alert channel is set and the agent can post there, and that the join rate actually crossed the Alert Threshold.
  • Alerts are throttled to one per window by design — a long raid still produces a single alert per window, not a stream.

The server is still locked after the raid?

  • The lockdown lifts after Lockdown Duration (min) plus a calm Cooldown (min) with no new join spikes. A fresh spike restarts the clock.

Verification stayed on phone-required?

  • The agent restores the previous verification level when the lockdown ends; if the lockdown is still active (see the banner on this tab), the raised level is expected.

On this page