Documentation

Docs

Setup, the prefix, and the access model. This covers what the bot and API actually expose today.

Getting started

  1. Invite the bot with the invite link. Accept the permission set it asks for — anti-nuke cannot reverse a change it has no permission to reverse.
  2. Check the bot can see the channels it needs. A channel override that denies View Channel wins over a server-level grant, so a bot that looks configured can still be blind to the channel you care about.
  3. Confirm it responds. Send ?ping in a channel it can read.
  4. Set the prefix if the default collides with another bot. See below.

Role position matters as much as the permission itself: the bot cannot act on a member whose highest role sits above its own, no matter what it has been granted.

The prefix

The default prefix is ?. It is stored per server, so changing it in one server does not affect any other.

Change it with ?prefix set <value>, and read the current one with ?prefix view. A prefix is 1 to 5 characters.

The usage strings on the command reference are rendered with the default prefix, not your server's. If you have changed it, substitute yours.

Who can do what

Server owner or extra owner only

Anti-nuke, panic, and warden. A server administrator is not enough, and there is deliberately no bot-owner bypass — the modules that can undo a mass deletion are also the ones an attacker with Administrator would disable first. Extra owners are added by the server owner.

Administrator or Manage Server

Everything else in the dashboard: automod, logging, autorole, tickets, containers, and the image block list. Ownership of the server also satisfies this.

Delegated, without the Discord permission

Warden grants one member one moderation capability with its own rate cap, so a moderator can ban without being handed Ban Members — which would also let them ban without limit and outside the bot's audit trail.