Skip to main content
Roster & verification

Your roster, pulled from Blizzard and synced every hour.

The bot reads your guild straight from Blizzard's game API, alts and respecs included, and refreshes it hourly. Members verify a character against that roster instead of typing a name from memory. So your signups, your planner, and your recruitment all read the same honest list of who's actually in the guild.

Free at the core·No Blizzard account linking, no manual roster upkeep
The problem it kills

Every guild roster you've kept by hand was wrong by Tuesday.

Someone made a Google Sheet. It was accurate the day they made it. Then a tank respecced, two people leveled alts, a recruit ghosted, and nobody updated the tab. By raid night you are signing up off a list that hasn't matched the game in weeks, and the officer who maintained it is the only one who knew which Druid was which.

HootusPlootus reads the roster from Blizzard on a loop, so it doesn't rot. The bot knows who is in the guild, what they are playing, and what they're geared in, because it asked the game an hour ago instead of trusting a cell someone typed last month.

The old way
  • "Is the roster tab up to date? It says he's Resto."
  • "He respecced weeks ago. Nobody fixed the sheet."
  • "Wait, which one's the alt and which is the main?"
  • "That person left in March. Why are they still on here?"
  • "Ash kept the roster. Ash quit. Now what?"
How the roster stays honest

Synced, verified, and seeded from your history.

Four things keep the list matching the game, not a spreadsheet's memory of it.

Pulled from Blizzard, every hour
The bot reads your guild roster straight from Blizzard's public game API and refreshes it on an hourly sync. Name, realm, class, spec, level, item level, and guild rank, for every character on the roster. When someone dings 70 or respecs overnight, the next sync already knows.
Alts and respecs come along
It is not just one main per person. Alts on the roster show up, and a character that swapped from Resto to Boomkin reads as Boomkin the next morning. The roster reflects the guild as it actually is, not as it was the last time someone updated a spreadsheet by hand.
Members verify who they are
A new member confirms a character, the bot checks it against the synced roster, and a race-check step trips up the obvious impersonator. There are three strictness modes, so you decide how hard the gate is. Nobody links a Blizzard account. They just prove the character is theirs.
Bring your history with GRM import
Already run Guild Roster Manager? Upload your exported GRM file to seed join dates and link alts the live sync cannot see. You pick which guild in the file maps to your server, review a dry-run before anything is saved, then commit.
Verification

A member proves who they are, no account linking.

When someone joins, the bot walks them through confirming a character. It checks that character against the roster it pulled from Blizzard, and a race-check step asks them to confirm the race, which trips up anyone trying to claim a name that isn't theirs. A match assigns the right class and rank roles on its own.

Nobody hands over a Blizzard login. You pick how strict the gate runs, from roster-only to armory-confirmed to officer-trust, in the settings. So a Mage can't quietly become your missing tank.

  • Members verify a character, they never link a Blizzard account
  • The bot matches the character against the roster it pulled from Blizzard
  • A race-check step asks them to confirm their race, catching the obvious faker
  • Three strictness modes: roster-only, armory-confirmed, or officer-trust
  • Class and rank roles get assigned on a match, no manual clicking
Synced from Blizzard
CharacterFjorvalt · Tauren Druid
SpecFeral · Tank
Level70
Item level128 avg
Guild rankRaider
Last sync41 minutes ago
Verified characterrace-checked
/whois reads this same row, so officers always know who owns the name.
One roster, read everywhere
  • Signups validate the requested role against the verified character
  • The planner reads real spec data when it checks group composition
  • Recruitment can look a character up against the same armory
  • /whois, /character, and alt management answer "who owns Fjorvalt?"
Because the bot knows who is who

The roster isn't a tab. It's the source the rest of the bot reads.

Once a character is verified and synced, everything downstream trusts it. Signups check the requested role against the real class and spec. The planner reads the same spec data when it looks at your composition. Recruitment can look a character up against the same armory. There is one list, and every feature reads it.

That's why /whois, /character, and the alt tools can answer "who actually owns Fjorvalt?" without anyone keeping a side note. The honest roster does the remembering.

GRM import

Bring the history Blizzard can't tell you.

The live sync knows the current state of your guild, but it can't see when someone joined or which alts belong together from years back. If you've run Guild Roster Manager, your saved file has that. Upload it in settings, pick which guild in the file maps to this server, and the bot seeds join dates and links alt clusters.

Nothing is written until you say so. You review a full dry-run first, then commit. Officers can manage members from there, and people who left or got dismissed stay tracked instead of vanishing.

  • Upload your exported Guild_Roster_Manager.lua
  • Pick which guild in the file maps to this server
  • Review a dry-run before anything is saved
  • Commit to seed join dates and link alts
A roster that doesn't rot

Let the game keep your roster, not a spreadsheet.

Add HootusPlootus, set your guild and realm, and let the hourly sync do the upkeep. Members verify themselves, and every feature reads one honest list of who's in the guild.