What Hootus is working on
No dates, no promises, no deck. This is what is being built, what is next, and what is still being argued about. Everything that is finished lives in the changelog instead.
Code exists and is being worked on now.
Hootus checking in when a server goes quiet
Getting startedHe can already work out that a server finished setup a week ago and still has nobody verified, and he already writes the message that would say so. The switch that sends it is off. What is left is deciding how often he is allowed to speak, and making sure he never says the same thing to you twice.
Decided and written down. Not started.
A sidebar for the signed-in app
The web appThe web app navigates from a top bar that has run out of room, with a second row of tabs under it on settings. A left rail takes both, carries the server switcher and your account, and knows which page you are looking at. The public pages keep the top bar they have.
An idea with evidence behind it. It may never happen.
More than one guild in one Discord
Running the serverThe database already lets a Discord server hold several WoW guilds, and one server is quietly doing it. Nothing in the interface admits that. Whether it becomes a real feature or stays an accident has not been decided.
Out in a release, and in the changelog with everything else.
Your dashboard saying what is broken
Running the serverShipped in v1.132.1Five of the servers that dropped
Hootus left carrying a fault he had never mentioned, while their own
dashboards told them the roster was clean. He knows nineteen ways a server can break now, says only the
ones that stop a real person getting anything, and says each of them once. The full list is in
the changelog.
Everything here started as somebody's raid night going wrong.
Hootus is one person and a couple of guilds, so the order is decided by what breaks for real servers, not by what would look good on a slide. If something you need is missing from this list, that is usually because nobody has said it out loud yet.