03 Sep 2026 to 05 Sep 2026 · v1.122.1 to v1.123.2
Fixes, 03 Sep 2026 to 05 Sep 2026
2 New
Four guides for the parts nobody had written down
Roll calls and recurring raids, the guild bank, the links that get somebody into your Discord, and what every number on the analytics screens actually counts. Eight subcommands had no explanation anywhere, and the guild bank is a whole feature members could use without a word written about it. Every figure there carries what it counts, where the number comes from, and what it leaves out. An officer benching a raider over a statistic can see what the statistic missed.
The things Hootus does without being asked are written down now
An hourly pass can take your Member role off overnight and nothing told you that. Your welcome post expires and Hootus DMs you about it. The bot nudges whoever installed him if setup is unfinished. Twenty-four of these ran quietly with no explanation anywhere, so somebody who lost a role had nothing to read. The verification guide leads on the symptom, "your Member role disappeared", and says what to check yourself before bothering an officer.
3 Improved
A quieter codebase behind the same behaviour
Sixty-nine dead-code findings down to five, sixty-seven duplicated blocks down to six. The raid web routes went from twenty-nine near-identical openings to none, all behind one resolver that will not let a route forget which permission it needs. Every test that passed before still passes, and nothing you can see has moved.
Getting accepted no longer sends you to a website first
Being told yes used to mean opening a link, signing into a second site with Discord, and clicking a button that granted nothing, only to be handed the server invite and told to run `/verify`. Both of those were already in the same message. Now if you are in the server you get one instruction, and if you are not you get the invite and then `/verify`. For anyone Hootus cannot DM at all, because Discord will not let a bot message a stranger, the application page carries the same thing.
The site stopped introducing him as a Classic-only bot
He picked up TBC, then MoP, then retail, and a dozen pages never got the memo and kept calling him a WoW Classic guild bot. They name all four.
20 Fixed
A guest can no longer read your whole roster
The check that was supposed to ask "is this person a member" asked nothing at all, so anyone signed in to your server could pull the full member list off the dashboard, including a guest the website itself sends to a no-access page. Member now means member. Guests keep everything that is theirs: their own characters, their own alts, their own spec, and verifying a character still works exactly as before, because that is the whole point of being a guest.
Everything agrees on when a raid ends now
A raid with no duration typed in held voice open for five hours, stopped showing as live after three, and put a four hour block in the calendar feed. Three numbers for one raid, and none of them was what actually happened. Five hours from the start, everywhere, exactly as promised. The estimate stays a label: it still shapes your calendar entry, because that is a diary block and nothing happens at the end of it, but it has never closed a raid and it still does not.
Nobody is a no-show for a raid nobody recorded
When a raid locks, Hootus writes down who was on the bench. That is a copy of the sign-up list, not a note about who turned up, but it was enough to make him treat the raid as recorded, and then everyone else on the roster looked like a no-show. One bench line could turn a whole night into a wall of absences an officer might act on. It is not evidence any more. Real attendance, from voice or from a log, still counts exactly as it did.
Hyphenated realms match again
Two halves of Hootus wrote realm names differently, one as nethergardekeep and the other as nethergarde-keep, so on a connected realm they could never agree they were talking about the same character. On Mirage Raceway that is most people. Loot reads the winner Hootus recorded at the time rather than guessing again from the name. That finishes the namesake fix from two days ago, which could work out the owner but still fell back to a name he could not match.
A recurring raid that stops posting now says why
Recurring raids ask their creator to approve each run, and nothing goes up without that. If the creator had DMs closed, the ask went nowhere and said nothing, so the series simply stopped and nobody knew why. Now your officers get told, once, naming the raid, the series and the person who needs to open their DMs.
The planner keeps your clock, and the share image keeps your timezone
A guild set to countdowns got them everywhere except the planner, which quietly showed server time instead. And the image posted to Discord rendered in Berlin time whatever your server was set to. Both read your guild timezone.
Four things Hootus said that were not true
The feedback settings said the ask is DMd to raiders; it is posted in the raid channel with a Raider ping. The PUG settings said the rules become a pinned message; it is posted once and edited in place. The revert prompt said it would ask again next hour when it waits a day. And an invite page mentioned a role for invites that never carried one. Verifying with the /verify command also clears your welcome post, so nobody gets a reminder a day later about something they already did.
Removing a game link no longer strips a role Hootus did not create
If your Raider role existed before Hootus arrived and he adopted it, taking a game link off could pull that role off everyone holding it. He now checks every role your server has told him about, thirteen slots including the raid ping roles, and leaves those alone. If he cannot read your settings at that moment he removes nothing at all.
Granting a role to someone new leaves a trace now
Giving Raider to a guest, a pug, or anyone who had not verified yet wrote nothing down. The officer saw it work, Discord agreed, and Hootus kept no record. Those grants are written down like every other role change, so who handed out what has an answer.
Officer means officer, not everyone with a page
Handing one web page to your Member role quietly made Member an officer role, which decided who could be offered access to officer-only channels. Officer is now your admin and officer roles and nothing else. Every guild on Hootus already had an admin role set, so nobody loses anything they were using.
Writes land on the guild you were actually checked against
Six officer actions looked up which server you were on a second time, after already being told. Nothing ever landed in the wrong place, because both lookups read the same thing, but one of them falls back to a default server when there is no session and that is not a thing worth leaving lying around. They use the answer they were given.
Fifty-five things the guides said that were not true
One guide documented the whole bot-health screen at the wrong address while another described it correctly, so two pages contradicted each other. The officer guide promised approved applicants a personal seven-day invite link; the DM sends verification steps and a standing code that never expires. Four things were described that do not exist at all, including a settings tab and a button in the planner. Twelve of the eighteen guides were wrong about something.
Upper Blackrock Spire goes out as a ten man
Hootus had UBRS down as a five man like every other Classic dungeon, so an LFG post for it offered five seats when the instance takes ten. It reads the size off the dungeon now rather than assuming. Lower Blackrock Spire and Maraudon stay at five, whatever the patch notes about ten-player caps suggest, because that cap is how many bodies fit inside, not how many the group is.
The original Naxxramas knows what it is again
The forty-man Naxxramas was sitting in the content tables as "Naxxramas (Classic 40)" with no boss count, no level and no patch against its name. It is Naxxramas, fifteen bosses, level sixty, patch 1.11, and it says so wherever Hootus lists it.
Opening a character sheet shows that character
Two raiders in the guild called Shiobanowl, and Hootus picked whichever looked most important rather than the one you clicked. The gear, achievements, pets and arena pages all read from the same guess, so an officer could sit and study the wrong person’s kit. He goes by who owns the character, which the planner knew all along and was not passing on.
Raider status stops leaking between namesakes on the roster
The roster matched raider status and role overrides on the character name alone, so two members with the same name on different realms wore each other’s flags. Hootus checks the realm now. On the Night Owls roster this corrects exactly two rows, both retail characters that were being flagged off a MoP character with the same name.
The soft reserve cap counts raiders, not names
The same pair of namesakes shared one soft reserve allowance between them, so the second to reserve got told they were out of picks. The cap goes by the signup now, which is what "max per player" meant. Swapping which character you signed as keeps your reserves in one pile, same as before.
Your loot history is yours
Loot is recorded against the name Gargul exported, so the same two saw each other’s drops on their profile. Hootus now works out who the winner was from the raid’s own signups when he can, and falls back to the name when he cannot. Older rows keep reading the way they always did, so nothing vanishes from anyone’s history.
No more raid nudges for a game you have never played
In a guild running more than one game, anybody who had not linked a character yet was counted as playing all of them, so a new raider with nothing on their name got poked about Thursday’s MoP run and Friday’s retail one. Hootus now waits until there is a character to go on. Link one and the nudges start.
Adding a raider by hand keeps the realm you clicked
One member with the same name on two realms, an officer picking the right one out of the list, and Hootus writing down whichever he happened to find first. The signup records the character that was actually chosen, and if that character has since moved he says so instead of guessing.