Why doesn’t the lockdown trigger during a raid?
A raid slipped past you and the bot didn’t declare a lockdown? Go through these checks in order, from the most common to the rarest.
- Open the anti-raid page Protection › Anti-raid & anti-nuke menu, Joins tab.
- Check “Protection enabled” It is the main switch: when off, none of the page’s protections work.
- Check “Join analysis” It watches for waves of joins. If it’s off, a lockdown already opened by hand keeps acting, but no wave is spotted.
- Check “Automatic lockdown” Without it, a suspicious influx is only reported: it’s up to you to declare the lockdown with the Declare lockdown button.
- Look at “Crowd analysis” When on, the bot only reacts if the newcomers look alike (new accounts, similar usernames, no avatar…). A raid made of varied accounts can therefore pass for a normal influx.
- Compare with the floors “Floor: joins” and “Floor: window (seconds)” set the minimum number of joins required. Below that, never an alert (see the joins article).
Bots don’t count as newcomers
When a bot joins the server, the anti-raid doesn’t treat it as a wave: the watch reads its permissions. See this article.
What if permissions are missing?
The lockdown may be declared but unable to act (invitations not paused, channels not locked). Look at the “What stops OriusBot from protecting this server” banner, explained in this article.
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.