Changelog

v1.0.4

Crit Display Overrides

• Fixed: Per-category crit color overrides (outgoing damage, outgoing healing, incoming damage, incoming healing) are now applied correctly regardless of whether the "Route to a different scroll area" toggle is enabled. Color and critFont settings were previously gated on an internal enabled flag that the UI never sets, causing all overrides to be silently ignored.
• Fixed: Incoming crit damage fallback color corrected from yellow to red, matching the default shown in the UI configuration panel.
• Fixed: Per-category critFont (size/face) overrides are now applied independently of scroll area routing, using the same decoupled path as color.

Incoming Damage Attribution

• Fixed: Outgoing spell icons (e.g. Drain Soul) could appear in the incoming damage scroll area when the player had an active cast state at the time an incoming hit was received. findBestCast is no longer called for player self-damage events; outgoing cast correlation is now restricted to the non-player UNIT_HEALTH path where it belongs.
• Fixed: Life Tap now correctly shows its spell icon in the incoming damage scroll area. Life Tap's health cost is detected via UNIT_HEALTH with no accompanying CLEU event; icon attribution now uses a whitelist of Life Tap spell IDs (all 8 ranks) matched against the most recent player spellcast within a 1-second window to accommodate server round-trip latency.

Notifications

• Fixed: XP gains now appear in the Notifications scroll area. The PLAYER_XP_UPDATE event was not registered, and the existing event handler discarded it before processing because XP events carry no string argument. The handler now registers PLAYER_XP_UPDATE, tracks the previous XP value via UnitXP, and emits a +N XP notification on each positive delta.
• Fixed: Honor notifications now match any capitalization of the word "honor" in the gain message. The previous case-sensitive pattern silently dropped messages where the client capitalized "Honor" or "Honor Points."
• Fixed: Reputation notifications now have a reliable fallback via the UPDATE_FACTION event and the watched-faction API (GetWatchedReputationValue). Previously, detection was 100% dependent on CHAT_MSG_COMBAT_FACTION_CHANGE pattern matching with no backup path. The watched-faction baseline is seeded at startup to prevent a false delta on the first event. The two paths share a dedup window so the same rep gain cannot appear twice.
• Fixed: ComputeWatchedReputationDelta was defined but never called; it is now the handler for the UPDATE_FACTION fallback path.