DREAMBREATH

Voidscar Arena

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

Log-verifiedn=12 runs · +10 to +14
12 runs of Voidscar Arena, with 8 pulls that appear in enough of them to be worth naming.
Thin sample: 12 runs.

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

Log-verifiedn=12 runs · +10 to +14
The hardest moment in Voidscar Arena is Brutok, a median spike of 4,171,986 landing 70s into the pull, led by Savage Leap.
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: 12 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 Voidscar Arena that spike, sorted by median spike.
PullRunsStartsLastsDamage takenSpikeInto pullLeading cause
Brutok122:53179s35,456,7684,171,98670sSavage Leap
Devouring Brutalizer1216:5470s24,267,8454,171,40630sDreadbellow
Voidtouched Magi1010s58s16,290,1903,728,55635sSearing Magma
Atroxus1212:46125s32,725,4373,524,79793sToxic Aura
Brutal Overseer810:4761s17,305,4383,524,39216sBrutal Slams
Raj'kess the Spellstorm1088s55s9,422,1793,339,42125sThundering Storm
Taz'Rah126:21137s37,561,7693,101,48883sNether Dash
Charonus1221:24164s36,375,6243,063,14554sUnstable Singularity

What the ramp looks like

Untestednot measured
No pull in Voidscar Arena 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 sheetMurder RowMeasured sheetRuby Life PoolsMeasured sheetTemple of SethralissMeasured sheetThe Blinding ValeMeasured 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.