What raid mode does
A raid is a large number of accounts joining your server within a very short time, usually less than a minute. It happens faster than anyone can react. Raid Mode is the part of Easy Auth that responds automatically, so you don't have to.
It monitors how quickly accounts are joining. When they start joining faster than the threshold you configured, it does two things at the same time: it changes what the server allows, and it takes action against the accounts that joined as part of the wave. You configure both behaviors, and they are not mutually exclusive.
All of it lives in your dashboard, under Raid mode. It is not in the /settings panel inside Discord, unlike verification and the Join Gate.
Set when it starts and how long it lasts
Three fields decide when raid mode starts, and how long it answers for.
- Joins, between 2 and 100. How many accounts have to arrive.
- Within, between 10 and 60 seconds. The stretch of time they are counted over.
- Response lasts for, between 1 minute and 24 hours. How long the answer stays in force once it has started. It is not a guess at how long the attack will last.
Raid mode
Ten joins within ten seconds, answered for five minutes. The switch at the top governs the automatic trigger, not raid mode itself: you can still raise the shield by hand with it turned off.
The window rolls. It is not a clock that empties and hands an attacker a fresh start: Easy Auth is always looking at the last stretch of time, wherever it ends.
If the joins reach your threshold again while raid mode is still active, the timer resets and no second alert is posted, so a single attack stays a single wave in your log. Once the joins stop, the timer expires and raid mode ends automatically. You don't have to remember to turn it off. That's why a longer duration is less useful than it might seem, and why five minutes is a good place to start.
It ends by itself
Choose what the server does, and what happens to accounts
The server side is three switches, and they add up. Turn on the ones that fit your server.
- Close verification. Nobody can verify while the wave lasts. This one is server-wide, so it also stops members who were already in and had not verified yet. What they see is
Verification is temporarily closed due to suspicious activity. Please try again later. - Pause invites Premium. Discord stops accepting every invite link to your server. It is the strongest of the three, because accounts stop arriving at all, and the only one that also protects the people you did not mean to hit: with invites closed they never arrive, so there is nothing to take back afterwards.
- Pause direct messages Premium. Discord blocks direct messages between members who are not friends with each other. This is the answer to a wave that joins in order to send scam links in private.
The last two are Discord's own security actions rather than something Easy Auth invents, so they need the Manage Server permission. Without it everything else is still applied and the alert in your log names the part that could not be done. Discord lifts them by itself when the time is up, so a restart in the middle of a wave does not reopen your server.
Raid mode
PremiumPause direct messagesPremiumWhat happens to accounts that joinPremiumActionBlock verificationThe two halves of the response. The server switches are cumulative, the action on accounts is a single choice.
The action on accounts Premium. It applies to every account that joins while raid mode is active. It also applies to the accounts that joined during the time window that triggered it. That's what makes raid mode effective.
A ban is the one you cannot take back
Block verification. The account stays in the server but cannot verify itself, so it never gets past your verification channel and nobody is removed. Kick and Ban both remove the account, and a kicked one can come back on its own once the wave is over. A banned one cannot: Easy Auth does not lift bans, you would take them off Discord's ban list yourself.Only your whitelist is trusted while a wave is active. Members on it are verified as usual, and raid mode never touches them. No one else is trusted: an invite link that normally verifies people on arrival won't, returning members who verified before must verify again, and the Join Gate checks are skipped. Instead, the configured action applies to everyone, which is stricter than any of those checks.
Leaving the action on Nothing is a real setting, not an unfinished one. It gives you the server responses on their own: the door shuts, and the accounts that got in are left for you to look at afterwards.
Start and stop a wave by hand from Discord
Three commands, in Discord.
/raidmode onraises the shield straight away. It works with the automatic trigger turned off too, as long as a duration and at least one response are set. It does not act on anyone already in the server, only on what joins from that moment: a person typing a command is not the same evidence as a threshold being crossed./raidmode offdrops it and posts the summary early. It releases only what Easy Auth paused, so invites you had paused yourself stay paused./raidmode statusshows what is running, or what would happen if a wave arrived right now.
on and off need the Manage Server permission. status needs Manage Roles.
Read the log, and undo a mistake
Two messages per wave, and only two. One when it starts, one when it ends.
Detected is the trigger that fired. Informations lists what was actually applied, not what is configured, so a missing permission shows up here as a line of its own.
Lasted counts from the alert, so it includes any time the wave extended itself. View Details opens the list of accounts it acted on, shown only to you. It needs Manage Roles and keeps working for good: the list is read back from your server history, so a wave from last month still opens.
The accounts are not logged one at a time while a wave runs. Three hundred blocks would be three hundred messages, and your log channel would be unreadable exactly when you need it. Both messages sit under the single Raid alert switch in your log settings.
To put a mistake right, /blocked reason:Raid detected lists everyone whose verification was blocked by a wave, newest first, with when it happened and whether they are still in the server. /unblock lets the ones you recognise through.