Claim your character once. It stays claimed.
Connect Battle.net and Hootus reads the character list straight off the account, spelled the way Blizzard spells it. You do not need to be in a guild to do it. The claim is keyed to you, so when you join another server running Hootus and that character is on their roster, it is already proven. You skip the typing and go straight to signing up.
- Realm
- Mirage Raceway
- Class
- Protection Warrior
- Proof
- Battle.net
- Proven
- 7 Aug 2026
Recognised anywhere this character is on the guild roster. The proof travels. Your guild list does not.
Verified means the character came out of a connected Battle.net account. A character somebody typed is marked claimed. Both are perfectly fine, and the badge is there so an officer never has to guess which.
Three things you stop typing.
Every one of these is a real thing that went wrong before the claim existed, not a hypothetical.
- Used to be: spelling it yourself
Your alts, read off the account
Bågbritta, Dotförbannad, the Rogue you rolled at 2am and named badly. One trip through Battle.net brings every character on the account across, spelled the way Blizzard spells it, diacritics and all, including the level 6 you made last night. That last one is the case typing a name has never worked for.
- Used to be: guessing the realm
The realm Blizzard actually returns
Mirage Raceway is five realms in a trenchcoat. Hootus used to stamp the guild realm onto everyone and got it wrong for one member in five, which is why armory lookups came back empty for people plainly standing in the guild. He now takes the realm per character, from Blizzard, and the hourly sync keeps it right.
- Used to be: starting from scratch
A second guild you do not re-verify for
The claim is keyed to your Discord account and the character, not to a server. Walk into another guild running Hootus, with that character on their roster, and it already reads as proven. Nothing to retype, nothing to wait on, no officer digging through the armory to confirm a name you have confirmed before.
One trip through Battle.net. Every character on the account.
Connecting is optional and Discord is still how you sign in. A Discord login is the whole requirement, no guild needed, so you can do it before you belong anywhere. What it buys you is a character list you did not have to spell, checked against the armory before any of it is saved.
- FjorvaltMirage Raceway · WarriorMainVerified
- MournhowlThunderstrike · DruidAltVerified
- BrightleafMirage Raceway · DruidAltVerified
- SkarnMirage Raceway · RogueLevel 6, made last nightVerified
- PyreclawMirage Raceway · MageTyped in before you connectedClaimed
Verified is not a promise that the list is complete. Other regions, other game versions, and characters made since your last import can all be missing, and the connect page says so rather than pretending otherwise.
- Read-only, and short-livedYour account ID, BattleTag, and the character list for this region and game version. Not your password, email, payment details or subscription status. The token is used once and thrown away, which is why re-importing means signing in again.
- Checked before it is savedEvery name goes past the armory first, so a character that lingers in the account list but no longer exists does not turn up on your roster. Verify does the same thing across connected realms rather than assuming the guild home realm.
- Disconnect and nothing vanishesOne click to unlink. Your characters stay exactly where they are and drop back to previously verified rather than disappearing off the roster mid-tier.
Proof follows the player, not the guild.
One record per character, keyed to a Discord account. No guild owns it, no guild can hand it over, and no guild can take it away.
Claim it once
Connect Battle.net from the web, or confirm the character on the armory with /verify in Discord. Either way Hootus writes down that this Discord account owns this character, on this realm, in this game version.
One character, one owner
The record is unique on the character, not on the character plus the guild. If somebody else goes for Fjorvalt on your realm, Hootus refuses the claim and hands it to an officer to look at instead of quietly giving it away.
The next guild already knows
Join a second server running Hootus and the character reads as proven the moment you arrive, as long as it is on that guild Blizzard roster. You sign up for the raid. Nobody types a name from memory and nobody waits three days for an officer to check the armory.
- Owner per character, globally
- 1Owner per character, globally
- Names you retype when their roster has you
- 0Names you retype when their roster has you
- The Battle.net token is used, then dropped
- OnceThe Battle.net token is used, then dropped
- Members whose realm was wrong before
- 1 in 5Members whose realm was wrong before
What happens when you walk in.
Onboarding at the second guild is not a cold start. Here is the whole of it, including the part where it decides not to.
- The moment the join lands
Checked before you have typed a word
Hootus looks up your Battle.net link on the join event, pulls the characters you have already proven for that server region and game version, and holds them up against the guild own Blizzard roster. All of it happens in the couple of seconds before the welcome message goes out.
- Matched on the Blizzard ID
The same character, not a similar name
Where the roster row carries a Blizzard character id, that is what has to match. Where it does not, it is the name plus the connected realm, and the class has to agree on top. Two rows that could both be you, or two identities pointing at one roster row, and Hootus refuses the lot rather than picking one.
- Approved with a class role
Your highest character sets the role
Highest level takes the lead, item level breaks a tie. You come in approved with that class role already on, and the main is set when the lead is clearly ahead of the rest. When it is close, Hootus DMs you to pick instead of guessing and getting it wrong in front of the guild.
- No match, no shortcut
Then you verify like anyone else
Different flavour, different region, or a guild whose roster you are not on yet, and recognition does not fire at all. You get the normal unverified welcome and /verify. A character somebody else in that server already claimed is skipped and logged for the officers. A ban or a hold beats the proof outright.
Global proof, not a global profile.
The record is global on purpose. What it is not is a window between guilds. A guild sees your characters in that guild WoW roster, plus any you attached in that server yourself. That is the whole slice, and it is the same slice whether you play in one server or six.
The only query in the system that crosses a guild line is the one that hands your own rows back to you. An officer can see that a character is proven. An officer cannot see where else you raid, and there is no setting anywhere that turns that on.
- Your characters in this guild WoW roster
- Any character you added in this server yourself
- Whether each one is verified or claimed
- A refused claim, when two people go for the same character
- Which other Discord servers you are in
- Which other guilds your characters raid with
- Alts you have never attached to this server
- Anything that would let an officer name your other guild
The more guilds run Hootus, the less typing you do.
This is not guilds getting access to each other. Nothing about your guild leaves your guild, and nothing about your other guilds arrives in this one. It is simpler than that. The proof is attached to you, so the first guild does the work of confirming who you are and every server after that starts from there instead of from nothing. Which is a perfectly selfish reason to want your next guild running it.
Prove your characters once and get on with the raid.
Connect Battle.net from the web, or confirm a character on the armory with /verify in Discord. The claim is yours either way, it travels with you, and the next guild running Hootus does not make you start over.