Questions, answered

A comma: ,. Change it per server with ,prefix add ! — the dashboard shows the current prefix for every server.

Run ,setup first: it creates the moderation roles, the jail channel, the mod category and the log channel. Then ,antinuke setup, ,filter setup and ,voicemaster setup for the modules you want.

No. Everything configurable in chat is also on the dashboard, and a change applies immediately — there is no restart.

Each one is tied to a feature: Manage Roles for reaction roles, View Audit Log so antinuke can attribute an action, Manage Channels for tickets and jail. The security page lists every permission and its job. It never needs Administrator.

The whole catalog runs on the prefix, and the dashboard mirrors it for the settings. Slash commands exist where the feature benefits from them; the command reference marks the syntax for each one.

Yes, with automod and antinuke doing the first pass. Assign the roles ,setup creates to people you trust before enabling punishments.

It watches the audit log for destructive actions — bans, kicks, channel and role deletions, webhooks, integrations — reverts what it can and punishes the account that did it, following the thresholds and whitelist you set.

Only accounts outside the whitelist and the extra-owner list, and never the server owner. Whitelist the people who need to act without tripping it.

A temporary role and channel pair that removes an account from the server's channels without banning it, so it can be reviewed and released later.

Yes. Bot guard can block additions, quarantine the bot that joined and DM the person who added it — with a vulnerability scan attached. It is a toggle, per server.

Someone the server owner trusts as a second owner for that server only: they can configure it and recover it, without being an operator of the bot.

Join the support server with the server id. Antinuke keeps a log of what it reverted, and a backup taken before the incident can rebuild the structure.

With Discord OAuth. The deployment runs the handshake, the bot hands the page a 12-hour session, and your password is never seen.

It lists every server you and the bot share, but only shows settings to Administrators, the server owner and its owner role.

Yes — the same routes the dashboard uses, documented on the API page. It is meant for your own dashboards and tools.

No. The session stays valid and the page retries by itself; the settings live with the bot and come back when the host does. The status page shows the reachability.

Server configuration, the ids you configured and anonymous command counters. There is no profile, no advertising id and no analytics script. Every field is listed on the privacy page.

Only a message that is a command, and only to run it. Ordinary chat is not stored.

Clear the configuration, remove the bot, or ask in the support server. Ticket transcripts can be deleted from the dashboard.

No. bleh is an independent bot that runs on Discord's API.

The support server — it is the one place a maintainer will see the question.

The server id, the command you ran, what you expected and what happened. A screenshot of the reply helps more than a description of it.

Yes, in the support server. Say what the server needs rather than which command to add — the shape of the fix is usually clearer from the problem.