Why was their key faster than yours?

Sponsor Visit This spot is open. One WoW-adjacent sponsor at a time, on free readers' result pages only. Pro and Guild readers never see it. Ask about it {dungeon} +{level} was {time} from timing Your closest miss at your level or above. One route fix or one fewer wipe turns it into a timed key and raises the floor. {dungeon}: timed at +{timedAt}, not yet at +{top} {dungeon}: never timed this season {dungeon}: not logged this season Best attempt +{bestLevel}, {over} over. Score gains are biggest where your key is lowest. Bring it up to the others; score gains are biggest where your key is lowest. A single timed run there adds more score than pushing a dungeon already at +{top}. {dungeon} +{level} timed with {spare} to spare That much slack is a +{next1} or +{next2} waiting to happen: the same route at a higher level. {n} depleted {dungeon} runs at +{top} or above Same key, same result. Compare the closest one against a timed run of the same level before the next attempt. {per} logged runs a week lately Score comes from timed keys in every dungeon; two or three keys a week in the untimed ones move it fastest. Raider.io score {dps} dps · {healer} healer · {tank} tank Warcraft Logs points {spec}, best perf. avg {avg} region rank #{rank} Kicks and dispels over the season Read from your own logged runs: what you pressed, against what there was to press. Dots are runs, green timed, red depleted. Reading kicks and dispels from your logged runs. The first time takes a while; it is kept for a day. Kicks a minute Dispels a minute This spec has no interrupt. This spec removes nothing, so there is nothing to price here. Dungeon Runs Kicks a minute Must-stop casts you stopped Dispels a minute Could have dispelled Must-stop casts here you {me}, group {group}, landed {landed} runs read kicks a minute dispels a minute could have dispelled Healing a minute Overheal Self-healing of what hit you, healed back by yourself Where the healing went By role across {runs} runs, and the buttons it came from. A target we could not place is left out of the split. To the tank To the damage To the other healer Spell Healed Overheal Where this run sits among the people who did this dungeon at this key level, on the metric your spec is ranked by. Not a parse: a parse pools every key level and hides the difference. It does not account for gear. median across your ranked runs Key % Ranked on healing Ranked on damage Your Key % for this run is {n}. The rows below are ranked parses, so almost all of them read close to 100. The distance from your own number is what they are for, not the order among themselves. Warcraft Logs keeps only each player’s best run per key level, so a run they have since beaten has no ranked row and shows a dash. {side} has none here. deaths a run of incoming damage mitigated of damage taken was avoidable {runs} runs in dungeons with a list Deaths a run Avoidable share Frontal share of damage taken was frontal cones Frontal cones here Avoidable hits here Deaths a run Avoidable share of damage taken no list {n} deaths {pct} avoidable You die {per} times a run in {dungeon}, against {elsewhere} elsewhere Across {runs} runs there. One dungeon standing out that far is a mechanic, not a bad night: open a run of it and read the death recap for the hit that carried the overkill. {per} deaths a run across {runs} runs Every death is a stop for you and a battle rez or a defensive spent by someone else. Compare a run against a same-spec peer to see which hits did it and what was ready. {pct}% of the damage you take is from frontal cones Across {runs} runs, mostly {top}. A frontal is a cone aimed where the mob faces; standing beside or behind it costs nothing. {pct}% of the damage you take is on the avoidable list Across {runs} runs, mostly {top}. That is healer time and your own defensives spent on hits the dungeon lets you sidestep. Your kicks a minute fall from {low} below +{at} to {high} at +{at} and above Higher keys have the same casters and more time between kicks; the rate should hold. Assign must-stop casts before the pull so the kick is planned, not reactive. In {dungeon} you stop {rate}% of the must-stop casts you could, against {elsewhere}% elsewhere Same class, same kick; the difference is knowing which casts matter in that dungeon. The must-stop list names them. No flask in {n} of {of} runs A flask is the cheapest throughput in the game and it lasts through a death. The log reads it from the buffs you had when the key started. No food buff in {n} of {of} runs Well Fed is a free stat block that costs one button before the pull. {per} potions a run A potion is a cooldown like any other: unused, it is worth nothing. This counts every potion you cast, healing ones included. {what} went round the party in {n} runs and you never took one Whoever supplies it, taking what is handed round is free output. This counts consumables two or more of the others used while you used none. Flasked and fed in nearly every one of {runs} runs Preparation is a habit here, not a good night. Nothing to change. {count} {type} applications ran their course across {runs} runs, and you can remove that type Each one is seconds of damage or a slowed party member the healer had to cover. A dispel is one global; the debuff usually costs more. {avg} kicks a minute, steady across {runs} runs That is a habit, not a good night. Keep it and spend the attention on the must-stop casts that still land. {name}: carried in {carried} runs, pressed in {pressed} {names}. The count is presses, not need: your own talent build proves you had the button in every one of those runs, and the log shows the runs where it was never touched. Died in {n} runs without pressing a defensive in any of them {n} of {of} runs with a death and not one personal defensive pressed from start to finish. A defensive is a global that turns a death into a stagger; the death cards on any of those runs say which hit it would have covered. {name}: {presses} presses in {possible} windows across {runs} runs ({pct}%) {spells}. Windows are counted on the base cooldown over each run's length, so presses above the count mean a talent shortened it and the share is a floor. A cooldown held for the perfect pull is usually a cooldown used once less. Defensives you carried Every personal defensive your own talent build had, across {runs} runs with a build on record, and how many of those runs saw it pressed at all. pressed in {n} of {of} runs never pressed in {of} runs {name} under {expect}% uptime in {under} of {runs} runs, {avg}% on average {spells}. Uptime is measured over each run's whole fight window, so time spent dead counts against it. A maintenance buff is one global and it pays out on every hit afterwards. Check that your build has {names} before reading it as a fault. Buffs you keep up The buffs your spec keeps up and the raid buff your class brings, across {runs} runs: average uptime over the whole fight window, and the runs it sat under the expected share. {pct}% on average, under in {n} of {of} (check your build) {who}: {spell} never up (expected {expect}%+). {who}: {spell} up {pct}% of the run (expected {expect}%+). Check that the build has it before reading it as a fault: {list}. Uptime is measured over the whole fight window, so time spent dead counts against it. A maintenance buff is one global and it pays out on every hit afterwards; the uptime bar is the cheapest number to move on this page. Buffs that were not kept up {name} up {pct}% of the run {name}: {pct}% against an expected {expect}% {name}: {pct}% against an expected {expect}% ({who}: {theirs}%) Uptime is measured over the whole fight window, so time spent dead counts against it. Check that your build has {names} before reading it as a fault. {who}: {spell} {presses} of a possible {possible}, off cooldown for about {idle} minutes in total. Windows are counted on the base cooldown over the run's length, so presses above the count mean a talent shortened it and the share is a floor. A cooldown held for the perfect pull is usually a cooldown used once less. Pro until {date} Guild plan: {seats} seats, until {date} Pro key accepted. That key is not active. This key is already in use on {limit} devices. Use one of those, or write to [email protected] and I will free a slot. This key is already paired with {limit} Warcraft Logs clients. A key pairs with one Warcraft Logs client: use the same client id here, or write to [email protected]. Could not check the key. Pro key removed. The route, on the map Every pull drawn where it happened, both runs on the same floor. Each shape is the ground a pull covered, each dot a mob that hit somebody, and the line is where the tank walked. Hover a pull for what was in it; click it to jump to its card. Every pull drawn where it happened. Each shape is the ground a pull covered, each dot a mob that hit somebody, and the line is where the tank walked. Hover a pull for what was in it; click it to jump to its card. Floor {n} You Them Both your route their route a pull, numbered as in the cards below Pull {n} Boss {n} mobs {pct} of the key Click to jump to the card Click the number to see it on the map Positions come from the log: every event carries where its source stood, so a mob that never touched anyone (or was never touched) leaves no dot. Floors are the game's own map art, straight from the client files. kicks: fits your budget kicks: tight kicks: over your budget kicks: unknown healing: fits healing: tight healing: over your ceiling healing: unknown {ok} of that is inside your group's kick budget and your healer's ceiling. {kick} merge(s) would ask for more stops a minute than you can produce, {heal} for more healing a second than your group managed anywhere in this run. mechanics: nothing stacks mechanics: needs choreography mechanics: unknown {n}x {mob}: {ability} fires on death. Killing them together stacks it, so stagger the kills. More healing or more damage does not change this. {n}x {mob}: {ability} is damage no button stops, and two casters overlap when pulled together. Managed by not pulling them at once, not by healing. The red healing here is the mechanic stacking, not the ceiling: it does not turn green with more damage. How it arrived: one hit did {pct}% of it, {s}s of damage in all. it built up over {s}s, no single hit did the work. {s}s of damage, the biggest hit {pct}% of it. Ticking through it: {n} hits over {s}s, {pct}% of the damage: position a defensive was ready an external was ready no time to react nothing would have stopped it Avoidable damage in the window was {amt}, more than the {over} they died by: not standing in it is the whole fix. {name} was off cooldown, and its {pct}% would have covered the margin. {name} was off cooldown on somebody else and would have covered the margin. All of the damage landed inside the reaction window, so no press was available to ask for. Nothing the log can see would have covered the margin. A healer triage step belongs here and needs range, line of sight and what the healer was already casting, none of which the log holds. Deaths a change would have stopped {pos} by position, {def} by a defensive, {ext} by an external. Asked one at a time, stopping at the first that covers the margin. is what decisions explain is the same work done slower, which no plan changes not a decision {t} at your own kill speed nothing at your own kill speed Over your ceiling means this group has not shown that healing yet, not that they cannot: the ceiling is set by what this run asked of them, so a red merge is a suspect and a green one is safe. with their hands with yours Their group kept up Your group kept up Your own classes could have cast, and did not keep up: Between them those are worth roughly {lo}% to {hi}%. The ones you could have cast are worth about {lo}% to {hi}%, and that half is a decision rather than a composition. {n} more were up on both sides, so they explain none of the difference. {who} bring no group damage buff at all ({brings}), so an empty line there is not a hole. Your damage was {phys}% physical and {magic}% magic this run, and the debuffs that lift one of those are priced against the share they actually touch. Buff registry read for patch {v} on {d}; every magnitude is a range because it depends on spec, gear and the damage split, and nothing here is subtracted from the numbers. Their group brought Your group brought {side} enemies took {pct}% more damage from everything all run ({names}), which is a share of every damage number below that nobody played their way to. Standing group buffs the two compositions did not share. No number is subtracted from the columns: buffs do not add up linearly and the other group does not exist to test against, so the split between hands and makeup is named, not calculated. Their side handed out Your side handed out A damage column is measured inside whatever buffs the group brought, so a row under an external cooldown reads higher than the same hands without it. The time beside each one is how long it was actually up, which is the size of the window to discount by. Nothing here is subtracted from the numbers; the passive half (raid buffs, damage-amplification debuffs, the composition itself) is not in the log at all. The dungeon's own buttons Cast by every class on the run, so they belong to the dungeon and not to a spec: buff objects, offerings and floor effects. Potions and food are under what everyone brought, and anything the dungeon put ON the party is left out of both. More is not automatically better. A buff object or an offering is a choice worth copying; a floor effect is time spent standing in the wrong place. Where the row says not identified, the log gives a cast and nothing that says what it was. floor effect: fewer is better dungeon buff offering consumable dungeon mechanic not identified {mech} merge(s) carry a mechanic that multiplies with the mob count and is solved by choreography, not by numbers. Kick demand {demand} a minute against your {supply}; damage intake {dtps} a second against your ceiling of {ceiling}. They took {theirs} a second on that pull. Kick budget, pull by pull What each pull asked of your interrupts against what your group can produce a minute. Supply is every kick, stun and knock at the cooldown each player actually achieved in this log. A must-stop cast that landed while somebody's kick was off cooldown is an assignment problem, not a capacity one. Stops a minute {kicks} kicks, {stops} stuns and knocks Landed while a kick was ready of {a} and {b} must-stop casts that got through of {a} must-stop casts that got through Busiest pull {pull}: {n} must-stop casts a minute, as a share of your supply Your group can produce about {n} stops a minute: Theirs about {n}: Pull Must-stop Stopped Landed A minute Of your supply Landed while ready {n} of the {of} must-stop casts that landed on you started while at least one kick was off cooldown. {n} pull(s) asked for more stops a minute than your group can produce; the worst was {peak} at {ratio}% of your supply. Their group can produce {b} stops a minute against your {a}: a composition gap, not a play one. {kicks} kicks, {stops} stuns and knocks · {used} pressed never pressed {n} of your {ceiling} stops a minute were never pressed once. {who} carried {list} the whole run. This run does not record what anyone had talented, so this counts what was pressed plus each class’s own interrupt, and the real ceiling is higher. What your group was holding, not only what it pressed: a button counts when the log shows a press, when the player’s own talent build took it, or when every player of that class has it. Anything unproven is left out, so this is a floor. What each pull asked of your interrupts, against what your group can stop a minute. What each player brings How this is measured How this is measured The numbers Them: {p} of {t}. What had to be stopped You stopped They stopped The two groups pulled {n} of these {of} packs the same way; the rest they routed differently. They never pulled this pack, so there is nothing to compare it with. Their pull {name}: {must} must-stop, {stopped} stopped, {landed} got through. Your pull {a} against their pull {b} Pull {n}, {time} into the run Cooldowns are base values shortened to the tightest gap each player actually achieved, so talents are accounted for where the log shows them. Range and line of sight are not in the log: "ready" means off cooldown, not "could have reached it". Where the healing went Every heal the two healers landed, split by who received it. Read the split against the load: a healer pouring into the tank while the tank took the damage is doing their job; a healer pouring into the DPS is answering mechanics. Every heal the healer landed, split by who received it. Read the split against the load: a healer pouring into the tank while the tank took the damage is doing their job; a healer pouring into the DPS is answering mechanics. a minute of fighting {pct} overheal Healing: tank {tank}, self {self}, DPS {dps} Damage taken: tank {tank}, healer {healer}, DPS {dps} Spell Casts Healing Overheal Tank / self / DPS {name} is a different class, so their spells are listed on their own. Your tank took {a}% of all damage against their tank's {b}%, and got {healA}% of the healing against {healB}%. That is tank sustain, not the healer picking the wrong target. {healA}% of your healing went to the tank against their {healB}%, while your tank's share of the damage was only {a}% against their {b}%: the healing followed habit more than the damage. Your DPS took {a}% of all damage against their DPS's {b}%. Mechanics eaten by the DPS cost healer globals before anything else does. {a}% of your healer's healing went to themselves against {b}% for theirs: a healer who is taking damage is a healer who is not healing. {a}% of your healing was overheal against their {b}%: casts spent on bars that were already full. Nothing to see here: both healers spread their healing the same way and both groups took damage in the same shape, within {gap} points everywhere. Whatever separates these two runs, it is not the healing. The biggest difference in this section is the healing that went to the tank: {a}% of yours against {b}% of theirs. The biggest difference in this section is the healing that went to the healer's own bar: {a}% of yours against {b}% of theirs. The biggest difference in this section is the healing that went to the DPS: {a}% of yours against {b}% of theirs. The biggest difference in this section is who took the damage: your tank took {a}% of it against their tank's {b}%. The biggest difference in this section is who took the damage: your healer took {a}% of it against their healer's {b}%. The biggest difference in this section is who took the damage: your DPS took {a}% of it against their DPS at {b}%. {a}% of the healing went to the healer's own bar: a healer who is taking damage is a healer who is not healing. The DPS took {load}% of the damage and soaked {heal}% of the healing: healing spent answering mechanics rather than tank sustain. The tank took {load}% of the damage and needed {heal}% of the healing: keeping the tank up was this healer's run. The healing followed the damage: the DPS took {ldps}% of it and got {dps}% of the healing, the tank {ltank}% and {tank}%. Nothing in the split stands out. Casts come from the cast table, healing from the healing table; a heal-over-time shows healing with few or no casts. "Self" is the healer's own bar. Warcraft Logs does not say which damage was avoidable: the damage-taken rows above and the difference between the two groups are the nearest thing to that answer. The healer, against the demand What this run asked of the healer, what they did with it, and what it cost. Every number here describes this run and none grades it: the cohort of healers who faced the same demand is not built yet, so nothing is coloured or ranked. Descriptive only, no cohort yet This run was captured before the party’s health was read, so only the demand, the cost and the credit split are here. What was asked Intake a second of combat, after mitigation {raw} before it; {spike} arrived in spikes (seconds over three times the median); {avoid} was avoidable. Seconds anyone living sat under 50% {deep}s of it under 30%; {share} of combat. Sampled at event resolution: a player nobody hits or heals keeps their last reading ({spm} readings a player a minute here). Where: {list} Who: {list} Half-life of the party’s gap after a spike {n} spikes (the party deficit rising by 0.6 of a pool within 3s). Median {med}s to close half of it, the slowest tenth {p90}s; {cut} cut short by a death and left out; longest {long}s on {pull}. Heals cast on someone at 60%+ while another stood 20 points lower {n} of {of} chosen heals ({share}). Possible, not certain: range and line of sight are not in the log. Procs, ticks and placements ({procs} and {aoe}) are not choices and are left out. Healing cooldowns on the five biggest intake windows {aligned} of {presses} presses fell inside one, or in the 3s before it; {covered} of the 5 windows had one. nothing pressed What it cost Mana spent, in bars ended on {end}%, lowest {min}% Healing landed per 1% of mana Of all party healing, overheal Non-healing casts in low-demand seconds {n} of {of} ({share}). A low-demand second is under a quarter of the median. Slack or good triage: a cohort decides that, not this number. Who closed the gap the healer the tank on itself others on themselves others’ heals leech shields absorbed Of all healing and absorption that landed on the party in combat. {self} of it was self-inflicted, damage a player did to themselves: {list}. The dungeon never asked for that. {dead}s of combat had somebody dead and is not in the count above, so a run with more deaths can read lower. healer dead {aligned} of {presses} presses fell inside one, or in the 3s before it; {covered} of the {alive} windows the healer was alive for had one. Two runs, two different censors: {da} and {db} deaths, {sa}s and {sb}s of combat with somebody dead. Side by side is not a cohort. The key needs 100%. You killed all {required} it counts; the log filed {reached}, so its per-mob values run a touch over for this dungeon. Things to do, from the numbers below On {pull} at {t}, {net} of damage arrived while {spells} sat ready and nothing was pressed ({n} such windows). Press the big button when the big hit comes. You ended the run on {end}% mana and never went under {min}%. Mana is for spending, not keeping: use the bigger heals and the cooldowns earlier. You stood without casting for {s}s of the {low}s when nobody needed healing. Fill those seconds with damage. {n} of your {of} chosen heals ({share}%) went to someone at 60%+ while another player stood 20 points lower. Look at the lowest bar before the cast; range may explain some of it. {share}% of what you healed through was {who} hurting themselves with {spell}. Ask them to stop, or to do it when nothing else is coming in. {s}s of the {of}s anyone sat under half health were on {pull}. Plan your cooldowns for that pull. Nothing on this run asks for a change from the healer. this run, the one you are reading not in Warcraft Logs’ rankings yet How hard the healer worked Healing a second against the healer's own ceiling, the party's damage intake, and mana, over the whole run. The ceiling is the best fifteen seconds this healer produced in this log: the only honest bound there is. Healer ceiling {avg} a second on average in combat; at 80%+ of the ceiling {pct} of the time Lowest mana finished the run at {a} and {b} finished the run at {a} Damage taken a second the whole party, in combat healing a second damage taken a second mana ceiling Pull Healing /s Peak Taken /s Mana Your healer's mana went down to {min}% ({n} pull(s) at or under 30%: {where}). Mana is the real limit on chaining packs. Your healer was at 80% or more of their ceiling {a}% of the fighting time against {b}% for theirs. Your party took {pct}% more damage a second than theirs ({a} against {b}). That ceiling is the most this group was asked for in this run, never the most they could give, so its error runs one way: damage that fits under it fits under the real ceiling too, while damage above it may still fit. Your group spent only {pct} of the fighting time near that ceiling, so read it as a lower bound rather than a measurement. Shaded bands are boss fights. Percentages next to a pull's healing are that pull's average against the ceiling; a mana cell shows start to end, with the lowest point in brackets when it dipped further. Every death, and what it cost The last five seconds of each death, the healing that arrived in the window, and whether a defensive or an external was up. Then the price: seconds out of the fight, weighted by that player's share of the group's damage. Deaths {a}s and {b}s of fighting without them {a}s of fighting without them Cost in fighting time seconds the pulls got longer for it With a defensive ready deaths where a personal was off cooldown and unpressed {n} of your {of} deaths happened with a defensive off cooldown. You died {a} times to their {b}, but yours cost {aS}s of fighting against their {bS}s: it is the price of a death, not the count, that separates the runs. {n} of your deaths were the tank or the healer. Those stall the whole pull and are not priced by damage share. one hit burst sustained Killed by from {who} Last five seconds: Healing received: nothing landed before the killing hit {total} in the last {s}s, {own} of it their own, {others} from others Defensives: none pressed anywhere in this run Externals: just used ready ready in {s}s Out for {s}s, {c}s of it in combat. About {s}s of fighting at a {share} damage share. A tank or healer death stalls the whole pull; not priced by damage share. No later action was logged, so the pull's end is used. Nobody died in {who}. More than a health pool deaths where more damage arrived than the player had health {n} of your {of} deaths happened with the healer more than {yd} yards away, which is further than a heal reaches. {n} of your deaths happened with a healthstone or a health potion off cooldown and unpressed, by a player who used one elsewhere in the key. {n} of your {of} deaths took half as much again as the player had health, or more. No single press covers those: they are a route or a stop problem. Each window is the stretch Warcraft Logs itself marks as the death, read as events rather than as its short recap: every hit with the health left after it, the healing that landed, and where the party was standing. Range is measured from the last cast each player made and only claimed when that reading is under {s} seconds old. A stone counts as off cooldown from the tightest gap that player achieved between two presses of it in this run. Line of sight is not in the log. What was it What happened What could have saved them Their own cooldowns {yd}y, out of range on {who} {n} ticks over {s}s {n} hits one hit and {n} more Could anything have stopped it? The party The healer this would have covered it They pressed nothing all key Feared by {spell} from {from}s before the end to the death: nothing of their own could be pressed. Stunned by {spell} from {from}s before the end to the death: nothing of their own could be pressed. Disoriented by {spell} from {from}s before the end to the death: nothing of their own could be pressed. Charmed by {spell} from {from}s before the end to the death: nothing of their own could be pressed. Pacified by {spell} from {from}s before the end to the death: no ability of their own could be pressed. They could not press anything for the whole stretch a press could have landed in, and nobody else's external would have covered the margin. This death is a crowd-control death, not a missed button, and is not counted as preventable. {n} under crowd control with no press of their own possible. never used Nobody was holding one {who} was {yd} yards away landed {amt} of the healing landed nothing on them They had {pool}. {times} times all of it {taken} arrived in {s}s. Health: {pool} pool, and {taken} arrived in {s}s: {times} times all of it. {pool} pool, and {taken} arrived in {s}s, {pct}% of it. Started on {pct}% health. Shields ate {amt}. Healer: {who} was {yd} yards away, further than a heal reaches. {who} was {yd} yards away. {who} was {yd} yards away, right on the edge of range. {who} was dead at that moment. No position for {who} within {s}s of this, so range is unknown. {who} was on another floor here, so range is unknown. This was the healer. Landed {amt} of the healing. {pct}% mana. Casting {spells}. Nothing landed on them for the last {s}s. Stone or potion: {total} of healing landed in {s}s, {own} of it their own, {others} from others {spell} was off cooldown and unpressed, worth about {amt} to them. {spell} went {s}s before the end and was not enough. {spell} had gone {s}s earlier and was still cooling. They pressed none all key, so whether one was in the bag is not in the log. They pressed none all key, while the rest of the group pressed {n}. Whether one was in this player's bag is not in the log. Nobody in the group pressed a healthstone or a health potion all key. a stone would have done it a potion would have done it no healing was coming {name} restores about {amt} on this player and was off cooldown, against the {over} they died by. Nothing they held would have covered the margin, and {who} was {yd} yards away. Nothing they held would have covered the margin, and {who} was already dead. {pos} by position, {def} by a defensive, {kit} by a stone or a potion, {ext} by an external. Asked one at a time, stopping at the first that covers the margin. {n} by a healthstone or a health potion they were carrying. {n} had no healing coming: the healer was dead or out of range. A defensive counts as "ready" when its last press plus its cooldown is behind the death, and "never used" when the player carried it (in their talent build, or baseline for the class) and pressed it nowhere in the run. Externals are anyone else's, judged the same way. Where the big cooldowns went Bloodlust and every cooldown of ninety seconds or more, against the pull it was pressed on. The biggest buttons belong on the pulls with the most health in them. no Bloodlust in the log pull ended within 10s out of combat Player Cooldown Presses On bosses On big pulls On small pulls Pull ended early {b}% of their big cooldowns went to bosses or big pulls against {a}% of yours. {n} of your {of} big cooldowns were pressed with less than ten seconds of pull left. Lined up in order, {n} of the {of} presses both groups made landed on different pulls: yours on {a}, theirs on {b}. Both groups pressed Bloodlust on the same {n} pull(s), in the same order; the extra press on {where} is what the longer run allowed, not a different plan. They pressed Bloodlust {n} time(s); your log has none. A big pull is one in the top third of your trash pulls by enemy forces ({a} for you, {b} for them). Sixty-second cooldowns are left out on purpose: those get pressed on whatever is in front. A big pull is one in the top third of your trash pulls by enemy forces ({a}). Sixty-second cooldowns are left out on purpose: those get pressed on whatever is in front. Avoidable damage, and what was mitigated Damage from hits that never had to land, by Archon's own per-dungeon list (the same one its app and Warcraft Logs' Mechanics view use), and how much of everything each player took was mitigated by armour, absorbs and defensives. Read the mitigated share against the same class in the other run: the kit is the same, so a lower share means the defensives were not up when the hits came. Avoidable damage a minute {a} and {b} of everything the two groups took {a} of everything the group took Mitigated of all incoming damage, whole group Damage from hits that never had to land, by Archon's own per-dungeon list (the same one its app and Warcraft Logs' Mechanics view use), and how much of everything each player took was mitigated by armour, absorbs and defensives. Biggest avoidable hit {n} on {who} Taken /min Mitigated Avoidable /min Frontal hits Your non-tank players ate {a} frontal hits ({dmg}) against their {b}, mostly {top}. A frontal is a cone aimed where the mob faces: step to its side. You took {a}k avoidable damage a minute against their {b}k, {pct}% of everything you took. Mostly {top}. You took less avoidable damage than they did: {a}k a minute against {b}k. {pct}% of what {who} took was avoidable, mostly {top}. {who} mitigated {a}% of incoming damage; {them}, same spec, mitigated {b}%. Same kit, so the difference is when the defensives were pressed. No avoidable list for {dungeon} yet; only the mitigated shares are shown. Damage from casts a kick would have stopped: Only what the log's shape says a player could have avoided counts: standing in a ground effect (the same spell ticking on you at a steady beat) and overlap (extra hits from a mechanic aimed at someone next to you). The targeted hit itself, and a deliberate soak, do not. of {n} standing in it overlap targeted, not counted Avoidable and interruptible lists are Archon's for this dungeon, read on {date}; a hit counts when its spell id or name is on the list. Mitigated is what armour, absorbs and defensives took off before the hit landed, the same figure Warcraft Logs shows as Mitigated. Archon's avoidable list does not cover {dungeon} yet, so no hit is called avoidable here. Mitigated shares need no list. {n} flagged casts were not kickable (a channel you break by moving, or crowd control only) and are left out of the budget. Kickable means on Archon's interruptible list for this dungeon, or stopped by a real kick in either log. Mitigated {a} of incoming damage against a median of {b} for those {n} peers; took {ta} a minute against their {tb}. Avoidable damage {a} a minute ({sa} of what you took) against their {b} ({sb}). {n} ahead of you in the queue, about {t}. Waiting for this hour's Warcraft Logs budget; it resets in {t}. Pro skips this queue. Waiting for this hour's shared Warcraft Logs budget. {n} ahead of you in the queue. You are next in the queue. {n} of {total} in the queue One reading at a time, in the order they arrived. Queued Reading now until the budget resets estimated wait estimated time left Your own place in the queue, and your whole season instead of ten runs. from {p} a month See the plans starts now Reading now, about {t} left. {pct}% of this hour's shared Warcraft Logs budget is used. Running on your own Warcraft Logs client, no queue. {n} points left on your client this hour. Pro: run it on your own Warcraft Logs client, no queue. Download PDF A PDF of this page, portraits and all, for a guild channel. Keystone Delta report generated How to improve What to change in how you play The measured gaps that are yours to close, biggest first. Every number comes from the two logs above. the other run {pct} less damage per active second than {who} Same spec, different buttons: {spells}. {name} {theirs} a minute against your {yours} Same spec and a similar spell mix, so the gap is timing and uptime rather than which buttons. Different specs, so read the spell list as background rather than a target. {gear} item levels of that gap is gear, not play. {mine} casts a minute against {theirs} Per minute of your own active time, so walking is already excluded. Fewer casts means empty globals: a filler skipped, a cooldown held too long, a cast clipped by movement. Active {mine}% of the run against {theirs}% Time with nothing cast: repositioning, waiting on the pull, or dead. That is output lost before rotation is even a question. {mine} deaths against {theirs} Every death is a full stop for you and a defensive or a battle rez spent by someone else. The damage-taken table says what did it. {pct} more damage taken a minute Mostly {top}. Avoidable damage is healer time and your own globals spent on defensives. Spread across many abilities, which usually means positioning rather than one mechanic. {mine} kicks against {theirs} Same role, fewer interrupts. A kick is a short cooldown meant to be spent; the interrupt table shows which casts got through. {count} debuff applications you could have dispelled ran their course {types}: types your class removes. You pressed {mine} dispels all run; {who} pressed {theirs}. Each one left standing is seconds of damage the healer had to cover. {landed} must-stop casts landed on your group The casts the game itself flags as lethal. You stopped {mine} of them; the group stopped {group} casts in total. Assign the flagged ones before the pull. Nothing to fix here: output within 5% Nothing obvious to fix on this player Where the runs differ, the route, the pull sizes and the deaths explain more than this player does. Compare the whole run. {pct} of the damage you took was avoidable Mostly {top}. {who}: {theirs}. Avoidable hits are healer globals and your own defensives spent on nothing the dungeon required. Mostly {top}. Avoidable hits are healer globals and your own defensives spent on nothing the dungeon required. {mine} of incoming damage mitigated against {theirs} Same spec, same tools. The gap is active mitigation and defensives pressed before the hit rather than after it. {name}: you {yours} a minute, they {theirs} {name}: you never cast it, they {theirs} a minute ({users} of {of}) Casts a minute of each player's own active time, against the median of the {n} closest ranked players of your spec at your key level and gear. They are ranked parses, so the gap is a direction, not a target. Check that your build has {names} before reading it as a fault. {name}: you {yours} a minute, {never} of {of} of them never cast it Not wrong by itself: a button the ranked skip is usually one their build replaced or one that costs a global they spend elsewhere. Worth asking what it does for you. {n} wipes cost {t} One wipe cost {t} Wipe {i} at {t} on {pull}: {first} died first to {ability}; {wasted} of fighting after the last kill was undone and the run back took {back}. Wipe {i} at {t} on {pull}: {wasted} of fighting after the last kill was undone and the run back took {back}. Wipe {i}: all five down within {span}s of the first, which reads as one mechanic. Wipe {i}: the healer went first and the rest followed over {span}s. Wipe {i}: the tank went first and the rest followed over {span}s. Wipe {i}: one at a time over {span}s. Wipe {i}: the same pack was pulled again {after} later and took {dur}. Wipe {i}: {spell} was spent in the wiped pull. They wiped {n} times, costing {t}. They wiped once, costing {t}. They did not wipe. On this capture the kill times are missing, so the whole pull up to the wipe is counted: an upper bound. A wipe is priced as the fighting after the last kill (every mob still alive resets to full health, so that time bought nothing; the kills before it still count) plus the run back. Damage already dealt to the mobs that reset is lost too and cannot be split out of the tables, so this is a floor. The re-pull is the same work again and sits inside the pull time. Deaths inside a wipe are not priced again under deaths, and the run-backs are left out of the stops item. {n} more deaths were inside wipes and are priced there. One more death was inside a wipe and is priced there. {t} of the stops is running back after {n} wipes, priced under the wipes. {total} on this pack all told: {before} before the wipe, {back} running back, {again} the second time. Wipe {i}: {total} on this pack all told, {before} before the wipe, {back} running back and {again} the second time. The tank went first and no battle resurrection came, so the other {n} followed within {span}s: {names}. Their cards are folded here. The healer went first and no battle resurrection came, so the other {n} followed within {span}s: {names}. Their cards are folded here. Wipe {n} first down to What did the killing across the collapse: all five within {span}s: one mechanic healer first, the rest over {span}s tank first, the rest over {span}s one at a time over {span}s fighting after the last kill run back at most pulled again {t} later, {dur} {spell} spent in the wiped pull Wipes {a} vs {b} lost: fighting after the last kill plus the run back {t} lost: fighting after the last kill plus the run back {n} wipes cost {t} inside the numbers above: {wasted} of fighting after the last kill undone, {back} running back. One wipe cost {t} inside the numbers above: {wasted} of fighting after the last kill undone, {back} running back. On this capture the kill times are missing, so the whole pull up to the wipe is counted. wipe {n} pulled again In {n} of the run's {of} wipes; the wipes cost the run {t}. In {n} of the run's {of} wipes and first to die in {first} of them; the wipes cost the run {t}. First to die in {n} of {of} wipes A wipe that starts with you is a wipe the group could not recover from once you were down. The wipe cards say what hit first and how fast the rest followed. {name} {presses} of a possible {possible} Presses against what the run's length allowed on the base cooldown. {name} sat ready for about {idle} minutes in total. A cooldown held for the perfect pull is usually a cooldown used once less. {n} of {of} deaths came with a defensive ready {names} off cooldown at the moment of death{killer}. Range and line of sight are not in the log; the button was. (killing hit: {killer}) {mine} overheal against {theirs} Healing that landed on full bars. Some is unavoidable on a healer who pre-casts; a ten-point gap at the same spec usually means reactive casts on targets the tank or a defensive had already covered. What hit you, and what you did about it Damage taken per minute of combat, how much of it armour, absorbs and defensives removed, and how much was on the dungeon's avoidable list. The list is Archon's, per dungeon; a hit counts on spell id or name. No avoidable-damage list for {dungeon} yet, so only the mitigated share is priced. Biggest avoidable hits Mitigated share Damage removed by armour, absorbs and defensives before it reached your bar. The same figure as Warcraft Logs' Mitigated column. Avoidable damage a minute Frontal hits Hits from cones the mob aims where it faces. The tank stands in them by design; anyone else stepped into one. Hits on the dungeon's avoidable list, per minute of combat. Lower is better. Avoidable share of what hit you How much of your damage taken the dungeon let you sidestep. Lower is better. Damage from interruptible casts a minute Casts a kick could have stopped. Lower is better; this is the group's kicks as much as yours. Self-healing against damage taken Your own heals and absorbs landing on you, as a share of what hit you. A tank's sustain; on a DPS, damage the healer did not have to cover. The big buttons Presses of every tracked cooldown against how many the run's length allowed on the base cooldown. A talent that shortens a cooldown shows as more presses than windows. For burst, where the presses fell: boss, big pull, small pull. Kicks and stops are priced above. Cooldown Where it went {presses} of {possible} ready {m} min unpressed boss {boss}, big pulls {big}, small pulls {small} {n} on a pull that ended within 10s Bloodlust Burst Healing cooldown Defensive External Every death, and what was in hand How much arrived against how much they had, where the healer was standing, and everything that was in hand at that moment: their own cooldowns, the healer's, and the rest of the party's. {who} did not die. {time} in {pull} Killed by {ability} from {source} one hit burst damage sustained damage {s}s out of combat, about {cost}s of your damage {s}s out; a tank or healer death stalls the whole pull Healing, against the damage that came in Healing per minute of combat, overheal, and where it landed against where the damage landed. A healer sending 30% to a tank who took 50% is keeping the DPS alive instead, and the tank is sustaining himself. Healing a minute Effective healing per minute of combat, overheal excluded. Overheal Healing on full bars. Some is pre-casting; a big gap at the same spec is reactive casting. To the tank Share of healing that landed on the tank, against the tank's share of the damage taken. To the DPS Share of healing that landed on the three DPS, against their share of the damage taken. To yourself Share of healing on your own bar, against your own share of the damage. A healer healing himself is a healer who was taking damage. against {pct} of the damage Top healing spells {share} of healing, {oh} overheal, {casts} casts Dispels Debuffs this player removed from the party, and with what. Could have dispelled Applications of debuff types your class removes that nobody dispelled. Lower is better. Enemy buffs taken off Buffs this player removed from an enemy, with Spellsteal, Purge, Dispel Magic or Soothe. Warcraft Logs files these as dispels, but they are a different job: nothing was on the party. Could have taken off Enemy buffs your class can remove that nobody removed. A buff counts when Method's per-dungeon list calls it Magic or an enrage, or when somebody in either run actually took it off, which proves it whatever the list says. Lower is better. this class takes none off held {s}s {n} of them Method marks as ones that matter matters Of these, {n} applications across {rows} debuffs are ones Method marks as mattering, and {left} of those ran their course. Of these, {n} applications are of one debuff Method marks as mattering, and {left} of those ran their course. {who} took {removed} of {all} off. {rows} of them Method marks as mattering, {left} left standing. One of them Method marks as mattering, {left} left standing. {who} carry a button for this: {removed} of {all} came off. They did not arrive spread out: took {n} took one (boss) {n} casts took two buttons where one would have done: One cast took two buttons where one would have done: The big buttons, over the season Presses against the windows your runs allowed. Windows come from the base cooldown, so a talent that shortens one shows as more presses than windows, not as a fault. A cooldown you never pressed is not listed: the log cannot tell “always ready” from “not talented”. Button Presses Windows Share What each of you took off the party Debuffs removed from a party member, by name. A buff taken off an enemy is a different job and is counted on its own row above. With The dungeon's own buttons Objects, floor effects and offerings every class pressed, so they are the dungeon's rather than a spec's. Kept out of the rotation tables for that reason. Button Enemy buffs taken off a minute magic enrage Must-stop casts landed Casts the game flags as lethal that finished on your group, and how many of them this player stopped. Kicks a minute Interrupts per minute of the run. Stuns and knockbacks are counted separately as control. {n} stopped no dispel on this spec rio you were {t} faster here you lost {t} here level this run {t} faster this run {t} slower This run against your season Your habit across the {runs} most recent logged runs, from the same tables. A gap here is a bad night; a match is a habit. this run season average Kicks a minute Dispels a minute Could have dispelled Enemy buffs taken off a minute Whole season, charted → 20 to 70% take it 70%+ of them take it 70%+ take it, you do not Ability Active All spells Back to players like you Bar length is the key level. Green timed, red depleted. Best key per dungeon Bosses do not count toward the key, so they show no percentage. Both builds on the tree Built from public Warcraft Logs data. Not affiliated with Blizzard Entertainment or Warcraft Logs. Cancelled Casts you let through Click any row Compare players Compare the whole run instead Copy link Damage taken per minute by enemy ability, biggest difference first. Usually a positioning or interrupt story. Date Debuff Debuffs you carried around Depleted Difference Enchant Enchants Enemy spell Every dungeon, every run Every pull Every pull, side by side Every spell, biggest share first. The rate gap is the honest per-player comparison. Every talent in this pool is near-unanimous. Fighting time versus walking time, then the same split checkpoint by checkpoint. Find players like Find players like this character Flask Food Full list per dungeon Gap Gear and build, side by side Gear at the pull Gems Got past them Got past you Healed back: How hard did you hit? Just me Key Keystone Delta Pro Kicks Loading Log the next one and come back; private logs never appear here. Loosen a row; every value shows how many players it would give you. Most worn among them My gear and talent build against theirs Mythic+ runs in that report Needs at least two logged runs. No gear record on this log. None. None. You have every talent the majority runs. Nothing matches all of that. Nothing matches that. Nothing stands out: your set pieces, enchants, gems and talents match what the ranked players of your spec run. On must-stop casts On them On you One column per run, oldest on the left. Green means brought, red means not; the bar above is how many potions you drank. One point per logged run, any dungeon. Green timed, red depleted. Open a dungeon for its runs. Each run can be compared against your best in that dungeon or against a run that timed it. Open it beside that run Open on Warcraft Logs Open on WowTool.tips Or set it yourself Packs they pulled together, and you did not Passed round and never taken by you Per minute Pick a run to measure yourself against Player against player Player by player Players like you Potions Prepared for Rendering the whole page as a report: every table, chart and portrait. Ten to twenty seconds. Still rendering, {s}s. The report is the whole analysis, so it takes a moment. Too many reports for now. Could not build that report ({code}). Could not build that report. Opened in a new tab. Your browser blocked the new tab, so it is downloading here instead. Preparing the report Pulls Question Quick picks Ranked players of the same spec at the same key level and gear, around one of the runs below. Reset week. Green timed on top of red depleted. Result Role Roles Runs per week Score Score over time Score and pace over the season Season profile Secondary stats at the pull: Seconds per minute Set Share Share difference Share of damage Share of the run Share this matchup. Share this profile. Show the full breakdown Slot Slot by slot Sort by Spec Stretch of the dungeon Stuns and knockbacks Taken by most of them, not by you: Talents Talents 70% or more of them take, that you do not: Talents that differ Talents they are split on, 20 to 70% each: The highest key logged in each dungeon, coloured by whether it was timed. Length is the key level; the label says how far under or over the timer. The link unfurls with the season summary and refreshes every ten minutes. The question The verdict Their group Their median /min Their pulls Them /min They dispelled They stopped This is a worked example. Time Time you lost there Timed Timed and depleted, by reset week. A week with many depleted runs at one level is a key being pushed, not a bad week. Tooltip unavailable right now. Total Type Used by Vs timer Was it your damage, or was it the route? What differs, player by player What each of you pressed What everyone brought What hit each of you What it is What the closest eight press that I do not What to change What you bring Gear and build Gear and build, against the ranked Compare in You are Which one are you? Top parses +{n} and above every key level above yours the top of the rankings Pick the dungeon; your own other logged runs of it are listed, newest first. every key level Warcraft Logs did not record which realm this player is on, so their season cannot be opened. Check this run on its own {crit} crit, {haste} haste, {mastery} mastery, {vers} versatility {n} leech {n} avoidance Warcraft Logs records the totals, not the enchant or gem each one came from. What Warcraft Logs recorded you wearing and pressing at your last logged pull ({where}). What Warcraft Logs recorded you wearing and pressing at your newest pull in {where}. What Warcraft Logs recorded you wearing and pressing at your last logged pull. {n} ranked players of your spec in {dungeon} at +{levels} are the comparison. How many sockets an item has is not in the log, so an empty socket and no socket look the same. Read from the buffs you had when that key started. Class set need {n} more not worn The tree as the game lays it out. Brightness is how many of the ranked players take a node, the number under it is the share of them who take it, a green border is one you take and a red one is a node 70% of them take and you do not. Your build on the layout the game uses. Hover any icon for the spell. {share} of them {share} of them, you too {share} of them, not you From {where}. your last logged run Enchant your {slot}. {share} of them have one. {share} of them have one, most often {spell} ({pshare}). Gem your {slot}. {share} of them have {what} there, so the slot takes one. {n} gems a gem Your {slot} is {yours}, their median is {theirs}. The common piece there is {item} ({share} of them). 1 set piece; most of them run {modal}. {n} set pieces; most of them run {modal}. No set pieces; most of them run {modal}. {share} have the 4-piece of {name}. That is the biggest single difference in this list. {share} have the 4-piece. That is the biggest single difference in this list. Not wrong on its own; worth knowing it is a minority build. healing damage Raw damage minus what the boss healed back, so a heal that landed no longer flatters the number above. The gap between the two lines is the heal. Healed back: {you} on you, {them} on them. step {n} of about {total} · {pct}% step {n} Timed, +1 Timed, +2 Timed, +3 The key gives you {t}. The run {t} too slow. {t} to spare. Times you stopped to fight {trash} trash pulls and {bosses} bosses. {trash} trash pulls and {bosses} boss. Trash cleared Priced in seconds further down. Nobody died. You needed {t}. The routing items below are worth about {t}, so you would have made it without anybody playing better. Routing gets you about {t} of it; the rest has to come from the items below and from damage. Nothing in the route stands out, so the time has to come from the items below. You timed this one. Here is what would still make it faster. The run split at the bosses. The percentage on each pull is {worth}: the dungeon asks for 100% and that pull delivered that slice. A big slice in a short time is a good pull. how much of the key it was worth Trash before {boss} After the last boss {t} in {n} pulls {t} in {n} pull {n} pulls, bosses included. Matched on spec where both groups brought it, otherwise on role and damage rank. Damage per second here divides only by the time that player was actually doing something, so standing still is already taken out. {click} to see what the two of them actually pressed. Show what each of them pressed {who} cast {casts} spells across {abilities} abilities, {rate} a minute. {who} cast {casts} across {abilities}, {rate} a minute. Almost the same rate, so the difference below is {which}, not how often. A real gap in how much either of them got to press. Different specs, so read the spell list as background rather than a target. only them only you {n} of {met} debuffs eaten without a single dispel. Every debuff met was dispelled at least once. Every dispellable debuff the party picked up (type from Wowhead), plus anything either group dispelled anyway, and how long each group walked around with it. Seconds are party-wide: 52s means someone had it for 52 seconds, not five people added up. Per minute is the fair column, because a longer key collects more debuffs. Every dispellable debuff the party picked up (type from Wowhead), plus anything the group dispelled anyway, and how long the party walked around with it. Seconds are party-wide: 52s means someone had it for 52 seconds, not five people added up. Per minute is the fair column, because a longer key collects more debuffs. You carried They carried {n} applications, {dispelled} dispelled{rate}. ate all {n} {n} of {all} unknown Enemy buffs removed (Soothe, Tranquilizing Shot and the like). Not something you carried, but the same job. you they {who} removed {n} of {all} {who} {never} On the party for the whole run in both logs and never dispelled, so not counted: {list}. On the party for the whole run and never dispelled, so not counted: {list}. Warcraft Logs does not say whether a debuff can be dispelled; the type column comes from Wowhead. {n} of these could not be looked up this time. "Ate all" means every application ran its course with nobody pressing a dispel. Dispelled can exceed applications when one application is cleansed off several people. Dispels What the closest {n} press that {who} does not You cast {yours} spells a minute; their median is {theirs}. A real gap in how much gets pressed. Compared against: {n} of {of} enchants {n} gems {n} gem {share} of them have {what} there, so the slot has a socket for them; if yours has none, that is a socket to add. {shared} talents in common, {diff} that differ. A lit node is one {them} took, a green outline is one you took, and a red outline is a node they took and you did not. {shared} talents in common. Every node is the same on both sides. {shared} talents in common. you take it {who} takes it theirs, not yours They took, you did not You took, they did not They had an enchant on {slots} where you had none. They had a gem on {slots} where you had none. Nothing between the two sets of gear stands out. {spec}, both of you. {a} against {b}. Every rate below divides by each player's own active time, so a slower key is not held against anyone. Within 3% of each other. You {what} by {pct}. They {what} by {pct}. healed more per minute took less damage a minute Overheal {a} against {b}. The healing table is first below; the damage rows are here because a healer's damage still counts against the timer. Mitigated {a} against {b}. Damage taken is the table below the advice; a tank's own damage is here too, because it is still part of the timer. Same output within 3%. You did {pct} more damage per active second. They did {pct} more damage per active second. On {n} more item levels. Warcraft Logs has no public rankings for {who} in {dungeon} around +{level} yet. {n} ranked {spec}s at +{a} to +{b}. Warcraft Logs ranks tanks by damage, so this list is ordered by damage; survival is compared player against player once you pick one. The gear view is instant: set pieces, enchants, gems and the talent tree against this same pool. The spell list reads eight of their runs the first time. Reads their eight runs the first time, then a day of cache. Comparing as {name}, {spec}. Pick another above to change it. {name} has no logged Mythic+ runs this season, so there is no run to search around. Log a key, or paste a log above and pick yourself. Pick the realm too, or type Name-Realm. The season view did not load. Reload the page and try again. Paste a Warcraft Logs character link (either the region/realm/name form or /character/id/12345), or type Name-Realm and pick the region. Pick yourself above to search around this run, or clear the box and paste your character link instead. Paste a link to your own Warcraft Logs Mythic+ run in the box above first. It looks like https://www.warcraftlogs.com/reports/CODE?fight=3 Pick one to see what changed between then and this run. timed depleted higher key lower key Earlier run (different week) score {n} +{lv} keys +{a} to +{b} keys same affixes ({list}) the same {n} specs at least {n} of your {all} specs {role} ({specs}) none found within {n} item levels of you faster than you by up to {n} minutes faster than you inside the timer inside the last 15% of the timer {list}. {sort} first. {who}'s gear against the ranked {spec}s two pieces turns on a bonus that applies to every pull. The bonuses are listed below. four pieces turns on a bonus that applies to every pull. The bonuses are listed below. You take {n} talents that 70% or more of the {builds} ranked players share. Outside reference: {link} top {spec} gear across every dungeon on Murlok this table is {dungeon} at +{levels}, read from the same rankings as the list of players. Warcraft Logs has no public rankings yet for {dungeon} around +{level}. Try again in a few days, or paste a run to compare against directly. {n} public runs of {dungeon} at +{a} to +{b}, found by searching the rankings once for each spec in your group. you brought {specs}, they did not identical setup to yours Compare against this {mins} minute run, {shared} of your {of} specs Both boxes need a Warcraft Logs link before two runs can be compared. Paste a Warcraft Logs link to a Mythic+ run first. Affixes: {list}. Both runs on the same affixes: {list}. Yours on {a}, theirs on {b}. unknown affixes Shared comparison. Share this before-and-after. Share this comparison. Shared run check. Share this run check. boss {v} group dps {v} dps {n} mobs 1 mob no key % {pct} of the key healed back {v} {v} healed into the boss {n} of {total} kills count for nothing {n} of {total} kills count for nothing ({mob}) Damage you had to do twice. This is a Magic buff on the boss, not a cast: Purge, Spellsteal or an offensive Dispel Magic removes it; a kick does nothing. Damage you had to do twice. This is an enrage: Soothe or Tranquilizing Shot removes it; a kick does nothing. Damage you had to do twice. A kick does not stop it, but crowd control breaks it. Damage you had to do twice. No button removes this one; it is denied by play. Damage you had to do twice. No button removes this one; it is denied by play. Method: {note} Damage you had to do twice. Your raw boss damage per second is fine; the health bar moved slower because it moved backwards. Purge the boss heal Soothe the boss heal Stop the boss heal Deny the boss heal Kick the boss heal Bloodlust {n} of {of} went somewhere else Bloodlust went to the same pulls The biggest cooldown in the run should land on the pull with the most health in it. Presses are compared first against first, so a run long enough for another one is not counted as a disagreement. An extra press is what a longer run buys, not a different plan. It is here so a count difference is not read as a disagreement. Head Neck Shoulder Shirt Chest Waist Legs Feet Wrist Hands Ring Trinket Back Main hand Off hand Tabard You cleared {pct}% of the trash the key counts when 100% is all it wanted, which is about {mobs} mobs' worth of killing nobody asked for. You spent {out} out of combat across {pulls} pulls, an average pause of {mean}s before each one. At {ref}s a pull, which is what a group that knows the route spends, that would be {less} less. That is {n} a minute. The game itself flags this one as a cast that must be stopped. The bosses healed back {a} on you. You stopped {you} of {of}. {a} avoidable damage a minute, {share}% of everything you took. {spell} at {t}, out of combat. {spell} at {t}, on {pull}. {spell} at {t}, on {pull}, pressed early. {spell} at {t}, on {pull} ({pct}% of the key). {spell} at {t}, on {pull} ({pct}% of the key), pressed early. Trash to {n}-piece none They ran a {theirs}, you {yours}. You ran a {yours}, they {theirs}. {n}-piece hero Both on a {n}. Diamonds are bosses. Everything else is the trash between them. Diamonds are bosses. Everything else is the trash between them, walking included. Same enemies, one fight instead of several. Splitting a pack costs you the walk in, and your area damage lands on fewer targets while your cooldowns are already running. Who actually pressed something. A kick is a short cooldown meant to be spent; a stun or knockback is usually a one-off you save. {a} in {na} pulls · {b} in {nb} {a} in 1 pull · {b} in {nb} ilvl {n} {n} deaths 1 death score {n} {t} over {t} to spare timed +{n} depleted they lead {p} you lead {p} /min difference Two public {dungeon} runs: {ours} against {faster}. A public {dungeon} run, {checked}. ours Paste your own log above to get the same for your key. The link unfurls with the verdict in Discord and on Twitter. The link unfurls with the result in Discord and on Twitter. {n} more pulls than they needed. Same or fewer pulls than them. certain roughly {n} pulls over {t} including the walk. They did it in one, in {theirs}. Their pull killed a different amount ({ratio}x), so read this as a hint. Show what they pressed Warcraft Logs counts {reached} of the {required} the key needs, but the key was timed, so the count was reached. The other {missing} is count the log does not file as a kill: its per-mob count values for this dungeon, or an affix mechanic. Read the percentages here as approximate. The key needs 100%. You killed {reached} of the {required} it counts. {boss} is healed to the finish, not killed: {yours} of healing landed on it from you ({ytot} over {ytime}) against {theirs} from them ({ttot} over {ttime}) Its seconds sit in the boss row above; the gap there is healer throughput and kill order, not group damage. Over the bosses you kill: {a} against {b}. {boss} trade an immunity: {spell}, {note}. Every second into the immune one is wasted and reads as low boss damage here; that is target discipline, not throughput. Both runs split at the bosses, because those are the only points the two routes are guaranteed to share. Within each stretch you can see your pulls against theirs even when the counts differ. The percentage on each pull is {worth}: the dungeon asks for 100% and that pull delivered that slice. A big slice in a short time is a good pull. Your run Their run This run Your earlier run Mythic+ run check Mythic+ comparison with the 4-piece bonus with a set bonus ahead of you on {metric} within 10% of your {metric} key timed key timed inside the last 15% no set bonus Reading that character Warcraft Logs links some characters by id, which needs one lookup before the season. One lookup against Warcraft Logs for their season: every dungeon, best run first. Looking for players like you Reading the Warcraft Logs rankings for your spec at your key level and {levels} either side. Repeat searches are instant. one level {n} levels one key level {n} key levels Looking up your earlier runs One lookup against your character on Warcraft Logs. Reading the eight closest {who}s One run each, closest by key level and gear. The first time takes a while; the result is kept for a day. Reading what the ranked {who}s wear Set pieces, enchants, gems, talents and the item in every slot across the rankings pool, against your gear at the pull. A few seconds the first time, then a day of cache. Reading both runs Two logs, one player each. The first read takes a moment; after that both are cached. A full dungeon is a lot of pulls, and each one is measured separately. This takes a moment the first time; after that both runs are cached. Reading the run Every pull is measured separately, plus every cast, death and heal. This takes a moment the first time; after that the run is cached. Looking for runs to compare against Checking the Warcraft Logs rankings for every spec in your group, {levels} either side. That is up to {n} lookups, so give it a few seconds the first time. Repeat searches are instant. Four ways of asking the same question, each removing a different excuse. If the boss row is level, your damage is fine and the clock went somewhere else. Four ways of asking the same question, each removing a different excuse. Boss damage is the raw number; trash damage is mostly the route; the last line is the one Warcraft Logs shows. How much damage did the whole group do per second on {what}? And per second of boss {what}? And per second on {what}? How much damage did it take to clear {what}? What does {what} say your group DPS was? bosses trash 1% of the trash health bar actually cleared Bosses have fixed health and you fight them one at a time, so nothing about the route can flatter this. This is your raw damage. Raw damage minus what the boss healed back, so a heal that landed no longer flatters the number above. Mostly decided by how many mobs you pulled at once. A big gap here is a routing gap, not a damage one. Mostly decided by how many mobs you pulled at once. Compare it against another run of the same key to read it as a routing number. The dungeon has a fixed amount of health in it. Two groups that clear the same dungeon land within about 1% here no matter how long they took, so a real gap means somebody killed different things. The dungeon has a fixed amount of health in it. Two groups that clear the same dungeon land within about 1% here no matter how long they took. Shown only so you can see how misleading it is. Warcraft Logs divides your damage by the entire run including every second you spent walking, so a slower key drags this down even when nobody played worse. Key level Affixes Group setup Gear Their time vs yours Timer Set pieces Their key Their {metric} vs yours Only +{n} 1 level either side 2 levels either side +{a} to +{b} Same as yours Any week Same {n} specs {a} of {b} Any Within {n} ilvl Up to {n} min faster Faster, any amount Barely timed Beat the timer Any, even depleted 4-piece bonus 2-piece or more Ahead of you Within 10% Timed or not Closest to you Fastest Closest time to yours Closest gear Most {metric} Fastest run Most like you A time you could hit Same gear, faster Fastest there is Closest to me My gear, more {metric} Same key, most {metric} Their group barely timed it Highest {metric} there is Same tank class Same healer class Same DPS classes Set pieces, enchanted slots and gems per player as Warcraft Logs recorded them when the key started. A missing set bonus or an empty enchant slot costs damage the comparison has already priced. Open a player's gear check for the slot-by-slot list against the ranked. Key % over time Every ranked run, in order. It moves with the pool as much as with you: a week when better players run the same key pushes it down without anything changing on your side. Check this run on its own Compare in timed +{n} The run {pct}% gem it {n} hits ilvl Player {n}-piece none {you} against {them}: {who} had a {theirs} set against your {yours} you had a {yours} set against their {theirs} no enchant on {slots} where they had one no gem on {slots} {n} item levels ahead {n} item levels behind 1 talent they took that you did not {n} talents they took that you did not This log does not carry the buffs each player had at the pull, so only the potions below are certain. {flasks} of {known} had a flask, {food} had food, and {potions} were drunk. You: {flasks} of {known} flasked, {food} fed, {potions}. Them: {flasks} of {known} flasked, {food} fed, {potions}. A flask and food are read from the buffs at the pull; a potion is a cast during the run. Whether one was the right choice, or drunk at a useful moment, is not in the log. rune: {name} Every dangerous spell the enemies started, and how many actually finished. Warcraft Logs counts stuns and knockbacks here as well as real interrupts, because they all stop the cast, so this is your whole crowd control record in one place. Per minute is the fair column: a bigger pull means more casters to deal with. Rows marked {tag} are casts the game itself flags as important, the ones every nameplate paints red. They sit at the top, and a flagged cast nobody stopped is listed too, rebuilt from the cast events. {link}. only one group met it channels that ended well short of their full length kick ready: Under each count: who pressed the stops, and for the casts that got past, who was holding a kick off cooldown at that moment. A player who never pressed their kick all run counts as ready throughout, which is the point of the line. Stopped, got past and cancelled add up to every cast that was started. Got past means the cast finished, whether it hit you or buffed the mob. Cancelled means the cast ended on its own: the caster died first, lost its target, or was knocked or dragged. Those are kills, not saves. A scissors mark counts channels that ended well short of their full length, which the log does not explain: a channel only counts as landed when it ran its course. A group that kills faster cancels more and simply needs fewer kicks, so read a lower stop count next to a higher cancelled count as speed, not sloppiness. A cast that finished can leave a buff on the mob (Evolve grants Evolved); the game flags that buff too, but it has no cast bar and was never a cast, so it is shown as what the cast gained rather than as a row of its own. a buff: purge or spellsteal it, a kick does nothing an enrage: soothe it a buff no button removes not a kick: crowd control breaks it not a kick: move out of it cannot be stopped cannot be stopped: the caster is immune to crowd control not a kick: move or crowd control Fighting Bosses {boss}, trash {trash} Walking and regrouping {a} for you, {b} for them An average pause of {s}s before each of {n} pulls. Trash you did not need {n} mobs’ worth About {t} of fighting for count the key never asked for. You stopped killing when the count was full. Short by Spare This is the whole target. inside the timer Fighting plus walking comes to {sum}, a little more than the {clock} on the clock. The clock is the keystone timer Blizzard reports; fighting and walking are measured inside the window Warcraft Logs recorded, which starts and ends a few seconds apart from it. Fighting plus walking comes to {sum}, a little different from the {clock} on the clock. The clock is the keystone timer Blizzard reports; fighting and walking are measured inside the window Warcraft Logs recorded, which starts and ends a few seconds apart from it. Damage per active second Your total damage over the seconds you were actually doing something. Damage per enemy forces point How much of the dungeon's health bar you personally removed. Duration-independent. Warcraft Logs DPS The column on the site: total over the whole run, walking included. Share of the group's damage How much of the group's total came from this player. Casts a minute Spells pressed per minute of active time. Kicks Real interrupts. Stuns and knockbacks are counted separately as control. (+{n} control) Deaths Times this player died in the run. Damage taken a minute Lower is better. Mechanics eaten, priced per minute of the run. What you brought Flask and food from the buffs at the pull, potions from the casts during the run. Set pieces Class set worn at the pull. The 2-piece and 4-piece bonuses are throughput before anyone presses a button. Enchanted slots Slots carrying an enchant. Ranked players of most specs carry eight. Gems Gems socketed. The log cannot tell an empty socket from no socket. Secondary stats Ratings at the pull, biggest first. Which enchant or gem each one came from is not in the log. same lead stat Reading {name}'s season from Warcraft Logs Could not load that character. Could not read the season habits. No readable runs yet. Warcraft Logs has no logged Mythic+ runs for this character this season. Log a key and come back. logged since {date} Highest timed key +{n} attempted also the highest attempted Runs logged {timed} timed, {depleted} depleted Dungeons timed {n} played Best-run score, summed best score in each dungeon, added up Not yet timed at +{level}: {list}. Those are the keys that raise the floor. Read from the buffs you had when each key started and the potions you cast during it, across the {runs} runs whose log records them. Whether a flask was the right one, or a potion well timed, is not in the log. Read from the buffs you had when the key started and the potions you cast during it, across the one run whose log records them. Whether a flask was the right one, or a potion well timed, is not in the log. Flasked Food buff Potions a run Augment rune {n} of {runs} runs. {n} in total, in {runs} of {all} runs. Counted above. The whole party was using these, so somebody was supplying them and you took them: in {runs} of {all} runs: no flask no food 1 potion {n} potions flask food pots oldest newest What you brought: Where you stand. Who cleaned up, and with what. Whole run You /min You dispelled You stopped You: Your earlier runs Your gear at the pull: Your group Your pulls Yours that few of them take: Yours: a faster one checked on its own compare this run against a faster one gear check must stop neither of you never removed it no counterpart in the other run no enchant no gem no potion nobody stopped it not recorded not taken nothing between them worth naming. nothing here: straight to the boss nothing here: they went straight to the boss players like me rarely taken role only same spec the log itself use this one which buttons you have it your gear and talent build your log Every logged run's score, in order. Rising points at the same key level are the same route getting cleaner. Method's ability tracker A lower mitigated share on the same class means the defensives were not up when the hits came. The death cards above say which ones were ready. A single log can only show what went wrong in it; what a better group does differently needs the second log. Avoidable by Archon's own list for this dungeon, counting only hits the log's shape says were standing in it or overlap. Each one is a healer global spent on nothing and a damage cast not made. Avoidable by Archon's own list for this dungeon: hits that never had to land. Each one is a healer global spent on nothing and a damage cast not made. Avoidable damage costs healer globals, which costs damage, which costs time. Bloodlust went to a small pull Bloodlust went to different pulls Boss damage is genuinely behind Casts that land are damage your healer has to answer, and time nobody spends killing. Chain the packs they pulled together Chaining packs asks the healer for the same healing in less time. Mana is the ceiling on that, and it is the one number no DPS meter shows. Chaining packs is what buys this: fewer pulls means fewer pauses. The seconds are a yardstick, not a measurement against another group. Check the immunity handoff first; a cooldown and talent review comes after that, and after the route. Do not spend a raid night on rotations when the clock says the route is what costs you. Enemies the key does not count Every extra pull costs the walk in, and your area damage lands on fewer targets while it ramps. Fewer stops, not faster running Long stops are recoveries, not routing: a corpse run, a rebuff, a regroup. Priced once in the total, and the deaths item points here. No overpull, no idle time worth naming, no deaths, no dangerous cast that got away and no healer mana problem. To find the next second, compare this run against a faster one. Not a capacity problem, an assignment one. The log cannot see range or line of sight, so read this as "possible", not "certain". Not a decision, so there is nothing here to do differently on the route. It closes with gear, practice and group makeup, and it is listed so the items above are not read as the whole difference. Not a separate job: this is what chaining packs buys you, priced on its own so you can see it. It is counted once in the total. Nothing stands out Cooldowns left on the shelf One global each, before the pull. This is the half of the composition gap that is yours to close, which is why it is here and not under the line that says no plan changes it. Priced at your own trash damage rate, before counting the walk to reach them. Routing gets you {t} of it; the rest has to come from damage. Seconds out of the fight weighted by that player's share of the group's damage, against the same figure for them: the time the pulls got longer for it. A tank or healer death stalls the whole pull and is not priced this way, and the walk back after a wipe is priced under stops. Seconds out of the fight weighted by that player's share of the group's damage: the time the pulls got longer for it. A tank or healer death stalls the whole pull and is not priced this way. Seconds out of the fight; the damage share of a tank or healer death is not what it costs. Shorter stops, not fewer Stand in less Stop killing enemies the key does not count Stop more The biggest cooldown in the run belongs on the pull with the most health in it. The biggest cooldown in the run should land on the pull with the most health in it, and the two groups disagreed about where that was. The count bar is the only thing the key pays for. Time spent on a mob worth nothing is time, however many of them there are; the pull card says how many. The fight ends when the boss is full, so the clock here is healing landed on the boss and whatever gates it, not group damage. The boss-damage line leaves this fight out. The mitigated share is what armour, absorbs and defensives took off before the hit landed. The routing items below are worth {t} between them, so you would have made it without anybody playing better. The same work, done slower Worth a cooldown and talent review. Chase it after the route, which is usually cheaper to fix. You ate a lot more You needed {t}. You timed this one. Here is what still separates the two runs. Your boss damage is not the problem already ahead already good approximate damage deaths defensives healer interrupts no time attached not a decision route to gain to gain on them to gain with this group with this group {t} if every merge were carried {t} your deaths cost Deny Kick Purge Soothe Stop Hide the full breakdown Where the {t} went You Them Spell There is one place where they killed the same enemies in a single pull and you took {pulls}. There are {places} places where they killed the same enemies in a single pull and you took {pulls} between them. The biggest is {names}: {yours} for you against {theirs} for them. Those seconds are priced at their kill rate. At your own trash damage rate the same merged pulls take longer, which puts the saving nearer {near}; the truth is between the two, because part of a lower trash rate is the smaller packs themselves. {zero} of the {kills} mobs in the {pull} pull were worth nothing to the count. {zero} of the {kills} mobs in the {pull} pull were worth nothing to the count ({n} {mob}). They killed {n} of the same kind there. They killed none of that kind there. {n} more pulls had ten or more such kills. One more pull had ten or more such kills. Method on {mob}: {note} You cleared {pct}% of the trash the key counts when 100% is all it wanted, which is {mobs} mobs' worth of killing nobody asked for. They finished on {theirs}%. Their key was timed on that {pct}%, so Warcraft Logs' count for this dungeon is off by at least {off} this week; read the {mobs} as approximate. You spent {yours} out of combat against their {theirs}. Your average pause between pulls was {yours}, theirs {theirs}. That is twice as long, so the time is in the length of each stop, not their number. That is twice as long, so the time is in the length of each stop rather than their number, and you also had {extra} more of them. That is {how} longer, so the time is in the length of each stop, not their number. That is {how} longer, so the time is in the length of each stop rather than their number, and you also had {extra} more of them. They are nearly the same length; you just had {extra} more of them. After a pull with a death your pauses averaged {after}, after a clean one {clean}: about {secs} of the stops is regrouping after {n} deaths. After the pull with a death your pauses averaged {after}, after a clean one {clean}: about {secs} of the stops is regrouping after it. That is where a death's real cost sits. The rest is stops that were long on their own. {through} of {begun} landed on you ({pct}% stopped). They let {through} of {begun} land ({pct}% stopped). Per minute that is {a} against {b}. The bosses healed back {a} on you and {b} on them. The bosses healed back {a} on you and nothing on them. Mostly {spell}. Mostly {spell} on {bosses}. You stopped {you} of {yourOf}; they stopped {them} of {themOf}. You stopped {you} of {yourOf}; they never faced it. {k} a second of healing landed on {name} from your side ({m} over {secs}). {k} a second of healing landed on {name} from your side ({m} over {secs}, {who} {pct}% of it). Against {k} a second from theirs ({m} over {secs}). Nothing of the kind is logged on their side. Method: {note} Across the bosses you kill you did {a} group damage per second against their {b}, {pct}% behind. A boss you kill has fixed health and no pack-size effect, so this one is not routing. {names} is healed, not killed, and is left out here. {name} trade an immunity ({ability}: {note}); every second into the immune one is wasted and reads as low boss damage here, which is target discipline, not throughput. You were {t} faster than them across the bosses. Everything you lost, you lost on trash and between pulls. On this page Sections Collapse all Expand all Fold this section {a} avoidable damage a minute against their {b}, {share}% of everything you took. Mostly {top}. {who} took {amount} of it. Same spec, same kit. {a} taken a minute against {b}. The mitigated share is what armour, absorbs and defensives took off before the hit landed. {a} per minute against their {b}, {times} times as much. Of the {total} must-stop casts that got through, {ready} started while at least one interrupt was off cooldown. Of the {total} must-stop casts that got through, {ready} started while at least one interrupt was off cooldown: {who}. Your group can produce about {supply} stops a minute ({kicks} kicks, {stops} stuns and knocks); the busiest pull asked for {peak}. {healer} bottomed out on {pulls}, and finished the run at {end}%. {healer} bottomed out on {pulls} and {more} more, and finished the run at {end}%. Their healer never went below {min}%. Yours went on {a}. Theirs went on {b}. Lined up in order, {n} of the {of} presses both groups made landed on different pulls: yours on {a}, theirs on {b}. Both groups pressed it on the same {n} pull(s), in the same order. Both groups pressed it on the same {n} pull(s), in the same order. The longer run came off cooldown again, so there were {extra} more press(es) on {where}, which is what the extra time allowed rather than a different plan. {list}, with that share of the run behind each one. Worth roughly {lo}% to {hi}% of damage between them. And about {pct}% off the damage everybody took. {who} to {killer}. {who} to {killer}, in one hit. {who} to {killer}, with {defs} ready. {who} to {killer} on {pull}. {who} to {killer} on {pull}, in one hit. {who} to {killer} on {pull}, with {defs} ready. They died {n} times for {secs}, priced at {theirs} against your {yours}. They died once for {secs}, priced at {theirs} against your {yours}. They did not die. That is the fighting-time cost only: about {secs} more sits in the stops after those pulls, priced in the stops item. Asked one at a time, in order: {n} would have lived by not standing in something. {n} by a defensive that was ready. {n} by an external somebody had up. {n} arrived too fast to answer. {n} nothing in the log would have stopped. {name} is healed to the finish, not killed {a} mitigated {apct}% of incoming damage, {b} {bpct}% {n} must-stop casts landed while a kick was ready 1 must-stop cast landed while a kick was ready {n} deaths, {stoppable} of them stoppable 1 death, {stoppable} of them stoppable {n} deaths, {secs} of fighting without them 1 death, {secs} of fighting without them Healer mana fell to {pct}% {n} group buffs your own classes can cast and did not keep up 1 group buff your own classes can cast and did not keep up The items above account for {acc} of the {total} between the two runs. The rest is the same trash killed at a different rate: {a} group damage a second of trash combat against their {b}, {pct}% apart, though part of that is their bigger pulls. The boss share of the gap is its own card above, not counted here. The rest is the same content killed at a different rate: {a} group damage a second of combat against their {b}, {pct}% apart, though part of that is their bigger pulls. The rest is the same content killed at a different rate. Their group averages {theirs} item level against your {yours}. On the bosses, where pack size cannot flatter either side, the gap is {pct}%. Their side also handed out {list} that yours did not, which lifts whoever received it. Your side handed out {list} that theirs did not. Composition: their group brought {list} and yours did not. Composition: yours brought {list} and theirs did not. {n} more were up on both sides, so they explain none of this. The buffs nobody in your group could cast are worth roughly {lo}% to {hi}% of damage between them, which is a share of this line that no play changes. Separately, {list} could have been cast by your own group and was not kept up, worth about {lo}% to {hi}%: that one is a decision, and it is listed above. {who} bring no group damage buff at all ({brings}), so an empty column there is not a hole. Their enemies took {pct}% more damage from everything all run ({names}), which is a share of this gap nobody in your group could have played their way out of. Your enemies took {pct}% more damage from everything all run ({names}). Item level Embellishments Hero talents yours they take it rarely enchanted {pct}% enchanted Their median is {n}. Average across the slots worn. {four} of them run the 4-piece, {two} at least the 2-piece. No class set worn. Most of them carry {what}. Sockets are not in the log; compare per slot below. {n} of {cap} A character may wear {cap}. They are crafted, so the empty slot is buyable. Both slots used. Enchanted slots none Whole season, charted now vs then theirs your pulls {n} pulls {a} for you, {b} for them, bosses included. theirs. Bosses do not count toward the key, so they show no percentage. {t} between the two runs: Reading from {log}. To find the next second, {link}. Reading from {yours} and {theirs}. Against what the ranked players of the spec run instead, open {link}. The party-wide cast count Warcraft Logs reports is {n} higher than the per-spell rows it returns for {who}. The shares above are worked out from the spells actually listed, so they add to 100% and stay internally consistent; the missing casts are not attributed to any spell we can name. {link} adds its Avoid and Interrupt flags, and tells a buff to purge from a cast to kick. timed +{n} not logged log vs your best whole run vs your timed one bigger dot, higher key {n} runs {n} timed timer {t} of {t} {t} to spare {t} over {dungeon} +{level}, {result} {dungeon}: +{level}, {result}, {time}, {date}. {runs}, {timed} timed. {dungeon}: no logged run. Week of {date}: {runs}, {timed} timed best +{level} {n} kicks a minute, {stopped} stopped, {landed} landed {n} dispels a minute, {could} could have been dispelled of {n} score {n} Saved as you Forget Mark as me Remember this character in this browser, so every screen can offer its runs. Stored in this browser only. Recent runs My last {n} keys {who}'s last {n} keys My keys Recent keys Check this run Compare it We recognised you as {name} from last time. Not you? Pick another. {spec} at this key level, one level either side, on your gear. Avoidable damage / what was mitigated Packs they pulled together / you did not {who} is still on the character tab. Search around that character Dungeon {runs} runs, {timed} timed Pick a dungeon to search in. The best run you logged there is what the players are found around. Remember {who} as you? Yes No How to improve this season for {spec} The log records the buffs you had when the key started and the potions you drank; whether one was the right choice is not in it. Read from what each of you wore at the pull; how many sockets an item has is not in the log. Where you both stand. Among {n} ranked {spec} in {dungeon} +{levels}, you are at the {you} percentile and {them} at {theirs}. Compared against {n} ranked {spec} in {dungeon} +{levels}, not against that opponent. {pct} of the ranked run the 4-piece. The ranked enchant {n} slots. The ranked gem {n} slots. Ranked parses only, so the floor is high: most players who ever ran this key are not in that pool. Among the {of} of them within {band} item levels of your {ilvl}, you are ahead of {pct}. A key percentile does not normalise for gear; this one does. A band this small is thin: read it as a hint, not a placing. Slots carrying an enchant. Something missing? What were you looking for? The thing you came to find out and could not. Or anything here that looks wrong. I wanted to know whether... Email, only if you want an answer Send Sending... Thank you. I read every one of these. A few more words, please. That is enough from here for one hour. Try again a little later. That did not send. Try again in a moment. Close