FFLogs progression tracker
See where your static is actually wiping.
Vigil ingests FFLogs data for one high-end FFXIV static and turns it into per-pull signal. Where you're losing pulls and whose originating fault caused each wipe. Whether you're DPS-gated or mechanics-gated. How your prog compares to the field, on the parts that are actually comparable.
What Vigil does
Wipe location histogram
Every wipe bucketed by phase + killing boss ability. See exactly which mechanic is the wall.
Fault attribution
Per-death root vs. cascade classification with mit-aware refinement. Surfaces the originating mistake, not the chain reaction.
DPS-gated vs. mechanics-gated
Per-phase DPS distribution from clearing groups, compared to yours. Tells you whether the wall is execution or output.
Mit audit
Planned mit slots from your strat compared to what actually fired. The dropped cooldown is the diagnosis.
Burst alignment
2-minute window detection + per-player in-window vs. drift percentage. Helps tighten polish in the optimization phase.
Failure cartography
Cross-group death-by-boss-ability map. Universal wall or you-problem? The answer is on the chart.
Recent updates
All news →- Site launch
This site is live. Marketing/docs for Vigil under studioholst.com/vigil. The /news feed mirrors CHANGELOG.md going forward.
- v1.17.1 — Auto-refresh fight_model on report ingest
v1.17.0 unified cloned encounter IDs but the fight_model only rebuilt when an operator explicitly POSTed `/api/encounters/{id}/fight-model/persist` (then `classify` + `annotate-ca…
- v1.17.0 — Canonical encounter unification (cloned-encounter merge)
FFLogs occasionally cuts the same logical encounter into a new `encounter_id` after a re-cut. DSR today is split across **1065 (legacy)** and **1076 (current)**. Before this ship,…
- v1.16.5 — Per-phase tabs use wipe counts; phase inference for "Unknown"; guessed-pill tooltip distinguishes mechanic vs phase
User feedback on v1.16.4: "The table all (X) should be for wipes not death" + "how are there unknowns? Use the timeline of the report and cactbot's timeline, taking into account d…
Built for one static, opened for everyone.
Vigil is open source. The docs cover setup, daily ops during prog, and the full data flow. If you run a static and want this for yourselves, clone the repo and read the README.