How scoring works

Category weights

Throughput

Damage done per second (healing per second for healers), over whole seconds of the kill.

Interrupts

Successful interrupts. A count, ranked once the spec's field uses it.

Dispels & decurses

Successful dispels and decurses. A count, ranked once the spec's field uses it.

Avoidable damage taken

Total damage from this boss's curated list of avoidable abilities; less is better.

Damage taken

Damage taken per second; less is better.

Tank mitigation

How much of the time spent tanking had active mitigation up.

Mechanic execution

Boss-specific mechanics handled, scored out of 100.

Deaths & uptime

Active time percentage minus 100 points per death.

How your parse is calculated

1. 01

   We measure what happened first

   Each uploaded log is parsed into raw facts for every player in every boss fight: damage and healing done, interrupts, dispels and decurses, damage taken, avoidable damage taken (from a curated per-boss list of abilities you can dodge), tank mitigation, boss-specific mechanics, deaths, and active time. Raw facts are stored before anything is scored, and the report shows them immediately.

   Wipes are analyzed like kills but never scored. Private logs are never compared against anyone.

2. 02

   You are compared with your exact field

   Every raw fact becomes a percentile against your field: every other character's best public, canonical kill of the same boss, by the same spec, in the same phase (and, after a balance patch, the same partition of it), difficulty, and raid size, one kill per character. A Frost Mage is never measured against a Fury Warrior, and a 20-player kill never against a 40-player one. When the same fight was uploaded twice, only one copy counts.

   Your best kill is the one in the field; your other kills on the boss are measured against that same field but never count in it, so a bad pull changes neither your ranked kill nor anyone else's number.

   Throughput and damage taken are ranked per second of the kill, so a longer fight does not inflate or punish them. Avoidable damage stays a total: every avoidable hit is a mistake, not a rate.

3. 03

   How a percentile is ranked

   Magnitude categories (throughput, damage taken, avoidable damage, mitigation, mechanics, deaths and uptime) use a cumulative distribution: the best score is 100 and even the lowest kill gets a positive share, never a literal zero. A kill that is not your best is placed in the field as if it were one more kill in it.

   Count categories (interrupts and dispels) use a percent rank, where zero means “did it zero times”. They switch on for a spec only once at least 10% of its ranked kills on that boss record one; before that they are not evaluated for anyone, so a lucky self-dispel cannot lift one player above a field that never had the option. When everyone in a window has the same value, everyone scores 100.

4. 04

   Weights turn percentiles into one parse

   Your category percentiles are combined by weight into one composite: Composite = Σ (category percentile × category weight). Your parse (Today %) is where that composite ranks among your field's best kills. Weights are set per boss and per role by the RaidCraft team and published in full above.

   A category with 0% weight on a boss, or one that could not be evaluated for you, is left out and the remaining weights are renormalized, so you are never penalized for something that could not be measured. Deaths and uptime ranks a single score: active time percentage minus 100 points per death.

5. 05

   Limited data

   A percentile needs a field to compare against. When fewer than 50 players are ranked in a window, the parse is still shown but marked limited data: a 100 in a field of three is “best so far”, not “best ever”.

6. 06

   Today’s parse and the parse you earned

   Scores are recomputed every morning at 07:00 UTC, so a new upload shows its raw facts first and its percentiles after the next batch.

   Leaderboards rank the live parse (Today %), which moves as more logs join the field. The as-earned parse (Earned %) is frozen the first time a kill is ranked, so the number you screenshot does not decay next week. Profiles show both.

7. 07

   Only public canonical kills count

   Rankings, profiles, and guild scores are built only from public logs. A private log stays readable by its uploader but never ranks, never appears in search, and never changes anyone else’s percentile.