UltraCombatStats

UltraCombatStats – Patch Notes

This update focuses on death handling, lowest health accuracy, and clarity between Normal and Hardcore modes.

Lowest Health reset on resurrection has been completely reworked. After dying, the player is now prompted on resurrection to confirm whether Lowest Health should be reset. If confirmed, UltraCombatStats waits until health and max health have fully stabilised before performing the reset. This prevents Blizzard’s post-rez health wobble (where health briefly shows 100% then drops to ~50%) from being recorded as a new lowest value.

Lowest Health now resets reliably to 100% only after health has remained effectively full for a short, stable period. Additional protection ignores health changes for a short window after the reset to prevent delayed dips being recorded.

Lowest Health tracking is now live on Normal mode. As health drops, the HUD updates immediately instead of waiting for combat end or out-of-combat timers. Hardcore behaviour remains unchanged and conservative.

Death announcements have been cleaned up on Normal mode. “Final  Level X” and “Lowest Health” have been removed from Normal death messages, as they are not meaningful outside Hardcore. Hardcore death messages continue to show Final Level, Lowest Health, and survival context as before.

Normal mode death messages now display a clean “Total Deaths” count without the “(Non-Hardcore only)” wording. Hardcore mode instead continues to show Survival Streak duration.

Internal event handling for PLAYER_DEAD, PLAYER_ALIVE, PLAYER_UNGHOST, and UNIT_HEALTH has been stabilised. Several edge cases that caused inconsistent resets or Lua structure errors have been resolved.

Overall stability improvements were made to prevent false Lowest Health values, especially around resurrection, max health recalculation, and rapid event firing.