v1.1.21

Better rDPS credit for support classes

• Self-buff debuffs now count. Some classes apply their party-wide damage-taken debuff as a self-buff on themselves rather than on the boss (e.g. a Gladiator's Murderous Burst). Previously the meter saw no debuff on the target and gave
  those players zero rDPS credit for the raid damage their debuff enabled. They now get proper credit.
• Fair split for duplicate buffs. When two players keep the same non-stacking buff or debuff up at the same time, its rDPS credit is now split between them by uptime instead of going entirely to one (no more winner-take-all when you
  have two of the same class).
• No credit leak from passive bars. A player's permanent self-buff bar is no longer mistaken for an active application, so it can't inflate the local player's rDPS or leak into uploaded fight data.

Fixes

• Fixed your own Combat Power (CP) occasionally not showing.
• Fixed a phantom 6th party member — a summoned pet (e.g. a Spiritmaster's spirit) getting mislabeled as an extra player.

v1.1.20

rDPS — the support-aware damage metric

What it is — rDPS (raid DPS) measures a player's real contribution to the party's damage, not just the number on their own row. Support classes (Templar, Gladiator, Cleric, Chanter) cast
buffs and debuffs that amplify everyone's damage; rDPS credits each supporter for the extra damage their buffs enable, and adjusts each dealer's number by the share that came from allies' buffs

Why it matters — a support who looks like they "do no damage" finally gets a fair number, and pure DPS can see how much of their output was self-earned versus buff-driven.
rDPS tab — a per-player breakdown of every buff and debuff and exactly how much damage each one added.
Buffs tab — now shows each buff's added damage in green.
Metric switch — set the meter's main column to rDPS, DPS, or total damage (Settings → DPS → Metric).

HPS — healing per second

What it is — the compact meter can rank the party by healing throughput instead of damage. Effective healing — counts only healing that actually restored HP (overhealing excluded), so healers are measured fairly and comparably at a glance.

v1.1.19

• Season 1 / Chapter 1 support — updated packet protocol for the latest client version: new OWN_CHAR marker, damage packet format changes, and shifted opcodes for mob/player spawn
• Brawler class — basic detection for the new Brawler class (격투성) added in Season 1; class icon and skill names coming soon
• 277 new bosses — boss database updated with all Chapter 1 dungeon and raid bosses across all 10 locales
• Fixed owner detection — the meter owner now appears reliably in the live display even before the OWN_CHAR packet arrives; roster reconciliation correctly identifies the owner's combat entity
• Fixed owner nickname override — OWN_CHAR now force-overwrites stale nicknames, preventing a wrong name from sticking on the owner row
• Player limit raised — party display limit expanded to 5–30 players (was 1–20)

v1.1.18

Upload system

• Fight uploads now retry automatically (3 attempts via backend, then fallback through WebView2 browser stack to bypass firewalls, then background retries at 1/2/5 min)
• Failed uploads from previous session are retried on next app launch (up to 3 fights within 24h)
• Upload status badges in fight history: ✓ for uploaded, ! for failed

Combat Power (CP)

• CP is now detected from party roster (0297), LiveStatus broadcasts, and gear-score packets (0x3692)
• CP displayed per player alongside Gear Score

Party & player detection

• Rewritten LiveStatus parser with server-anchored name scanning — works reliably for both KR and TW
• New compact roster parser for the variable-length 0297 format (extracts names, class, CP)
• Self-proxy merge is now deferred until class confirmation from the roster — prevents wrong-class party members from being merged as the owner
• Wrong self-proxy merges are auto-undone when the real player spawn arrives

Bug fixes

• Skill-based class detection now takes priority over roster jobCode (roster can be stale)
• Removed owner_hint redirect for DOT damage — fixes phantom attribution (matches Flow/fundps/Kuroukihime behavior)
• Player deaths now counted from both 0x3641 and 0x8D21 packets (TW only sends 0x8D21 for players)
• known_player_ids preserved across fights — fixes DOT mis-attribution after combat reset
• Owner Gear Score correctly read as u16 (was u32)
• CP/GS entity caches cleared on zone change; name caches preserved for cross-fight continuity

v1.1.17

Bug fixes:

• Fix summon DOT phantom rows — DOT damage from confirmed summons (familiars/spirits) now resolves through summon_storage instead of trusting the packet's owner_hint field. Previously, the hint could point to a random nearby player entity, creating a phantom row with ~26k damage that survived all merge/filter passes. The summon owner is now resolved authoritatively from SPAWN40_FF8 data.
• Fix live party surfacing for DOT-only entities — Added a gate requiring ≥2 distinct non-DOT skills before an entity can be surfaced into live_party_ids. Previously, a phantom entity with only DOT damage could enter live_party and become immune to orphan merge and party name filtering.
• Roster name binding: prevent non-party name overwrite — When a spawn packet binds a nearby non-party player's name onto a party member's entity (e.g. healer gets adjacent player's name), the roster name now
  wins. Added ROSTER_KEEP, ROSTER_OVERRIDE, and ROSTER_FIX guards.
• Legion name cleanup — Marking a name as legion/guild now also purges it from self_nick_scores and inferred_self_name, preventing phantom self-bindings.
• SELF_BIND post-check — Verify the name binding took effect after attempting it (can be rejected by legion guard), preventing false "bound" logs.
• 0297 roster: found_names ordering — Names are added to found_names only after passing the legion denylist, so guild names no longer block real player names from binding.

Improvements:

• Boss wipe-retry naming — When a party wipes and the boss respawns with a new entity ID, the new entity inherits the mob_code from the wiped boss (within 3 min window), keeping the correct boss name instead of falling back to "Boss #".
• Boss HP revive detection — If a "dead" boss receives REMAIN_HP with hp > 0 (revive/fake-death mechanics), the death flag is cleared so the fight continues correctly.
• Boss kill: HP overwhelm threshold — A boss is considered killed if total party damage exceeds 95% of max HP, even if the local player died during the fight. Reduces false no-kill results.
• Boss saved targets: revive unsave — Finalized boss targets that come back alive are removed from the saved list, allowing the fight to resume.
• Max HP validation raised — REMAIN_HP accepts up to 500M (was 50M), supporting high-HP bosses.
• Own-char name cache — The character name is cached to disk so mid-session restarts can use it as fallback before the own-char packet arrives.

v1.1.16

DPS Meter 1.1.16 — Bug Fixes

Boss names now appear in fight history even when the meter is opened mid-fight.
Previously, if you started the meter after a fight had already begun, the boss was shown as Boss # for the entire fight and in history — its spawn packet (the only carrier of the boss ID) had already been sent before capture started. The boss name is now recovered from the boss-death packet, so the finalized history record shows the correct name.

A second party member of the same class is no longer dropped from the meter (in mid-fight).
When the party had two players of the same class (e.g. two mages), the owner-detection merge could fold the second player's damage into the meter owner, making that player disappear. The merge is now skipped when the owner's own entity already deals its own damage, so both same-class players show correctly.

Your own character is no longer occasionally shown with the wrong class.
On a mid-fight start with no own-character packet, the owner could be bound to a same-timing party member of a different class (e.g. shown as a gladiator instead of a mage). The owner's class is now cross-checked against the party roster and re-bound to the correct character.

v1.1.15

• Fix for some VPNs & game accelerators. When a local proxy/VPN such as NordVPN or a ping booster was active, the meter could attach to the wrong (loopback) connection and show nothing. It now picks the connection that actually carries combat data, so DPS, boss HP and party info populate normally.
  • Boss HP bar stability. Fixed the boss HP bar jumping up and down mid-fight (it was occasionally reading stray values from compressed network frames).
  • Chalice of Muspel raid. Its bosses are now shown by name and tracked correctly: Iscariel, Kaldrix, Blazing Guardian Sword (Normal & Hard).

v1.1.14

v1.1.14 — What's changed

• Party members no longer disappear from the meter before your character is identified — your whole party's damage shows up right away.
• Your own row also stays on the meter (as #id, without the highlight) when the game hasn't sent your character info yet — previously it would vanish.
• More reliable boss-name detection — fewer fights shown as "Boss #id".
• The party roster is now picked up even when the meter is started after you've already entered a dungeon.
• Added IDs of all bosses in Chalice of Muspel

v1.1.13

aion2t.com DPS Meter v1.1.13 — big update

✨ New

• DPS TOP — check out your progress on any boss and compare yourself to other players on https://aion2.app/dps-top
• Gear Score & Combat Power shown per party member, with a GS/CP toggle.
• Region support (TW/KR) — first-launch region selector; cross-server party members shown with a [TAG] prefix.
• Characters links you can click on nickname of players and go directly to their leaderboard page with full details of their gear & skills.

🐛 Fixes

• Boss names now detected from the spawn opcode (0x3641), not just 0x3640.
• Boss death/HP tracking overhauled: phase transitions no longer kill a live boss; no more ghost boss after a kill, frozen HP bar, fake deaths, or timer resets.
• Authoritative kill signals (combat-death packet + "next boss engaged at <10% HP") instead of unreliable HP-zero flickers.
• Summon/pet damage attributed to the owner; party-member class detection fixed (boss/shared skills no longer mislabel players).
• Idle/abandoned bosses no longer re-spam the meter; stale-boss filtering; enriched upload payload (class, level, region, serverId).
• Russian class names + fuller UI localization (numeric fight dates, etc.).

v1.1.11

Bug fixes:

• Full party data now saved in fight history and uploaded to leaderboard
• Boss add damage included in details when 'Boss adds' is enabled
• Upload sends only the final fight snapshot (fixes wrong duration on site)
• Update notification now works correctly