Documentation
ROGUE Docs
How to set the bot up, what each system does, and where to change it.
Commands are written with the default , prefix — swap in
whatever your server uses.
Getting started
Rogue needs three things to be useful: the invite, a role high enough to act, and whichever systems you want turned on.
- Invite the bot. The invite asks for Administrator because most systems need it. You can grant less, but role, channel and moderation commands will fail on anything the bot cannot reach.
- Move its role up. Discord will not let a bot act on anyone above it. If role commands silently do nothing, this is almost always why — the guild overview flags it when it applies.
- Open the dashboard. Sign in with Discord and pick a server. You need Manage Server or Administrator there.
- Set up what you need. Nothing is mandatory. Each system below is independent.
Prefixes
The default prefix is ,. Mentioning the bot always works
as well, so @Rogue help gets you in even if someone has
changed it and not said what to.
,prefix | Show the server and personal prefix |
,prefix set <new> | Change it for the server — Administrator |
,prefix remove | Reset the server to , |
,prefix self <new> | Your own prefix, in every server |
A personal prefix works alongside the server's rather than replacing it, so you can keep one you like without affecting anyone else.
The dashboard
Channels, roles, categories and emojis come from the running bot, so the dashboard shows your server as it is now. Settings are saved straight away — there is no separate publish step.
Access is checked against your live permissions, not the ones you had when you signed in: losing Manage Server removes access on the next page load rather than when your session expires.
| Overview | Problems worth acting on, and links to the tools |
| Settings | Prefix, and the bot's nickname and avatar here |
| Modules | Turn whole feature groups off for this server |
| Commands | Disable individual commands, server-wide or per channel |
| Audit log | Who changed what from the dashboard |
| Command usage | Which commands your server actually runs |
Modules and commands
A module is a group of related features. Turning one off disables every command in it for your server only. Core commands — help, info, and the bot's own configuration — cannot be disabled, since switching them off would leave no way to switch anything back on.
Individual commands can be disabled without touching the module:
,command disable <name> | Off across the server |
,command enable <name> | Back on |
,command channel disable <name> #ch | Off in one channel |
,command list | What is currently disabled |
Disabling a group disables its subcommands too, so turning off
role also turns off role add.
Moderation
Every action writes a case with a number, so a member's history is one lookup rather than a scroll through the audit log.
,ban ,kick ,unban | The obvious ones, with a reason |
,timeout ,untimeout | Discord's native timeout |
,mute ,unmute | Role-based, for servers that prefer it |
,jail ,unjail | Restrict to one channel pending a decision |
,warn | Log it without acting |
,purge | Bulk delete, filtered by user, bots, links, images |
,imagemute ,reactionmute | Take away one ability, not all of them |
,shutup | Timed silence that lifts itself |
Run ,setup once to create the mute and jail roles and
pick a log channel, or ,setupmute for the mute role on
its own. ,jailcheck reports whether the jail setup is
still intact.
Protection
Three independent systems, all Administrator-only, all off until you
configure them. Each has a recommended subcommand that
applies sensible thresholds so you are not guessing at numbers.
,antinuke |
Caps how fast mass bans, kicks, channel and role deletions can happen, and punishes whoever crosses the line. Trusted members can be exempted. |
,antiraid |
Watches join rate, account age and missing avatars, and can lock the server down on its own. |
,antispam |
Message rate, invite links and a banned word list, with channels and roles you can whitelist. |
,antinukecheck, ,antiraidcheck and
,verifycheck report whether each system is actually
configured and whether the bot can act — worth running after setup
rather than finding out during a raid.
Tickets
A panel is a message with a button. Pressing it opens a private channel with your support role, and closing it writes a transcript you can search later.
,ticket quicksetup— a working panel from a preset in one step.,ticket panel— post the panel where members will use it.,ticket settings— review what is configured.
The dashboard's Tickets tab does the same with a live preview, and adds application forms — questions asked when the ticket opens, so the first reply is not always the same three questions.
,ticket add ,ticket remove | Pull someone into a ticket, or out |
,ticket close | Close and write the transcript |
,ticket transcriptchannel | Where transcripts are posted |
The archive at Ticket Archive on the guild overview searches every transcript and exports the index as CSV.
Roles
Four ways to hand out roles, depending on how much friction you want.
,reactionrole | React to a message to get a role |
,buttonrole | A button instead — no stray reactions left behind |
,autorole | Given automatically on join |
,color | A colour picker members drive themselves |
,boosterrole gives boosters a personal role they can
name and colour, and optionally share with someone else.
,role handles the bulk work — add or remove a role from
everyone, all humans, all bots, or everyone who already has some
other role.
Welcome messages and logging
Welcome, goodbye and boost messages are built in the dashboard with a
live preview, so you can see the embed before anyone else does.
Placeholders like {member} and {server} are
filled in when it sends; ,variables lists all of them.
,logs setup picks a channel and turns on the common
events. ,logs events shows what can be logged and
,logs toggle changes one at a time — useful when joins
and leaves are worth keeping but message edits are noise.
Aura
Aura is the bot's currency: one balance per person, shared across every server. Members earn it by chatting and spend it on the shop, gifts and boards.
It is on by default. ,aura disable turns it off for your
server, and ,auraignore channel excludes a channel so
bot-command spam does not pay.
Troubleshooting
- A command does nothing at all.
-
Either its module is off, the command is disabled, or you lack the
permission it needs.
,why <command>answers which. - Role commands fail on some members.
- The bot's role is below theirs. Discord blocks that regardless of permissions — move Rogue's role above the ones it manages.
- The bot ignores me entirely.
-
Check the prefix with
@Rogue prefix. A mention always works even when the prefix has changed. - The dashboard says I cannot manage this server.
- It reads your live permissions, so a recent change applies immediately. You need Manage Server or Administrator.
- Music will not connect.
- Playback runs through a separate audio server. If it is unreachable the rest of the bot is unaffected — status shows whether it is up.
- Something else.
- Browse every command, or ask on the support server.