Not Everyone Is In Your Guild

Hootus writes down how big your server is

He only ever knew the day he arrived, so a server that had doubled since still read at its install-day size. The six hourly snapshot now records the count alongside everything else it keeps, which turns one frozen number into a line you can follow.

A server that needs a look can now be dealt with

The list of servers in trouble was a list. You could read it and that was all, so it only ever grew. Each one can now be snoozed for a week, a month or for good, nudged with the specific thing that is wrong on it, or left. Leaving asks you to type the server id first, and Hootus keeps quiet about it afterwards rather than asking the owner what went wrong.

He asks what kind of Discord this is now

Setup opens with one question: is this your guild’s Discord, or a place where people from lots of guilds gather. Answer community and he stops asking for a WoW guild, stops syncing a roster nobody has, stops gating a welcome channel and stops chasing anyone to verify. A character on file is the whole requirement, and the armory still says whether it is real.

Signing up for an open raid no longer sends you to a website

A raid open to anyone used to hand every stranger a link and hope. One server posted six public Molten Core nights and took nothing, because everybody who pressed a button was pointed at a browser. You can now put a character on file without leaving Discord, by name or by connecting Battle.net, and you land straight back on the raid you clicked.

One thing every few days, only if you ask for it

He can show you the parts nobody finds on their own. Battle.net, soft reserves, attendance off who was in voice, roll call, LFG, away. One every three days, six at most, and he never mentions something you already use. Nothing starts on a timer, somebody has to offer it to you first. Not now pushes it back, stop ends it, and he ends it himself when he runs out.

He tells you when everyone who verifies comes out a guest

A recruiting server had five people verify cleanly, then ten in a row land as guests because the armory had their character in another guild. Nobody was told. That is not a rejection and on a recruiting server it is the normal case, so he now says it out loud once it starts repeating, and points at the member list where you promote them.

The super admin page tells you something now

It was four links and a list of server names. It now opens with how many servers installed, finished setup, reached one verified member and ran one thing, then ranks the servers that need a look with the reason spelled out rather than a score. Roster refused, wizard abandoned at a named step, a hundred and thirty two arrivals and nobody verified.

The operator console reads like the rest of the product

Five pages that shared a URL and nothing else. Half the servers on it showed as an unnamed row of digits, when their names had been on file since the day they installed. The servers that need a look now sit at the top with the reason written out, the twenty-row ledger folded away underneath, and every sub-page has a way back.

The Admin menu held one link and has gone

The activity log was the only page in the whole product with an admin audience, so it grew a top-level menu of its own, next to Officer, wearing the same shield. It sits under Officer now. Who can open it has not changed.

The check-in knows what kind of server it is talking to

It asked every server the same three questions, which on a community server means asking about a welcome channel nobody wants and a roster that does not exist. It now asks what applies: has a raid gone up, and can anyone actually sign up for it.

Clicking sign up when you are not on the roster now does something

It used to say the buttons are for guild members, tell you to run a command, and send you off to find a raid leader. That is a dead end at the exact moment somebody is trying to join your raid. It now offers to verify you on the spot, or to connect Battle.net once and pull every character on your account, alts included.

The check-in arrives on day one, not day seven

It waited a week and only spoke to servers that had verified nobody, so a guild where things half-worked heard nothing at all. It now lands a day after setup, comes back twice more, and reaches a working server the moment something is genuinely in the way.

/hootus check ends with what to do next

It listed roster age, permissions and who arrived, and left you to work out which of it mattered. There is a What to do next line now, carrying the same blockers the check-in DM would send, or the next real move when nothing is in the way.

A check-in about a typo no longer ends by asking if you want out

The closing line offering to hear that Hootus was not what you wanted was written for a server that had verified nobody in a week. It was going out attached to things you could fix in a minute, like a realm spelled differently on the armory. It now only appears when nothing is actually broken.

A member an officer chose to keep no longer looks like a fault

Somebody left a guild in game, the bot asked whether to keep them, an officer said yes, and the drift report then spent eleven days presenting that decision as unexplained. It reads the override now, says who made the call and what it costs, and offers the one thing that can be done about it.

Charts answer a tap on a phone now

Tapping a bar opened the tooltip, tapping another moved it, and tapping away left it hanging there until you reloaded. The chart library only listens for a finger that moves, so a still tap fell through to whatever the browser felt like doing. A tap is now treated as what it obviously is, and a tap somewhere else puts it away.

Dates stopped disagreeing with themselves

A raid on the guild page rendered as Thu 10 Sept from the server and Thu 10 Sep in your browser, which made React throw the whole tree away and draw it again. The two are on different versions of the same month-name data. Nothing now asks the system for a month or a weekday name. Two quieter bugs went with it, one of them routing raid channels off that same name.