Legal

Disclaimer

Placeholder. This page describes the maintainer's current intent. It has not been reviewed by a lawyer.

Not affiliated with Square Enix

Vigil is a fan-made tool. It is not affiliated with, endorsed by, or sponsored by Square Enix Co., Ltd. or any of its subsidiaries.

Not affiliated with FFLogs

Vigil reads data from the FFLogs API. It is not affiliated with, endorsed by, or sponsored by FFLogs (Kihra, LLC). Vigil's existence does not constitute endorsement of any specific FFLogs feature, ranking, or interpretation.

Diagnostics are heuristic

Vigil's fault attribution, mit audit, DPS-check verdict, mechanic classification, and optimization scores are derived from heuristics applied to FFLogs event data. They are best-effort and intended as a discussion starter for your static, not as a definitive judgment.

In particular:

Fault attribution classifies deaths as root / cascade / mit-failure / heal-failure based on the killing ability's classification and the presence of preceding deaths or successful mit casts. It cannot read the mind of the dying player, nor know about mistakes that didn't result in deaths.
Mit audit flags planned cooldowns that didn't fire in a raidwide window. It does not know about ad-hoc cooldown reassignments made mid-pull.
DPS-check verdict compares your phase-by-phase raid DPS against the distribution from logged clears. The "clearing groups" distribution can be biased by parse-padding and is not a prescription.
Mechanic classification (raidwide / tankbuster / aoe_party / enrage / cosmetic) is inferred from damage signatures and is occasionally wrong on edge cases (e.g. delayed-fuse mechanics, cosmetic-but-actually-lethal casts).

Use the data as a starting point. Don't bench someone over a single fault score.

No warranty

See Terms.

Reporting issues

If Vigil produces a clearly incorrect result for your pulls, please open an issue with the report code (if public) and the specific output that's wrong. That's how the heuristics get tightened.