ultratears
Unofficial native Windows port of Tears of the Kingdom 1.4.3 using static recompilation. Builds locally from the player's own extracted game dump; no game files included.
翻譯準備中
DPS/HPS Meter for FFXIV
翻譯準備中
正在載入完整 README。
檢視完整 README ↗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 |
/meter cd or the meter's menu.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.
/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.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.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.
以上為 README 的開頭部分。其餘內容請閱讀原文。 檢視完整 README ↗