What StaticOps tracks during a raid night.
Each screen answers a concrete question: what happened, who died, which mechanic failed and where the group is stuck.
Every attempt stays in the history.
Local tracking splits supported boss fights and groups them by raid night, encounter and session type.
What is tracked
- Pull start, end, duration and result
- Deaths, timeline and observed progression
- Roster, PF prog, training or other tags
- Custom folders to organize several session groups freely
Sources
- Local ACT log
- SQLite
Limits and fallback
ACT must produce a recent log. Dungeons are excluded, and an unrecognized encounter stays outside automatic tracking.
The recap separates the killing blow from the wipe cause.
Observed events are placed in order to distinguish one death, a cascade and the mistake that actually triggered the wipe.
What is tracked
- Killing blow, HP, overkill, healing and shields
- Debuffs, missed soaks, group failures and mechanics
- Responsibility, evidence and confidence level
Sources
- FF Logs Events
- Local ACT log
- cactbot / oopsy
Limits and fallback
Without a matched public fight, the local recap remains a labelled estimate. A debuff present at death never identifies fault on its own.
rDPS, healing, HP, MP and uptime keep their source.
Verified FF Logs numbers and local measurements are not mixed. Every column and chart clearly identifies its origin.
What is tracked
- rDPS, aDPS, nDPS, DPS and actions
- HPS, effective healing, shields and overheal
- Zoomable HP, MP and DPS charts, with resource selectors limited to players
- Real uptime, damage taken, food, potions and job analysis
Sources
- FF Logs Tables
- FF Logs Graph
- xivanalysis
Limits and fallback
FF Logs requires a matched public report. Job analysis depends on the encounters, levels and patches supported by xivanalysis.
Phases show where progression stops.
The diagnosis compares several pulls instead of drawing a conclusion from one attempt.
What is tracked
- Latest 20 pulls, 3 nights or all history
- Reached phases, transitions and stopping points
- Filters by encounter, night and session type
Sources
- FF Logs Fights
- Local history
Limits and fallback
Pulls without an FF Logs phase remain in coverage totals but are excluded from rates that require a known phase.
The timeline compares the same moments of the encounter.
The chronological view aligns your run with an automatic or manually selected public reference, phase by phase.
What is tracked
- Separate lanes for the main rotation, potions, mitigation and utility actions
- Prepull and P1, P2, P3 and later phase markers
- Synchronized zoom, horizontal movement and time-range selection
- Reference selected from a public FF Logs report and fight
Sources
- FF Logs Events
- FF Logs Fights
Limits and fallback
Precision depends on the events and phases exposed by both reports. Runs with very different durations should be compared phase by phase.
Cloud remains optional and entirely manual.
StaticOps works without an account. Discord sign-in only enables up to three private history snapshots stored in Supabase.
What is tracked
- Creation and restore explicitly started by the user
- Up to three private snapshots per account
- Restore verification and a local safety backup
- Account deletion without deleting the local database
Sources
- Local SQLite
- Discord OAuth
- Private Supabase storage
Limits and fallback
A snapshot contains the raid history required for restore, including player names. It never includes secrets, settings, ACT logs, caches or images.
The recap can be shared without exposing configuration.
Discord tracking and the HTML report include useful raid-night information without carrying local secrets.
What is tracked
- Optional Discord webhook with confirmation before every recap
- Selected pulls remain visible before publishing
- Standalone HTML raid-night report
- Sanitized diagnostic export
Sources
- Local database
- Stored FF Logs data
Limits and fallback
Discord remains optional. Webhooks, FF Logs credentials, ACT paths and the SQLite database are never included in public exports.