Ascent

Still a beta. What changed about that: the addon has now been played across sessions on Burning Crusade Classic, and the three separate reports about the live combat summary turned out to be one defect with one cause -- a sweep that was switched off. What has not changed, and is why this is still a beta: ui/ has no tests, and the promise that the sources add up to exactly the experience of a level is verified on the levels that have actually been played, not on all of them.

Added

• The combat summary has a page of its own. It answered to two settings, one of which had no checkbox anywhere and existed only as a chat command, while all six options pages were about the bar. It now has shown, locked, scale, width, opacity, how long it stays, how many rows, which of its seven zones to draw, and three axes of its own look over the bar's -- plus a demo button, a reset, and /ascent options plate for the one case a panel cannot help with: a plate dragged off screen or made invisible, because you cannot click what you cannot see. It still follows the bar's skin and palette on purpose. The summary's source bar uses the experience bar's segment colours so that what you learn on one you read on the other without translating, and two palettes would not be two tastes but two vocabularies, the second to be learned mid-fight.
• What a creature pays now depends on how many of you split it. Every average this addon shows is measured -- that is the whole claim -- and the bucket holding those measurements kept kills and experience and nothing else, so the same creature killed alone and killed in a five-man landed in one number. Level alone, then run a dungeon, and every estimate was inflated about five-fold; go back to solo and the dungeon's kills dragged it down. The live summary, the kill-quest forecast and the panel's breakdown all read from it, so all three were wrong at once and in the same direction. The group size is sampled at the instant of the gain and travels with it, so stepping into a dungeon does not reclassify the level you earned outside one.
• The time a level could not place. Experience balances to the unit because whatever cannot be attributed lands in an explicit bucket. The seconds measured against places had no such bucket and could quietly fall short of the seconds actually played: one level measured 8931.6s of 9304.2s, and the missing 4% -- loading screens, where none of this runs -- could only be found by subtracting the two by hand. It is left unknown rather than zero when the level never received the server's own figure, because zero is a claim that level is not entitled to make.

Changed

• The breakdown draws one row per population, not one per creature. A creature killed solo and the same creature killed in a group are two measurements, and merging them is the thing this version exists to stop doing.
• The combat summary has its own lock. It borrowed the bar's, and the bar's lock is disabled while the client's bar slot suspends its position -- so a setting about the client's own experience bar decided whether the summary could be dragged at all. If you locked the bar in order to lock both, the summary will be loose once.
• Your recorded history is converted, not discarded. AscentCharDB goes to schema 4 and rewrites every creature bucket, filing what it already held under an unknown group size: that history is still worth something as long as nothing passes it off as measured. Going back to an earlier version is not clean, though -- an older build reads the new line and takes the group size for a creature id, silently -- so if you roll back, clear the breakdown rather than trust it.

Fixed

• The live summary stayed empty through entire fights. It hides while a pull has nothing to say, and "nothing" was defined by kills and damage alone, so a creature beating on an absorb shield left all four figures at zero and the summary stayed down for the whole fight with the creature enrolled and the pull open. A pull with a creature in it has something to show.
• A creature crossing the ground toward you was not counted until it arrived. The nameplate sweep that exists to see one coming ran only while a fight was already open, and only the client's combat flag opened one -- so the single mechanism that could see a creature early was gated behind the very thing it existed to precede. It runs always now: four times a second in a fight, once a second outside one.
• A caster is counted from the moment it starts casting at you, which is the earliest thing the combat log will ever say about one, instead of when the spell lands.
• Every creature in the fight is counted, not only the ones you hit.
• The played-time answers the addon asks for no longer reach your chat. One request comes back two to four times in the same instant, and the silence was being released on the first answer -- inside the very dispatch that then printed the rest. It is held on a timer now, because the number of repetitions is not knowable: two to four were seen on Burning Crusade Classic and the figure has never been measured on Classic Era, so calibrating to a count would fail silently on a client that sends one more.