Reading a Logbreakdown report

A report is one raid night, read from the combat log file, as a page of tabs. This page is how those tabs are read: what the Fights scope does, how a role is decided, what red and yellow mean, and how each sheet is built. None of it depends on which version of the game the log came from. What counts in a given version, which flasks, which potions, which drums, which trash, sits on that version's own pages: CLA in TBC Classic and RPB in TBC Classic.

Above the tabs, the report sums the night in two lines: kills, wipes, deaths and what needs fixing, then how the evening was spent: hours raided from the first pull to the last fight, the share of that time in combat (boss pulls and trash packs together), and the longest break with the boss that followed it. On a night with several raids the whole-night page counts the walk between instances as a break; each raid's own page does not.

Under those lines, a short paragraph puts the same findings into sentences: the night's numbers, then the two or three things worth raising, named raiders and all. It is composed from the sheets below it, never from a second opinion, and it stays on boss kills so it does not move when the Fights menu does.

Two sheets on one page

The old raid-lead spreadsheets came in two halves, and the report keeps the names. CLA, Combat Log Analytics, is preparation: what each raider brought to the pull. RPB, Role Performance Breakdown, is performance: what they did once it started, judged by their role rather than against the whole raid. The page has four tabs, and the sheets sit under them: Raiders is the night on one screen, Prep is what was brought to the pull (the CLA half), Combat is what each raider did in the fights and Pulls is the night pull by pull (the RPB half).

Which fights the numbers count is picked in two places. On a night with more than one raid, the Raid chips under the title pick the whole night or one raid, and change the page. The Fights menu at the top of the sheet picks the boss kills, every boss pull, the full raid, trash only, or a single boss of that raid, and changes only the numbers. The checks read from lists of items, enchants and consumables. A raid team can copy those lists and edit them: allow something the list forbids, mark an item cheap instead of wrong, or forbid it only in one raid. Until a team copies the lists, reports use the defaults. Visitors of a shared link see that team's lists, not their own. A chip with the team name on the report means those lists are in use.

Fight scope

Every number on the report follows the Fights menu at the top. It lists the whole night and each raid, and under a raid the four scopes below and every boss of that raid in pull order. Pick one boss and Raiders, In combat, Graph, Group buffs, Drums, Casts, Debuffs, Gear and At pull all count that boss's pulls. A tab that cannot follow the pick is greyed and says why when opened: Gear, At pull and Group buffs on Trash only, since gear and buffs are read at boss pulls, and the Trash tab on one boss, since trash requirements are counted per raid.

A kill no scope sums is left out of the Graph sheet and of Missed pots the same way; see below. What a scope is not: a filter on preparation. Gear and buffs are read at the pull, so a raider's flask share and gear problems follow which boss pulls you pick but have nothing to show for trash, and the trash minimums are counted per raid whatever is picked. Missed pots and Open (s) sit outside it too, on purpose: a potion cooldown does not care which fights you have picked. The one pull they do skip is an encounter the raid does not fight itself, the Chess Event: no scope counts it, so it is not a missed pot and the Graph sheet does not draw it.

The open scope is part of the address, the same way the tab is. A link like #combat&scope=night opens In combat on the full raid. Boss kills is left off the hash. #scope=trash or #combat&scope=trash is the trash scope. One boss is #scope=boss: followed by the encounter id, which the menu writes for you. Bare #trash is the trash-requirements tab, not this control. More under sharing.

Logs parsed before trash fights have Full raid and Trash only disabled until you re-upload. The report says so. The graph and Missed pots / Open (s) wait on a re-upload too, and so does the list of bosses in the menu.

Stop at 3 deaths. A pull that has lost three raiders is a wipe in progress, and what happens after says little about anyone. With the box ticked, every per-pull number on Raiders, Consumables in combat and Casts stops at each pull's third death, kills included, as Warcraft Logs' wipe cutoff does. The scope line says how many pulls were cut. The Deaths tab and the potion graph keep counting to the end.

Roles

Four roles: tank, healer, caster and physical. The role comes from the spec in the log and from what the raider did, voted on boss pulls including wipes. Trash fights do not vote. The role picks which checks apply, which potion is expected, and who the raider is compared with on the Casts tab. Every tab can be filtered by role with the buttons above it.

A role is a job for the night, not a class. The same druid can be a tank on one night and a healer on the next, and the report follows what they did, not what the armory says.

Raiders

The first tab is the night on one screen: one row per raider, every check as a column, sorted so the raiders with the most to fix come first. The Fights menu picks which pulls the columns count, from the whole night down to one boss, and the line under the tabs spells out the pick. The colours are the same everywhere on the report: red is a talk, yellow is a nudge, a dash is nothing to say.

The last row is the raid average. Click a count and the matching tab opens with that raider's row expanded. Open a row here and the fight numbers appear under it, for the selected fights. On Trash only a line says flask, food and gear are still share of boss pulls. Clicking the name opens the row too; the small badge beside it is the way out to that raider's own page, and it is the same wherever a name is shown on the report.

It is a checklist, not a ranking. The sort puts the most red on top so the raid leader reads those rows first, but two raiders with the same red count can have had very different nights: one missing enchant on a fresh upgrade is not the same as one item that does not belong in a raid. Open the row before writing the message.

Own, received and given. TBC logs put Windfury Attack swings, Judgement of Light and Improved Leader of the Pack heals, Thorns hits and Judgement of Wisdom mana on the player who benefits. The opened row shows what a raider received through those buffs and what they gave others, split by damage, healing and mana. A share that cannot be placed stays on the receiver and is listed there. By default the report counts them where the log put them. A team rule under Team rules → Attribution moves each buff to the giver, and the line under the tabs says which buffs are moved. Logs parsed before 0.8.0 need a reparse before that rule can move Windfury, Judgement of Wisdom or Vampiric Touch mana. Given damage is an estimate: the extra Windfury swing as logged, Power Infusion as 20% of the spell damage under it; crit and proc luck stay with the receiver. Innervate and Misdirection are counted, not valued.

On a night with more than one raid, a raider who is wrong in one instance and clean in the next stays red on the whole-night page. Chips next to the name show which instance is which: red if that raid has a serious problem, yellow if it only has cheap ones. Open the instance page to see that raid alone.

See the Raiders tab on the sample report.

Deaths

One row per death in the selected fights. The first death of each pull is starred. A hunter's Feign Death is not a row, and neither are the fifteen seconds a priest spends as a spirit after the killing blow. Open a row for the last ten seconds: damage and heals with the health line, the killing blow with its overkill, how long before it the last heal landed, and the defensives that were ready and not used.

A one-shot is a hit that took more than 60% in one go. A combo is two or more within a second and a half. A ramp is everything slower. Fen on Magtheridon is a ramp: Shadow Grasp ticks the health down, a Flash of Light lands 0.7 s before the end, then Blast Nova. 'Ready and unused' is a fact, not a verdict: a healer with a potion off cooldown at 0.7 s from the last heal had no time to drink it. Deaths in the seconds after a pull ended are listed under that pull and not counted elsewhere.

See the Deaths tab on the sample report.

Pulls

The Pulls sheet is the night in the order it happened: one row per boss pull in the selected fights, with the result and the length, how many died and who went first, when Heroism went out and who cast it, how many damage dealers had a potion, a drum and an on-use trinket up in the Heroism window, and the share of the pull the always-up debuffs were on the boss. A pull without Heroism on a fight over a minute is red in that column; more than one cast is wasted under Exhaustion. Open a row for that pull's deaths and every debuff with its owner. Deaths and Debuffs, the two sheets beside it, hold the same pulls from the other side: every death, and every debuff across the pulls.

See the Pulls sheet on the sample report.

Gear

At every boss pull the game records what each raider is wearing, with enchants and gems. The Gear tab lists everyone who fails a check. A raider with a clean set is not on the tab at all. Open a row and each problem is a short stack: slot, item name when we have it, enchant when the problem is the enchant, then the verdict, then where it was worn. The combat log often has no item name, only a slot; the report says so rather than pretending the enchant is the item. The tab follows the Fights menu down to one boss, and has nothing to show on Trash only, since gear is read at boss pulls.

A cheap or missing enchant is a property of the enchant and the slot, so boss names are only where it was worn, and a long list is collapsed. A check that depends on the boss, gear that is fine on one encounter and wrong on another, keeps the boss in the verdict. The Raiders tab splits it all into wrong gear, in red, and cheap, in yellow. On a night with more than one raid every problem is listed per raid, so a team rule that allows something in one instance only applies there. Which checks exist is a matter of the game version: the TBC Classic list.

Blessings at the pull are on this tab too: Salvation on tank when a tank had Blessing of Salvation, No Kings / No Might / No Wisdom when that blessing was missing while someone else in the pull had it, and Talent points when fewer than 61 points were spent.

What Gear is not: a gear score, a best-in-slot check or an item-level list. A raider in dungeon blues with every enchant and gem in place is clean here, and a raider in full tier with one empty socket is not. The tab asks whether what they wore was finished, not whether it was good. Bosses that call for resistance get a Resistance block above the list.

See the Gear tab on the sample report.

Consumables at the pull

The At pull sheet asks one thing for every boss pull: was the buff up the moment the encounter started? The answer is given as the share of pulls, over the pulls the Fights menu selects: pick one boss and it is the share of that boss's pulls. Buffs are read at boss pulls, so Trash only greys this sheet.

A snapshot at the pull is not uptime. A flask that ran out halfway through a long fight still counts for that pull, and food eaten twenty seconds after the pull does not. That is the trade the old sheet made too: the question is whether the raider was ready when the tank charged, not whether the buff lasted. A buff that counts but is the cheaper version is named in red under Cheap buffs, so the raider knows what to swap. A buff that was up at the pull but ended during the fight and never came back while the raider was alive is listed under Dropped, with the pull and the cause.

Which buffs make up the columns, and which ones are the cheap versions, depends on the game version: the TBC Classic list.

See the Consumables tab on the sample report.

In combat and the Graph

The In combat sheet is the other way round from At pull: it counts what each raider used between the pull and the end of the fight, in the selected fights, and never looks at what was up beforehand. On Boss kills, Boss pulls and one boss the numbers are uses per fight; on Full raid and Trash only they are plain counts, because trash pulls are too uneven to average. Each role has a potion it is expected to drink, and that column is coloured. The Graph sheet draws the same uses on a timeline against the potion cooldown, over the same fights, one boss included.

Which potion a role is expected to drink, how long the cooldown is, and therefore how Missed pots and Open (s) are counted, are facts of the game version: how it works in TBC Classic, with a drawing.

Fight numbers

Open a raider's row on the Raiders tab and the groups that apply appear for the selected fights: Activity, Output, Damage taken, Interrupts and Cooldowns, plus Healer for a healer and Mitigation for a tank. A line is only shown when it applies to that raider, so a mage does not get a line for parries. A number with a list behind it — which abilities, which raiders, where the mana came from — is underlined; click it and the list opens as a panel of its own instead of crowding the line.

Activity

• Active: the share of the time alive spent casting or swinging, averaged over the pulls in the selected fights. Pulls where the raider was alive under 30 seconds are skipped. The slack number. It is not DPS: a raider at 95% who casts the wrong spells is still at 95%. Under 80% on a kill is where to look first.
• Deaths in the selected fights. Yellow from the first one. A hunter's Feign Death is not one: the game writes it as a death, but without the killing blow a real death has.
• Hits per AoE cast: enemies hit per cast of the raider's area spells, direct hits only. Druid, paladin and warlock AoE ticks over time rather than per cast, so the line is not shown for them.

Output

• Damage to boss and Adds sit side by side, with the add names under the number. Adds is the rest of the damage on that boss pull: never trash. On Full raid a third line, Trash, holds the pulls between bosses, and the three add up to the total. Trash only keeps a single Damage done line. Logs from before the split also show the single total. Raw totals, no ranking, no percentile. Read them next to the other raiders of the same role, not the whole raid.
• Healing done and absorbed. Healing done is effective healing. Pets and totems count for the owner. Same rule: a total, not a rank.
• Overheal: the wasted amount and its share of raw healing, healers only. Yellow above 40% and red above 60%. A ret paladin's Flash of Light still shows in Casts.
• Engineering: damage from bombs, grenades and the like.
• Racials used.

Damage taken

• Total and avoidable: the fire, void zones and other damage a raider can step out of, following per-boss rules; the rule is written under the number. Yellow when above zero. Trash has none. Above your peers is the same idea without a list: abilities that hit this raider clearly more than the others in the same role, shown as hits while the median raider in that role took none. Read it as a question, not an answer. A tank's total is their job; a mage's avoidable is a habit.
• From engineering and friendly fire: damage from other raiders' bombs, and from their spells.
• Reflected onto you: damage a raider took from their own abilities, the way a reflecting boss or a backlash hands it back. Abilities that hurt their user by design are not counted.
• Attacks you parried: incoming swings the raider parried. Always shown for tanks.
• Physical, Spells and Absorbed, tanks only: the total by school, and what shields ate before it landed. By ability: the ten abilities that hurt most, as a share of the total. Crushing blows: melee hits that landed at 150 %. Red from the first one. For a tank the line also says how many landed while Shield Block or Holy Shield was up, and how many without.

Mitigation

• Tanks only, and only on logs parsed with the hit flags (recompute on an older file is not enough). Melee swings against you with the hit table: hit, crit, crush, block, dodge, parry, miss and absorb as shares of every swing an enemy took at you. Share of tank melee: your share of the swings that went at any tank in the selected fights. Uptimes and the Sunder line are described on the game version's page.

Interrupts

• Spells interrupted, with the names of what was stopped.
• Times interrupted: the raider's own casts cut short. Yellow when above zero.
• Dispels: successful dispels, decurses and spellsteals, with a Magic / Curse / Poison / Disease / Enrage split and the names and counts of what was removed. Hidden when the raider did none.

Healer

• Healing on tanks and on the raid, with the three raiders healed most. The two add up to Healing done.
• Seconds at 2 % mana or less: how long the healer sat empty, added over the selected pulls. Yellow from 15 seconds, red from a minute.
• Mana gained and where from: mana spring, Innervate is listed by count since the game does not log what it gives, potions, runes, Shadowfiend.
• Earth Shield and Lifebloom at three stacks on the tanks, as a share of the fight time.
• Under the numbers: overheal per spell, and a mana line per boss pull with marks for Innervate, Mana Tide, potions, runes, Shadowfiend and Evocation.

Cooldowns

Cooldowns: for each major cooldown the raider has, uses against how many were possible in the selected fights. Possible follows the wall clock: a chance when the cooldown is ready and the raider is alive on a pull, then the next chance after a full cooldown, including time between pulls — not a fresh chance on every pack. Yellow under three of four, red under two of three. Defensive cooldowns are listed without a colour. An on-use trinket that was worn and never activated is a yellow line. Which cooldowns and trinkets are counted is a matter of the game version: the TBC Classic list.

Lines that only make sense in one game version, a shout uptime, a judgement count, a stack that must be kept up, are listed on that version's page: the TBC Classic lines.

Open a row on the sample report.

Drums and Trash

Two tabs only appear when the game version calls for them. Drums lists every drummer with the drums cast in the selected fights and how many raid members each cast reached, so a raid can see whether the drummers took turns. Trash counts the kills of named trash packs against a minimum per raid, the way the old sheets asked for proof of a full clear. It is a kill count per raid, not the Trash only scope, so it has nothing to show on one boss. Both are game facts: drums and trash in TBC Classic.

Group buffs

The Group buffs tab is who stood in which of the five raid groups on the selected boss pulls, and whether the buffs that group lives on were up. The log never names the group: two raiders who had Leader of the Pack from the same druid, or Sanctity Aura from the same paladin, were in the same group. Casters and healers are placed by the Mana Spring totem and the shadow priest that fed them mana, so they show as unknown only on logs parsed before that was kept, or when raiders swapped groups mid-fight. Mana Spring is the one totem measured on the raider: the share of fight time it ticked on them. The other totem columns are not uptime on the raider: it is the share of fight time a shaman in that group had the totem down, averaged only over pulls where the group is known. Range is unknown, and a totem that dies to AoE can still count as down. Windfury Totem is not marked red when the shaman is twisting; Windfury procs are the proof. Under 80% is worth a word; a dash is a buff nobody in the raid could give; a grey “no giver” is the same thing in a cell. Low numbers on a fight that spreads the raid are the fight, not the raider.

Which buffs the columns are, and what the log cannot see, depends on the game version: the TBC Classic list.

See the Group buffs tab on the sample report.

Casts

The Casts tab is one matrix per role, not the whole raid: pick the role with the buttons above the table. A column per raider, a row per spell that matters for that role, the way the old sheet tracked the abilities each role lives on. Rows are grouped by class, with the spells several classes share under Shared. Healing spells the old sheet named after overheal% show that share as the cell, with the cast count under it, so a Chain Heal rank mix reads as the wasted share per rank. Uptime rows give the share of the raider's fight time in the selected fights a buff was on them, over every pull they were in: a buff already up at the pull counts from the start, and a pull where it never went up counts as zero. Switch classes off above the table to read one class at a time.

It is a comparison between raiders who had the same job on the same night, not a rotation check and not a parse. A low count next to the rest of the role is the question to ask. A low count alone says nothing, since a boss with a long transition gives everyone fewer casts.

See the Casts tab on the sample report.

What is not in it

There is no DPS ranking against other guilds and no percentile. The numbers are per night, per raider, next to the raiders who had the same job. If you want parses, Warcraft Logs does that well. The report is for the raid leader's message the morning after.

What the report needs from the log

Gear, the buffs at the pull and the raiders' specs come from the snapshot the game writes at each pull, and that snapshot only exists with advanced combat logging on. Turn it on once and it stays on. Everything else, the fight numbers, the potions, the drums, the trash counts and the casts, is in every combat log.