What it does
- Protect the role hierarchy
- Flanker Protection sits above ordinary staff roles. Members below it cannot use Discord's native ban, kick or timeout controls against protected members. Flanker's own highest role must remain above the roles and members it manages.
- Control dangerous access
- Advanced setup can guard Administrator grants, strip dangerous permissions from untrusted bots, and enable Channel Shield and Webhook Lock. Flanker Admin lets staff work through bot commands without holding Discord Administrator or Manage Server.
- Contain an attack
- With antinuke, ban protection and the default native-ban brake enabled, the first unknown native ban starts panic, even if the ban is legitimate. Panic lowers action limits to one and pauses dangerous permissions on roles below flanker. Known bans sent by flanker are excluded.
- Keep recovery accountable
- Supported ban, role and channel recovery follows containment. Permission snapshots survive restarts and failed restores remain retryable. Ending panic requires the owner and, when configured, the backup owner's approval.
Get started
Type the slash command in Discord and fill in its fields, or mention flanker before it. Commands still require their usual permissions.
- Add flanker and place its highest role above the roles it must manage.
- As the server owner, open guided setup and review beginner or advanced protection.
/antinuke setup - Review the enabled modules, thresholds, punishments and trusted bots.
/antinuke config - Read panic status and the native-ban brake behavior before using native moderation.
/antinuke panic show
Common questions
Can an antinuke bot prevent every ban or server nuke?
No. Discord role hierarchy, the server owner's inherent permissions, API limits and actions already accepted by Discord all constrain a bot. Flanker reduces available attack paths and reacts to supported events; it cannot promise zero damage.
Can fake permissions change antinuke settings?
No. Fake permissions and the Flanker Admin role alone do not unlock antinuke configuration. Security commands use separate trusted authorization, and weakening advanced protection follows owner and backup-owner approval rules.
What is the difference between antinuke and antiraid?
Antinuke handles destructive administrative actions such as mass bans, channel deletions and dangerous permissions. Antiraid handles waves of joining accounts, coordinated chat floods and resource bursts.