Nexus RaidOps

Private Alpha Guide

Current Alpha

This private alpha validates the real raid-leader workflow: roster management, Warcraft Logs import, Raid Night review, player evaluation, leadership review, and published results. Expect rough edges and incomplete category coverage while we test the product with real raid teams.

Home Getting Started How Scores Work How to Report a Bug

Core workflow

What we want testers to exercise

Build or review the roster

Confirm Raiders, Trials, Reserves, characters, and player identities. Use roster reconciliation when an imported Warcraft Logs character is not linked to the correct NRO player.

Import a Warcraft Logs report

Use Import Raid, review the report, classify participants, and save the Raid Night. The saved Raid Night becomes the source for evidence and evaluation.

Review the Raid Night

Open encounters, evidence, mechanics, assignments, and participant details. Resolve identity or evidence issues before relying on the evaluation.

Run the evaluation

Create or recalculate the Evaluation Run from the Raid Night. NRO processes supported evidence, scores, and cross-night improvement without rewriting the original report.

Review and approve

Required review items must be resolved before leadership approval becomes available. Approval and publication are separate governance actions.

Review published results

Use Evaluations to review published Team coverage and Player results. N/E is shown whenever eligible evidence is not strong enough for a fair score.

Evaluation coverage

What NRO evaluates today

Mechanical Execution

Automatic

Automatic scoring from validated mechanic opportunities.

Assignment Execution

Automatic

Automatic scoring when assignment ownership and compliance are supported.

Role Performance

Partial

Role-scoped implementation. Coverage depends on supported role evidence.

Utility & Team Contribution

Automatic when supported

Confirmed player-owned opportunities score automatically. Shared needs, incomplete capability evidence, strategy-dependent actions, and assignment-owned work are excluded instead of becoming failures.

Consistency

Automatic

Automatic scoring when sufficient comparable evidence exists.

Adaptability & Improvement

Visual trend

Shows the player's historical Mechanical average at the center of a relative speedometer, with the current result moving left or right by its +X.X or -X.X difference. It is not a sixth scored category.

Terminology

NRO glossary

These terms mean the same thing everywhere in NRO. Capitalization identifies a specific NRO workspace, record, or workflow.

Guild: The organization that owns people, Raid Teams, invitations, and shared integrations.
Team: A Guild's specific raid group, with its own roster, permissions, Raid Nights, evaluations, and coaching.
Raid Night: One saved Warcraft Logs report and its NRO review, evidence, and evaluation workflow.
Encounter: All pulls against one boss within a Raid Night.
Pull: One attempt against an encounter boss.
Player: The person represented in NRO; a Player may have one or more Characters.
Character: A World of Warcraft character linked to a Player and optionally used on a Team roster.
Evaluation Run: A versioned calculation of player evidence and scores for a Team and Raid Night.
Evidence: Imported or derived facts that support an evaluation result without replacing the original Warcraft Logs data.
Review Queue: Evidence that requires a leadership decision before it can affect player scoring.
Leadership Decision: An audited classification made by an authorized Team leader, including a structured reason and written notes.
Systemic Pattern: A result affecting the raid broadly enough that strategy, ownership, data quality, or the mechanic definition needs review before personal scoring.
N/E: Not Evaluated. NRO does not have enough eligible evidence to issue a fair score.

Recovery

If an evaluation fails

NRO will show an Evaluation Failed state, the stored failure message, and a reference code when one is available. Use Retry Evaluation from the Raid Night after correcting any obvious input or evidence issue.

If retrying does not resolve the problem, include the failure reference and evaluation Run ID in your bug report.

Expected alpha behavior

Not every empty score is a bug

Some players will be N/E or unscored when NRO does not have enough eligible evidence. Role Performance remains partial, and categories stay N/E when the underlying evidence is insufficient. Adaptability & Improvement is shown separately as a Mechanical trend visual rather than as a sixth score.

Private-alpha feedback

Report problems with enough detail to reproduce them

Send the report through the private-alpha feedback channel provided by your NRO administrator. Include the items below whenever they apply.

What you were trying to do
What you expected to happen
What actually happened
The page or screen where it happened
Raid Night ID or evaluation Run ID when visible
Warcraft Logs report code when the issue involves an import
Failure reference code when NRO displays one
A screenshot if the issue is visual or difficult to describe

Suggested report format

Area:
What I was doing:
Expected:
Actual:
Raid Night ID:
Evaluation Run ID:
WCL report code:
Failure reference:
Screenshot / additional notes: