> ## Documentation Index
> Fetch the complete documentation index at: https://docs.celestia.rest/llms.txt
> Use this file to discover all available pages before exploring further.

# 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

<Tip>
  Use the `extraowner` command to assign trusted users with elevated antinuke control. Use `antinukeadmin` to assign users who can only enable protections.
</Tip>

***

## Commands

<AccordionGroup>
  <Accordion title="antinuke" icon="shield-halved">
    Opens the main antinuke control panel to manage all protections.

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

    <CodeGroup>
      ```bash Syntax theme={null}
      ,antinuke
      ```

      ```bash Example theme={null}
      ,antinuke
      ,antinuke config
      ,antinuke help
      ```
    </CodeGroup>

    **Aliases:** `an`
    **Permissions:** Server Owner, Extra Owner, or Antinuke Admin
  </Accordion>

  <Accordion title="extraowner" icon="crown">
    Manage extra owners who have elevated antinuke control equivalent to the server owner.

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

    <CodeGroup>
      ```bash Syntax theme={null}
      ,extraowner [@user]
      ,extraowner remove [@user]
      ,extraowner list
      ```

      ```bash Example theme={null}
      ,extraowner @user
      ,extraowner remove @user
      ,extraowner list
      ```
    </CodeGroup>

    **Aliases:** `eo`, `xowner`
    **Permissions:** Server Owner only
    **Limit:** 3 extra owners per server
  </Accordion>

  <Accordion title="antinukeadmin" icon="user-shield">
    Manage antinuke administrators who can enable protections.

    <Warning>
      Antinuke admins can only enable protections. They cannot disable them or change punishments.
    </Warning>

    <CodeGroup>
      ```bash Syntax theme={null}
      ,antinukeadmin [@user]
      ,antinukeadmin remove [@user]
      ,antinukeadmin list
      ```

      ```bash Example theme={null}
      ,antinukeadmin @user
      ,antinukeadmin remove @user
      ,antinukeadmin list
      ```
    </CodeGroup>

    **Aliases:** `ana`, `antiadmin`
    **Permissions:** Server Owner or Extra Owner
    **Limit:** 3 admins per server
  </Accordion>

  <Accordion title="antivanity" icon="link">
    Protect your server's vanity URL from unauthorized changes.

    <CodeGroup>
      ```bash Syntax theme={null}
      ,antivanity <on/off> [ban/kick/strip]
      ```

      ```bash Example theme={null}
      ,antivanity on strip
      ,antivanity off
      ```
    </CodeGroup>

    **Permissions:** Server Owner or Extra Owner (enable only: Antinuke Admin)
  </Accordion>

  <Accordion title="antiban" icon="gavel">
    Protect against mass bans and unauthorized ban actions.

    <CodeGroup>
      ```bash Syntax theme={null}
      ,antiban <on/off> [ban/kick/strip]
      ```

      ```bash Example theme={null}
      ,antiban on strip
      ,antiban off
      ```
    </CodeGroup>

    **Permissions:** Server Owner or Extra Owner (enable only: Antinuke Admin)
  </Accordion>

  <Accordion title="antibot" icon="robot">
    Protect against unauthorized bot additions to the server.

    <CodeGroup>
      ```bash Syntax theme={null}
      ,antibot <on/off> [ban/kick/strip]
      ```

      ```bash Example theme={null}
      ,antibot on ban
      ,antibot off
      ```
    </CodeGroup>

    **Permissions:** Server Owner or Extra Owner (enable only: Antinuke Admin)
  </Accordion>

  <Accordion title="antichannel" icon="hashtag">
    Protect against mass channel creation or deletion.

    <CodeGroup>
      ```bash Syntax theme={null}
      ,antichannel <on/off> [ban/kick/strip]
      ```

      ```bash Example theme={null}
      ,antichannel on kick
      ,antichannel off
      ```
    </CodeGroup>

    **Permissions:** Server Owner or Extra Owner (enable only: Antinuke Admin)
  </Accordion>

  <Accordion title="antikick" icon="boot">
    Protect against mass kicks and unauthorized kick actions.

    <CodeGroup>
      ```bash Syntax theme={null}
      ,antikick <on/off> [ban/kick/strip]
      ```

      ```bash Example theme={null}
      ,antikick on strip
      ,antikick off
      ```
    </CodeGroup>

    **Permissions:** Server Owner or Extra Owner (enable only: Antinuke Admin)
  </Accordion>

  <Accordion title="antirole" icon="user-tag">
    Protect against mass role creation, deletion, and permission changes.

    <CodeGroup>
      ```bash Syntax theme={null}
      ,antirole <on/off> [ban/kick/strip]
      ```

      ```bash Example theme={null}
      ,antirole on ban
      ,antirole off
      ```
    </CodeGroup>

    **Permissions:** Server Owner or Extra Owner (enable only: Antinuke Admin)
  </Accordion>

  <Accordion title="antimemberrole" icon="user-lock">
    Protect against unauthorized assignment of dangerous roles to members. Dangerous roles include Administrator, Manage Guild, Manage Roles, Manage Channels, Mention Everyone, and Manage Webhooks.

    <CodeGroup>
      ```bash Syntax theme={null}
      ,antimemberrole <on/off> [ban/kick/strip]
      ```

      ```bash Example theme={null}
      ,antimemberrole on ban
      ,antimemberrole off
      ```
    </CodeGroup>

    **Aliases:** `amr`, `memberroleprotect`
    **Permissions:** Server Owner or Extra Owner (enable only: Antinuke Admin)
  </Accordion>

  <Accordion title="antisettings" icon="gear">
    Protect server settings from unauthorized changes.

    <CodeGroup>
      ```bash Syntax theme={null}
      ,antisettings <on/off> [ban/kick/strip]
      ```

      ```bash Example theme={null}
      ,antisettings on strip
      ,antisettings off
      ```
    </CodeGroup>

    **Permissions:** Server Owner or Extra Owner (enable only: Antinuke Admin)
  </Accordion>

  <Accordion title="antiwebhook" icon="webhook">
    Protect against unauthorized webhook creation, deletion, and webhook nukes.

    <CodeGroup>
      ```bash Syntax theme={null}
      ,antiwebhook <on/off> [ban/kick/strip]
      ```

      ```bash Example theme={null}
      ,antiwebhook on strip
      ,antiwebhook off
      ```
    </CodeGroup>

    **Permissions:** Server Owner or Extra Owner (enable only: Antinuke Admin)
  </Accordion>

  <Accordion title="antiprune" icon="users-slash">
    Protect against unauthorized member pruning.

    <CodeGroup>
      ```bash Syntax theme={null}
      ,antiprune <on/off> [ban/kick/strip]
      ```

      ```bash Example theme={null}
      ,antiprune on ban
      ,antiprune off
      ```
    </CodeGroup>

    **Aliases:** `pruneprotect`
    **Permissions:** Server Owner or Extra Owner (enable only: Antinuke Admin)
  </Accordion>
</AccordionGroup>

***

## Protection Modules

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

<CardGroup cols={2}>
  <Card title="Antiban" icon="gavel">
    Prevents unauthorized bans or mass ban attempts
  </Card>

  <Card title="Antibot" icon="robot">
    Blocks unapproved bots from being added to the server
  </Card>

  <Card title="Antikick" icon="boot">
    Prevents unauthorized kicks or mass kick activity
  </Card>

  <Card title="Antichannel" icon="hashtag">
    Prevents harmful channel deletion or mass channel creation
  </Card>

  <Card title="Antirole" icon="user-tag">
    Protects roles from unauthorized creation, deletion, or permission changes
  </Card>

  <Card title="Antimemberrole" icon="user-lock">
    Blocks unauthorized assignment of dangerous permissions to members
  </Card>

  <Card title="Antivanity" icon="link">
    Prevents unauthorized changes to the server's vanity URL
  </Card>

  <Card title="Antisettings" icon="gear">
    Blocks unauthorized edits to major server configuration settings
  </Card>

  <Card title="Antiwebhook" icon="webhook">
    Prevents unauthorized webhook creation, deletion, or modification
  </Card>

  <Card title="Antiprune" icon="users-slash">
    Blocks unauthorized mass member pruning
  </Card>
</CardGroup>

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:

<Tabs>
  <Tab title="Strip">
    Removes all roles from the offending user, leaving them with no permissions.
  </Tab>

  <Tab title="Ban">
    Permanently bans the offender from the server.
  </Tab>

  <Tab title="Kick">
    Removes the offender from the server (they can rejoin if they have an invite).
  </Tab>

  <Tab title="None">
    Takes no direct action but logs the incident for review.
  </Tab>
</Tabs>

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

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

***

## 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.

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

***

## 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.

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

***

## 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.

<Info>
  All antinuke actions are automatically logged to your configured logging channel if enabled.
</Info>