How Puggers works

Getting started

Before you can apply or post, you need to tell us which WoW character you play. The fastest way: add a character by pasting a Raider.IO URL. We verify it exists and tie it to your session - no password, no email, no third- party app.

The core loop

1. A leader posts a key on /lfm/new — dungeon, key level, role they're playing, scheduled time, optional notes / spec preferences.
2. The listing shows up on /lfg with the leader's class, item level, current R.IO score, and a roster summary.
3. Applicants pick a character + spec(s) they're offering and apply. Applying with multiple specs flexes the slot — the leader picks which role to accept the applicant as.
4. The leader accepts applicants from /groups or the detail page. Accepted applicants get a Discord DM and need to confirm their slot.
5. Once the comp is full + everyone's confirmed, the in-game group forms using the unique “+12 NPX #XXXX” code as the Premade Group Finder name. Important: keep the code as-is and do notadd any Puggers branding to the in-game name or description — Blizzard treats site promotion in WoW as a code-of-conduct violation and will silence accounts based on player reports.
6. After the run, the leader marks it completed. Raider.IO ingests the in-game run; we detect it and attach it to everyone's history.

Pickups: claiming runs done in-game

Mythic+ rarely fills cleanly from a single LFG post. You start with 4, recruit a 5th from in-game chat or your guild, and now that fifth person isn't in your Puggers roster — but they ran with you.

When the leader marks the run completed, the completion detector writes a “pickup” row for every non-Puggers character that appears in the matched Raider.IO run. The leader can then send each pickup a one-click invite link — that link routes through /welcome and, after the recipient signs in (Discord or email) and links Battle.net, the run lands in their history automatically.

The point: a leader who picks up the same in-game player twice ends up with a real cross-realm record of who they ran with, even though that player only just joined the site.

Useful flags: ASAP, OCE, min R.IO

• ASAP — for leaders who want to run right now. The group auto-expires 30 minutes after posting unless the leader extends it. Surfaces as a gold pill on listings and is its own filter on /lfg.
• OCE — Oceanic-timezone group. Battle.net doesn't have a separate OCE region (it's all under US), but latency between NA-coast and AU/NZ players is rough enough that mixing the two ruins runs. Leaders flag their group OCE so OCE applicants self-select in and NA applicants can skip on latency.
• Min R.IO — leader-set floor on applicant R.IO score. Applicants whose character is below the gate get auto-rejected immediately. Keeps low-IO applicants from sitting in the queue waiting for a no they'd eventually get.
• Region mismatch — WoW invites are region-locked. A US character can't be invited to an EU group. If your eligible characters are all in a region different from the listing's, we replace the Apply button with a warning rather than let you apply into a dead end.

What's public vs private

Puggers shows other players the data they need to decide whether to run with you — and nothing more.

These stay private to you:

• Your sign-in identifiers (Discord ID and/or email address and/or Battle.net ID, depending on which paths you used) and timezone
• Run notes you sent to leaders when applying
• Your private notification preferences and account settings

These are public to anyone signed in:

• Your character roster (name, class, region, ilvl, R.IO)
• Your display name + avatar (Discord display name if you signed in via Discord; otherwise the email local-part or whatever you set on /me/settings)
• Your bio if you set one on /me/settings
• Run history once you mark a run completed (your roster + the dungeon you ran together)

See the privacy page for the formal version, including data-export and account-deletion paths.