The anti-nuke didn’t stop an attack: what should I check?
An attacker deleted channels or roles and the bot stopped nothing. Here are the possible causes, in order.
- Switches On the Anti-raid & anti-nuke page, “Protection enabled” and “Anti-nuke” (Anti-nuke tab) must be on. “Watch bots” and “Watch administrators” must be on too if the perpetrator was one of the two.
- Permission diagnostic The “What stops OriusBot from protecting this server” banner must be empty. Without View Audit Log, the anti-nuke “sees no action”. Without Manage Roles, it can’t cut the attacker’s rights.
- Role hierarchy If the diagnostic lists roles with dangerous permissions above OriusBot’s, their members are out of reach. Move the bot’s role up (see the article).
- Trusted accounts An account or bot listed under “Trusted accounts and bots” is never watched. Check that the perpetrator isn’t on it. The server owner is never touched either.
- Thresholds An action is only stopped beyond the limit in the “Anti-nuke thresholds” card within the set window. Three deletions spaced 30 seconds apart don’t exceed a limit of 3 per 5 seconds. The panel states that three times these thresholds per minute also stops a slow nuke.
- “Alert only” sanction If “Sanction for a human” or “Sanction for a bot” is set to Alert only, the bot warns but cuts nothing.
Afterwards
Open the History tab: the “Attack stopped” row (or its absence) tells you what the bot saw. To rebuild what disappeared, see the server map.
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.