# AstraMaster Documentation (Full Text) AstraMaster (also written "Astra Master") is a Discord security bot offering anti-nuke protection, quarantine, automod, moderation, logging, backup and restore, and server management. Website: https://astramaster.vercel.app/ Docs: https://astramaster.vercel.app/docs Legal text: https://astramaster.vercel.app/llms-legal.txt --- # Antinuke URL: https://astramaster.vercel.app/docs/security/antinuke Category: Security Antinuke (also called Bunker Buster™) monitors a Discord server for mass-destruction attempts and responds immediately. It is fully independent of the Quarantine system and can be enabled at any time. ## Access - Commands: `b2!antinuke`, `b2!antinuke disable`, `/antinuke` - Access: Server Owner only ## What it detects | Action | Threshold | Time window | |---|---|---| | Mass channel deletion | 3 deletions | 15 seconds | | Mass channel creation | 3 creations | 15 seconds | | Mass channel edits | 3 edits | 15 seconds | | Mass category deletion | 3 deletions | 15 seconds | | Mass category creation | 3 creations | 15 seconds | | Mass category edits | 3 edits | 15 seconds | | Mass role deletion | 3 deletions | 15 seconds | | Mass role creation | 3 creations | 15 seconds | | Mass role updates (permission changes) | 3 updates | 20 seconds | | Mass webhook creation | 3 webhooks | 15 seconds | | Mass kick | 3 kicks | 15 seconds | | Mass ban | 3 bans | 15 seconds | | Mass ping (@everyone, @here, large role) | 3 pings | 15 seconds | ## What happens on detection - The executor (the nuker) is immediately banned. - The server is automatically restored from the latest backup. - A notification is sent to the configured log channel, if one is set up. ## Commands - `b2!antinuke`: shows the current antinuke status, or enables antinuke if it is not yet enabled. - `b2!antinuke disable`: disables antinuke. - `/antinuke`: slash command equivalent, with the same enable/status behavior. ## Auto-backup When antinuke is enabled, AstraMaster creates an initial backup immediately and then schedules automatic daily backups. ## Whitelist All highly trusted admins and trusted bots must be whitelisted in antinuke specifically. Selective or channel-specific whitelists do not apply to antinuke. Run `b2!whitelist` and go to the "Anti-Nuke Whitelist" page to manage entries. Warning: if the whitelist is not configured, AstraMaster will flag and punish any admin who triggers a threshold, even if they are legitimate. ## Critical: double gate security AstraMaster provides double gate security against nuke attempts. Even members who are whitelisted for specific actions may still be flagged if they exceed the defined thresholds. To do bulk actions without being flagged, whitelist the role(s) or user(s) in the Anti-Nuke Whitelist. ## Change: backups require server owner DMs (introduced 19 July, 2026) The server owner's DMs with AstraMaster must be enabled for backups to function correctly. If AstraMaster cannot deliver the latest backup to the server owner (DMs disabled or any other external issue), backups for that server may be affected. That can prevent a successful server restoration after a nuke attempt. ## Important notes - If a nuke attempt is detected and AstraMaster is restoring the server, do not intervene. Wait for restoration to complete. - Give AstraMaster the top role in the role hierarchy for the most accurate and complete restoration. - Make sure AstraMaster can DM the server owner for backup delivery. If the owner has DMs disabled, backups may not be delivered. Next page: Backup and Restore (https://astramaster.vercel.app/docs/security/backup) --- # Overview URL: https://astramaster.vercel.app/docs/security/overview Category: Security AstraMaster™ is a Discord security bot that protects servers from nukes, spam, raids, and unauthorized activity. Its systems are modular — you can enable what you need and configure each one independently. ## Core Modules - **Automod** — Automatically filters messages (swears, links, spam, GIFs, pings) - **Quarantine** — Isolates violating members - **Antinuke** — Detects and responds to mass-destruction server attacks - **Backup & Restore** — Creates server snapshots, restores automatically on nuke detection - **Buster Call** — Emergency permission lockdown for all roles server-wide - **Logs** — Sends moderation events to a designated log channel - **Whitelist** — Exempts trusted users from being flagged by Automod or Antinuke - **Manage Panel** — GUI panel for managing Extra Owners and elevated access ## Prefix All commands use the prefix `b2!` ## Important Requirements Warning: AstraMaster must have the top role in the server's role hierarchy for all systems to function at full capability. Next page: Quick Setup (https://astramaster.vercel.app/docs/security/setup) --- # Quick Setup URL: https://astramaster.vercel.app/docs/security/setup Category: Security The Quick Wizard automates the initial setup of AstraMaster in 4 steps. It is the recommended way to get started. ## Access Command: `b2!setup` — Server Owner only ## What it does (in order) - **Anti-Nuke** — Checks if antinuke is already enabled. If not, enables it and creates an initial backup. Sends a confirmation DM to the server owner. - **Bot Role + Quarantine** — Verifies that AstraMaster's role is at the top of the hierarchy, then enables the Quarantine module. If the bot role is not at the top, this step is skipped. - **Automod** — Enables the Automod system (requires Quarantine to be active). - **Logs** — Prompts you to set a log channel. ## After Setup You should complete these steps: - Run `b2!whitelist` and add trusted admins to the **Anti-Nuke Whitelist** page. - Run `b2!whitelist` and review channel/user exemptions for Automod. ## Note: Warning: Managing Whitelists is super important for maintaining your server's security, if you skip this step then we don't recommend you to use AstraMaster, as bot will punish innocent users. ## Web quick setup You can also run setup from the dashboard. It covers everything `b2!setup` does, plus a few extra modules: per-filter whitelists, quarantine role management, bot role management, and **Shogun's Guard** — a join gate that automatically kicks unverified bots, very young accounts, accounts with no avatar, bots requesting dangerous permissions, and accounts with suspiciously long names. Same rule applies here as everywhere else: AstraMaster's role needs to sit above every other role for Quarantine to turn on. The dashboard will check this for you and tell you which role is in the way if it isn't. One thing to know — only the **server owner** can run the web wizard. Extra Owners can use most of the dashboard, but setup is owner-only. Next page: Automod (https://astramaster.vercel.app/docs/security/automod) --- # Automod URL: https://astramaster.vercel.app/docs/security/automod Category: Security Automod watches your server around the clock and acts on violations automatically. No manual intervention needed for the filters below. ## Access Command: `b2!automod` or `/automod` — Can be accessed by Owner, trusted moderator, and extra owner. ## Filters - **Swear Blocking** — Deletes messages containing blocked words automatically. - **GIF Blocking** — Prevents members from sending GIFs (non-Tenor sources) where enabled. - **Link Blocking** — Deletes messages containing external URLs. - **Spam Blocking** — Detects and removes repeated or rapidly-sent messages. - **External Apps Protection** — Detects spam caused by external applications and automatically punishes the user responsible. - **Mass Ping Protection** — Removes messages that ping an excessive number of members (@everyone, @here). ## Managing Automod Run `b2!automod` or `/automod` to open the interactive Automod panel. From there you can toggle each filter on or off individually. ## Whitelisting for Automod Use `b2!whitelist` to exempt specific users or channels from Automod filters. Each filter has its own whitelist page — exemptions on one page do not carry over to others. ## Tuning Filters from the Dashboard Swear, GIF, Link, External Apps, and Mass Ping filters can each be fine-tuned from the dashboard — not just toggled on or off. For each one you can set: - **Base Timeout** — how long a member is timed out for on a first violation. - **Max Multiplier** — how much longer the timeout gets each time the same person repeats the violation. - **Reset Window** — how long someone has to stay clean before their escalation level resets back down. Spam Blocking doesn't have this tuning yet — it's on/off only for now. Every change made here is logged, and you can reset any filter back to its default timing at any time. ## Note: Warning: AutoMod can be punitive if not whitelists for automod specific page is not configured properly. Next page: Quarantine (https://astramaster.vercel.app/docs/security/quarantine) --- # Quarantine URL: https://astramaster.vercel.app/docs/security/quarantine Category: Security Quarantine is the core module of AstraMaster's protection system. ## Access Slash Command: `/quarantine` Prefix Commands: `b2!quarantine` Access: Extra owner or trusted moderator(for prefix commands); Owner for enabling via slash command. ## How it Works When a member is quarantined, AstraMaster removes their ability to send messages in all channels by assigning a restricted quarantine role. The quarantine role is automatically configured to deny `Send Messages` in every channel. ## Enable Quarantine Run the slash command `/quarantine` to enable the quarantine system. AstraMaster will create a quarantine role and sync it with all existing channels. ## Commands - **`b2!quarantine @user`** — Manually places a member into quarantine - **`b2!quarantine remove @user`** — Lifts quarantine and restores the member's access - **`/add-quarantine`** — Slash equivalent for placing a member into quarantine - **`/remove-quarantine`** — Slash equivalent for releasing a member from quarantine ## Whitelists for Quarantine Whitelists for the Quarantine module can be configured to allow specific users or roles to bypass SPECIFIC or FULL quarantine restrictions. ## Warning: Warning: If whitelists are not configured properly, the Quarantine module may inadvertently punish legitimate users for un-authorized actions. We recommend configuring whitelists carefully to avoid unintended consequences. Next page: Antinuke (https://astramaster.vercel.app/docs/security/antinuke) --- # Backup & Restore URL: https://astramaster.vercel.app/docs/security/backup Category: Security AstraMaster can create a full snapshot of your server structure and restore it on demand. Backups are also created and used automatically by the Antinuke system. ## Access Commands: `b2!backup`, `b2!restore` Access: Extra owner (b2!backup) and Owner (b2!backup, b2!restore) ## Create a Backup Run the following command: `b2!backup` Creates a backup of the server immediately. AstraMaster sends the backup file (JSON) directly to the **server owner via DM**. ## Restore from a Backup Run the following command: `b2!restore` Attach the backup JSON file that AstraMaster previously sent to the owner. AstraMaster will begin restoring the server from that snapshot — recreating channels, roles, and permissions. ## Auto-Backup (via Antinuke) When Antinuke is enabled, AstraMaster automatically backs up the server every **1 day**. This backup is used for automatic restoration if a nuke is detected. ## Important Notes - AstraMaster should have the **top role** in the hierarchy for the most complete backup and restore results. - During a restoration triggered by Antinuke, do not intervene — let AstraMaster finish the restoration process. Next page: Buster Call (https://astramaster.vercel.app/docs/security/buster-call) --- # Buster Call URL: https://astramaster.vercel.app/docs/security/buster-call Category: Security Buster Call is an emergency command that strips dangerous permissions from all roles server-wide instantly. Use it only when an attack is actively happening or you believe one is imminent. ## Access Commands: `b2!buster-call`, `b2!rewoke-call` Access: Extra Owner or Server Owner ## Commands - **`b2!buster-call`** — Strips dangerous permissions from all roles server-wide. AstraMaster DMs affected members to notify them. - **`b2!rewoke-call`** — Restores permissions that were removed during the buster call. Only roles affected by the buster call are restored. ## Important Notes - AstraMaster must have the **top role** for best results. Without it, some roles may not be affected. - This is a highly sensitive command — use it only when genuinely needed. - `b2!rewoke-call` only restores the permissions that were stripped during the most recent buster call. Next page: Logs (https://astramaster.vercel.app/docs/security/logs) --- # Logs URL: https://astramaster.vercel.app/docs/security/logs Category: Security AstraMaster can log server moderation activity to a channel of your choice. ## Access Commands: `b2!logs #channel`, `b2!logs remove` Access: Server Owner only ## Enable Logging `b2!logs #channel` Replaces `#channel` with a mention or channel ID. AstraMaster sends all moderation events to that channel. ## Disable Logging `b2!logs remove` Stops logging. Moderation events will no longer be recorded. ## Change Log Channel Run `b2!logs #channel` again with a different channel to update the destination. ## Events Logged | Event | Description | | --- | --- | | Timeouts | Member mute/timeout actions | | Role toggles | Member role update actions | | Bans | Member ban actions | | Kicks | Member kick actions | | Whitelist | Updating of whitelist for any action | | Backups | Server backups | | Quarantines | Isolation events | | Anti-Nuke Alerts | Nuke detection events and responses | ## Note: Warning: Logs will be only produced by bot actions via commands such as b2!to etc. and via bot's self automated actions. Logs won't occur for actions not liable to bot. Next page: Whitelist (https://astramaster.vercel.app/docs/security/whitelist) --- # Whitelist URL: https://astramaster.vercel.app/docs/security/whitelist Category: Security The Whitelist panel manages which users and channels are exempt from being flagged or quarantined by AstraMaster's systems. ## Access Command: `b2!whitelist` Access: Administrator or Trusted Mod role (for Automod pages); Server Owner (for Antinuke page) ## Whitelist Pages The panel contains separate pages for each Automod filter and one dedicated page for Antinuke: - Swear Blocking Whitelist - GIF Blocking Whitelist - Link Blocking Whitelist - Spam Blocking Whitelist - Mass Ping Whitelist - Quarantine Whitelist - Anti-Nuke Whitelist ## Automod Whitelisting - Each Automod filter has its own whitelist. Being exempt from one filter does not exempt you from others. - You can whitelist individual **users** or **channels** per filter. - Use the **Add Channel** and **Remove Channel** buttons on Automod pages to manage channel exemptions. ## Antinuke Whitelisting - Antinuke uses a **global whitelist only** — selective (per-action) whitelisting does not work with Antinuke. - All highly trusted admins and bots that perform bulk server operations **must** be listed here. - If an admin is not whitelisted and triggers a threshold, they will be flagged and banned. ## Quarantine Whitelist Quarantine Whitelist is a selective whitelist for specific actions, enabling server owners to have full freedom over security. It contains whitelists for: - Channel creation - Channel deletion - Mass ping (only quarantines if mass ping protection is enabled via b2!automod) - Role creation - Role deletion - Role permission changes (update) - Webhook creation - Ban - Kick - Give roles (dangerous permissions only) - Bot add - Server update - Channel edit - Category edit ## When selective modules are enabled If only some modules are enabled, and others are disabled, then whitelist only show pages for the enabled modules. For example if only automod is enabled, then only automod specific whitelist pages will be shown. If all modules are enabled, then there will be full access to all whitelist pages. Next page: Manage Panel (https://astramaster.vercel.app/docs/security/manage) --- # Manage Panel URL: https://astramaster.vercel.app/docs/security/manage Category: Security The Manage panel is a GUI interface for owners to manage elevated access roles — specifically the Extra Owner whitelist, which grants trusted users access to high-level commands. ## The 11th July, 2026 changes: Warning: After careful consideration, we have decided to remove role support from the Trusted Moderator and Extra Owner fields. Roles can no longer be added to either of these fields, and any previously added roles have been automatically removed. This change has been implemented to enhance server security. ## Access Command: `b2!manage` Access: Server Owner or Extra Owner ## Who Can Use It - **Server Owner** — always has access - **Extra Owner** — a role/user granted elevated privileges by the server owner ## Extra Owners Extra Owners are users who have been granted elevated privileges by the server owner, allowing them to access additional commands and manage the server's security more effectively. ## What Extra Owners Can Do Extra Owners have access to commands that go beyond regular admin permissions, including: - `b2!buster-call` / `b2!rewoke-call` - `b2!manage` - `b2!backup` - `b2!automod` - `b2!quarantine @user` / `b2!quarantine remove @user` - `b2!whitelist` - `b2!strip` / `b2!unstrip` - `b2!to @user ` / `b2!rto @user` - `b2!role @user ` - `b2!ban @user` - `b2!kick @user` ## Trusted moderators Trusted moderators are users who have been granted elevated privileges by the server owner or extra owner(s), allowing them to assist in managing the server's security and enforcing rules. ## What Trusted Moderators Can Do Trusted moderators have access to commands that go beyond regular admin permissions, including: - `b2!automod` - `b2!quarantine @user` / `b2!quarantine remove @user` - `b2!strip` / `b2!unstrip` - `b2!to @user ` / `b2!rto @user` - `b2!role @user ` - `b2!ban @user` - `b2!kick @user` ## Risks of Granting Elevated Access Warning: Giving Extra Owner or Trusted Mod access is a serious risk — they can easily be abused to take over the server. Roles our Users added in Extra Owner and Trusted Mod pages must have Administrator permission, so be especially careful with those. ## Important Notes - Only the server owner can open the Manage panel to grant or revoke Extra Owner access. - Extra Owner is not the same as Trusted Mod — each level has distinct command access. Next page: Strip & Unstrip (https://astramaster.vercel.app/docs/security/strip) --- # Strip & Unstrip URL: https://astramaster.vercel.app/docs/security/strip Category: Security Strip and Unstrip allow moderators to remove and restore a specific member's dangerous permissions quickly without fully quarantining them. ## Access Commands: `b2!strip @user`, `b2!unstrip @user` Access: Owner, extra owner, trusted moderator ## Commands - **`b2!strip @user`** — Removes dangerous permissions from the specified user - **`b2!unstrip @user`** — Restores the permissions that were stripped from the user ## Important Notes - Strip targets a single user, unlike Buster Call which affects all roles server-wide. - Unstrip only restores the permissions that were removed by the most recent strip on that user. Next page: Warnings & Best Practices (https://astramaster.vercel.app/docs/security/warnings) --- # Warnings & Best Practices URL: https://astramaster.vercel.app/docs/security/warnings Category: Security Read this before configuring AstraMaster. These are the most critical things to know. ## Whitelist Management is Critical Warning: If legitimate members or admins are not whitelisted, AstraMaster will flag and punish them. This is especially important for Antinuke — any admin who triggers a threshold and is not on the Anti-Nuke Whitelist will be banned and the server will be restored. ## AstraMaster Must Have the Top Role Critical: Place AstraMaster's role above all other roles in the server's role hierarchy. This is required for: - Quarantine to correctly manage permissions - Buster Call to affect all roles - Antinuke to restore the server completely - Backup to capture all role and channel data accurately ## Do Not Intervene During Restoration When Antinuke detects a nuke and begins restoring the server, do not manually make changes. Wait for AstraMaster to finish the restoration process. ## Antinuke Whitelist Must Be Set Up Before an Attack The Anti-Nuke Whitelist is not retroactive. Configure it as soon as Antinuke is enabled. Use `b2!whitelist` and navigate to the Anti-Nuke Whitelist page. ---