DREAMBREATH

Murder Row

Where the damage lands in Murder Row, how long you have before it arrives, and what went out ahead of it in the runs that handled it well.

Log-verifiedn=11 runs · +12 to +14
11 runs of Murder Row, with 11 pulls that appear in enough of them to be worth naming.
Thin sample: 11 runs.

PTR data, so tuning may have moved · leaderboard sourced, so this is the top of the spec and not the middle

Log-verifiedn=11 runs · +12 to +14
The hardest moment in Murder Row is Zaen Bladesorrow, a median spike of 4,709,715 landing 7s into the pull, led by Fel-Infused Freight.
The spike time is measured from the start of the pull, not from the start of the fight. That is the number a ramp is planned against: it says how long you have after the pull begins, which is the only clock you can actually see.
Thin sample: 11 runs.

PTR data, so tuning may have moved · leaderboard sourced, so this is the top of the spec and not the middle

The pulls that spike

Sorted by median spike. Every row is a median across the runs that contained that pull, so the run count in each row is its own sample size and is not the dungeon's.

Start is measured from the beginning of the run; spike is measured from the beginning of the pull. Pulls appearing in fewer than 60% of runs are not listed at all, so this is the dungeon's spine rather than a full route.

Pulls in Murder Row that spike, sorted by median spike.
PullRunsStartsLastsDamage takenSpikeInto pullLeading cause
Zaen Bladesorrow1111:32156s43,228,3234,709,7157sFel-Infused Freight
Felmaster Lucsei917:57181s48,221,5214,379,426101sBlade Dance
Defiled Golem1125:0195s26,966,5074,159,35137sDefiled Slam
Xathuux the Annihilator1120:21154s33,773,8303,918,12641sFel Lightning
Shivan Orbweaver1117:4894s27,095,6843,406,98441sDemonic Frenzy
Bribed Captain1151s73s15,649,6953,302,74229sFel Missiles
Kystia Manaheart116:05187s44,924,0693,231,23258sChaos Barrage
Massive Felwyrm73:4967s21,670,4813,193,78525sBurning Fel

All 11 pulls, with the ramp for each.

What the ramp looks like

Untestednot measured
No pull in Murder Row has cast data from enough runs to say what the ramp was. Cast data was only recorded for some runs, and this dungeon is in the part without it.

Other dungeons

Altar of FangsMeasured sheetDen of NalorakkMeasured sheetKings' RestMeasured sheetRuby Life PoolsMeasured sheetTemple of SethralissMeasured sheetThe Blinding ValeMeasured sheetVoidscar ArenaMeasured sheet
How these numbers were measured

Runs come from Warcraft Logs. Preservation Evoker only, Mythic+ only.

Only one report counts per key. Two players in the same group each upload the same run, so the raw data holds that key twice. 27 of 352 logged rows are a second copy of this kind, and only one of each pair is counted. That is where 325 comes from.

Runs whose event stream was cut short are excluded, because their totals would be low by an amount nobody can measure. None have hit that yet.

A pull is listed only if it appears in at least 60 percent of that dungeon's runs. What you see is the dungeon's spine, not one group's exact route. If your group skips a pack listed here, or takes one that is not, nothing is wrong.

An ability is called part of the ramp only if it appears in at least 60 percent of the runs with ramp casts for that pull. One player's habit on one key does not reach the page.

Casts are only collected from the 30 seconds before a damage spike. That is a setting, not a finding, so nothing here can tell you whether a ramp starts earlier than that. Where you see a window, it is the window we looked in.

Ramps are worked out one run at a time and then compared, rather than by taking each ability's average timing separately. Doing it the second way produced ramps of six casts inside four seconds, which is faster than the game allows anyone to press buttons.

Damage figures are the whole party added together. Nothing here records who took the damage, and most autoattack damage lands on the tank. Use these numbers to compare one pull against another. They are not an amount you have to heal.