The player journey

Five kinds of people walk through GuildPro. This is each of their paths, node by node, drawn from what the product actually does today — including what it does not do yet. Green is built. Amber is half-built. Red is a hole.

Built — works today Half-built — works, with an asterisk In build — being made right now Missing — the journey dead-ends here

The player

8/10 built

Anyone with a character. No guild required — this is the widest door.

built Finds GuildPro Lands on the boards — drop rates, PvP ledgers, world stats. The demo data makes the site worth looking at before any commitment. built Signs in with Discord One OAuth screen. No GuildPro password exists, on purpose. built Installs GuildPro One installer puts the addons into every WoW client on the PC — Era, SoD, TBC, private servers alike. built Just plays The addons count everything in the background: kills, loot, deaths, PvP, distance walked, gold looted. built Data syncs itself The app watches SavedVariables and uploads on every /reload or logout. The manual paste path exists for the app-less. built Characters claim themselves Uploads are tied to the account by the app's token, so characters attach without a claim ritual. built Sees their own story The /me profile: their PvP ledger, their world ledger, their characters, per realm and season. built Shows up on the boards Realm and expansion leaderboards — most kills, K/D, distance, the fun ones. missing Links their profile to friends HOLE: /me is private-only. There is no public profile page to send to anybody, which kills the bragging loop. missing Earns achievements HOLE: nothing to chase yet. Milestones over data we already hold (10,000 kills, every dungeon cleared) would give solo players a reason to stay.

The guild master

10/12 built

Owns the Discord, owns the problem. The whole funnel exists for this person.

built Signs in Discord OAuth again — and it doubles as discovery, because we learn which servers they manage. built Sees their Discords listed The dashboard lists every server they could add the bot to. No typing, no IDs. built Adds the bot in one consent Manage tier by default: read, post, and make channels/events. Never Administrator, never kick or ban. Minimal tier one link away. built Answers the setup wizard Guild, style, teams, nights, signups, loot, channels — seven questions, then it all persists. built Channels appear or attach The bot builds a clean #signups/#rosters/#recaps set, or slots into channels the Discord already has. Their choice. built Installs GuildPro The wizard now says so before Finish: the app is what moves the raid data. built Publishes the first signup sheet The bot posts it where setup said; raiders click buttons in Discord. built Runs a raid night Comp builder, published roster, the addon recording everything in the instance. built Wakes up to a recap Attendance and loot wrote themselves down. The ledgers are the receipts. built Hands officers the keys Roles on the members page — admin, officer, raider. Site roles, not Discord roles, because they are different claims. missing Recruits in public HOLE: the recruitment board renders listings but a GM has no way to post one. Browsing exists; supply does not. missing Pays for the good stuff HOLE: no billing, no pro tier. Fine for now — the free product must earn it first — but the journey ends without a till.

The raid leader

6/6 built

Officer, not owner. Runs Tuesday night; did not create the guild and should not need to.

built Gets made an officer An admin flips their role on the members page. One click, scoped to this guild. built Builds the comp The comp builder — drag the roster into groups, see buffs and gaps. built Publishes the roster Posted to the team's roster channel; benched players see it in the same place as everyone else. built Chases the missing The sheet knows who has not answered, and the chase pings them — the raid leader never plays secretary. built Runs the night In game with the addon on. Pulls, deaths, loot — recorded, not remembered. built The recap posts itself Next morning the recap channel has the story and the attendance ledger has the rows.

The raider

6/7 built

In the guild, not in charge. The product must cost them nothing and give them receipts.

built Signs in Same one-click Discord door as everyone. built Joins the guild on the site An invite link, the shape everybody knows from Discord: an officer mints one with an optional expiry and use cap, and following it signs them in and puts them in the guild — choosing which of their characters come with them. Auto-join from holding the guild's Discord role is still not a thing. built Signs up in Discord Buttons on the sheet, in the channel they already read. They may never visit the site at all — that is fine. built Appears on the roster Picked or benched, visibly and early. built Attendance follows them Their record accrues from the raid data — no officer with a spreadsheet. built Their characters are theirs Claimed to their account; history follows the account, not the guild. Leaving takes it with you. half-built Chooses what is public HALF-BUILT: the privacy policy promises an opt-in public profile — but the visibility toggle it describes is not built yet. The policy is ahead of the product.

The Discord admin

5/5 built

Has Manage Server in a community Discord. Controls the server, not the guild — and the product knows the difference.

built Adds or repairs the bot Manage Server is what Discord requires and all we require. Re-running an install repairs; it never forks a second guild. built Becomes officer, not admin First installer gets admin; after that, controlling the Discord earns officer. “I have Manage Server” and “I run this guild” are different claims. built Chooses the bot's reach Manage tier posts and builds channels; the minimal tier is read-and-post only, for the careful. Both on Discord's own consent screen. built Routes the posts The bot page maps signups, rosters, recaps, loot and announcements to channels — per team when there are several. built Lets the assistant in The MCP hookup, for guilds that want the AI to run the Discord end. Needs the manage tier it explains.

The routing web

how a post finds its channel

Everything the bot posts is one of five kinds, and every kind answers the same question the same way: most specific wins, checked top to bottom. The setup wizard writes the basics; the Bot page holds the full matrix; the sheet itself gets the last word.

Signups The sheet people press buttons on. Rosters The published comp, with confirm and swap. Recaps After the raid: kills, loot, hall of fame. Loot The ledger. Often the same channel as recaps. Announcements Reminders and calls to arms.

built “Post this one to #here” A one-off channel picked on the sheet itself at publish time — beats everything below. The picker is on the new-raid form and the channel is checked against the guild's own Discord before it is used. built The raid's own channel Karazhan signups → #tbc-10-sign-up, Gruul → #tbc-25-sign-up: per-instance routes, set on the Bot page. One tab per scope, every raid against every kind, and a team's cell beats the whole guild's. built The team's own channel Team TBC-25 overrides the guild default for any kind of post — one cell in the Bot page's routing matrix. built The guild default One channel per kind — what the setup wizard writes on the Channels step. A one-team guild never needs more than this row. built The legacy /setup channels Last resort, for guilds configured by the old in-Discord command before routes existed.

The holes, in one place

8 to close

Every amber and red node above, plus the gaps no single journey owns. This list is the roadmap wearing its honest name.

Links their profile to friends The player /me is private-only. There is no public profile page to send to anybody, which kills the bragging loop.
Earns achievements The player nothing to chase yet. Milestones over data we already hold (10,000 kills, every dungeon cleared) would give solo players a reason to stay.
Recruits in public The guild master the recruitment board renders listings but a GM has no way to post one. Browsing exists; supply does not.
Pays for the good stuff The guild master no billing, no pro tier. Fine for now — the free product must earn it first — but the journey ends without a till.
Chooses what is public The raider the privacy policy promises an opt-in public profile — but the visibility toggle it describes is not built yet. The policy is ahead of the product.
Loot capture → live drop rates systemic The addons record loot, but live per-instance drop tables are not yet aggregated from uploads — the loot pages lean on demo data in live mode until enough raids sync.
“Who killed this mob?” reverse index systemic We can say what a player killed; we cannot yet ask a mob who killed it. The reverse index (mob → killers, item → looters) would power pages we have not drawn.
Battle.net verification systemic Discord proves who you are to your guild; Battle.net would prove you own the character. Deliberately later — it adds trust, not capability.
Era client telling 1.15 from private 1.14 systemic One folder serves both Blizzard Era and private servers; the build-number sniff that separates them is not written.
Retail systemic Everything here is Classic-family. Retail is a different addon API and a different audience.