Anti-Nuke

Detect rapid channel and role changes and message spam, with moderation actions and an optional ignored role.

What Anti-Nuke protects

Anti-Nuke monitors rapid channel creation/deletion, role creation/deletion and message spam. Use it to help contain destructive activity or flooding. It is not a server snapshot and does not automatically recreate deleted channels, roles or messages.

For structural abuse, SHADO5 attempts to kick the responsible member. If Discord forbids a kick, it can attempt a one-hour timeout. For message spam, it attempts a one-hour timeout first and then removes matching recent messages from the triggering channel. Permissions and role hierarchy determine which actions can succeed.

Set up Anti-Nuke

Open Dashboard, select your server and choose Anti-Nuke under Protection.
Choose an optional log channel and, only when necessary, an ignored role. Complete the vote check when requested.
Use Enable & Save for a disabled module, or save changes for an enabled module.
Wait for confirmation and check the module status before testing.

Keep SHADO5 above the roles it must moderate. It needs View Audit Log to attribute structural changes, Kick Members or suitable moderation permissions to act, and Manage Messages plus Read Message History for spam cleanup. The slash-command setup also checks that the bot has Administrator.

Available settings

Setting	Behavior
Log Channel	Optional destination for detected events and moderation outcomes. Allow the bot to view it and send embeds.
Ignored role	Members with this role bypass Anti-Nuke checks, including message-spam checks. Leave it unset unless the exemption is intentional.

Configure from Discord

/antinuke status:on log_channel:#security-logs
/antinuke status:off

The caller needs Discord Administrator. status offers on/off; log_channel and ignored_role are optional. A vote is required to enable, not to disable. Supply the desired settings when enabling: omitted optional fields are cleared.

Check unexpected behavior

Check audit-log access, the bot’s role position and the ignored role. Owners and members at or above the bot cannot be kicked by it. A missing log is not proof that no action was attempted: verify the log channel still exists and allows embeds.

After an incident, review Discord permissions. If structural restoration is needed, use a previously created Server Backup. See Troubleshooting for general access issues.