Antinuke security
Per-module protection, revert-then-punish handling, quarantine, panic lockdown and per-user whitelists so your staff can still work during an attack.
bleed runs antinuke protection, full moderation, an embed studio with import/export scripts, reaction and button role panels, starboards, streaks and per-server temp voice — every setting configurable in place, with live stats to prove it.
Counters are read straight from the running bot — no caching, no screenshots.
Waiting for live data…
The long names still work, but every daily command has a short alias — ,tz for ,timezone, ,bump for ,bumpreminder, ,gaw for ,giveaway.
These same numbers are available to anything that can make a request. CORS is open, responses are cached for a minute.
Every destructive action is watched per module. When something trips, bleed reverts what it can, punishes the actor, quarantines the account and logs the whole thing — including who tried what.
,antinuke enable
Strips every dangerous role from the account, stores the original role list and restores it exactly with ,unquarantine — including the roles that were removed for being risky.
One command locks the server down, snapshots the structure first and lets you lift it again without losing the layout. Panic-whitelisted roles keep working while it's up.
Whitelist users, roles or bots per guild, mark extra owners, pick a log channel and get DM'd on every trigger. Nothing fires on a whitelisted actor.
Everything is per-server, nothing is paywalled, and every module can be switched off individually.
Per-module protection, revert-then-punish handling, quarantine, panic lockdown and per-user whitelists so your staff can still work during an attack.
Ban, tempban, softban, mute, jail, warn thresholds, snipe, purge, sticky messages, force-nick and a searchable case history in ,history.
,embed create is a live preview builder. Export any embed as a script and paste it back anywhere — import and export are exact inverses.
Reaction or button role panels, exclusive mode, self-role limits, button-role studios by label or emoji, and sticky roles that come back on rejoin.
Daily streaks with restores and reward roles, starboards, keyword highlights, suggestions, giveaways, invite tracking and DISBOARD bump reminders.
Queue, filters, crossfade, seek and presets, plus VoiceMaster hubs that spawn temp channels each with their own control panel and owner.
Embed colour, accent and bot name are all server settings — these are the defaults.
Pick a category to jump into the filtered list. The counts come from the running bot when its API is reachable.
Every command keeps its full name — these are just the short forms. Tap one to open the command and read what it does.
Prefix , · click any command to read what it does and copy it. Press / or ⌘K to search, ? for shortcuts.
Every key below resolves per guild and can be changed in place with ,config — no restart, no dashboards to learn.
| Key | Label | Type | Default | Description |
|---|
bleed ships its own emoji so replies stay on-brand without Nitro.
Add it with the admin scope so antinuke can actually revert destructive actions, then run ,config once to set branding.
,antinuke enable, whitelist your staff and your own bots, then pick a log channel. Panic mode is there if it ever goes wrong.
Reaction roles, starboard, streaks, bump reminders and temp voice each take one command to switch on.
It is , by default. Change it per server in ,config under branding, and every command also answers to its short alias — ,tz, ,bump, ,av.
Each module watches its own action type. Anything from a whitelisted user, role or bot is ignored; the whitelisted extra owners and panic-whitelist roles always bypass. Everything else is reverted where possible, then the actor is punished with the configured punishment and quarantined if quarantine is set up.
No. Antinuke only acts on destructive changes, and panic mode takes a structural snapshot before it locks anything so the layout can be restored intact.
The bot exposes GET /api/stats from the same process that serves Discord. This page calls it on load and renders whatever comes back; if the API is unreachable it falls back to the numbers baked in at build time.
Yes — it is a plain Node project. Run npm run site to regenerate this page from your own command source, and set SITE_API_BASE if your stats API lives on another host.
Three ways, all of them forgiving. ,help <command> takes a name or an alias, ,help search <word> matches descriptions, and a typo gets you the closest names as buttons you can click. This page does the same: search above, and a near miss still finds it.
Every command answers to its full name and its aliases — ,rank and ,r, ,purge and ,clear. Arguments are the forgiving part: mentions, IDs or names usually all work, and most commands ask rather than guess when something is missing.
Run ,config for an interactive panel, or target a key directly — ,config <key> <value>. This page lists every setting the bot knows about, with the same names and defaults, in the settings table above.
Clicking any command opens what it does, how it is used, its aliases and its examples.