Protection (anti-nuke & anti-raid)
Stop staff or bots that go rogue, then undo what they did.
#How it works
Each protection watches one kind of action. When someone does too many of them too fast — say, deletes 3 channels in 10 seconds — Apera punishes them, logs an incident and then undoes the damage: deleted channels and roles come back with their permissions and position, and channels or roles they spammed are deleted. Everything starts off; you turn on what you need on the Protection page.
#What happens during an attack
- Someone deletes channels faster than your limit.
- Apera removes their roles (or jails, kicks or bans them — your choice) within a second.
- An incident is logged with who did what.
- Deleted channels and roles are recreated with their permissions and position; spam channels and roles are deleted.
#What each protection watches
- Mass channel / role changes — creating or deleting many channels or roles.
- Mass ban / kick / prune — a moderator removing lots of members.
- Anti-bot — someone adding a bot you didn’t approve.
- Anti-webhook — webhooks created to spam.
- Role, channel and server edits — permission changes, renames, icon changes; Apera reverts them.
- Dangerous role perms / role add — giving Administrator or other powerful permissions.
- Emoji, sticker and invite deletes.
- Anti-raid — many new accounts joining at once.
#Reference: recommended settings
A safe starting point for each protection. Set most delete/ban/kick limits to 3 actions in 10 seconds → Remove roles, anti-bot and dangerous-perms to 1 → Kick/Revert, and anti-raid to 5 joins in 60 seconds. The full table is below; open Protection to apply them.
| Protection | Watches | Suggested limit | Suggested punishment |
|---|---|---|---|
| Mass channel | Creating / deleting channels | 3 in 10 s | Remove roles |
| Mass role | Creating / deleting roles | 3 in 10 s | Remove roles |
| Mass ban / kick | Banning or kicking members | 3 in 10 s | Remove roles |
| Anti-bot | Adding bots | 1 | Kick the bot + remove roles |
| Anti-webhook | Creating webhooks | 1 | Remove roles |
| Dangerous role perms | Giving Administrator & co. | 1 | Revert + remove roles |
| Server edits | Name, icon, settings | 1 | Revert |
| Anti-raid | Many new accounts joining | 5 in 60 s | Kick (ban in raid mode) |
Remove roles works on everyone below Apera. Timeout does not work on administrators — Discord doesn’t allow it.
#Set one up
- Open Dashboard → your server → Protection. Every protection starts off — you turn on what you need.
- On a protection’s card, flip the switch to Enabled (①). The pills (②) show its current rule at a glance — Action, Limit and time Window.
- Click Settings › (③) on that card to fine-tune the rule.
- In the box: set Threshold — how many actions (①), Interval — in how many seconds (②), and Action — what happens: Remove roles, Jail, Timeout, Kick or Ban (③). Then press Done (④).
- Repeat for each protection you want. A solid start: channel/role delete 3 in 10s → Remove roles, ban/kick 3 in 10s, and anti-bot on.
- Add your trusted staff and bots to the whitelist so they’re never punished for normal work.
Turn on just the protections you need and set how strict each one is. The two pictures below are numbered to match these steps.
#What Apera can’t do
- It can’t punish the server owner or anyone whose role is above Apera’s — keep Apera’s role at the top.
- It can’t bring back messages inside a deleted channel; the channel returns empty.
- Administrators can’t be timed out (a Discord rule) — use Remove roles or Ban for them.
#Punish first, then undo
When someone breaks a protection rule (edits a role’s permissions, renames a channel, adds a webhook…), Apera first punishes them, so they can’t keep going, and then undoes what they did. Apera’s own undo is marked, so it is never mistaken for an attack and never undone again.
#Who can change protection
Protection and security settings can be changed by the server owner, the trusted admins the owner picks, and everyone who has the highest role with Administrator. Open Trusted admins on the dashboard to see that role, who holds it (all of them, however big the server), and to add or remove trusted admins.
Commands in this guide
Next steps
Was this page helpful?
Thanks for telling us!