Set up StaticOps

This guide starts from a Windows 10 or 11 PC with FFXIV installed. By the end, ACT records combat, StaticOps retains every pull, and FF Logs enriches the analysis automatically whenever its public upload is running.

Outcome and requirements

Without FF Logs, local history, pulls, ACT deaths and local measurements remain available. Metrics marked FF Logs, exact phases and the most reliable death diagnostics require a public report.

1. Install ACT and the FFXIV plugin

1. Download Advanced Combat Tracker, install it and launch it.
2. In the wizard, choose Parsing Plugin > FFXIV Parsing Plugin, then Download/Enable Plugin.
3. Open Plugins > Plugin Listing and confirm that FFXIV_ACT_Plugin.dll is enabled.
4. Keep the Deucalion capture method offered by the plugin.

Deucalion is built in: Npcap, a firewall rule and running ACT as administrator are normally unnecessary. Detailed guide: ACT, OverlayPlugin and Archon.

2. Add an in-game DPS meter (optional)

The overlay only displays numbers during combat. StaticOps reads the ACT log and works even when no meter is visible.

1. In ACT, open Plugins > Plugin Listing > Get Plugins….
2. Install OverlayPlugin, restart ACT, then create an overlay from Plugins > OverlayPlugin.dll > New.
3. In OverlayPlugin > Event Settings, enable End ACT encounter after wipe and End ACT encounter out of combat for clean pull boundaries.

3. Verify the ACT log

1. In ACT, open FFXIV Settings > Log File Location.

2. The usual folder is:

   %APPDATA%\Advanced Combat Tracker\FFXIVLogs
   

3. Attack a training dummy for a few seconds.

4. Confirm that ACT creates an encounter and updates the latest .log file.

Keep this folder: ACT, Archon and StaticOps must all use exactly the same path.

4. Install StaticOps

1. Download the installer from the latest GitHub release.
2. Run the installer, then open StaticOps. Administrator rights are not required; WebView2 is installed automatically when missing.
3. Complete the assistant: language, privacy, ACT folder, FF Logs, optional Discord, then the final check.
4. In Settings, confirm that the ACT folder matches the previous step.
5. Open Command and select Run check again.

The desktop application contains the dashboard; no separate browser is needed. Trials, Raids, Savage, Ultimate and Criterion are tracked. Dungeons and open world zones are intentionally excluded from automatic boss tracking.

5. Enable FF Logs with Archon (recommended)

1. Sign in to FF Logs.
2. Install Archon and select Final Fantasy XIV > Live Logging.
3. Choose the same FFXIVLogs folder as ACT.
4. Select your region, visibility Public, then start Go Live.

StaticOps discovers the recent report from Archon’s local logs. Private reports are unsupported. Archon help: App Help and FAQ.

Personal API credentials (optional)

Official builds preconfigure public FF Logs API access. On first launch, these credentials are imported into the Windows user’s DPAPI vault; no entry is needed.

To replace them, create a client in FF Logs API Clients, leave redirect URLs empty, then enter its Client ID and Client Secret in StaticOps > Settings. This does not replace your Archon sign-in or the Go Live button.

If the report is not detected

First verify Archon, public visibility and the log folder. As a last resort, select the FF Logs status in StaticOps’ top bar and paste the report URL or code. Automatic matching is preferred because it checks timestamps, encounter and roster.

6. Add Discord (optional)

1. In Discord, open Server Settings > Integrations > Webhooks.
2. Create a webhook in the target channel and copy its URL.
3. Paste it into StaticOps > Settings > Discord webhook, save, then use Test webhook.

No bot or user token is required. Documentation: Intro to Discord webhooks.

7. Start a raid session

1. Launch FFXIV.
2. Launch ACT and confirm that FFXIV_ACT_Plugin.dll is active.
3. For advanced data, start Archon with Public Go Live.
4. Launch StaticOps, open Command, and run the check again.
5. Enter supported content, wait for the ready state, then begin the pull.

The local pull appears as soon as it ends. FF Logs enrichment usually arrives on the next cycle, up to about 90 seconds after the fight becomes available. No manual report link is required during normal operation.

8. Read states and delays

A local value remains visible as an independent control. Data marked FF Logs ✓ comes from the matched fight. High confidence means several pieces of evidence agree; it does not turn an inference into an observed fact.

9. Data, backups and updates

• History, settings, application logs and backups live under %LOCALAPPDATA%\StaticOps.
• The FF Logs Client Secret and Discord webhook are encrypted with Windows DPAPI in the user profile.
• The dashboard API only listens on 127.0.0.1.
• Verified SQLite snapshots are created automatically; a manual snapshot can be started from Settings before an important operation.
• An update is never installed during an active pull. StaticOps waits for the pull to end and protects the database before replacing files.
• Sanitized crash reports are disabled without explicit consent, and that choice remains reversible.

Never post secrets.dat, staticops.json, a SQLite database, an ACT log or a webhook URL in a public issue.

Quick troubleshooting

For a reproducible problem, use GitHub issues without attaching sensitive data.

30-second checklist

• ACT running, FFXIV plugin enabled and recent .log
• Same FFXIVLogs folder in ACT, Archon and StaticOps
• Archon on Public Go Live when FF Logs data is wanted
• Supported content detected
• No blocking pre-raid check error
• Recent snapshot and enough disk space
• Discord ready when the webhook is used