Nothing Pinned On Them

You can tell him you do not use a role

Leaving a role slot blank never meant "we do not have one". It meant "go and find something called Member and use that", so a guild whose structure is Guild Master, Officer and Raider kept being handed a member role it never asked for, and Hootus kept reporting people as owed a role that does not exist in their world. Clearing a slot in Settings, Roles is a decision he respects: he stops looking, stops granting, and stops counting anyone short.

He goes back for the roles he owed you

When Discord refuses Hootus a role, he now writes down who he could not dress. The moment the block clears, whether you moved his role or fixed a permission, he goes back through that list and pins the roles on, then tells your officers whose. Before this, a member who verified during a bad ten minutes stayed roleless until somebody noticed and fixed them one at a time, and nothing anywhere recorded that they were stuck. `/hootus check` counts them for you in the meantime.

/hootus check says the thing that is actually wrong

It used to tell a server with no Blizzard credentials to run `/manage sync`, which could never work. It now names missing credentials for what they are, says out loud that an unlinked WoW guild means every verification lands in `/pending` for you to wave through, and counts the members who are on the roster without the roles he owes them. Bot health has also come out from behind the "Show advanced" toggle in Settings, which did not even render on a phone.

A new guild's roster is read in minutes, not an hour

Roster sync swept once an hour, so a guild that finished setup at five past could wait fifty-five minutes for its first read. Everyone who verified in that window came out as a guest, because there was no roster to match them against, and nothing said so. The sweep runs every ten minutes now; each guild still throttles itself to its own interval, so nobody is asking Blizzard anything extra. An empty answer from Blizzard also stopped counting as a successful sync, which was hiding a misspelled guild name for six hours at a time.

Nine roles for a server that wanted four

Setup made the same nine roles for everyone, whether you had asked for raiding or not, and it matched your existing roles so narrowly that a server with a role called Guild Member got a second one called Member sitting next to it. Setup makes only the roles your answers actually use, so a social server that just wants verification sees five instead of nine, and it recognises the obvious variants: Guild Member, Raiders, Social and Recruit get used where they fit rather than duplicated.

Setup stops at step one until he can reach your roles

The first screen used to show a warning and let you walk straight past it, and on a fresh server it did not even show that, because the check had nothing configured to compare against and read an empty list as healthy. It now names the roles he is sitting under and holds Continue until you have moved him. It also re-checks by itself when you come back from Discord, so dragging his role to the top clears it without pressing anything. And the checklist no longer says "permissions look good" directly underneath a warning that he cannot hand out a single role.

Every role is now a choice, not a button

The roles step used to have one button that made whatever it thought was missing, and an auto-match that quietly picked roles for you without showing its working. Each status is one row now: pick a role you already have, or have Hootus make that one. Whatever he matched is sitting there in the row where you can change it. The build-my-server path gets the same list, so answering "brand new" at the first question no longer means you cannot map anything. The legacy Friend slot only shows up on servers that already set it.

The first message tells you the first job

The instruction that prevents all of this, drag the HootusPlootus role to the top, used to be given on the page before you had authorised him, when the role did not exist yet. It is now in the message he sends the moment he lands, naming the exact roles he is sitting under, and the FAQ finally has the question a stuck owner would actually type: my members verified but got no roles.

Opting out of raiding sticks

`/raider` took the role off you and left the note saying you wanted it, so the next time anything repaired your roles you were quietly opted back in. It writes both. A gap between the two is a real failure rather than an old answer.

A raider with no raider role is not silently dropped

Whether you are a raider is read off the Discord role, not the answer you gave at verify, so a failed grant quietly took you off raid reminders, roll call, the feedback ask and the analytics with nothing anywhere saying why. It happened to a guild master, who is exactly the person you least want missing from a raid ping. `/hootus check` now counts anyone in that state and tells you how to put it right.

The check for this had never once fired

Hootus has always known he can only hand out roles that sit below his own, and has always had a check that says so. It compared role names letter for letter. Your Raider role is called ↦ Raider, your Mage role is called Mage with an emoji in front, and none of them matched, so the check looked at a broken server and reported it healthy. He now resolves the roles exactly the way he resolves them when he is handing them out: by id first, then by name with the decoration ignored, then by the default name he falls back to. A role id that no longer exists falls back to the name instead of quietly matching nothing.

Setup will not finish pointing at a role he cannot reach

The wizard used to auto-match your existing roles by name, tick "Roles created", and send you on your way without ever asking whether Hootus could actually hand any of them out. The role picker now marks every role that sits above him, will not silently pick one, and Continue stays shut until it is sorted. The done screen checks again once the roles are actually saved, because that is the first moment the check has anything real to look at. Saving a role from Settings later gets the same refusal.

Not a failure if he was never touching that role

Hootus reported every managed role he could not reach, whether or not your verification involved it. A guest verifying on a server with a high Raider role got told their verification half-failed, and had their welcome announcement and their DM held back, over a role that was never going in the plan. Only a role he was about to add or remove counts as blocked.

A new arrival failing stops vanishing into a log

The Unverified and Applicant roles that go on the moment someone joins failed into a log line nobody reads, so a locked-down welcome channel could quietly let strangers straight past the gate with no sign anything had gone wrong. Those now reach your officers like every other role failure. And a welcome channel Hootus cannot post in used to throw right out of the join handler instead of falling back to a DM, which meant the new member got nothing at all and you never heard about it.

He tells your officers which role is in the way

Hootus knew exactly which role he could not reach and then told your officers "Discord turned me down without saying why", because the message he writes for himself did not match any of the phrases he checks for. The report names the role and the fix, so an officer reads "↦ Raider sits above me in the role list" rather than a shrug.