Antinuke System

Complete server protection framework to safeguard your Discord community

Overview

The Antinuke system is a complete server-protection framework designed to safeguard your Discord community against malicious actions such as mass bans, unauthorized bot additions, role abuse, and configuration tampering. It provides a centralized control panel where authorized users can enable or disable protections, configure punishments, and review the system’s status in real time through an interactive interface.

---

Access Control

The Antinuke system uses a three-tier permission hierarchy:

• Server Owner — Full access to all antinuke features including enabling, disabling, changing punishments, and managing all user tiers
• Extra Owners — Elevated access equivalent to the server owner for antinuke purposes. Can manage antinuke admins, enable/disable protections, and change punishments. Limited to 3 per server
• Antinuke Admins — Restricted access. Can enable protections but cannot disable them or change punishments. Limited to 3 per server

Use the extraowner command to assign trusted users with elevated antinuke control. Use antinukeadmin to assign users who can only enable protections.

---

Commands

antinuke

Opens the main antinuke control panel to manage all protections.

This is a dangerous command and will allow the user to entirely alter the antinuke configuration.

Syntax

,antinuke

Aliases: an Permissions: Server Owner, Extra Owner, or Antinuke Admin

extraowner

Manage extra owners who have elevated antinuke control equivalent to the server owner.

Extra owners have near-full antinuke access. Only assign this to highly trusted users.

Syntax

,extraowner [@user]
,extraowner remove [@user]
,extraowner list

Aliases: eo, xowner Permissions: Server Owner only Limit: 3 extra owners per server

antinukeadmin

Manage antinuke administrators who can enable protections.

Antinuke admins can only enable protections. They cannot disable them or change punishments.

Syntax

,antinukeadmin [@user]
,antinukeadmin remove [@user]
,antinukeadmin list

Aliases: ana, antiadmin Permissions: Server Owner or Extra Owner Limit: 3 admins per server

antivanity

Protect your server’s vanity URL from unauthorized changes.

Syntax

,antivanity <on/off> [ban/kick/strip]

Permissions: Server Owner or Extra Owner (enable only: Antinuke Admin)

antiban

Protect against mass bans and unauthorized ban actions.

Syntax

,antiban <on/off> [ban/kick/strip]

Permissions: Server Owner or Extra Owner (enable only: Antinuke Admin)

antibot

Protect against unauthorized bot additions to the server.

Syntax

,antibot <on/off> [ban/kick/strip]

Permissions: Server Owner or Extra Owner (enable only: Antinuke Admin)

antichannel

Protect against mass channel creation or deletion.

Syntax

,antichannel <on/off> [ban/kick/strip]

Permissions: Server Owner or Extra Owner (enable only: Antinuke Admin)

antikick

Protect against mass kicks and unauthorized kick actions.

Syntax

,antikick <on/off> [ban/kick/strip]

Permissions: Server Owner or Extra Owner (enable only: Antinuke Admin)

antirole

Protect against mass role creation, deletion, and permission changes.

Syntax

,antirole <on/off> [ban/kick/strip]

Permissions: Server Owner or Extra Owner (enable only: Antinuke Admin)

antimemberrole

Protect against unauthorized assignment of dangerous roles to members. Dangerous roles include Administrator, Manage Guild, Manage Roles, Manage Channels, Mention Everyone, and Manage Webhooks.

Syntax

,antimemberrole <on/off> [ban/kick/strip]

Aliases: amr, memberroleprotect Permissions: Server Owner or Extra Owner (enable only: Antinuke Admin)

antisettings

Protect server settings from unauthorized changes.

Syntax

,antisettings <on/off> [ban/kick/strip]

Permissions: Server Owner or Extra Owner (enable only: Antinuke Admin)

antiwebhook

Protect against unauthorized webhook creation, deletion, and webhook nukes.

Syntax

,antiwebhook <on/off> [ban/kick/strip]

Permissions: Server Owner or Extra Owner (enable only: Antinuke Admin)

antiprune

Protect against unauthorized member pruning.

Syntax

,antiprune <on/off> [ban/kick/strip]

Aliases: pruneprotect Permissions: Server Owner or Extra Owner (enable only: Antinuke Admin)

---

Protection Modules

Each protection module targets a specific category of server abuse. The system currently includes the following protections:

Antiban

Prevents unauthorized bans or mass ban attempts

Antibot

Blocks unapproved bots from being added to the server

Antikick

Prevents unauthorized kicks or mass kick activity

Antichannel

Prevents harmful channel deletion or mass channel creation

Antirole

Protects roles from unauthorized creation, deletion, or permission changes

Antimemberrole

Blocks unauthorized assignment of dangerous permissions to members

Antivanity

Prevents unauthorized changes to the server’s vanity URL

Antisettings

Blocks unauthorized edits to major server configuration settings

Antiwebhook

Prevents unauthorized webhook creation, deletion, or modification

Antiprune

Blocks unauthorized mass member pruning

Each protection can be toggled individually and is fully independent.

---

Available Modules

The antinuke system monitors the following Discord events:

• bot_add — Bot join protection
• role_update — Role update protection
• role_create — Role creation protection
• role_delete — Role deletion protection
• channel_update — Channel update protection
• channel_create — Channel creation protection
• channel_delete — Channel deletion protection
• guild_update — Server settings and vanity protection
• kick — Mass kick protection
• ban — Mass ban protection
• member_role_update — Dangerous role assignment protection
• webhook_create — Webhook creation protection
• webhook_delete — Webhook deletion protection
• prune — Mass member prune protection

---

Permission Hierarchy

Action	Server Owner	Extra Owner	Antinuke Admin
Manage extra owners	✅	❌	❌
Manage antinuke admins	✅	✅	❌
Enable protections	✅	✅	✅
Disable protections	✅	✅	❌
Change punishments	✅	✅	❌
Configure Verdict Mode	✅	✅	❌

---

Punishment System

Punishments define how the system responds when a protection is triggered. The available actions include:

Strip

Removes all roles from the offending user, leaving them with no permissions.

Ban

Permanently bans the offender from the server.

Kick

Removes the offender from the server (they can rejoin if they have an invite).

None

Takes no direct action but logs the incident for review.

Punishments are stored per protection, but the system also provides a global selector to apply a chosen punishment across all modules simultaneously.

Only the server owner and extra owners can change punishments. Antinuke admins cannot modify punishment settings.

---

Control Panel Interface

The primary antinuke command opens a fully interactive control panel built with Discord Components V2. The interface is composed of:

• Header describing the Antinuke system
• Real-time status display listing all protections, their enabled/disabled state, and assigned punishment
• Individual toggle buttons for each protection module
• Global controls:
  • Enable All
  • Disable All
  • Set Punishment (global punishment menu — full access only)

All actions immediately update configuration values and refresh the control panel to reflect the changes.

Only the user who executed the command can interact with the control panel. When the session expires, the panel remains displayed but becomes inactive.

---

Enable All / Disable All

The system supports bulk actions for efficiency:

• Enable All: Activates every protection and assigns “Strip” as the default punishment
• Disable All: Fully disables all protections — restricted to server owner and extra owners

Bulk actions also trigger logging entries to ensure full transparency.

---

Best Practices

• Assign extra owners only to highly trusted individuals as they have near-full antinuke control.
• Use antinuke admins for staff who should be able to activate protections but not alter the overall configuration.
• Always whitelist your staff and bots to avoid false positives.
• Regularly review your settings with ,antinuke config.
• Test the system in a safe environment before going live.

Improper configuration may result in staff or bots being punished. Always whitelist and trust your staff and bots.

---

Logging Integration

Every configuration change — including enabling, disabling, and punishment updates — is recorded in the logging system. This ensures complete auditability and allows server owners to track all modifications to their Antinuke settings.

All antinuke actions are automatically logged to your configured logging channel if enabled.