How does anti-raid spot a wave of joins (without blocking a real influx)?
A raid is recognised by two things: joins are too numerous for this server, and the newcomers look alike. Anti-raid checks both, so it does not mistake a streamer’s audience for an attack.
The switches of the “Joins” card
| Switch | What it does |
|---|---|
| Protection enabled | Master switch for the whole page. |
| Join analysis | Watches for waves of joins. |
| Crowd analysis | Only triggers if newcomers look alike (accounts created together, serial usernames, new accounts without a picture). A streamer’s audience gets through. Off, the pace alone is enough. |
| Automatic lockdown | Without it, a suspicious influx is only flagged. See the Lockdown article. |
The three numeric fields
Under the switches, three boxes. Each saves when you leave the field or press Enter.
| Field | What it means | Values |
|---|---|---|
| Floor: joins | Minimum number of joins, within the window next to it, to speak of a wave. Below it, never any alert. | 2 to 50 (default 5) |
| Floor: window (seconds) | The duration over which those joins are counted. | 1 to 30 (default 2) |
| Minimum account age (days, 0 = none) | Discord accounts created less than this many days ago are kicked on arrival. | 0 to 3650 (default 0 = off) |
Example
Floor 5 and window 2: 5 joins in 2 seconds or more trigger the crowd check. If the 5 accounts were created the same day, have serial usernames and no picture, it is a raid. If they are 5 normal viewers of a live, they get through.
The learned normal pace
On top of the floor, the bot learns your server’s usual pace (status card: “Learned normal pace: ~N join(s) per hour”). A big server therefore does not lock itself on a busy evening. For the first days, “still learning” is shown: this is normal.
Still stuck?
Contact support with the title of this article, the step where you are stuck and what you see on screen.
Contact support More articles: ProtectionLast checked: 13 November 2026.