Nexus RaidOps
Changelog
Patch 0.9.31
CurrentTeam and Guild Recruiting Center
Makes recruiting easier to manage at the Team level and easier to scan at the Guild level, with structured class, spec, and role needs that automatically roll up into Guild recruiting.
Added a Guild Recruiting Center that brings each raid Team's active recruiting needs into one compact Guild view while preserving Team ownership of the underlying recruiting data.
Teams can enter structured recruiting needs by class, specialization, role, priority, quantity, roster placement, status, and note. Active needs automatically feed the Guild Recruiting Center, public recruiting directory, and generated recruiting posts.
Specific class or specialization requests use World of Warcraft class visuals, while broad Tank, Healer, Melee DPS, Ranged DPS, general DPS, Support, and Flex needs use role-based symbols.
Guild recruiting now uses compact Team cards with current progression, Team label, schedule, readiness, active opening count, and stacked recruiting needs so leadership can see the Guild's recruiting picture at a glance.
The Guild Recruiting Center now summarizes total openings and current DPS, Healer, and Tank demand across raid Teams before leadership reviews individual Team cards.
Team Recruiting now leads with Current Recruiting Needs, keeps active openings in compact editable rows, and separates Filled/Closed and Paused needs into collapsed sections.
Guild-only controls such as Mega Guild post inclusion and Team ordering remain in the Guild workspace, while Team leaders manage Team-owned schedules, labels, requirements, contacts, public listing details, and recruiting openings from the Team page.
Recruiting is now easy to find from My Team, Team Overview, My Guild, and Guild Overview instead of being buried in settings or the More menu.
Team Recruiting no longer redirects Guild Owners and Administrators into the Guild Recruiting Center. Team recruiting stays Team-scoped and the saved data rolls up to the Guild automatically.
The Add Recruiting Need workflow now opens full-width beneath the recruiting header instead of floating in a right-side column, and its Status, Priority, Class, Spec, Role, Number Needed, Placement, Note, and action controls align to one consistent grid.
Existing recruiting rows no longer render with nested double borders, and layout regression coverage now protects the compact Team recruiting structure.
Patch 0.9.30
Guild and Team raid progression
Adds Warcraft Logs-backed Guild and Team progression dashboards with boss-by-boss progress, current targets, progression pace, rankings, and cross-Team comparison.
Guild Overview now includes a Progress area with separate GUILD and TEAMS views so leadership can see overall Guild raid progress and compare each NRO raid Team without leaving the Guild workspace.
Team Overview now includes a dedicated Team Progress section sourced from that Team's imported Warcraft Logs raid history.
Normal, Heroic, and Mythic progress are tracked separately with segmented boss bars, boss kill totals, current-reset +X THIS WEEK indicators, boss portraits, and latest progression context.
Progress cards show the current unbeaten progression boss and the best recorded boss-health percentage from Warcraft Logs pull history, while completed difficulties are clearly marked Complete.
Boss-kill milestone history shows how progression moved over time, including the date each new kill advanced the Team's raid total.
Progression pace calculates average days per new boss kill and compares the latest interval with the Team's own recent cadence, using Faster, Steady, or Slower labels only when enough evidence exists.
Guild Team Comparison identifies the Team furthest ahead for each raid, shows each Team's current boss, best pull, pace, and weekly gains, and marks the fastest evidenced progression pace.
Warcraft Logs World, Region, and Realm progress ranks appear when WCL returns a valid rank for the linked parent Guild or raid Team. Teams without a WCL rank continue to render normally without fabricated values.
Raid Nights now persist the Warcraft Logs zone ID and raid name so progression groups by the actual WCL raid instead of relying on report titles or encounter-name inference.
Historical Warcraft Logs raid data was backfilled after deployment: 88 existing Raid Nights across 69 unique reports received their WCL raid-zone identity with zero failures and zero remaining missing-zone records.
The progression release includes dedicated contract and behavioral regression coverage for zone grouping, weekly kills, current targets, milestone history, pace calculations, ranking response shape, Team comparisons, and backfill safeguards.
Patch 0.9.29
Scoring integrity, raid QoL, and Mechanical reliability
Brings the roster rollout through production hardening, corrects the core score evidence paths, repairs recurring Mechanical failures, and makes day-to-day raid review clearer and faster.
The unified roster now carries historical weekly rosters forward safely, routes old lineup links into the current planner, preserves departed or unmapped players for review, and keeps copied raid plans isolated by date.
Raid leaders can edit planned class, specialization, and role directly in roster rows, including confirmed Flex alternatives, while cached Battle.net portraits and saved score evidence stay visible in the same workspace.
Roster score columns now align consistently, use the normalized NRO score colors, and match the seasonal score presentation across the site.
Published roster sharing to Discord is cleaner and can be resent when needed, while roster profile text and encoding issues were repaired.
Battle.net and Discord provider sign-in now use the intended OAuth scopes and a cleaner provider-first sign-in flow.
Role Performance now requests Warcraft Logs parse percentiles in Parse comparison mode and the current report window, preventing tier-best ranking percentiles from appearing as the player's actual fight parse.
Role Performance evidence is more tightly scoped, and activity remains supporting context instead of being allowed to distort the formal role score.
Consistency was rebuilt around comparable pull evidence, with corrected score-column alignment and full-width detail rows for easier review.
Assignment Execution now grades timing by how far an assigned action occurred from its expected window instead of reducing the result to a simple pass or fail.
Adaptability was replaced by a clearer Improvement Trend view that centers progress on the player's own prior average and comparable raid evidence.
Mechanic Parse cards are more compact and now compare a raid night's mechanic performance with the player's broader average; reviewed role-specific exceptions, including tank handling where appropriate, are preserved.
Utility scoring now requires validated evidence, explains its evidence accounting, and limits breadth credit to capabilities the character could actually provide.
Mechanical evidence queries were bounded to keep large raid analyses from doing unnecessary work while preserving the validated evidence contract.
The first Mechanical persistence repair added pre-finalization reconciliation, terminal handling for deterministic integrity failures, Consistency recomputation, and a Raider.IO transient-failure circuit breaker with Blizzard fallback.
NRO can queue Warcraft Logs raid reports for server-side bulk reanalysis, so incident recovery does not require each raid leader or player to manually rerun old reports.
The recurring Mechanical Alpha health failure was traced to auto-classified fallback results that lacked matching persisted opportunity and evidence rows. The fallback path now persists canonical Mechanical evidence and reconciles it before finalization.
Finalization no longer depends on the expired long-running transaction pattern that caused repaired Mechanical runs to fail late. The production canary preserved all 12,340 expected Mechanical opportunity/evidence row pairs.
My NRO's performance gate and focused evidence reads were corrected so personal views remain consistent with the repaired production scorecard path.
Season scorecard hydration now avoids rebuilding large nested SQL objects for every opportunity row, reducing cold-read overhead without changing scoring formulas or eligibility.
A plain-English Getting Started guide now walks players and raid leaders from account creation through Guild and Team setup, roster cleanup, Warcraft Logs import, evaluation, scoring, and roster publication, with current screen examples and score explanations.
Team members can reach published lineups through permission-aware navigation without being shown leadership-only creation actions.
Team pages default to the latest evaluated and published raid difficulty where appropriate and expose season results instead of opening on stale or less relevant difficulty context.
Category score pages expose the evidence behind the result, and Mechanical N/E now explains why a score was withheld instead of leaving the user with an unexplained missing value.
Loot & Vault activity now resets on the actual World of Warcraft regional weekly boundary, and Needs Attention counts link to actionable issues instead of acting as dead-end totals.
Player development goals are shared consistently between Growth and Coaching, score context is easier to see, and anonymous peer context can be shown without exposing another player's identity.
Raid workflows now favor the latest completed analysis, support automatic import follow-through, and reduce repeated manual steps after a log has already entered NRO.
The global navigation now stays above page menus, and imported raid progress is visually distinguished from an actually published result.
Normal Nymrissa contact-only mechanic coverage was corrected so valid contact-based evidence is not lost from Mechanic scoring.
Patch 0.9.28
One workspace for raid rosters
Plan Heroic and Mythic segments, compare saved evidence, publish clear player decisions, and record what happens during the raid.
Copy a 27-player Heroic segment into Mythic and work through the seven cuts in one compact workspace, with planned specs, composition coverage, leadership controls, and mobile movement controls.
Deterministic roster suggestions are reviewed before applying. NRO generates Active and Bench reasons automatically, keeps N/E as uncertainty, and labels Heroic evidence used for Mythic planning.
Preview each player's exact shared reason, publish immutable roster versions, and share that same version to Discord. My NRO shows current published status and original decision history.
Raid execution records late arrivals, no-shows, Bench activation, temporary replacements, and segment transitions while preserving the original plan and existing attendance reviews.
Existing saved plans, manual spec overrides, weekly availability, boss responsibilities, and cooldown imports carry forward. Reusable composition profiles support different role targets and explicit encounter exceptions.
Patch 0.9.27
Sign in with Battle.net or Discord
Removes the separate NRO registration step and gives players a faster provider-first onboarding flow.
New and returning players can continue directly with Battle.net or Discord. The same button creates a normal NRO account when needed or opens the existing account when that provider identity is already connected.
Battle.net and Discord can both be connected to the same canonical NRO account through Settings without silently merging accounts from matching emails, names, BattleTags, Discord names, or characters.
Battle.net-first players can synchronize their World of Warcraft characters and choose a Main during onboarding. Discord-first players can connect Battle.net immediately or continue and do it later.
Provider sign-in preserves invitation destinations, shows readable cancellation and collision errors, and gives new provider-created accounts only normal default access.
Patch 0.9.26
Faster reports and safer processing
Restores one blocked raid analysis, makes core report pages consistently faster, and hardens production telemetry and builds.
Raid imports now carry their Team Season from the selected lineup, and the affected failed analysis is retried only after its source season is unambiguous.
My NRO and Team difficulty scorecards reuse approved published evidence instead of rebuilding the full season graph on every visit.
Encounter pages and compact custom report links read the immutable snapshots already prepared for them, with live fallbacks for older data.
Content Security Policy reports accept a larger bounded payload, redact and cap stored fields, and suppress repeated violations.
Railway builds clear only the transient Turbopack database before compiling, preventing stale-cache file removal failures.
Patch 0.9.25
Build and share your raid roster
Adds AI roster suggestions, flexible raid specs, and Discord sharing directly from the roster workspace.
AI roster suggestions use saved NRO player scores, required buffs and utility, roster size, role targets, availability, and players you choose to keep. Review the proposed team, explanations, and alternates before saving it.
Share a saved roster proposal or published roster to a Discord channel you choose. Preview the character names, planned specs, and role groups before sending. Proposals are clearly labelled and do not publish a lineup.
Raid leaders can edit planned specs and roles in the player pool and composition boards. A player's logout spec no longer dictates their raid build; Guardian can remain Tank while that character plays another spec outside raid.
The roster workspace uses compact player rows and separate tank, healer, melee, ranged, and flex groups so larger teams are easier to compare.
Roster suggestions read evidence already saved in NRO without another Warcraft Logs import. Missing scores stay N/E, and Heroic evidence used for a Mythic proposal stays clearly labelled.
Patch 0.9.24
Auditable post-raid scores
Repairs category arithmetic and routing, makes incomplete evidence explicit, and freezes difficulty-specific Discord scorecards at send time.
Consistency headlines now preserve the approved weighted Execution, Performance, and Dependable Floor calculation. Missing required components remain N/E.
Adaptability now opens on its own category route and records the earlier and later Raid Night, date, difficulty, and source log for every comparison.
Adaptability history is restricted to the same Team, player, metric, and raid difficulty, and seasonal confidence cannot exceed the source run's evidence label.
Utility coverage now distinguishes participants, players with a validated contribution, provisional scores, and N/E results.
Mechanical Execution now reports a resolver coverage warning when source signals exist but no validated player-owned opportunities can be produced. Scores remain N/E.
Discord season reports now use a persisted immutable snapshot bound to the selected difficulty and carry a stable score fingerprint through every shared-report link.
Patch 0.9.23
Cleaner decisions at the right difficulty
Separates raid decisions by difficulty, adds evidence-bound coaching and Boss Performance, and makes the Team workspace faster to navigate and share.
Role Performance now defers and retries transient Warcraft Logs ranking failures before an evaluation can become immutable. Genuine source gaps remain N/E instead of becoming invented scores.
NRO Coach can generate a concise Coach's Read on an individual encounter from the deterministic receipts already on the page. The coach explains the evidence without changing NRO's scores.
Existing Team Coaching follow-up and active development goals remain in the Team workflow, while repeated coaching summaries and other duplicate overview content were removed.
Normal, Heroic, and Mythic season scores and latest-raid decisions are separated so one difficulty cannot drive lineup decisions for another. Needs attention and recent raid history still show the whole Team.
Team difficulty switching now updates only season scores and latest-raid decisions, keeps the rest of the Team overview mounted, preloads safe difficulty summaries, and prevents slower requests from winning a rapid switch.
Boss Performance shows every boss for the season at the selected difficulty, including pulls to first kill, kills, raid-night coverage, best remaining health, and pull-by-pull progression.
Raid leaders can share Boss Performance to Discord and choose any writable text or announcement channel for each report send. The saved Team channel stays unchanged unless they explicitly save a new default.
Weekly Great Vault, Mythic+, and Delves information now lives together under Loot & Vaults, and old Team routes forward to the consolidated workspace.
The side navigation and duplicate command-center panels were replaced by a compact top navigation with My NRO, My Team, My Guild, and account menus.
The account menu now shows the current Main character's portrait and name and lets the player switch their Main without leaving the page.
Boss cards no longer stretch 56-pixel encounter thumbnails across the full banner; portraits stay at native size with responsive cropping so desktop, mobile, and high-DPI layouts avoid visible blocky upscaling.
Mechanic Performance now applies reviewed encounter rules to historical imports, shows actual multi-pull avoidable failures and eligible successes, and explains when evidence is not scoreable instead of presenting a row of unexplained zeroes.
The Player Evidence Matrix restores Warcraft Logs parses when ranking rows omit server metadata through a conservative unique-name match. Not applicable, not ranked, missing metadata, and provider failure are now distinct states.
Player Episode Performance, the Player Evidence Matrix, and score evidence pages now lead with readable findings and next actions while keeping the complete technical audit fields behind progressive disclosure.
Team Coaching now uses one responsive card per player with inline note, development-goal, leadership-assessment, and history workflows. Player selection, privacy, evidence links, validation, permissions, and audit history stay intact.
Raid Night Progression now pairs every encounter's chronological pull table with an accessible boss-health line graph, including kill, duration, death, and missing-health context.
Attendance Review no longer asks leaders to enter Minutes Attended. Existing stored history is preserved while attendance result, minutes late, source context, and leadership notes remain editable.
My NRO Raid Nights now uses a clear View raid night action for the internal NRO page and no longer exposes backend provider enum labels in the player-facing list.
Patch 0.9.22
Growth follows the player
Makes My Growth use the raid logs where a player actually appeared, whether the log was imported personally or by one of their Teams.
My Growth now includes analyzed raid nights from every Team where the player's NRO-linked character appeared. The player does not need to upload the same log again.
NRO can recognize the player through their connected account or their linked Battle.net character, so the same person can be followed across different Team rosters.
Growth history now labels whether each result came from a personal upload or a Team log.
The same Warcraft Logs report counts once when it was imported into both a personal workspace and a Team workspace, so it cannot create a duplicate trend point.
Team logs contribute only that player's scores and pull coverage to My Growth. Officer notes and other players' results stay private to the Team.
Players with access to the source Team can open its full raid review. Older Team results can still contribute a personal growth summary after Team access ends.
Patch 0.9.21
Trustworthy personal growth scores
Makes My Growth count real raid nights, show everything imported from the latest log, and withhold scores that are not backed by enough information.
Recalculating the same raid no longer appears as several different analyses or creates a fake score trend.
My Growth now shows every boss and pull found in the latest raid log, plus which of those pulls actually recorded the player's character and can affect personal scores.
Role Performance now shows N/E when Warcraft Logs has not provided a comparable role ranking. Activity data remains available as context instead of becoming an unfair zero.
Pull-wide damage totals without exact event timing no longer become confirmed mechanic failures or lower a player's score.
Attending a pull without a confirmed utility contribution no longer creates a placeholder score of 50.
Score cards now say whether evidence is missing or whether another distinct Raid Night is needed to measure change.
Existing private draft scores created by the affected rules are returned to N/E during deployment without changing published historical reports.
Patch 0.9.20
Cleaner raid and Mythic+ reviews
Straightens out roster layouts, makes raid findings easier to scan, and turns personal Mythic+ logs into practical run reviews.
Roster and lineup columns now keep the same widths, so player, character, class, role, and availability information lines up correctly.
Wowhead mouseover cards can load their official styles again instead of spilling large unformatted text over the page.
The post-raid report now matches the rest of the Raid Night cards and uses plain wording for successful interrupt coverage.
Discord copies now include common wipe patterns, improvements worth keeping, assignment follow-up, and useful phase timing changes.
Automated pull-review cards have more breathing room and start closed, so officers can open only the findings they want to inspect.
Personal Mythic+ reports now explain what went well, what needs attention, and the three best things to work on next.
Trash-only fights are left out of the Mythic+ review. Dungeon runs now show completion, time, player deaths, interrupts, and dispels.
Re-importing a Mythic+ report adds the event evidence used by the new review while keeping older saved reports safe.
Patch 0.9.19
Personal Mythic+ log review
Moves Mythic+ log review out of raid-team operations so every NRO player can use it from their personal workspace.
M+ Log Analysis now lives in the Personal section and is available to every active NRO account.
Imported Mythic+ runs belong to the person who imported them instead of a raid team.
The old team M+ address now sends users to the new personal page, so saved links do not lead to a dead end.
Warcraft Logs reports marked with dungeon difficulty 10 or Challenge Mode are now correctly recognized as Mythic+ reports.
Existing M+ imports keep their original team information for history while personal ownership controls access going forward.
Personal imports are private, repeat imports refresh the same run, and each import leaves an account audit record.
Patch 0.9.18
Workflow polish and reliability
Makes the complete raid planning, review, reporting, and player improvement workflow safer and easier to operate.
Assignment plans, analysis requests, and import retries now leave a clear officer audit record.
Private coaching and encounter review now show dedicated loading screens and useful retry pages if something fails.
The post-raid report works better on small screens and announces copy-to-clipboard success to screen readers.
New database indexes speed up player goal history and Raid Night processing lookups.
Import retries remain limited to failed or cancelled jobs and resume saved work without starting two jobs for the same Raid Night.
Added a fictional demo Raid Night seed and an end-to-end workflow check for quick release validation.
Regression checks now protect automated wipe conclusions, assignment blockers, privacy rules, permissions, and the new operational safeguards.
Patch 0.9.17
Player improvement loop
Gives each player a small, private set of practical goals backed by real raid evidence.
Players now have a private review page that shows only feedback leadership chose to share with them.
Each player can have up to three active improvement goals, keeping the focus clear and achievable.
Goals can name an owner, set a target date, and link directly to the exact pull and time that supports the feedback.
Officers can track each goal as Still inconsistent, Improved, or Resolved.
Published scores continue to show change across raid nights alongside the player's current goals.
Leadership-only goals and notes remain hidden from the player page and public raid reports.
Patch 0.9.16
Post-raid report
Turns the detailed Raid Night evidence into a short report an officer can review and share within a few minutes.
Raid Night Overview now includes a concise officer report covering progress, best pulls, kills, and the most common wipe categories.
The report calls out assignments missed on multiple pulls and meaningful changes in phase timing.
Successful mechanics and other evidence-backed improvements are included so the report preserves what the team should keep doing.
Every report ends with exactly three practical priorities for the next raid.
Officers can preview and copy a Discord-ready version or publish the report through the existing protected Raid Night share link.
Detailed findings remain available below the short report when officers need to verify the supporting evidence.
Patch 0.9.15
Assignment-aware review
Compares the saved encounter plan with what actually happened while checking whether each responsibility was possible before judging it.
Assignments can now save a primary player, backup player, spell, expected time, and allowed early or late window.
Encounter review now reports Completed, Completed by backup, Missed, Blocked by earlier event, Unverifiable, or Plan needs review for planned responsibilities.
NRO checks whether the assigned player was in the pull and alive before the expected action before calling it missed.
The review recognizes when the saved backup performed the action inside the expected window.
Incomplete and duplicate plan entries are sent back for plan review instead of being treated as player mistakes.
Ambiguous mechanic and dispel evidence remains Unverifiable so missing data does not become automatic blame.
Patch 0.9.14
Automated wipe analysis
Helps raid leaders understand why attempts ended without treating every death as a separate mistake.
NRO now identifies the first supported failure in each wipe and separates it from deaths that happened during the later collapse.
Pulls are grouped when the same mechanic appears to start the failure, making repeated problems easier to spot.
Cooldown plans now produce clear early, late, already-used, and missing cooldown findings for each pull.
Added boss-health progression and phase consistency findings across pulls.
Every automated finding explains what happened, when it happened, the evidence behind it, confidence, and the recommended next action.
Officers can open the exact evidence and correct a mechanic classification from the review.
Interrupt and dispel misses stay marked Not evaluated until the imported data proves a real missed opportunity, preventing unsupported blame.
Patch 0.9.13
Pull comparison workspace
Gives raid leaders one place to compare attempts and understand what happened at each point in the fight.
Raid leaders can compare any two pulls by duration, result, players, deaths, and successful interrupts.
Each pull now has one timeline for phase changes, deaths, successful interrupts, and officer notes.
Timeline times can be copied as links that reopen the same pull and exact moment for another reviewer.
Officers can leave a private note on a pull and optionally attach it to a specific time in the fight.
The Pulls tab now works as a review workspace while the Mechanics and Assignments tabs keep the deeper failure and cooldown evidence.
Patch 0.9.12
Visible and recoverable raid imports
Makes it easier to follow a Warcraft Logs import after leaving the import screen and recover when server processing does not finish.
Raid History now shows whether each saved raid is waiting, processing, ready, or needs another attempt.
Active imports show the server step currently being worked on, such as raid structure, combat events, deaths, or evaluation.
Raid leaders can restart failed or cancelled processing from Raid History without importing the same Warcraft Logs report again.
The Raid History summary now calls out active imports and raids that need attention.
Retries keep completed server steps when safe and restart from the first incomplete part of the raid analysis.
Patch 0.9.11
Encounter assignment planner
Lets raid leaders prepare each boss plan before raid and give every responsibility a clear owner and order.
Added lineup assignments for mechanics, interrupts, dispels, soaks, defensives, healing cooldowns, utility, and other responsibilities.
Assignments can be placed in execution order and include the encounter, difficulty, player, and timing or instructions.
Raid leaders can copy an earlier lineup's assignment plan as a reusable starting point for the next raid.
Added one-click copying of a compact assignment note for Discord or an in-game raid note.
Copied plans keep assignments for players who are still on the lineup and clearly leave other responsibilities unassigned for review.
Patch 0.9.10
Raid readiness dashboard
Gives raid leaders one clear place to see whether an upcoming roster is ready and what still needs attention.
Added a readiness dashboard to each raid lineup with a simple Ready or At risk result.
Players can now answer Available, Maybe, or Unavailable for a raid, and raid leaders can update responses when needed.
Added clear warnings for missing players, unanswered availability, unavailable players, role gaps, missing characters, and missing raid buffs or boss debuffs.
The lineup now shows how many bench players are available as backups and keeps availability controls easy to use on smaller screens.
Patch 0.9.09
Raid planning foundation
Adds the shared information NRO needs to plan a raid and connect that plan to the raid results afterward.
Raid plans can now save whether each player is available, unsure, unavailable, or has not answered yet.
Raid leaders can now save mechanic, interrupt, dispel, soak, defensive, healing cooldown, utility, and other assignments for each encounter.
Officers can now save internal notes for a planned raid, completed Raid Night, encounter, or individual pull.
The raid data foundation now connects planning, the selected roster and bench, imported encounters and pulls, player goals, and officer review information.
Patch 0.9.08
Player growth and controlled sharing
Turns private analysis into an ongoing player growth experience while keeping every share and Team connection under the player's control.
Added My Growth with category trends, recent private analysis history, personal goals, and evidence-based milestones.
Added revocable 30-day links that share one selected player review without exposing other logs, goals, notifications, or account details.
Raid leaders can request a Team connection from a player-shared review, while the player keeps the final Accept or Decline decision.
Accepting a Team invitation connects the player's account and current Battle.net Main to the Team roster in one step.
Added focused in-app notifications for goals, private links, milestones, and Team connection decisions.
Patch 0.9.07
Private player log analysis
Lets an individual player run a full NRO review from Warcraft Logs without waiting for a Guild or Team leader to import and publish the raid.
Added Analyze My Log so a player can paste a Warcraft Logs report, securely match one of their linked Battle.net characters, and queue the existing durable NRO analysis worker.
Added owner-only personal analysis history and results with strengths, improvement focus, category scores, confidence, and evidence coverage.
Personal analysis uses the same versioned NRO methodology and resumable server checkpoints as Team analysis instead of a simplified preview calculation.
Private analysis workspaces stay hidden from Guild setup, Team navigation, and active-Team counts while preserving a strict account ownership boundary.
Players no longer need a Guild or Team connection before getting useful NRO feedback from their own Warcraft Logs report.
Patch 0.9.06
Player-first personal experience
Makes the signed-in NRO experience useful to an individual player before their Guild or raid Team adopts the leadership workspace.
Added My NRO with a clear first-use path, published performance, current strength, improvement focus, character context, and one recommended next action.
Rebuilt the signed-in Home around personal performance, characters, coaching, and weekly readiness while keeping Guild and Team operations available as a secondary workspace.
Players without a Guild can now start with Battle.net, choose a Main, and preview the value of a player report instead of being forced into leadership setup.
My NRO now loads only published evaluation runs, so drafts, reviews, withheld results, internal notes, and withdrawn publications cannot appear on a player dashboard.
Patch 0.9.05
Adaptability & Improvement evaluation
Adds the sixth Nexus RaidOps evaluation category with conservative cross-night evidence rules while preserving every earlier methodology as an immutable historical version.
Added Adaptability & Improvement scoring from comparable Mechanical Execution and Assignment Execution evidence for the same player across raid nights.
Added Adaptability review detail showing improved, stable, and regressed trends, confidence, and the underlying earlier-versus-later evidence used for the result.
Missing or non-comparable evidence remains Not Evaluated, confidence stays separate from performance, and one isolated later failure cannot create a negative Adaptability judgment.
Venomous Abyss evaluations now preserve the frozen Alpha.10 result and promote it into a new Alpha.11 child run for Adaptability instead of rewriting the previous methodology.
Both one-click and staged Raid Night evaluation flows now finish on the Alpha.11 result, and published Team evaluations include Adaptability coverage and player scores.
Alpha.11 promotion recovery no longer treats an incomplete prior child run as finished; a retry can safely create a fresh immutable child from the Alpha.10 source run.
Patch 0.9.04
Evaluation review and publication governance
Completes the leadership decision path between a calculated evaluation and the player-visible published result.
Added Return for Review so leadership can send an evaluation back with a required reason instead of approving it prematurely.
Added Withhold Evaluation for approved results that leadership does not want published.
Added Withdraw Publication for already-published evaluations, with a required reason and audit history.
Published and superseded evaluations are treated as historical snapshots; corrections must move through recalculation rather than silently rewriting published history.
Standardized evaluation governance controls so the primary decision stays visible and secondary actions live under More.
Patch 0.9.03
Private alpha safety and feedback
Adds the required private-alpha acknowledgment and a complete in-site path for testers to report problems and communicate with NRO administration.
Added a versioned Private Alpha disclosure that must be acknowledged before an active tester enters the protected workspace.
Added Report an Issue and My Reports with contextual Guild and Team information validated on the server.
Added urgent privacy/access reporting and a Site Admin feedback queue with status triage, tester-visible replies, and private internal notes.
Alpha acknowledgments now record the user, policy version, time, fixed source, and site-private-alpha scope, and a future policy version automatically requires a new acknowledgment.
Feedback report ownership and administration paths are permission-checked so testers cannot open another tester's report by changing the reference.
Patch 0.9.02
Site consistency and changelog
Continues the site-wide cleanup so the pages players and raid leaders use most follow the same compact, predictable layout.
Added a Changelog page and a permanent Changelog link at the bottom of the sidebar.
Rebuilt Operations Home around the current work queue, compact Team rows, and recent Raid Nights instead of large dashboard cards.
Standardized My Characters and Battle.net character management with compact character rows, smaller status summaries, and technical sync detail moved lower on the page.
Standardized Guild Overview, Guild People, Raid Teams, Invitations, Activity, and Integrations into the same compact leadership workflow.
Standardized Raid Nights into a compact history view instead of a wall of large cards.
Standardized Team Evaluations so coverage gaps are clearly separated from performance and technical version detail is no longer front-and-center.
Standardized Team Coaching and individual Coaching Profiles so current coaching priorities stay visible and history stays collapsed.
Standardized My Coaching so Work On, Doing Well, current scores, goals, and leader feedback follow the same page hierarchy.
Standardized Team Administration, Team Access, and Team People with compact status indicators, searchable rows, one primary action, and secondary workflows grouped under More.
Corrected permission-aware navigation so Team Leads can reach Raid Teams while restricted Team actions are no longer offered to roles that cannot use them.
Removed misleading or inaccessible links and corrected several coverage, activity, and Team-access labels found during the 0.9.02 review.
Moved low-priority technical and historical details farther down pages or into collapsed sections where practical.
Patch 0.9.01
Administration, settings, and raid-team command center
Introduced the first site-wide administration tools and began the full Nexus RaidOps interface standardization.
Added global Site Administration with site-wide account search, account review, suspension, banning, removal, and moderation history.
Added personal Settings for account name, Battle.net status, sign-in providers, sessions, and sign out everywhere.
Rebuilt Team Overview as a raid-leader command center focused on raid analysis, blockers, progression, evaluations, and coaching.
Standardized the Team Roster with smaller readiness indicators, one primary action, and secondary actions grouped under More.
Added shared compact page, card, section, disclosure, and action-menu standards for the rest of the site conversion.