Nobody Told Them

Your dashboard now says what is broken, and where to fix it

One guild re-ran the wizard, picked a game version their realm does not exist on, and every roster read came back empty for seven days before anyone noticed. Two more had six role slots each pointing at roles they had deleted, so verifying handed out nothing. All three dashboards were saying nothing needs attention. Hootus now keeps one list of everything that can leave a server broken, checks it against Discord and the armory on every page load, and puts each one on the dashboard with what it costs you and a link straight to the page that fixes it. When nothing is wrong the list is not there at all.

You choose whether raid feedback carries a name

Each questionnaire is now anonymous, named, or left to the person answering, which is how it has always worked. Named suits an officer check-in where you want to follow something up. Anonymous suits the honest question about last night. Whoever is answering is told which one they are in before they write a word, and changing the setting only ever affects raids you ask about from now on. Anything already given anonymously stays that way, because no name was ever written down to reveal.

Your own messages can name a channel, a role or the raid

One guild wanted to point new members at a channel, found nothing to reach for, and sent the word placeholder to every person they approved. Every custom message now has a row of chips under it for the things it is allowed to mention, and dropdowns of your real channels and roles. What gets stored is the channel, not its name, so renaming it later changes nothing.

Hootus can be asked to pass on a message

Until now he could only say the four things he was built to say. There is a composer behind the console: pick one of five situations he already recognises and it fills itself in with that server’s own guild, realm and dates, or write your own. What lands is shown before it sends, and a message written by hand says so rather than passing itself off as an automatic notice.

A failing roster sync can be looked into instead of stared at

It said Blizzard refused the sync and left it there, which is the most common real fault across every server and the one with the least to go on. It now shows exactly what was asked for, guild name, realm, region and game, with the address the bot actually calls, so a name spelled differently on the armory is visible by eye. And a button that tries again and says what came back.

One notice for everything, and it never repeats itself

Permissions and roles used to post separately, and only those two things ever spoke up at all. Now anything that actually stops the product working goes into one message that is edited in place as things change and rewritten to say so when they clear. Everything else waits on the dashboard rather than pinging an officer. Nothing that only the person hosting the bot can fix is ever sent to a guild.

/hootus check has moved to where you were already looking

It was the only place any of this was visible, which is why nobody found it. The server half is the dashboard now. The half that reads one person, what Hootus makes of them and why, and the Fix roles button, is `/manage member check`, next to the rest of the member tools.

A realm that does not match the game version is now spotted, and only spotted

One guild set up on TBC Classic, synced fine, then re-ran the wizard four hours later and picked Classic Era. Spineshatter is not a Classic Era realm, so every read since has come back empty, and nothing said so for a week. Hootus now notices that shape and says what he sees. He does not touch it: Blizzard’s realm lists and its guild lookup do not always agree, so this is a question, not a verdict.

The audit trail reads like sentences instead of database rows

One person wiring up their channels came out as fourteen consecutive lines of raw ids, and a minute of editing tags came out as eight rows, two of which recorded that nothing changed. Edits made together are now one line saying who did what and how much of it, with the before and after a click away, and a change where nothing moved is counted rather than printed.

Posting a raid into a channel Hootus cannot see

He checked that he was allowed to send messages and never checked that he could see the place he was sending them, which are two different permissions. So his own check passed, Discord refused, and the error told the raid leader to try again. One server tried six times in an hour. Both are checked now, in the one place all three paths ask.

A realm that is not on your game version is named as the reason

Blizzard keeps a separate realm list per game version, and Spineshatter is on the TBC one, not the Classic Era one. Pick the wrong pair and every roster call returns nothing while the failure reads as a spelling mistake. Hootus now checks the realm against the right list and says which game it actually belongs to, instead of blaming your typing.

Deleting a channel Hootus posts to no longer goes unnoticed

Point a duty at a channel, delete the channel, and everything Hootus sent there quietly went nowhere. Attendance reports, the audit log, applications. He now spots a wiring that points at a channel that is gone and says which duty it was.

Deleting a role Hootus was told to use no longer looks like a bug in Hootus

Two servers rebuilt their roles and left the old ones mapped. Hootus then told them he had no Guest role on file, which sent them to a settings page where a Guest role was plainly mapped, and they were right to think something was broken. He now tells the difference between a slot nobody filled in and a role that has since been deleted, checks every half hour rather than waiting for someone to fail a verification, and refreshes from Discord before saying it so a hiccup never gets called a deletion.

Rules text can no longer grow past what Discord will send

Raid rules go out inside a message Discord caps at 2000 characters, and nothing stopped you saving more than that. One more paragraph on the longest set in use and every raider reaching that step would have hit a dead button. The editor now counts down against the real limit, allowing for the words Hootus wraps around it, and says no before you save rather than cutting you off mid-sentence.

Underline survives being saved, and a soft return stops leaving a slash

The editor had an underline button that quietly threw the underline away on save, and a shift-return wrote a stray backslash into the message Discord showed your members. Both were the editor speaking a slightly different markdown to the one Discord reads.

Writing {raid} in your own reminder now fills in the raid

Substitution ran on the line Hootus would have sent and never on the one you wrote instead, so a guild who used the documented placeholder in a custom reminder had the braces posted to their raiders verbatim. Both lines go through the same path now.

An officer keeping one of their own people is no longer reported as a fault

When somebody leaves the guild in game, Hootus asks whether to keep them. An officer answering yes was then filed as unexplained drift, aged in days, with a fix suggested to somebody who does not run that guild. A decision is not drift. Those are counted as settled now, and what is left is only the cases nobody chose.

The audit trail stopped reporting that somebody read it

It kept a row every time the console, the audit trail, the support inbox or the drift report was opened, which on a console only one person can reach is a log of itself. It stopped writing them this morning, and the ones already on file are now hidden from the feed and its counts rather than deleted.