qBot is the bot in the MCME Discord server. It runs on Red-DiscordBot ("Red"), an open-source Discord bot. Red's features come in modules called cogs: some are built into Red (moderation, warnings, cleanup), others were written for MCME (the suggestion and bug boards, account linking, Patreon roles). This page is for staff and moderators: how to give qBot a command, which commands you will use day to day, and which role each one needs. Players only need the first two sections.

How to give qBot a command

qBot only answers when you mention it. The old ! prefix no longer works, and qBot has no slash commands yet.

1. Type @qb and pick qBot from Discord's suggestion list (Tab or Enter). It turns into a blue tag. Typing @qBot as plain text does nothing.
2. Type the command after it and send: @qBot help.

The mention must be the first thing in your message. Every example on this page is written as @qBot <command>. Words in <angle brackets> are required, words in [square brackets] are optional; leave the brackets out when you type. For the details of any command, send @qBot help <command>.

Why: Discord only lets a bot read the text of messages that mention it, unless Discord grants it a special permission (the Message Content intent). qBot does not have that permission. Buttons, drop-down menus and pop-up forms on qBot's posts work as normal.

Mentioning a member or a role in a command pings them. To avoid that, type their user ID or role ID instead (right-click, Copy ID; turn on Developer Mode in Discord's Advanced settings first). Commands that take a role also accept the role's name.

Commands for everyone

Suggestions and bug reports work with buttons, not commands:

• Suggest something: click Submit a Suggestion on the suggestion panel and fill in a title and description. Everyone can vote with the thumbs-up and thumbs-down buttons on a suggestion; click again to take your vote back. The author gets a DM each time the suggestion changes status.
• Report a bug: click Report a Bug on the bug panel, pick a category and fill in the form.
• A member can send one suggestion and one bug report per minute, and have at most 5 of each waiting for review. Staff are exempt.
• The dashboard panels next to them have private buttons: My Suggestions and Search for suggestions; My Tasks, My Reports and Search Bugs for bugs.

Who can use what

Each staff table below has a Role column:

The server owner chooses which Discord roles are qBot's Mod and Admin roles, with @qBot set roles addmodrole @Role and @qBot set roles addadminrole @Role. The server owner passes every check. If a command or button refuses you and you think it should not, ask an admin.

As of November 2026 no Mod or Admin role is set, so a command marked Mod or Admin works only through the Discord permission in its row, or for the server owner. Making a role qBot's Mod role opens every Mod command to it. To open a single command to a role instead, the bot owner loads Red's Permissions cog once with @qBot load permissions, and the server owner or an Administrator adds a rule, for example @qBot permissions addserverrule allow whois @Staff.

Moderation

Example: @qBot ban 123456789012345678 1 Repeated griefing.

Warnings

A warning is worth points (1 unless you say otherwise). Admins can set automatic actions, such as a kick, when a member's points reach a total.

If qBot answers that custom reasons are not allowed, use one of the reasons from @qBot reasonlist.

Modlog cases

When an admin has set up a modlog channel, every kick, ban and warning becomes a numbered case there.

Cleanup

All cleanup commands need Mod or Manage Messages, and qBot needs Manage Messages in that channel. They work in the channel where you type them.

• Pinned messages are kept. Add true at the end to delete them too: @qBot cleanup messages 20 true.
• Discord does not let bots bulk-delete messages older than 14 days.
• cleanup text and cleanup duplicates compare message text, which qBot cannot read. Don't use them.

Keep cleanup messages, cleanup user and cleanup bot at 100 or fewer. Above 100, qBot asks you to type yes or no, but it cannot read your reply, so it cancels. Run the command again for the next batch.

Custom commands

A custom command is a short reply that anyone can call up, for example a link to the rules.

cc is a short form of customcom, so @qBot cc list works too. A reply can be at most 2,000 characters.

Suggestion board

A suggestion moves through channels: pending, then approved, then implementation underway, then implemented. Staff can also deny it. Each suggestion gets a discussion thread when it is submitted, and the author gets a DM at every status change.

Buttons on each suggestion (Role: Board staff):

Overview commands (Role: Admin or Manage Server; the board staff role alone is not enough):

Bug-report board

A bug report is open until someone claims it or is assigned, then in progress, then resolved or closed. Each report gets a discussion thread.

Buttons on each report:

Overview commands (Role: Admin or Manage Server):

Role audit

Find out when a member got or lost a role, and who made the change. Role: Board staff (the audit staff role) or Manage Server.

Example: @qBot audit role Builder. Discord keeps its audit log for about 45 days. For roles that admins put on qBot's watch list, qBot keeps its own copy for longer (180 days by default). Results come in pages; the Previous and Next buttons only work for the person who asked.

Escalation alerts

Discord lets someone with Manage Roles hand out every role below their highest role, so even a role with no permissions can extend what they can reach. qBot watches for this on its own; there is nothing to set up. A powerful role is one with Administrator, Manage Server or Manage Roles. Bot-managed roles don't count, because nobody can assign them.

qBot sends an alert titled Possible Permission Escalation when:

• A role is assigned that lets a member hand out a powerful role they couldn't before. The alert names the member, who gave the role and what they can now hand out.
• The role list changes with the same effect: a role is dragged, gains or loses a permission, or is created. Server Settings → Audit Log shows who made the change.

Alerts go to the bot owners by DM and to a private log channel.

If the change was meant to happen, such as a real promotion, there is nothing to do. If not, remove the role or move it lower in Server Settings → Roles. qBot only reports and never undoes a change itself.

To see who can hand out what right now, use @qBot auditset escalation (Admin or Manage Server). Alerts only fire on changes, so this is how you see what has always been that way. Each group in the report can hand out the role named and every powerful role below it. Nobody can hand out their own highest role, so someone whose highest role is Valar / Admins appears in the group below it.

How the watch works in detail is on the staff-only MCME Redbot page.

Account links

These commands work in the main MCME Discord server (qBot's home server for account links).

forcelink refuses when the member is already linked, or when the Minecraft account is linked to someone else: unlink first. Don't add or remove the Verified Ingame role by hand: qBot puts it back the way the links say and logs a warning.

Who has linked?

qBot's link records are what count, not the Verified Ingame role. Perks reads those records to give supporters their perks, and whois and linkset list read them too. To check one member, use @qBot whois @member or @qBot whois <Minecraft name>; to see everyone, use @qBot linkset list.

The role is a badge that shows a member has linked. It can be wrong for a while: someone can add it by hand until qBot takes it off again.

With no Mod role set (see Who can use what), only members with Manage Server can run whois. It shows which Discord account owns which Minecraft account, so open it to another role only if you trust that role with that.

The Verified Ingame role

• qBot finds the role by its ID, so renaming it or changing its colour breaks nothing. Don't delete it and create a new one: the new role has a new ID, an admin has to set it again with @qBot linkset role @Role, and members who linked earlier don't get it.
• Keep it below Staff in Server Settings → Roles. It has no permissions, but Discord lets Manage Roles (and kick, ban, timeout and nickname changes) reach only below a member's highest role. Placed above Staff, it becomes the highest role of every Staff member who links, and they can then hand out every role in between. The same rule goes for the Patreon tier roles.
• qBot enforces this for the roles it hands out. @qBot linkset role refuses a role ranked above any role with Administrator, Manage Roles, Kick, Ban or Timeout Members, or Manage Nicknames (bot roles don't count), even for the server owner. If the role is moved too high later, qBot stops giving it out or putting it back. Linking and perks keep working, because they come from the link and not the role. Members who already hold the role stay lifted until it is moved, so qBot posts Verified Role Too High in the account link log channel and DMs the bot owners, naming who it lifts right now, then Verified Role Position Fixed once it is back down. @qBot linkset checkperms shows the check. The same move also sets off an escalation alert.
• The Patreon sync won't give out a tier role ranked above those roles either. It lists the role as an error in every sync report until it is moved, and members whose subscription lapsed still lose it.
• A member's name takes the colour of their highest coloured role, so with the badge placed low, roles such as Supporter keep their colour.

Patreon checks

qBot gives Patreon members their Discord roles on its own, on a schedule (hourly by default), and removes them when a membership ends. These commands work in the main MCME Discord server. Role: Admin or Manage Server.

Admins set up the boards, their channels and staff roles, the link and Patreon settings, and the modlog channel. The word filter is switched off, because it needs to read message text.