Skip to main content
All patches

25 Aug 2026 · v1.113.0

Only The People You Meant

Hootus had been generous with things that were never meant to be shared. The pending list went up in the channel with everyone's name and live approve buttons on it, the PUG invite was a permanent link any member could pull, opening recruitment quietly published your guild to the open web, and on the right server anyone at all could sign in as a dashboard admin. All of that is shut. He also stopped stating a week-old roster as today's fact, and stopped losing your spec every time you changed your main.

2 New3 Improved10 Fixed

2 New

  1. Opening recruitment now tells you what goes public first

    Turning recruitment on publishes your guild name, realm, faction, raid nights, roster size and progression to a page search engines can index. Nowhere said so, and the FAQ answered a nearby question about sandboxing instead, which read as reassurance. The recruitment settings page now lists what leaves your server and what does not, next to the switch, with the address it will live at.

  2. The health check knows when a database update is still pending

    The status endpoint could say the database was reachable but not whether it was actually up to date, which is the state that matters right after an update, when the site is running new code against the old database. It now names exactly which updates have not landed yet.

3 Improved

  1. Roster numbers say how old they are

    The roster read out a cached snapshot as present fact, and one line even claimed it was coming from the Blizzard API when it was a database read. Every roster figure now carries when it was last synced, the apply page dates its numbers or counts live, and an empty roster tells you which of the reasons it is: no credentials, no guild linked, no realm set, never synced, or synced and genuinely empty.

  2. The destructive admin commands write down that they happened

    Resetting a member, promoting one, and setting or clearing their membership all changed things permanently and left no trace, while the harmless roster sync was the one thing keeping a record. They all get an audit entry now.

  3. The support form stopped being knockable-over

    A long enough page address made the whole ticket unsendable at Discord's end, so the form said thanks and the message never arrived, retrying forever. Every field is bounded now. There is also a ceiling on tickets per hour across the whole instance, not just per account, so a pile of alt accounts cannot bury the inbox.

10 Fixed

  1. The pending list stopped posting itself to the channel

    Running /pending put every waiting applicant, their character and their class into whatever channel you happened to be standing in, with working Approve and Deny buttons attached for anyone walking past. Only the first line had ever been private. The whole thing is yours alone now, it shows the oldest twenty-five at a glance, and it hands you the first few to act on rather than carpeting the channel.

  2. Nobody gets dashboard admin just for being in the server

    On a server where @everyone carries Manage Server, every single person who signed in got full dashboard admin, because @everyone is a role like any other and Hootus was counting it. Same for anyone holding a moderator or utility-bot role that happened to have Manage Server on it. The dashboard now asks the same question the bot does, which is whether you are the owner, a Discord admin, or in a role you were actually given. Running setup is untouched.

  3. The PUG invite stopped being a members-only secret in name only

    /pug link never checked who was asking, so any member could pull a permanent, unlimited invite to your server and it would never expire. It is a raid leader command now, as it always claimed to be. If one does get out, /pug link rotate:true kills the old link and mints a new one, and he tells you plainly if the old one is somehow still alive.

  4. Changing your main stopped wiping your spec

    Setting a different main blanked the spec, avatar and item level on the character you already had, and raid signups read that spec, so your next signup had no spec and no role guessed for you. Worse, every roster sync was quietly zeroing item level on every matched character, because Blizzard's guild roster does not carry it and Hootus was writing the blank down anyway. He keeps what he already knows now, and only overwrites it with something real.

  5. Tank and healer counts stopped being a guess from class names

    Every Warrior was counted as a tank and every Paladin, Priest, Druid and Shaman as a healer, with Druids and Paladins counted as both, so the roster could confidently report more tanks and healers than it had people. The numbers come from actual specs now. What someone could fill on an offspec is said separately, and the totals in one embed finally agree with each other.

  6. Guilds with an apostrophe or an accent stopped being invisible

    A guild called something like Lightning's Blade never resolved at Blizzard, so its roster, activity and crest quietly failed and got reported as a credentials problem. Accented and non-Latin names were being mangled a second way on the web side, leaving guilds with a numeric URL and no listing. Both are fixed, the way Blizzard actually does it, and a guild whose address cannot be worked out is now asked to pick one instead of silently getting a number.

  7. Officer channels stopped getting raw error text

    When something failed, four hundred characters of the underlying error went straight into your officer channel. Officers now get a sentence about what went wrong and what to do about it. The raw text still exists, it just goes to whoever runs the bot instead of into your server.

  8. The stale roster warning stopped resetting every time the bot updated

    If your armory guild name was wrong, Hootus was meant to mention it once a day. He kept the timer in memory, and every update restarts him, so a guild with a genuinely wrong name got a fresh officer post every single time the bot was deployed. He writes the date down now. He also stopped ticking it off before actually managing to tell anyone, which used to buy him a day of silence for a message nobody received.

  9. The last few commands stopped failing silently before setup

    /away, /ginvite and /roster slipped past the check that answers with a setup link, so on a half-set-up server they failed in ways that explained nothing. The check now runs for every command in one place instead of being remembered one file at a time.

  10. The invite links page let officers in

    The officer guide sends officers straight to the invite links page, and the page was gated on a permission that did not exist, so it turned everyone away except admins. It now uses a real one that shows up on the permissions page like everything else.