Skip to content

Setup Assistant

The Setup Assistant builds your Server out and checks it for problems, one confirmed step at a time. It has two halves:

  • Build (/setup start) proposes a starter layout of roles, channels and settings, and applies each part only when you press Yes.
  • Review (/setup review) checks the permissions and settings you already have and offers a fix or a how-to for each problem it finds.

Code finds the problems, checks every name and makes every change. The assistant's AI voice, the Quartermaster, only explains and suggests: anything it proposes still comes to you as an ordinary step to approve. The assistant's messages are only visible to you.

Who can run it

Command Who
/setup start The Server owner, or a Member with the bot's admin permission
/setup review The Server owner, Manage Server, or the bot's admin permission

Each Yes checks again, right then, that both you and the bot hold the Discord permissions that step needs (for example Manage Roles to create roles, Manage Channels to create channels, Manage Server to change a Server setting). You can't use the bot to make something you couldn't make yourself.

Build: /setup start

1. Fresh or Existing

The bot looks at your Server and guesses: a Fresh Server has at most 10 channels and no roles beyond what one of Discord's own server templates made; anything else is an Existing Server. You confirm the guess or switch it.

  • A Fresh Server made from a Discord template (for example Friends & Family or Study Groups) is offered tidier names for the template's defaults, such as Text Channels → Chat. Keeping #general is fine.
  • An Existing Server is never renamed. It only gets the pieces it is missing.

2. Tell the assistant (optional)

If AI is available, you can describe your Server and the Quartermaster tailors the layout: extra channels in its categories, extra roles with a named permission set, or new names for its pieces (say, Member → Trooper). It shows what it changed in plain words, and you can tell it more up to five times per Build. Then press Build it.

Don't include personal info when you describe your Server: no member names, contacts or anything private. See What the AI sees.

If the AI is switched off, out of requests for the day or doesn't answer, nothing breaks: you get the standard layout.

3. Proposals

The bot then posts one Proposal at a time:

  • Yes applies it now.
  • No, let me rename opens a box with one name per line, so you can pick your own names first. Invalid names (empty, too long, @everyone, invisible characters, things that would ping) are refused with the line number.
  • Cancel skips it.

Each Yes is safe to repeat: anything that already exists is left as it is, so running /setup start again picks up where you left off. The bot never deletes anything.

4. Wiring

Once the channels exist, the assistant offers to:

  • Send the mod log to #mod-log.
  • Switch welcome messages on in #welcome (edit the message on the Dashboard).
  • On a Fresh Server, move Discord's join messages from #general to #welcome.

5. Finish

The last step picks your Server's type (its Profile) and which features to switch on, or keeps what you have. You can change the Profile later on the Economy dashboard page. The closing message points you to role menus for #react-roles and to the Dashboard for everything else.

The starting layout

Part What you get
Roles Admin, Moderator, Member
Info #rules (read-only), #announcements (read-only), #welcome, #react-roles (read-only)
Chat #general
Voice 🔊 Lounge
Staff #mod-chat, #mod-log (staff only)

Roles only ever get one of three named permission sets, never Administrator:

  • Member: everyday chatting, reactions, threads and voice.
  • Moderator: Member, plus managing messages, threads and nicknames, kick, ban, timeout, the audit log and moving people in voice.
  • Admin: Moderator, plus Manage Server, Manage Roles, Manage Channels, events and Mention @everyone.

Read-only and staff-only channels get permission overwrites for @everyone, your staff roles and the bot.

Review: /setup review

The Review runs a fixed list of checks, so the same Server always gives the same results.

Major Findings (free)

  • @everyone holds a dangerous permission (Administrator, Manage Server, Manage Roles, Manage Channels, Ban, Kick, Mention @everyone, Manage Messages).
  • A channel lets @everyone manage it or its permissions.
  • A role menu or auto-role hands out a role with a dangerous permission.
  • The bot's role is too low to hand out a role your menus or auto-roles give.
  • The bot has Administrator. Servers that added the bot early granted it; the Review names the role that does. If it is the bot's own role, re-invite the bot with the scoped link and Discord swaps Administrator for the permissions the bot uses. If it is a role you gave the bot, untick Administrator on that role instead. There is no automatic Fix. Once the bot loses Administrator, channel permission overwrites bind it, so a private channel that locks out everyone may lock out the bot too; the Review counts channels it can't see.
  • No verification level.
  • The explicit content filter is off.
  • No mod log channel.

Nitpicks (Premium)

Premium Servers also get smaller hygiene checks:

  • Join messages land in #general.
  • New members get a notification for every message by default.
  • Roles nobody has (roles a role menu or auto-role offers don't count).
  • Two roles with the same name.
  • Roles anyone can mention.
  • Channels outside any category, and empty categories.
  • Invites that never expire (your vanity URL aside).
  • 2FA isn't required for moderator actions (only the Server owner can change this).

Fix and Undo

Where the bot can fix a Finding safely, it has a Fix button. Fix shows exactly what will change and waits for Yes; afterwards an Undo button puts things back the way they were. Findings without a safe automatic fix say how to fix them yourself.

Press Re-scan to confirm your fixes. Each Server gets one Review plus one re-scan every 24 hours.

Channels the bot can't view aren't checked; the Review tells you how many it skipped instead of calling your Server clean. The same goes for invites when the bot lacks Manage Server.

The Quartermaster's take

If AI is available, the first Review is followed by the Quartermaster's explanation of the Findings in plain words, and a few Gaps: missing pieces worth adding, such as a rules channel. Gaps are advice, not Findings.

Role menus: /setup rolemenu

Posts a role-button menu: pick the channel, set the title, description and mode, then list existing roles one per line. To edit menus later, use /rolemenu edit (see Roles) or the Roles dashboard page.

What the AI sees

The Setup Assistant sends placeholder tokens for your channel and role names to Google Gemini, never the names themselves, member data or messages.

In practice, Gemini gets the starting layout above, whether your Server already has each piece, counts of your roles and channels, your Server's type (its Profile) and the names of any Findings. What you type into Tell the assistant is sent too, with any of your channel, role or category names (and your Server's name) swapped for tokens like <role:3> first; the bot swaps them back before showing you the answer. The bot never logs or stores what it sends Gemini or what comes back. See the Privacy Policy.

Everything is recorded

Every change the Setup Assistant makes is written to the Activity Log (setup.apply and setup.fix) and posted as a line in your mod log, naming who ran it.

Retired commands

The old click-through wizards (/setup server, /setup channels, /setup roles and /setup profile) are gone. /setup start builds the Server, and the Profile is set by the Setup Assistant or on the Economy dashboard page.