How it was checked
Every number on this site was read from Warcraft Logs or rebuilt from its dated records. The audit worked from scratch and only compared against older numbers once its own were final. This page explains how, and how to check any of it yourself.
Where the numbers come from
Warcraft Logs is the site raiders upload their combat logs to. It ranks every kill: each player's healing or damage per second on each boss becomes a parse, and parses are ranked on boards, one per boss, class and spec, difficulty and raid size. All-Star Points sum a player's standing across a raid's bosses.
The audit read Warcraft Logs through its public API and saved the exact responses behind every receipt. It counts each raid on its hardest difficulty, at the raid size players competed at, in the phase that raid was current. Boards for larger, non-competitive raid sizes are left out. A raid counts only while it was the current raid.
Mortivius healed as a mage, a spec Warcraft Logs ranks on its own Mage-Healer board. Every ranking on this site says what it ranks against: the Mage-Healer board, all healer classes pooled together, or complete-raid HPS.
Official, reconstructed or captured
Every figure carries one of these labels, everywhere it appears. The label never relies on color alone.
- Official
- Read straight from a current value of its record keeper: Warcraft Logs, and for Classic and Retail also Blizzard's armory and Hall of Fame, and WoWProgress for older guild ranks. An All-Star total, a rank on a board today, a speed rank, an achievement's date. Sums and counts of official values stay official, and say so. Official figures are gold.
- Reconstructed
- Derived from timestamped parse histories, because Warcraft Logs doesn't keep old boards. "Rank-1 at the time" is the main example, and a standing at a past moment is another (below). Reconstructed figures are silver, and never presented as official values.
- Captured
- A value a record keeper showed at the time, kept by a dated screenshot or an Internet Archive copy that agrees with what survives. The screenshot or copy is always shown with it, today's standing is given beside it, and it never replaces a current official value (below). Captured figures are jade.
- Unprovable
- A figure the surviving data can't settle. It never appears as a figure outside the receipts page, where its note says why and what would settle it.
What "rank-1 at the time" means
A parse was rank-1 at the time if, when that kill ended, no surviving ranked parse on the same board was higher. That includes parses from the same kill and his own earlier ones. An equal amount doesn't beat it, and every tie is flagged.
Warcraft Logs also stamps each parse with the percentile it had when the site first ranked it. A stamp at the very top of the scale means Warcraft Logs itself ranked the parse first at that moment. The audit's headline counts include a parse only when both measures agree that it was rank-1. Every case where they disagree is listed with its cause.
For the all-healers board, the audit pools the healer spec boards. Warcraft Logs' own class-free board isn't used, because it mixes in damage specs. Where an all-healers case can't be settled, the count is given as a range.
The complete-raid index
A complete-raid parse scores a healer over a whole clear of a raid, not one boss. For each raid, the index takes his best complete-raid HPS as a percentage of that raid's top complete-raid HPS across every healer spec. Then it averages those percentages over every raid with complete-raid rankings. Zul'Gurub has none, and a raid without a ranked clear would count as zero.
Every input is an official Warcraft Logs value: each clear's HPS and each board's top clear. Scarlet Enclave is read at the season's end, so the index is labeled reconstructed. Every healer is scored the same way, so the index compares careers fairly across classes. A second reading compares him only with the top of the Mage-Healer board; both are in the receipt, with the numbers raid by raid.
Standings at a past moment
Warcraft Logs shows All-Star standings only as they are today. When a figure needs a standing from the past, such as where he stood the night he retired, the audit rebuilds each boss board as it was at that moment: today's board, cut at that moment, with every character whose best came later read from their own dated history.
It then scores the rebuilt boards with Warcraft Logs' own All-Stars formula, which it first identified and checked against today's official values on every board it read. Where Warcraft Logs' daily history of a board brackets the moment, the rebuild is pinned to it. A rebuilt standing is labeled reconstructed, and when rivals' missing records leave room, it is printed as a range rather than a single place.
Screenshots from the time
Warcraft Logs keeps no old boards, so a standing it showed years ago survives only where someone saved it. Mortivius kept screenshots. One of them can carry a receipt, labeled captured, when the audit can date it and it agrees with the surviving logs: its date comes from the phone's clock written into the file, or from the kills its own values match, and every value on it is checked against the parses Warcraft Logs still holds.
A captured figure records something Warcraft Logs no longer shows, such as who led a board on a given night. It never replaces anything Warcraft Logs reads today; today's standing is printed beside it. A screenshot can also settle a rank-1 at the time that the rebuild left open, where an unreadable rival might have been ahead: if it shows the parse at the top of its board after the kill, at the value Warcraft Logs holds today, nothing that survives could have been ahead of it. The counts that include such a parse stay reconstructed, and say so.
Every screenshot is checked by eye for anything private before it's published, and cropped where the browser around the page shows more than the page.
A board without the players who weren't healing
Warcraft Logs files each character under a spec by what their log reports, so a healer spec's board can rank characters who weren't healing in the kills it ranks them for. Where a figure turns on that, the audit may rescore the board without them, and only on proof. Each character ranked above him is read from their own logs in every kill behind their place: casts, damage and healing. One goes only if healing was a small share of everything they did in every one of those kills; the audit's methodology sets the line. His own kills are read the same way, and must pass.
The rescoring uses Warcraft Logs' own All-Stars formula, first checked against every official value on the board; the largest difference becomes the range the result carries. On each boss the removed entries go and everyone below them moves up. A rescored standing is labeled reconstructed, carries its range, and always appears beside the official standing, never in its place.
Which characters count
The Morty Dynasty is one player's characters: Mortivius, Mortybop, Mortypoo, Mortytide and Mortytree. Each is tied to its own Warcraft Logs record, and a parse counts for a character only when the name matches and the report and fight are among that character's own parses. That holds across realm moves and merges: parses logged on Living Flame before the realms merged resolve to the same characters on Crusader Strike.
The guild a parse was logged with is read from the rankings, or from the guild's own reports when a personal log carries no guild.
The C'Thun kill
- The kill's date, length and roster are read straight from the report of the fight.
- "Healed it alone" means he was the only player Warcraft Logs put in the healer role for that fight. His share of all the healing done is on that receipt.
- C'Thun is only vulnerable in windows, and each window opens when a pair of Flesh Tentacles dies; the next pair appears only after the window closes. A kill in which only one pair died had a single window. That is the only thing the audit reads from the tentacles.
- Speed ranks are tested on the kill's competitive board, the one guilds raced on, against every guild listed there. Faster kills on boards that weren't competitive are noted on the receipt, not counted.
Classic and Retail
Beyond Season of Discovery, Mortivius has raided on Retail since Vanilla and on the Classic re-releases. Those receipts follow the same rules and labels, with more record keepers:
- Blizzard's own records. The armory and Battle.net's achievement data, read through Blizzard's API, date each achievement to the second on the character that earned it; every other character on the account carries a copy rounded to the minute, so "his own" means the one with seconds. When his kill shares the second with his guild's achievement for it, he was in that guild's run.
- Warcraft Logs. The same rules as in Season of Discovery. Retail counts the hardest difficulty; Classic counts each raid in the phase Warcraft Logs files it under, named on the receipt.
- Guild ranks. A guild's rank belongs to the guild; his part in it is a receipt of its own. Warcraft Logs' progress ranking covers recent tiers and WoWProgress older ones. A value on WoWProgress's live page rests on a screenshot of it, a past value on an Internet Archive copy (captured), and a guild's place on one boss from those years is rebuilt from the guilds' own kill times (reconstructed).
- Sources that agree. When independent record keepers agree on a figure, its receipt lists each of them and is marked corroborated.
- Not in the public record. Where part of a line rests on Mortivius's own account, such as which guild a kill was with when Blizzard's data doesn't say, the site says so beneath it.
Parses Warcraft Logs ranks but All-Stars leaves out
In Karazhan, Warcraft Logs' boards still rank his best parse on some bosses where its All-Stars total counts a lower one instead. The audit rebuilds the standing counting the parses the boards rank, with Warcraft Logs' own formula checked against every official value on that board. It is labeled reconstructed, carries its range, and appears beside the official standing, never in its place.
Limits: Warcraft Logs holds nothing on Retail before Throne of Thunder, some guilds' logs are private, and renamed or moved characters are tied together by their Warcraft Logs records and his word.
How a receipt gets its status
The audit started from the record Mortivius kept himself and checked every figure in it against the record keepers: Warcraft Logs, Blizzard's own data, WoWProgress and dated screenshots. It kept what held, changed what didn't, and added what it found on the way. Every receipt carries one of these statuses:
- Verified
- Checked against the record, and it holds, whether it came from his record or the audit found it.
- Not proven
- The surviving data can't settle it. The note names exactly what would.
Check one yourself
Click any number on the site. Its receipt opens: what it records, the value, its label, its status, its scope and its evidence.
Here is one to try it on.
Its receipt, opened in the page:
Receipt № 187Verified
<cartel>'s C'Thun kill took 157.7 seconds.
2:37.7Officialreceipt № 187Read straight from a current value of its record keeper.
Status
Verified. Checked against the record, and it holds.
What a reader must know
Fight length from the report: 157,684 ms. The pull began at 2025-01-27T02:49:46Z, 9:49 PM on 2025-01-26 US Eastern time. A dated capture agrees: a video of the kill posted on Discord, 2025-01-28 (UTC): Potence posts the YouTube video "Cartel : That's a Gap | Heroic Ahn'Qiraj | World of Warcraft Season…" (channel Matre); its thumbnail is Warcraft Logs' fight list: "C'thun Heroic (20 Player)", "Last Pull - Kill (2:37)", "9:49 PM". The thumbnail is a video's picture of Warcraft Logs' fight list, in whole seconds.
What it ranks against
- Character
- Mortivius
- Raid
Temple of Ahn'Qiraj (AQ)- Encounter
- C'Thun
- Difficulty (Warcraft Logs id)
- 4
- Size
- 20-player
- Partition (Warcraft Logs id)
- 1
On Warcraft Logs
- Open the reportsod.warcraftlogs.com/reports/YJMW16njAZpvXCKq#fight=19cartel's kill, deep-linked to the fight
- Open the rankingssod.warcraftlogs.com/zone/rankings/2016#metric=speed&boss=100717&difficulty=4&size=20&partition=1
Watch it: his own recording of this fight
The saved snapshot
the API data this claim rests on
Name Total Type Mortivius 216,145 Mage Ramtram 34,963 Priest Justincranks 21,672 Warlock Vaxxqt 20,154 Priest Onepunchx 13,358 Paladin Bopt 12,857 Paladin Kurkis 8,907 Warlock Matree 8,361 Warlock Meaqt 4,445 Warrior Cronon 3,923 Warlock Showing 10 of 20 rows · Download the raw file (3 KB)
Screenshots

a dated capture that agrees (captured) · Cut to the page; nothing inside it was changed. Open the Warcraft Logs link on the receipt. It goes straight to the report and the fight, or to the board.
Compare. The receipt's saved snapshot is the exact response the audit read, as a table and as a raw download. Values read from a board today can move as new logs arrive, so every receipt carries the date it was true.
This receipt's snapshot: cthun-date.json · True as of September 27, 2026
What the audit can't see
No audit of Warcraft Logs is complete. These are the known holes, and each receipt's notes say when one touches it:
- Logs that were deleted, made private or hidden, and rankings Warcraft Logs removed. The stamped percentile still covers these on spec boards.
- Anonymous rivals, whose histories can't be looked up.
- Unlisted or private reports.
- Parses reclassified after the fact.
- Uploaders whose computer clocks were wrong.
This audit run
- Generated
- November 1, 2026 (UTC)
- Audit code
- f48c3486f272bf000e2b5cfd7a931b0a7c3a139b
- Receipts
- receipts.json
Every raw response the audit read is cached, so the whole analysis re-runs offline and must reproduce the same receipts. Before the numbers are called final, a separate reviewer that hasn't seen the audit's code re-derives a random sample of receipts.