Cadence
Know when to press your cooldowns.
You're in a +12. The tank pulls, the pack detonates, and you realize three seconds too late that you should have used your defensive. Again.
Cadence puts a countdown on your screen before the moment that matters. Not a generic "boss is casting something" warning — a specific reminder that you planned, for your cooldown, at the timing you chose.
How it works
You pick a boss. You drop your cooldowns onto its timeline: Anti-Magic Shell at 0:34, Vampiric Blood at 1:17. When the fight gets there, a cue appears — spell icon, countdown, sound, glow. Whatever you set up.
That's the whole idea. No trigger logic, no conditions, no scripting. You decide when you want to press things, and the addon reminds you.
Boss ability timings come bundled, pulled from high-key logs, so you can start planning immediately. Run a boss yourself and Cadence records that fight's timings too.
Team mode
One person builds the plan for the whole group. Five slots, one lane each, cooldowns assigned wherever you want them. Share it with the party and everyone gets their own lane — they see only what's theirs, nobody has to read someone else's assignments.
Already have your own cues set up? Send them to whoever's running the plan. They review what you sent, accept it, and it drops into your lane. You don't lose the work you already did.
Change something later, hit Share again. Everyone updates without another popup.
Interrupts
Set a kick priority — Rogue first, then Shaman, then whoever else. Cadence spreads the interrupts across the roster, respects each kick's cooldown, and drops a cue in each player's lane telling them exactly which cast is theirs.
Getting started
- Type
/cador click the minimap icon - Pick a dungeon and a boss
- Click a cooldown on the left, click a time on the right
- That's it
Open the timeline view if you want to see the boss's abilities laid out and place your cues against them.
Notes
Built and tested on the 12.1 PTR. Bundled timings come from high-key logs, so they cover longer fights than a single run would.
Cadence works fine on its own — BigWigs is optional, nothing breaks without it.
This is version 0.1.0. Personal mode is solid. Team mode works but has had far fewer eyes on it, so if something looks wrong there, tell me.
Feedback
Bug reports and suggestions welcome in the comments. If something breaks, /cad debug TEAM (or CONFIG_UI) turns on the relevant logging — paste what it prints and it'll save us both time.

