KP_DashMeter

1.3.7 (2026-04-07)
- Fixed an issue where combat records sometimes did not display; added data structure checks and validation tensure `_G.KP_DashMeterCharDB` and `self.sets` are valid tables
- Fixed empty failed record issue; ensured only combat records with actual data are saved to saving empty records
- Fixed non-combat damage not refreshing the panel issue; simplified non-combat event handling, ignoring damage and healing events when not in combat
- Fixed bost data issue; expanded combat event types to ensure events are correctly processed in tentative mode
- Fixed death record issue; fixed percentage calculation to avoid abnormal values like 999%nsuring "XXX died" death records are displayed
- Fixed dungeon reset prompt issue; added missing variable definitions to ensure the function executes properly
- Fixed party join/leave prompt functional ensured the reset data prompt is displayed based on settings when the player joins or leaves a party
- Fixed display logic for history and current records, as well as maxsets (maximr of records)