Docs
Setup, the prefix, and the access model. This covers what the bot and API actually expose today.
- 01Getting startedInvite the bot and confirm it can see the channels you want it to act in.
- 02The prefixWhere the command prefix comes from and how to change it per server.
- 03Who can do whatWhich Discord permission each module requires, and which two ignore admin entirely.
- 04Command referenceEvery command the bot has published, with aliases, usage, and cooldowns.
- 05System statusLive dependency health and latency for the bot and the API behind it.
Getting started
- 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.
- 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.
- Confirm it responds. Send
!pingin a channel it can read. - Set the prefix if the default collides with another bot. See below.
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.
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.