Somebody Has To Be First

He speaks up before setup is finished

Until setup completes Hootus does nothing you can see, so a server that never got round to it takes every new arrival in silence. One has taken a hundred and thirty two of them. When somebody joins an unconfigured server he now posts in the server itself, says what he cannot do yet and who can fix it. Three times at most, a day apart, then he leaves it. He will not post your setup link in a public channel, so the message points at `/setup` instead.

Your roster loads before the wizard says done

Nothing read your WoW roster at Finish. The first read was whenever the next sweep came round, and everyone who verified in that window was filed as a guest with nothing saying so. He reads it the moment setup saves now, and the Done screen waits for the answer: how many characters landed, or the actual reason Blizzard would not give them up. Three failures that used to happen in a log file, no credentials, no guild linked and a guild name the armory does not recognise, are now a sentence on screen while you are still sitting there.

Verify yourself, and watch what he makes of it

Post the verify panel from the Done screen and Hootus waits. Click the button, tell him your character, and he reports back on the same page: verified as a member with the roles on, landed as a guest because the roster has no such name, or sent to an officer. If the roles would not move he says which one and why. The person who can fix a broken server finds out before the first member does.

A week in with nobody verified, he asks what is stuck

Of the servers that have removed him, four out of five had never verified a single member. That is not a mystery worth guessing at. Seven days after setup, if nobody has verified, he sends one message naming what he thinks is in the way: no welcome channel, a roster that will not load, or people owed roles Discord will not let him hand out. He asks twice at most, a week apart, and he leaves a way to tell him the whole thing is not for you.

The welcome channel is always on offer

The picker for it only appeared if you had ticked verification as a goal, so unticking one box two screens earlier silently took away the channel the whole verify flow hangs off. One server finished setup without one, took ten arrivals and produced no members of any kind. The picker is always there, and leaving it empty gets you a plain sentence about what that costs before you move on.

A name claimed in another server says so

Character names are held across every server Hootus is in, so a common name claimed somewhere else blocks it here. He used to say it was claimed by another member and tell the officer to have them run `/character remove`, which nobody in your server can do. He says where the claim really lives and points at Battle.net, which is the only thing that can settle it.

The quiet jobs say what they did

The hourly membership pass logged nothing at all when everyone was already correct, so a healthy run and a run that never happened looked exactly the same. An armory bug sat behind that for a month. It says what it checked and what it changed, every time. And a role slot your server has no role for is reported rather than skipped, unless you have told him you do not use that slot.

The background roster sweep writes down how it went

The new record of the last roster read only got written when something asked for a sync by name: the setup wizard, `/manage`, a re-install. The ten-minute sweep took a different door and wrote nothing, so the guild you most want a record for, the one quietly failing every ten minutes with nobody asking, was the one guild it never covered. The sweep writes it too, and where a guild has more than one game linked, reading either one counts as read.

Approve means approved

An officer pressing Approve on someone the armory could not confirm got them back as Unverified moments later, because Hootus re-derived the decision from the same evidence that had already failed. The officer is the evidence at that point. He also wrote no character row for them, which is what made the next check say verified with no character on file, and then DMd them about guest access they had not been given. The decision stands, the character row gets written, and the DM names which of the three landings it was.

Deny takes the roles back

Turning somebody down marked the record and touched nothing else, so a denied applicant kept every role they were wearing and could keep clicking a live welcome card. Deny now clears the roles the same way every other standing change does, tidies the greeting away, and says so if Discord refused any of it.

He stops reporting roles he never moved

When Discord would not hand him a member, the role pass came back with no error and no roles, which every caller read as a clean success. An officer was told a member had moved, the log said roles restored, and the roster embed listed them as done. Nothing had happened. A refusal is its own outcome on screen, in the log and in the embed, and it says plainly that the record changed and the roles did not.

A class your expansion has not got

If your server is set to one expansion and your roster holds a class from another, a Death Knight against a Burning Crusade setting say, Hootus dropped the row on the floor and told the member he could not find them, then offered a class list their class was not in. He now says he has them, names the class, names the expansion the server is set to, and points at the officer rather than the member.

An expansion he does not recognise no longer takes verify with it

A stored expansion or region he did not know threw an error straight out of the middle of the verify path, past every guard around it. He falls back to a default and writes the oddity down. One warning in a log, rather than a member who cannot verify at all.

A permission check that failed is not a check that passed

If reading your channel permissions fell over entirely, the wizard drew the green card saying he could reach every channel he uses. Total failure and total success looked identical. They do not now, and the same goes for the panels he posts at Finish: anything that did not land is named on the Done screen instead of a log file.