KeyAudit

Key Audit

Damage meters tell you what you did. Key Audit tells you what you didn't.

At the end of every Mythic+ key it opens a report showing, for each of your cooldowns, how long it sat off cooldown and unused — converted into the number of casts you left on the table. Then it tells you, in order, what to fix.

What it measures

Cooldown efficiency. Every major cooldown, ranked by how much of the key it spent available and unpressed. Green under 12%, red above 25%. The "worst gap" column is usually the more useful one: four minutes of idle spread evenly is a rotation problem, four minutes in one block means you forgot it existed through two boss fights.

Cooldown pairings. Pressing Shadow Blades without Symbols of Death, or Summon Demonic Tyrant without your demons out, wastes the entire cooldown rather than a slice of it — and it's invisible in a damage meter, because you still did damage, just far less than you should have. Key Audit warns you on screen the moment it happens and tallies it in the report. 25 specs ship with rules.

Death review. On every death it records what you had available that could plausibly have changed the outcome — and only that. Your personal defensives are counted when you were the one who died. Externals you can spend on someone else are counted always. Interrupts get a softer mention. Everything else in your kit is never named, because a DPS filler being off cooldown is not a finding.

Which means it will also tell you when a death wasn't yours. "3 of 4 deaths happened with nothing of yours that could have helped. Those were not yours." That verdict is worth as much as the critical ones.

Stealth openers. Rogues get a nudge when you're out of combat in a dungeon with Stealth ready and you're not stealthed.

It learns your cooldowns

Cooldown durations are secret values in patch 12.x — no addon can look up how long your Combustion is. So Key Audit measures it: the gap between your cast and the cooldown coming back is the duration, with your talents and haste already baked in. It gets more accurate every key, and it's correct for your build rather than a wiki's.

The first key or two will show - in the UNUSED column while it gathers samples. /ka spells shows the progress.

Built for Midnight, not ported to it

Patch 12.0 removed the combat log from addons and made health, enemy casts, aura data and cooldown timings secret. Most analysis addons lost their data source. Key Audit was written afterwards, on the data that survived: your own casts, your own cooldown availability, and the clock.

It queries nothing about anyone else's state, reads no enemy information, and makes no in-combat decisions for you. It's a retrospective, and it can't affect the run it describes.

Things it deliberately does not claim to do, because they're no longer possible for any addon:

Track other players' cooldowns or defensives Tell you what killed someone Read anyone's health, including your own Track your own buffs or debuffs directly

Charge-based cooldowns are reported with cast counts only. currentCharges is a secret value, so nothing can distinguish 1-of-2 from 0-of-2, and inventing a number there would be worse than admitting the gap.

Commands Command What it does /ka Open the report (or click the minimap button) /ka spells Tracked cooldowns, learned durations, active pairing rules /ka start / /ka stop Manual session, for testing outside a key /ka ignore <spell> Leave a spell out of reports /ka unlock / /ka lock Drag the on-screen warnings where you want them /ka tips on|off Coaching verdicts vs plain numbers /ka combat on|off Count idle in combat only (default on) /ka minimap on|off Hide the minimap button /ka wipe Clear history and learned durations Notes Every spec gets the cooldown audit, death review and trend history — the tracked list is built from Blizzard's own Cooldown Manager, so it's always correct for your spec and talents with nothing to configure. 25 specs additionally ship with pairing rules. Specs without them simply skip that check. History keeps your last 30 runs per character and compares each new key to your recent average. No library dependencies. Nothing embedded that can collide with the rest of your UI.