The data stays on the PC
Pulls, history, configuration and backups are stored locally.
FFXIV raid tracking
Track the pulls.Understand the wipes.
StaticOps brings ACT and FF Logs together to show rDPS, healing, uptime, deaths, mechanics and progression in one place.
Free · Windows 10 / 11 x64
No account requiredHistory stored locallyPublic FF Logs reports
After the pull
Two deaths. One wipe. In what order?
The recap brings deaths and the end of the fight together to help the group understand what happened.
Fictional recap example. These numbers illustrate how to read the analysis; this is not an application screenshot.
Pull 12Duration · 03:20
- 02:50
First death
A player dies. The killing blow and healing received can be inspected.
- 03:01
Second death
The timeline shows how the events unfolded.
- 03:15
Wipe
25 seconds separate the first death from the wipe.
What still needs checking
The first death alone does not establish the wipe cause. Events, mechanics and confidence complete the picture.
The basics
Where the data comes from and where it stays.
FF Logs verifies the numbers
The public report provides exact metrics and events whenever it is available.
The wipe cause stays readable
The first mistake, the deaths that follow and the wipe are shown separately.
During the raid night01Exact FF Logs events 02ACT + FF Logs tables 0320 pulls / 3 nights / all history 04No daily data entry
What StaticOps tracks after every pull.
Why the player died
Killing blow, statuses, healing, shields, likely mechanic, cascade and wipe relationship.
DPS, healing and uptime
rDPS, aDPS, nDPS, HPS, real activity, damage taken and actions per player.
Where progression stops
Phase transitions, best pull, mortality, trends and roster comparisons.
What runs automatically
Pre-raid check, Archon detection, Discord and the HTML raid-night export.
Tracking starts with the first pull.
StaticOps reads ACT, stores the raid night and adds FF Logs as soon as the public report is available.