Fixes, 07 Sep 2026

You can try him before you configure him

Post a raid the minute he lands, in the channel you ran the command in. Eighteen commands work on a fresh install: `/raid`, `/lfg`, `/rollcall`, `/away`, `/gbank`, `/roster`, `/whois`, `/gear`, `/notes` and the rest. Before this, every command except five sat behind the setup wizard, so a server that had just added Hootus could not watch him do a single thing. What stays behind the wizard is only what hands out a Discord role. That part he cannot guess at.

A pass over every word Hootus says

Twelve read-throughs of the whole product: the splash pages, the setup wizard, the help guides, every slash command reply, every button, the settings pages and nine hundred changelog entries. Out went a promise that setup takes five minutes when the measured middle is eight, a claim about Battle.net the privacy page had already withdrawn, seven references to a team that is one person, and a Discord events feature that was described in two places and built in none. The guides stopped opening by counting their own sections, and the changelog stopped ending every entry the same way.

Setup errors that tell you what to do about it

Fifteen messages named a problem and then left you there. "Check the highlighted fields" when nothing is ever highlighted. Raw Discord error codes handed to an officer. A dead-end screen with no button on it. The worst was the one telling you to grant a permission or re-invite the bot when your role list would not load, which is a Discord hiccup that no permission fixes. Every one of them names the actual cause and the actual next step. The dead-end screen has three buttons on it.

One wording for the one instruction that matters most

Discord only lets a bot hand out roles below its own, which makes dragging Hootus up your role list the most load-bearing thing anyone is ever told to do here. Seven versions of it had drifted apart, disagreeing on whether to drag him to the top or just above the roles in question, and three left out the reason it matters at all. One wording, in one file, and it always names the cost: anyone who verifies while he is stuck lands on the roster with nothing pinned on them.

Ten minutes, because that is how long it takes

Setup said five minutes in three places and ten in another. Measured against every guild that has actually done it, the middle of the pack is eight and the tail runs a good deal longer. The wizard, the guide and the nudges say ten now. The marketing pages still say five, and that is the next thing to put right.

The feedback buttons stop sending you to a DM that does not exist

Every recoverable error in the raid feedback flow told you to tap Give feedback in the DM. There has never been a feedback DM. It is a post in the raid channel, and it always was, so eleven different messages were sending raiders off to hunt through an empty inbox. They point at the post.

Turning somebody down no longer tells you they were approved

When the roles would not move on a denial, the officer got the copy written for an approval: that the applicant was saved as approved, that the welcome announcement was held back, and that their DM was held with it. All three were false, and the DM had already gone out. Deny has its own note.

Four commands pointed you at the wrong settings tab

Settings, Roles opens on Permissions. The role slots live one tab across, on Assigned roles. So `/demote`, `/raider`, `/raid comms` and `/manage` all sent an officer with a missing role to a page that could not fix it. Each one names the right tab, and `/pug` stopped pointing at Features for a channel that is set under Channels.

Death Knights and Monks get a sign-off like everyone else

The welcome DM ends on a line written for your class. That list was built when there were nine classes, so a Death Knight or a Monk verifying on MoP got a blank where a Warrior gets "Do not let the healers down". Two lines added, and the lookup now tolerates a class the list has not met yet rather than trailing off.

The role tally shows up on the dashboard, not just in Discord

Tank, healer and DPS counts are on by default, and eleven places in the bot read them that way. The guild dashboard read the same setting as off. A guild that had never touched the toggle saw the tally on its raid posts and not on its own page, with the switch reading on the whole time.

He stops using a role just because it has the right name

If a role slot was empty, Hootus went looking for a role called Member, or Raider, or Guest, and used whatever he found. On a server that had configured none of them he would hand those out, and take them back off again, entirely on the strength of a name. A slot is the role you pointed him at or it is nothing now. Every guild set up before this keeps exactly the roles it already had, because he writes down what he was resolving before he stops resolving it.

The wizard stops promising things it does not do

Ticking Raiding said it switched raid signups on. It switched nothing on. The Focus step said it changed your dashboard when what it changes is your public guild page. The Ranks step created a Raid Lead role and quietly threw it away. The welcome screen promised two steps that get skipped on a brand new server. Worst of the lot: the warning shown before you press Finish, the one listing what is about to be overwritten, left out a setting it overwrites. Each of those five says the thing it does.

The Done screen counts verifications, not rows

A first-time setup with one arrival greeted you with "Set up again. Your members stayed exactly where they were." It was counting every member record, including people who had only walked in the door. Verified members only, and the wizard already knew whether this was a first run.