How to set up a guild Discord bot. Five minutes, no YAML.
Invite Hootus, walk a short wizard, push the raid button. This is the whole path from a fresh server to your first signup, including the exact permissions and why each one is asked for.
Four steps from invite to first signup.
Each one is a button or a short form. No editing files, no restarting anything.
- 01
Add the bot
One click. Discord's OAuth screen does the rest. You pick the server, confirm the permissions, and Hootus lands on a branch in your guild. No token to paste, no app to register, no host to rent. The bot runs on our side.
- No bot token, no developer portal, no .env file of your own
- Nothing to host. The bot is already running, you just invite it
- The permissions screen shows exactly what it asks for, listed below
- 02
Walk the wizard
The bot DMs your leadership a link to a setup wizard the moment it joins. Pick your flavour, point Hootus at your channels, map your ranks. Five minutes start to finish, and every choice has a sane default if you would rather skip ahead.
- Pick TBC Classic Anniversary or Mists of Pandaria Classic
- Point the bot at your welcome, raid, officer, and log channels
- Map your existing Discord ranks to officer, raid lead, and member tiers
- Set your WoW guild and realm so the roster sync knows where to look
- 03
Let members verify
New joiners hit a welcome message with two buttons: member or just passing through. Members verify a character, the bot checks it against the synced roster, and assigns the right class and rank roles. PUGs get a guest role and access to the pug channels, nothing more.
- Members verify a real WoW character, not a self-typed name
- The bot matches against the roster it pulls from Blizzard
- A race-check step catches the obvious impersonator
- Class and rank roles get assigned, no manual role clicking
- 04
Push the raid button
Run the raid command, pick the instance, and the signup post lands in your raid channel. Tank, healer, and DPS buttons that check class against role. The roster syncs from Blizzard every hour, so signups know who is actually 70 and who respecced last night.
- Class- and spec-aware signups, validated on every click
- Slots auto-lock 30 minutes before pull, bench gets pinged
- Open the web planner to drag the lineup, or run it all from Discord
- Nobody types 'who's tank tonight' for the rest of the tier
Seven permissions. Here's what each one is for.
The OAuth screen asks for exactly this list and nothing else. No Administrator, no scary scopes.
So Hootus can see the channels you point him at: the welcome channel, the raid channel, the officer log. He cannot post where he cannot see.
To post the welcome embed, the raid signup, the lineup, and the reminders. The whole job is talking in the right channel at the right time.
Raid posts, rosters, and gear checks are rich embeds with class emoji and links, not walls of plain text. This is what makes them readable.
To spin up a voice channel and a discussion thread when a raid starts, and clean them up when it ends. No leftover voice rooms next Tuesday.
To assign class and rank roles when a member verifies, hand a PUG the guest role, and take it back when they drift off. Hootus only ever touches roles below his own.
So he can find and update his own earlier posts, like editing a raid embed live as signups change instead of spamming a new one.
To mint a raid-scoped invite when a PUG signs up through a public link, so guests land in the right place and the invite expires with the raid.
No Administrator permission. No reading channels he was not pointed at. No reaching above his own role in the hierarchy. If the bot ever needs something it does not have, it tells your officers plainly instead of failing quietly.
Verified against Blizzard. Not a name they typed.
The part that decides who actually gets into your raid roster.
When someone joins, Hootus posts a welcome with two buttons. Pick member and the bot walks them through verifying a WoW character, then checks it against the roster it pulled from Blizzard. A match assigns the right class and rank roles automatically. A race-check step asks them to confirm their character's race, which trips up the obvious impersonator.
Pick just passing through and they get the guest role and the pug channels, nothing else. No stranger lands in your officer chat by accident. You choose how strict verification runs, from roster-only to armory-confirmed to officer-trust, in the settings.
- Member clicks the welcome button
- Verifies a real character
- Bot matches it against the synced roster
- Class and rank roles assigned, done
No. That's the whole point.
If you have ever fought a generic bot's config file, this is the reassurance you came for.
No YAML, no config repo
There is no file to fork, no config to commit, no schema to learn. Every setting lives behind a button in the wizard or the web settings page.
No hosting tutorial
You are not running a bot. There is no VPS, no Docker compose, no token to keep secret. Hootus runs on our side and shows up when invited.
No admin, no scary scopes
The permission list above is the whole list. No Administrator checkbox, no access to messages he was not asked to read, no spooky OAuth scope.
Invite to first signup.
Add Hootus to your Discord, walk the wizard, push the raid button. Roster from Blizzard, signups that know your class, the lineup posted by raid night.