Anti-Nuke

Stop mass delete and ban waves before they destroy your server.

The idea

A nuke never comes from a stranger but from an admin account: a moderator whose account was stolen, or a bot added with wide permissions, starting to delete channels and roles in bulk. This system puts a ceiling on every dangerous action within a time window, and whoever crosses it is stopped before they finish.

The six watched actions

Per-action sensitivity

Punishment and response

The alert channel

A channel where an alert is posted the moment the guard fires, so you learn what happened and who did it without waiting for someone to tell you.

The whitelist

Tips

A nuke never comes from a stranger: a stranger cannot delete a channel. It comes from a stolen admin account, or a bot added with wide permissions, that starts deleting channels and roles in bulk. The difference between light damage and a lost server is a handful of minutes.

The idea is simple: every dangerous action gets a count limit within a time window. Six actions are watched: channel deletes and creates, role deletes and creates, webhook creates, and bot adds. Each has its own count, window, and roles allowed to perform it specifically, so you can open channel creation to a team without opening deletion.

The best first punishment is stripping all roles: it stops the damage in a second without removing anyone and without an irreversible decision, leaving you room to review calmly. Alongside it sit a formal warning, a kick, a ban, or jail, whichever you choose.

The alert channel is not a detail: a guard that fires without you knowing is no help in an investigation. Set it from the first moment so you learn what happened and who did it. And keep the whitelist very narrow, because the guard exists precisely for a stolen admin account.