Cadence 0.3.0

Every boss timing now comes from live season logs — measured on keys +12 and up.

The previous timings were mined on the PTR. This release re-measures all 28 bosses from roughly a thousand live keystone runs, so the lane shows the fight as it is actually played this season: higher keys keep bosses alive longer, so most lanes now show MORE casts, at times that match what you see in the pull.

Your cues

• Cues attached to an ability follow it automatically, including the handful of abilities the patch re-keyed. One line at login says what was carried.
• Cues placed at a clock time deliberately do NOT move. The old timeline was replaced, not nudged - no rule could carry a hand-placed time honestly. If you keep at-time cues, give them one look against the new lane.

Cleaner lanes

• The season affix (Void Pulsar) no longer appears as a boss ability on every single boss, and an environmental logging artifact is gone from eight lanes.
• Timing confidence markers (the shown-but-uncertain badge, spreads, hit rates) are re-measured from the live runs.

Accuracy reports

• Post-boss accuracy reports start a new revision. Old runs stay readable but will not be averaged with new ones - the lane they measured no longer exists.

Known limits

• The Golden Serpent's Serpentine Gust still shows previous-era times: the live id changed but BigWigs bars the old one, and cues anchored there keep firing off the live bars. The displayed times will catch up when BigWigs re-keys.

Cadence 0.2.0

Boss timers are more accurate, and the addon now tells you when it is not sure.

Your existing plans are carried across automatically the first time you log in. Nothing needs re-doing by hand, and /cad undotimeline puts everything back if you disagree with the result.

Boss timings moved

Every boss timing was measured against the start of the cast instead of the moment it lands. 528 marks moved, most of them 2–5 seconds earlier, a few by up to 10. This is the difference between a cue that warns you and a cue that tells you what just happened.

Your cues moved with them. A cue placed at 0:10 because the lane said an ability fired at 0:10 is still on that ability. You will see one line at login saying how many moved; /cad undotimeline reverses all of it.

One row per ability

Bosses that reused a spell name showed the same ability two or three times. Nalorakk had five rows for two abilities. Twelve of those groups are now a single row — decided by measuring whether the ids actually fire together across hundreds of logged runs, not by matching names, so genuinely different abilities that share a name stay separate.

A report after every boss

/cad accuracy shows how close the timers were on the pull you just did: how far each bar was from where the timeline said it would be, split into the first minute and later, and whether your own cues fired when they were supposed to. /cad accuracy all walks the history.

If you have ever wondered whether a timer is trustworthy on a particular boss, this answers it with your own runs rather than a claim.

BigWigs: what it is actually for

The old message said cues were off without BigWigs. That was wrong and wrong in the direction that matters: time-based cues work fine without it. Only cues that follow a boss cast need BigWigs, because a bar is the only way to know a cast started.

You are now told how many cues in your plan actually depend on it — and nothing at all if you use none. Imports say the same thing before you accept them, and /cad bigwigs shows the download link in a box you can copy with Ctrl+C.

Smaller things

• The timeline update refuses to move a cue before the pull, and says so loudly if the cue count ever changes while it runs.
• A cue pointing at an ability the timeline no longer has is announced by name instead of sitting silently dead in the editor.
• Encounters that produce nothing (no bars, no marks, no cues) no longer clutter the accuracy history.

Known limits, stated plainly

• Late-fight timings drift. On phase-gated bosses a mark two minutes in can be many seconds out, and re-timing does not fix that — it is the fight varying, not the measurement. The accuracy report shows first-minute and late-fight separately so you can see it for yourself.
• Occurrences the data cannot place reliably fire silently rather than guessing: visible on the timeline, no countdown. A spoken countdown on an ability that lands anywhere in a 30-second window is worse than saying nothing.
• Cues that follow a boss cast do nothing without BigWigs.