DREAMBREATH

Temple of Sethraliss

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

Log-verifiedn=36 runs · +10 to +20
36 runs of Temple of Sethraliss, with 8 pulls that appear in enough of them to be worth naming.

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

Log-verifiedn=36 runs · +10 to +20
The hardest moment in Temple of Sethraliss is Sandfury Stonefist, a median spike of 4,615,844 landing 26s into the pull, led by Serrated Charge.
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.

PTR corpus, 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 Temple of Sethraliss that spike, sorted by median spike.
PullRunsStartsLastsDamage takenSpikeInto pullLeading cause
Sandfury Stonefist3669s73s26,125,4694,615,84426sSerrated Charge
Agitated Nimbus3615:3384s25,005,8264,489,94836sRelease Charge
Orb Guardian3621:33203s48,904,7944,055,35653sCaustic Stomp
Merektha3611:49193s52,207,9163,974,76667sBurrowquake
Scaled Krolusk Rider357:41132s31,513,2283,579,33257sSerrated Charge
Galvazzt3618:13147s42,777,3353,569,47273sGalvanized
Avatar of Sethraliss3626:15206s30,548,0023,347,17189sTainted Strike
Adderis and Aspix362:35197s42,142,0243,106,10859sGust

What the ramp looks like

Untestedno data exists yet
No pull in Temple of Sethraliss has cast data from enough runs to say what the ramp was. Casts are only ingested for a subset of the corpus, and this dungeon is in the part without them.

Other dungeons

Altar of FangsMeasured sheetDen of NalorakkMeasured sheetKings' RestMeasured sheetMurder RowMeasured sheetRuby Life PoolsMeasured 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.