v0.11.17

This release focuses heavily on getting the Throne of Thunder boss-spell data right. The old database was inherited from MoP-original references and contained many wrong IDs, which meant cast triggers silently failed to fire. A live combat-log dump plus WCL cross-referencing fixed every ToT boss in turn.

Throne of Thunder encounter IDs corrected (v0.11.8 – v0.11.9)

Five ToT bosses had wrong internal encounter IDs. The client fires real IDs, our table had MoP-original values — so encounters either started under the wrong name or didn't trigger assignments at all. Auto-migration moves your stored assignments to the corrected IDs when you log in:

• Megaera 1591 → 1578 (was colliding with Council of Elders)
• Council of Elders 1578 → 1570
• Tortos 1573 → 1565
• Iron Qon 1572 → 1559
• Lei Shen 1570 → 1579

Throne of Thunder boss spells refreshed (v0.11.9, v0.11.16, v0.11.17)

Every ToT boss now has cast IDs verified against either live /cdp dumpbosses output or the WCL Casts tab — both are ground-truth SPELL_CAST_START/SUCCESS events. The previous values for several bosses (Primordius, Dark Animus, Iron Qon, Twin Empyreans, Lei Shen, Ra-den) were almost entirely wrong; those are now rebuilt from scratch.

SPELL_ID_MIGRATIONS automatically updates assignments that referenced the old wrong IDs (e.g. Megaera Cinders 139836 → 139822, Council Sand Bolt 136338 → 136189). Migration prints in chat at login so you can verify.

Rampage finally fires (v0.11.10)

Megaera's Rampage (139458) is implemented as a self-aura, not a spell cast. The CLEU filter only accepted SPELL_CAST_START and SPELL_CAST_SUCCESS, which silently dropped Rampage on the floor — no count, no trigger, ever. The filter now also accepts SPELL_AURA_APPLIED when source = destination (i.e., boss applies an aura to itself). Other bosses with similar self-aura mechanics will also work correctly going forward.

WoW-native pull timer + DBM/BigWigs broadcast (v0.11.12)

/cdp pull <seconds> now uses the native C_PartyInfo.DoCountdown API for the big screen-centered countdown when available (raid leader only). Additionally broadcasts to DBM (D4 prefix) and BigWigs (BigWigs prefix) so raid members running bossmods see a synced timer bar. All existing dependencies — pre-pull alert offsets, auto-sync on pull, encounter-end cleanup — continue to work unchanged.

Sync now button is raid-leader-only (v0.11.11)

The button used to be clickable for everyone, which led to confusion: raid members thought clicking it would pull the leader's assignments to themselves (it actually pushes their own — and was a frequent source of accidental raid spam). Non-leaders now see the button greyed out with a tooltip explaining how syncs flow. Leadership changes mid-session are reflected immediately.

Auto-jump and auto-switch for raid members (v0.11.12, v0.11.13)

Raid members opening the planner now land directly on the boss the leader most recently synced (within the last 30 minutes), with the synced profile auto-selected. No more clicking through the encounter picker to find your assignments. Raid leaders and personal-mode users keep their own selection intact.

Third sort mode: "mine only" (v0.11.12)

The sort toggle at the top of the assignment list now cycles through three modes:

• trigger — all assignments by time/cast/percent (default)
• player — grouped by raid member
• mine — just your own assignments

Especially useful for raid members who want a clean view of just their CDs.

Configurable alert hold time (v0.11.11)

The "USE NOW" alert previously had a fixed 4-second linger. Settings popup now has an extra-hold-time setting that cycles 0s / +1s / +2s for raid leaders who want a longer reaction window. Casting the assigned cooldown still dismisses the alert immediately as before.

Diagnostic tools

Three new commands to debug "my trigger doesn't fire" cases:

• /cdp learn (v0.11.3, enhanced v0.11.14, v0.11.15) — shows every boss cast observed this encounter, matched against the DB; flags your assignment IDs as OK (fired) or NOT FIRED (waiting). If a trigger ID never fires but another ID with the same spell name did fire, the same-name suggestion tells you which to use.

• /cdp dumpbosses (v0.11.3) — dumps all observed boss spells across all your pulls, sorted by frequency. Persistent in SavedVariables across sessions. The maintainer-friendly format makes it easy to share.

• /cdp probeid <spellID> (v0.11.14, v0.11.15) — inspects any spell ID: its name + icon, whether the addon ever observed it as a boss cast, which of your assignments reference it. If a spell with the same name was observed under a different ID, suggests that ID as the more likely cast variant.

Persistent boss-spell observation (v0.11.3+)

Every cast the addon observes during an encounter is now stored permanently in SavedVariables under observedBossSpells. Accumulates across all your pulls, giving us a continuously growing ground-truth database that fixes wrong IDs in subsequent releases.

Encounter-end usage report player-specific (v0.11.4)

The post-fight summary now shows two numbers:

Encounter end: 4/4 yours (100%)  17/22 total (77%). Victory!

"Yours" is reliable (your client always sees your own casts). "Total" is best-effort (range-limited).

UI polish

• Done button stays on-screen (v0.11.11) — multi-select popups auto-flip upward if they would extend off the bottom of the viewport.
• Stale "Pick multiple players" header fixed (v0.11.11) — yellow title text from a previous multi-select no longer leaks into the next regular popup.
• Scroll bar hidden when not needed (v0.11.11) — UIPanelScrollFrameTemplate shows a scrollbar even on short popups; now hidden dynamically when content fits.
• Megaera head aliases (v0.11.7) — encounter-detection match now recognises Flaming/Frozen/Venomous/Acid/Arcane/Shadow Head as Megaera, so auto-start fires correctly.
• /cdp diag extended (v0.11.7) — also shows active profile name, per-profile assignment counts, synced-profile age, and whether a fresh sync would override the planner pick.

Healthstone correction (v0.11.12)

Now 120s (was 60s). Guardian Spirit briefly went to 120s by mistake in v0.11.11 and is back at 180s.