CoU feedback: revive harmless personal-best crit trackers via read-only C_DamageMeter fields

TL;DR: While you are reworking addon restrictions for Curse of Ula’tek, please consider adding a few read-only, out-of-combat, self-only record fields to the per-spell C_DamageMeter data (for example maxCrit, maxHit, critCount, and the same for healing). It is a tiny, non-actionable addition that would bring back an entire category of harmless “personal best” addons the lockdown killed as collateral.

First, so there is no confusion: this is not a “give the combat log back” post. I fully support the Midnight combat philosophy. Addons should not play the game for you, and live granular combat data is what enabled rotation helpers and pressure overlays. I am not asking for any of that.

The all-or-nothing lockdown, though, took out a whole class of addons that never had anything to do with combat advantage: personal-best crit trackers, biggest-hit displays, milestone counters (CritMatic and its kin). These never solved combat for anyone. They just let a player keep a scoreboard of their own hits and celebrate a new record. Since C_DamageMeter exposes only aggregate totals and no crit or max-hit data, that entire category is currently dead.

The ask (small): extend the per-spell C_DamageMeter struct with a few self-only record fields, for example:

  • maxCrit, maxHit, critCount per spell
  • the same for the healing meter type (heal crits are the other half of these addons)

Why it is safe, three hard rules:

  1. Out-of-combat only. The fields return nothing usable while you are in combat, so they can never feed a live decision, rotation helper, or pressure overlay. By the time you can read them, the fight is over.
  2. Aggregate records only, not a per-event stream. “My biggest Pyroblast crit this session was X” is a single number, not a replayable timeline. It cannot be stitched back into a reconstructed combat log.
  3. Own character only. No raid-wide or other-unit reads, so it cannot power parse overlays or gatekeeping tools.

Precedent you have already set: C_DamageMeter already surfaces a per-hit maximum today, the source-level maxAmount (your single biggest hit of the session). So a per-hit extremum is already considered safe here. This request is the same nature of data one level finer: the existing max, moved to the per-spell struct and split crit vs non-crit. Per-source attribution and per-spell spellID keying already exist, so this is a few fields behind an out-of-combat gate, not a new subsystem.

Nothing here helps anyone press a button better. It is pure goodwill: restoring a beloved, harmless category of progression and vanity addons at zero cost to the stated combat-philosophy goals.

Thanks for reading, and thanks for the ongoing work with addon authors through the CoU PTR.