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

# Panic Mode

> One-click emergency response to shut down an ongoing attack on your server.

# Panic Mode

> One-click emergency response to shut down an ongoing attack on your server.

## What is panic mode?

When your server is under attack, panic mode gives the owner a single panel of emergency actions — lock or hide channels, strip dangerous permissions, wipe webhooks, and clear mass pings. You pick exactly which actions to run, and raze executes them all at once.

<Warning>
  Panic mode actions are drastic and server-wide. Some are irreversible (deleting channels). Only the server owner or extra owner can trigger it.
</Warning>

## Trigger the panel

<CodeGroup>
  ```bash Full theme={null} theme={null}
  ;panicmode
  ```

  ```bash Alias theme={null} theme={null}
  ;panic
  ```
</CodeGroup>

This opens a **multi-select** menu — choose one or more actions and raze runs them together. The result is sent as an ephemeral message only you can see.

## Actions

| Action                    | Effect                                                              |
| ------------------------- | ------------------------------------------------------------------- |
| **Auto Safety Module**    | Lock channels + clear webhooks + clear @everyone pings, in one step |
| **Lock Channels**         | Deny sending in all channels — channels stay **visible**            |
| **Hide Channels**         | Hide all channels from @everyone                                    |
| **Delete Channels**       | Permanently delete every channel                                    |
| **Emergency Mode**        | Strip dangerous permissions from all roles                          |
| **Clear Webhooks**        | Delete all existing webhooks                                        |
| **Clear @everyone Pings** | Delete recent messages containing @everyone / @here                 |

<Info>
  **Lock** and **Hide** are separate on purpose — locking only removes send permissions so members can still see channels, while hiding removes visibility entirely.
</Info>

## Configuration

Panic mode config lives under the `antinuke` group.

<Tabs>
  <Tab title="Enable / disable">
    ```bash theme={null} theme={null}
    ;antinuke panicmode enable
    ;antinuke panicmode disable
    ```
  </Tab>

  <Tab title="Alert channel">
    ```bash theme={null} theme={null}
    ;antinuke panicmode channel (#channel)
    ```

    Sets where panic mode alerts are announced.
  </Tab>

  <Tab title="Auto-trigger">
    ```bash theme={null} theme={null}
    ;antinuke panicmode autotrigger (on | off)
    ```

    When on, antinuke events automatically fire panic mode instead of waiting for a manual trigger.
  </Tab>

  <Tab title="View config">
    ```bash theme={null} theme={null}
    ;antinuke panicmode
    ```

    Run with no subcommand to see the current panic mode configuration.
  </Tab>
</Tabs>

<Info>
  Panic mode configuration commands require antinuke owner permission.
</Info>