Skip to content

Raid Check

Raid Check inspects profile members who are currently in the group against addon-owned current-Retail enchant and gem rules, plus an optional profile minimum item level, then whispers results and awards loot points or Attendance.

Only an admin of the selected loot profile can run a check. Enchant and gem rules are not configured per profile. Minimum item level is. Preview as Non-Admin uses the same local non-admin restriction: a check cannot be started while the preview is on. If a run is already in flight when the preview is enabled, its awards, Reward Pot changes, logs, and admin whispers are aborted as a unit and are not replayed after the preview ends.

Where to look

  • Raid Equipment is a top-level Raid Tools category. It works with no loot profile and no Loot Helper session.
  • Pre-Raid Check and Raid Check remain on Loot Helper → Session.
  • Point awards, whispers, and Reward Pot deduction settings also remain on Loot Helper → Session.

Current equipment rules

Prepared means a complete inspect of current gear found:

  • an item in every tracked slot, except a legitimate empty Off Hand when Main Hand is a two-handed weapon (INVTYPE_2HWEAPON) or a bow, gun, or crossbow. A ranged equip location alone is not enough: wands and other ranged-style weapons still require an Off Hand. If that weapon identity has not resolved, the observation stays incomplete instead of reporting a missing Off Hand;
  • enchants on Head, Shoulders, Chest, Legs, Boots, both rings, and Main Hand;
  • an Off Hand enchant only when that item is an actual weapon (INVTYPE_WEAPON, INVTYPE_WEAPONOFFHAND, or INVTYPE_WEAPONMAINHAND);
  • no weapon enchant required for shields, held-in-offhand items, relics, or other non-weapon offhands;
  • every socket filled;
  • if the player has one or more usable sockets, exactly one current-expansion limited gem (Midnight Eversong Diamond family). Zero sockets requires zero limited gems;
  • when the active profile has Require Minimum Item Level enabled, an overall equipped item level greater than or equal to that whole-number minimum. A player exactly at the minimum passes.

The item level is Blizzard's overall equipped value: C_PaperDollInfo.GetAverageItemLevel for the local player and C_PaperDollInfo.GetInspectItemLevel for inspected players. Spectrum does not average the tracked slots itself. The requirement is off by default, including for existing profiles and older snapshots that do not contain the fields.

A real empty slot is not the same as unresolved equipment. Missing item links, unresolved offhand type, an unidentified limited gem, or a missing item level while the requirement is enabled make the observation incomplete. Incomplete inspects are Inspection Failed, not Unprepared. A missing item level is never treated as zero or as a failed requirement.

Raid Equipment page

Open Raid Equipment to review the current group. The page works with no loot profile and no Loot Helper session. It shows each visible member, Blizzard's overall equipped item level, the last known item in each tracked slot, and pulsing indicators for missing items, required enchants, empty sockets, or a missing limited gem. When an active profile has a minimum item level and the player's known item level is below it, the iLvl value itself pulses red. The rest of the row does not. With no active profile, or with the requirement disabled, item level is shown with no threshold warning.

Enable Auto Refresh is off by default and is stored as lootHelper.raidCheckAuditAutoRefresh. It does not require a profile. Use Refresh Snapshot for a short manual inspect pass. Raid Equipment background inspection runs while this page is open and auto refresh or a manual refresh window is active. Early Preparation Whispers can keep the same shared inspect pipeline running while that page is closed. Turning one of those consumers off does not stop inspection the other one still needs.

Equipment observations are runtime-only. /reload clears them. Older SavedVariables equipment snapshots, if present, stay on disk and are not used.

Session prompt

When you run Pre-Raid Check or Raid Check:

  • If a Loot Helper session is already active for the selected profile, the check starts immediately.
  • If a session is active for a different profile, the check still runs against the selected profile. A warning explains that consequences stay local to that profile and will not synchronize through the unrelated session. The addon does not switch profiles or end the other session.
  • If no session is active, a prompt appears:
  • Yes starts a Loot Helper session for the selected profile, then starts the check only if local session startup succeeds. Inspection may begin immediately. Synchronized consequences wait until the local SES_START send is accepted. If that announcement cannot be sent, the unfinished session is cleared locally without SES_END, the check finishes with local-only results, and the next check prompts again.
  • No runs the check without a session.
  • Escape / close / Cancel aborts. Nothing is inspected and no session is started.

Explicit No is the only no-session path. Duplicate clicks do not open a second prompt or start a second run.

Combat

If the check starts in combat, targets and the selected profile still freeze, then inspection pauses until combat ends. If combat starts mid-run, completed results are kept and remaining targets resume afterward. Time spent paused does not consume the inspect time budget. Manual Blizzard Inspect is treated the same way: a temporary system pause, not Unprepared.

Who is evaluated

At run start the addon freezes:

  • the selected profile and its consequence settings, including whether minimum item level is required and the configured minimum;
  • the target set = that profile's members who are currently in the group.

A settings change during the run does not reclassify players against a new threshold. The next run uses the updated profile. Changing the minimum reevaluates cached observations and does not start a new raid-wide inspect when those observations are still authoritative.

Someone who joins after freeze is ignored. Someone who leaves stays in the run and is classified from accumulated inspect evidence. Changing the selected profile mid-run does not redirect the check.

Results

Pre-Raid Check reports results. It does not award points, Attendance, or Reward Pot changes.

Raid Check additionally:

  • awards configured loot points in Point Based mode, or 1 Attendance in Reward Pot mode, to Prepared members;
  • deducts from the Reward Pot once if any evaluated member is Unprepared (policy or never inspectable). Inspection Failed does not deduct.

Recently Verified

If a player cannot be refreshed only because they are out of range, and a complete runtime observation from this session is at most about 120 seconds old, the check may treat them as Recently Verified using that last-good result. A technical inspect failure in this run is not replaced by that fallback.

Inspection Failed

Inspection Failed means Spectrum attempted to inspect the player and the data was incomplete or the inspect timed out. It is reported separately to the admin. It does not:

  • award Prepared credit;
  • count as Unprepared for the Reward Pot;
  • send a missing-equipment whisper.

A later out-of-range state does not rewrite Inspection Failed into Unprepared.

Whispers

Profile whisper toggles are disabled by default and are configured on Loot Helper → Session. They do not control the admin system-message summary.

Templates support {player_name}, {missing}, {point_name}, and {points_awarded}. {missing} is the shared list of failed requirements, including item level when that requirement fails. Default missing-result templates refer to requirements rather than only enchants and gems. A template an admin already customized is left unchanged. With no active Loot Helper session, missing-requirement whispers are suppressed for the same check type on the same calendar day. During an announced session, Early Preparation, Pre-Raid Check, and Raid Check share one missing-requirements warning per profile member for that session. A prepared or point-award whisper is separate and is not suppressed by that warning. Inspection Failed does not send a missing-gear whisper.

Early Preparation Whispers

Enable Early Preparation Whispers is a local setting on Loot Helper → Session. It defaults to on, including when an older saved settings database has no value for it. It is not stored on the loot profile and is not synchronized as profile data.

While you are the coordinator of an announced Loot Helper session, you are in a raid, and no Raid Check has successfully started for that session, Spectrum inspects profile members who are in that raid. A party is not scanned. A complete, current observation that the shared preparation policy classifies as Unprepared sends the Pre-Raid Check missing-requirements whisper. That send does not depend on Enable Whispers During… → Pre-Raid Check. Prepared players, incomplete inspects, and stale observations do not send a whisper.

One missing-requirements contact per profile member per session is a hard user-facing invariant. Before Early Preparation, Pre-Raid Check, or Raid Check delivers that whisper, the current session coordinator grants an exclusive, session-scoped, coordinator-epoch-aware claim. The warned state is recorded only after the whisper is sent; unsuccessful claims are released or expire. Other admins learn about a recorded warning through a session notice, the initial session announcement, the coordinator heartbeat, and the session reannounce sent to someone joining an existing session. A client that accepted the session through that announcement uses the same session dedupe for Pre-Raid Check and Raid Check missing whispers. A new session starts with a clear warning list. Pre-Raid Check does not stop the background scan. The first Raid Check that successfully begins for the session does, and the scan stays off for the rest of that session. Combat pauses new inspect acquisition the same way Raid Check does; it does not by itself turn Early Preparation off or relax the complete-observation rule.

Early Preparation does not award points, Attendance, or Reward Pot changes, and it does not write a Raid Check presence log.

What gets recorded

Point Based awards are loot-point log entries with Raid Check as the author. Reward Pot awards are Attendance log entries with the same author. A Reward Pot deduction is a Reward Pot change with Raid Check as the author. Each settled Raid Check also writes one RAID_CHECK_PRESENCE log for the frozen group, roster, and players classified Prepared. Presence credit is independent of Prepared/Unprepared. Preparedness credit requires both presence and a Prepared classification from the current Raid Check equipment rules. If there is no matching announced session, those logs are saved locally and are not synchronized.

The Loot Helper roster temporarily hides the Att. and Prep. glance columns, but Raid Check still records the same presence and preparedness history. Neither metric is derived from loot points or Reward Pot Attendance. A player who was not on the roster and not in the group for a recorded check is omitted from that opportunity rather than marked absent. When those columns return, no recorded opportunities display as —, and presence logs written before preparedness was stored display — in Prep. rather than inventing a 0% history.

Run checks from Loot Helper → Session, or use /sf raidcheck pre and /sf raidcheck raid.

Running Raid Check more than once can award points or Attendance again and, in Reward Pot mode, deduct from the pot again.