🔥

Phoenix

Raid Hub


Loading roster data...

Officer Dashboard

Back to Roster
Click a player row to open their profile card below the table. From there you can edit class, spec, role, trial/bench status, join date, BiS source, nickname, M+ exclusion, and officer notes.
To rename a player (character name or realm change), use the Name/Realm field in their profile card and click Save. This also updates their name in the Attendance and Loot sheets.
+ Add Player button in the top-right of the roster table header adds a new player directly to the Roster sheet.
The trial promotion banner appears automatically when a trial has been on the roster long enough with sufficient attendance to warrant a promotion review.
Filter:
Role:
Sort:
RCLootCouncil Export String

Import both Heroic and Mythic separately in the addon -- each import adds to what's already there instead of replacing it.

RCLootCouncil Export String -- click Generate to build an encoded string from the current priority order and roster. Copy it and paste it into RCLootCouncil in-game to sync loot priorities to your council.
Priority List -- read-only view of every item's ranked priority order as set in the Priority Order sheet. The Heroic/Mythic toggle above the list shows one difficulty at a time (Heroic by default) instead of stacking both under every item. Each ranked player shows their current wishlist tag for that item (or "No wishlist tag" if they never tagged it), so you don't have to leave the tab to check what they actually set. Use the search box to jump to a specific item. Above the list sit three collapsible summary sections, each starting collapsed with a one-line overview -- click a section's header to expand it for the full detail: "Priority List Conflicts" (stale-after-Heroic #1s and same-boss #1 stacking), "Drift" (see below), and "#1 Priorities Held" (every player currently holding at least one #1, with their count and a flag if any of those #1s share a boss -- two items both locked behind the same kill; counts of 4+ are highlighted in red as worth a look). The badge count on this sub-tab covers just the Conflicts and Drift sections, not the full #1 table, since holding several #1s is expected once the raid has 30+ managed items.
Drift -- a saved item/track priority order (the one committed via the Priority Edit modal) whose top 3 no longer matches what the scoring generator would suggest today. This can mean scores shifted enough since the save to reorder or bump a player in/out of the top 3, but it's just as often a saved order that was intentionally hand-adjusted away from the generator's suggestion in the first place -- the check has no way to tell those two apart, since it only compares the saved order against today's generator output, not against what the generator suggested at save time. "Check for Drift" recomputes and compares live; it also runs automatically right after committing Scoring tab performance updates. A drift flag isn't automatically wrong -- it's worth an officer's eyes to confirm the saved order is still the intended one, not a signal that something needs fixing.
Unmanaged Items -- items that appear in players' BiS lists but have no priority order assigned yet in the sheet. The badge count shows how many need attention.
Contested Items -- items wanted by 6+ players (counted from raider wishlists), collapsed by default -- click an item to see who wants it and their current priority rank.
Notes -- every item with a raider-written wishlist note, and who wrote it (e.g. a pure-DPS raider explaining an off-spec BiS want). The gold badge is just a "something's here" flag, not a problem to fix. Read-only context for sequencing calls -- doesn't affect the generated priority order itself.
Incomplete Wishlists -- raiders who haven't tagged a status for every gear slot yet. Worth checking before generating a suggested priority order; see the BiS Manager > BiS Lists sub-tab for which slots each raider is missing.
Refresh from WCL -- pulls the latest raid nights from Warcraft Logs and populates the attendance grid. Run this after each raid night.
Commit Attendance Scores -- calculates each player's weighted attendance score/% and saves them to Scoring, which is what the Priority Generator uses. Safe to run multiple times; it always recalculates from scratch. The roster's live attendance % display doesn't depend on this -- it's already computed fresh from attendance data on every load.
Manual edits -- click any status cell in the grid to change a player's attendance for that night (Present, Late (with notice), Late (no notice), Excused, No Show, etc.).
Refresh from WCL -- fetches the last raid reports from WCL and calculates Recent/Trend/Best scores for each DPS player, using whichever metric is selected: Ilvl Bracket % (percentile within same-gear players -- consistent across gear levels, but the comparison pool grows as the tier goes on, which can push scores down over time even with steady play) or Overall % (percentile across everyone who logged the fight -- a stabler pool over the tier, but rewards being ahead on gear). Tanks and healers are skipped and marked Manual. Scores are held in a session draft until committed.
Commit Performance Scores -- saves the Recent score from the draft above into Scoring (performance_score), which is what the Priority Generator uses. Safe to run multiple times; it always recalculates from scratch.
■ >= 7.0 — Strong ■ >= 5.0 — Average ■ < 5.0 — Below average ■ Trend fallback (no recent data) ■ No data ■ Excluded (Tank/Healer) Scores = selected percentile / 10
Raid Nights Since Last Item -- how many raid nights have passed since each player's last loot award, grouped by role.
BiS Demand vs Awards -- ranks items by how many active players want them on their BiS list, next to how many times each has actually been awarded in the selected season. High demand + low awards is what to prioritize.
Priority Order Health -- flags stale priority order entries for players no longer on the active roster, active non-bench players missing from priority order entirely for a season, and saved Mythic #1s where the player already received the Heroic version of that same item.
Season Loot Pace -- items awarded per week of the season, compared to the same week last season. "Week 1" is measured from this team's first tracked loot award of the season, not from the raid-lockout calendar and not from the first raid night the season is scored against, so a week here lines up with the two seasons being compared rather than with the attendance window.
Tier Sets -- each active roster player's tier-set piece count (out of 5), so you can see who's behind without opening every profile card. Synced from Raider.IO via the "Sync Roster Tier Counts" button here (same sync as the Priority tab's).
Role:
Sort:

Loading...

Season View

The season your team is planning items/BiS for, and the season your views of raiders' wishlists show. Leave on "Live season" and the Priority tab, BiS Lists, and those wishlist views reflect the current raiding season automatically. Pick a specific season here to prep its item catalog and BiS ahead of time without touching the live raid -- useful once that season's raid zone has been added in Season Settings > Raid Progression for a future tier, or to audit an old season's data. A season with no items imported yet will show up empty here -- that's expected until the import for it is finished. This does not affect signups; see Signup Season below for that.

Trial Promotion Thresholds

At least weeks on roster and % attendance

Target Roster Sizes

Shown to raiders signing up as Tank or Healer: once the confirmed roster plus already-approved incoming roster meets or exceeds a target, they see a nudge to consider DPS/backup instead, or talk to an officer. Leave a field blank to skip the nudge for that role -- raiders still see the plain count either way.
Tanks Healers

WarcraftLogs Guild URL

This team's own WarcraftLogs guild page (Phoenix and Hellfire log separately even though both are part of the same WoW guild). Powers the WCL icon link in the header. Raider.IO and Armory are guild-wide and not set here.

Discord Signup Sheet

The bot posts one message per raid night showing the whole roster's RSVP status, and edits it in place as people respond. Channel ID: leave blank to use the bot's default attendance channel. Lead Time: how many hours before the raid the sheet gets posted (default 48 -- e.g. a Tuesday 9pm ET raid posts the preceding Sunday at 9pm ET). Use Verify to confirm a channel ID resolves to the channel you expect -- many of our channels are named nearly identically across teams (e.g. phoenix-raid-attendance vs hellfire-raid-attendance).

Team Officer Bios

Shown publicly on the "About" tab's Team sub-tab, in the order listed here. Picking a roster player fills in their name/character name/class/spec to start -- everything stays editable afterward and isn't kept in sync with the roster, so it's fine for someone who has since changed spec or left. Photos are static files -- send Kat the image you want to use and she'll add it and give you the path to paste into the Image Path field. Leave blank to show initials instead.

Officer Workflow Reference

Import RCLootCouncil loot history

  1. Entries are tagged with the current tier, the one the Loot > Import panel names; there is nothing to set first.
  2. In-game, open RCLootCouncil and use its export feature to copy your loot history JSON.
  3. Go to Loot > Import, paste the JSON into the text box, and click Import.
  4. Duplicate entries are skipped automatically -- you can paste multiple nights at once or re-paste old exports safely.

Refresh attendance from Warcraft Logs

  1. Go to the Attendance tab.
  2. Click Refresh from WCL. This pulls the latest raid nights from Warcraft Logs and populates the attendance grid.
  3. Select a raid night from the dropdown to review or edit player statuses.

Manually edit attendance status

  1. Go to the Attendance tab and select the raid night from the dropdown.
  2. Find the player in the grid and use the status dropdown on their row to set: Present, Bench, Late (with notice), Excused, Late (no notice), No Show, Extended Leave, Medical Leave, or Not on Roster.
  3. The change saves immediately -- a checkmark confirms success.

Commit attendance scores

  1. After reviewing the attendance grid, click Commit Attendance Scores on the Attendance tab.
  2. Confirm the prompt. This calculates each player's weighted attendance score/% and saves it to Scoring, which is what the Priority Generator uses.
  3. The roster's live attendance % display doesn't depend on this -- it's already computed fresh from attendance data on every load. Run this after any manual edits or a WCL refresh to keep Scoring current for the Priority Generator.

New tier workflow

  1. Go to Season Settings and click Close Season (History sub-tab) for the tier that ended. This records it in Season History and resets every player's submitted BiS source, M+ exclusion, and Bench status team-wide. The new tier is already the season everyone is on.
  2. Still in Season History, run the just-closed tier's WCL Performance Baseline fetch -- the row only appears next to the newest history entry, so do it now or you won't get another chance once another tier closes. This seeds the Heroic priority baseline before the new tier has raid reports of its own; a status label on the row shows whether it's already been done.
  3. Import this tier's loot via Loot > Import -- old loot history doesn't need clearing, it stays tagged by season.
  4. On the Attendance tab, click Refresh from WCL to pull the new season's raid nights.
  5. Commit updated scores via Commit Attendance Scores.

Track a found BoE through sale and payout

  1. A raider reports the drop through the form at the top of the BoE page; it appears under BoE Sales > Open on the same page.
  2. When it goes to the auction house, click Record Listing and enter the listing price. Relists just get another Record Listing -- the history stays on the item.
  3. When it sells, click Record Sale and enter the sale price. The finder's payout and the guild cut are computed from the guild-wide split policy and shown under Awaiting Payout.
  4. After mailing the finder their gold, click Mark Paid. The item moves to History.
  5. Retire closes out an item that never sold or was reported by mistake.
  6. Listing, sale, retire and edit need the BoE manager grant (assigned by a site admin). Mark Paid, Donate to Guild and Undo Payout are open to officers and team leaders on their own team's finds, since they're the ones handing out the gold.

Season Properties

Currently Excluded
These recurring nights drive the raid calendar raiders see (Home widget and the Calendar page) -- add one row per weekly raid night, edit and click Save per row. Raiders are auto-marked Present unless benched; an Optional night has no automatic Present and everyone must respond instead (#895).
Use One-Off Changes below to cancel a single occurrence of a weekly night, or add an extra night that isn't part of the regular schedule.
Cancelling or removing a night does not touch any RSVPs raiders already submitted for it -- those rows are left in place but become harmless.
Each night says Heroic or Mythic, so the boss lineup can tell which of the week's kills count for it. Set the team's usual difficulty once under Raid difficulty; every night follows it unless you pick another for that night. Pick Heroic into Mythic for a night that starts on Heroic and pushes into Mythic; it counts as Mythic.
Date
Start Time (added only)
Duration (added only)
Note
Set Priority

Drag to reorder. Click a player on the right to add.

Add Player

Officer Access