A damage and healing meter that lives inside the game.
A combat meter for Final Fantasy XIV built on Dalamud, in the spirit of World of Warcraft's Details!. No external parser to start and nothing to attach: the numbers are read straight from the combat results your client already receives, and drawn in game.
| View | Shows |
|---|---|
| DPS / Damage Done | Damage per second and total, with each player's share of the group |
| HPS / Healing Done | Effective healing per second and total |
| Damage Taken | Who soaked what, and from which ability |
| Overhealing | Healing that landed on a full bar (estimated) |
| Deaths | Who died, how often, and to what |
- Segments. Every pull is its own segment, plus an Overall segment across all of them. Pick any past pull from the header.
- Breakdowns. Click a bar for that player's abilities (hits, crit and direct-hit rates, average and biggest hit), damage taken, a DPS/HPS graph, and a recap of the seconds before each death.
- Party cooldowns. Raid buffs, party mitigation, healing cooldowns and tank invulnerabilities for the whole party: a grid of icons that grey out and count down while recasting, or a timeline of the pull with every use and its recast.
/meter cdor the meter's menu. - Several windows. Open as many meters as you like, each on its own view; lock them, or let clicks pass through to the game.
- Streamer mode. Show other players by job ("Dragoon 2"), job abbreviation or initials, everywhere: bars, tooltips, breakdowns, death recaps, copied summaries and saved files.
- Your look. Five window presets, background colour and style, border, header, accent and text colours, a faint watermark; four bar styles, job, role or single-colour bars, fonts and sizes for names, numbers and header, opacity, spacing and rounding.
- Pets and allies. Summons and pets count toward their owner; Trust and Duty Support allies show up as party members.
- Chocobos. A chocobo companion is a combatant of its own, shown as "Bocchan (Kael Highwind)" in chocobo yellow, with the same chocobo icon the party list uses. In streamer mode its name becomes "Company Chocobo" and its rider is hidden like everyone else.
Aethermeter can write the fight as an ACT network log, the format FFLogs reads, and you upload it with the Archon App (FFLogs' uploader). No ACT needed.
- Live log. Switch it on with the record dot on the meter's header,
/meter log, or Settings → Logs. It can run everywhere or only while you're in a duty. Point the Archon App's live logging at the log folder. - Single pulls. The current zone's log is kept in memory, so any pull can be saved as its own small file from the meter's menu ("Save pull log for FFLogs"), or every pull automatically.
- Your folder. Pick any folder, use the default (
Documents\Aethermeter\FFXIVLogs), or ACT's folder, which is where the Archon App looks first. Files are named*_Aethermeter.log, so they never mix with ACT's. - Auto-clean. Delete Aethermeter's logs older than 1 week, 2 weeks, 1 month or 3 months, on load and every six hours (and saved segment files too, if you like). ACT's own logs are never touched.
What goes in: abilities and their raw effects (21/22) with their effect results (37), DoT/HoT ticks (24), HP at each death (39), director updates such as pull start, wipe and clear (33), combatants (03/04), statuses (26/30), casts (20/23), deaths (25), zone, player, party and stats (01/02/11/12), and combat state (260).
Not for rankings. The log follows ACT's network log format, but it is written by Aethermeter, not by ACT's FFXIV plugin, and it says so in its first line. FFLogs reads it and shows your pulls, then marks the report invalid for rankings, as it does for any log its logging-plugin check doesn't recognise. For ranked logs, use ACT or IINACT, which run ACT's own plugin. We're asking FFLogs whether a third-party writer can be supported.
One line is reconstructed rather than read: the effect result (37) that confirms a hit landed. The game handles it in a function Aethermeter doesn't hook, so it is written when the target's HP moves, with the HP it moved to.
| Command | Does |
|---|---|
/meter |
Show or hide the meter windows |
/meter config |
Open settings |
/meter reset |
Clear every segment |
/meter lock · /meter unlock |
Lock or unlock every window |
/meter new |
Add a meter window |
/meter test |
Play a made-up fight to preview the meter |
/meter log |
Start or stop the live log for FFLogs |
/meter news |
Show what's new |
Aethermeter hooks two game functions, both located through FFXIVClientStructs rather than private signatures:
ActionEffectHandler.Receive— every action's damage, heals and misses, on every target.StatusManager.ProcessHotDot— DoT and HoT ticks.
Both are read-only taps: the game's own code always runs. Names, icons and jobs come from the game's sheets, so they follow your client language and new jobs and actions work without an update.
The server leaves the status out of ordinary ticks, and may send one combined tick for every DoT on a target. Aethermeter settles the ticks of each server tick together, per target:
- Ticks that name a status (ground effects such as Salted Earth, Doton or Asylum) go to their source — or the source's owner, when the source is the ground effect's own actor. With no source, the status on the target, or on the caster for caster-side effects, names one.
- When every player with a DoT on the target sent their own tick, each tick is credited to them exactly.
- Otherwise the total is shared among the DoTs on the target by each one's per-tick value, learned from the exact cases during the fight.
Totals always match what the server sent; only the split of a combined tick is an estimate, as it is for ACT and FFLogs.
Shields count as healing by their caster, for the damage they actually absorbed. The client keeps one shield gauge per character (a whole percent of max HP) plus the shield statuses, so Aethermeter reads both each frame: the gauge rising as a shield appears is that shield's size; the gauge dropping right after damage is damage absorbed, taken from the oldest shield first; a drop with no damage is a shield wearing off. Shield statuses are recognised from their description, and any other status that raises the gauge is learned on the spot.
- Overhealing is estimated from the target's HP when a heal lands, so it can differ a little from FFLogs.
- Each shield is accurate to about 1% of the target's max HP, the gauge's resolution.
Aethermeter never posts to chat and never sends anything anywhere. Saved segments go to the plugin's own config folder.
dotnet build -c Release
Then copy bin/Release/Aethermeter.dll, Aethermeter.json, Aethermeter.deps.json and the Assets folder into a dev plugin folder and add it under /xlsettings → Experimental.
Questions, ideas, or a parse to show off? Join the Discord: it's also where new versions are announced first. If you enjoy Aethermeter, you can support its development on Patreon.
Fonts: Barlow, Barlow Condensed and Bebas Neue, under the SIL Open Font License (see Assets/Fonts/licenses).