Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Robert5204/FFLogsUploader/llms.txt

Use this file to discover all available pages before exploring further.

Most issues with the FFLogs Uploader plugin fall into a small set of known categories. Work through the relevant accordion below to diagnose and resolve the problem. If none of these solutions help, check the Dalamud plugin log for detailed error output.
To view the plugin’s diagnostic log, run /xllog in the FFXIV chat box. The FFLogs Uploader prefixes all its log entries so you can filter by [Login], [Parser], [LiveLog], or [Retry] to narrow down the relevant output.
The most common cause is an incorrect email address or password.Steps to resolve:
  1. Open fflogs.com in your browser and confirm you can log in with the same email and password. If that fails, reset your password on the FFLogs website first.
  2. In the plugin login window, re-enter your credentials carefully — the password field does not show characters as you type.
  3. If you recently changed your FFLogs password, disable Remember me, log out of the plugin, and log back in with the new password.
  4. Check /xllog for a [Login] entry showing the HTTP response code. A 400 or 401 response confirms the credentials were rejected by FFLogs; a network error suggests a connectivity issue instead.
The plugin downloads the FFLogs parser JavaScript bundle from fflogs.com the first time it runs and caches it for 24 hours. Several things can cause this download to fail.Common causes:
  • Cloudflare challenge: fflogs.com uses Cloudflare bot protection. Occasionally the plugin’s HTTP client triggers a challenge page instead of the real parser page. Wait a few minutes and try again — challenge cookies rotate periodically.
  • Partial download or changed page structure: If the downloaded file is smaller than expected or missing required markers, the plugin rejects it and logs an error.
  • Stale or corrupt cache: A previously downloaded but invalid bundle may be cached on disk.
To force a fresh download, delete the cached parser file and restart the upload:
%APPDATA%\XIVLauncher\pluginConfigs\FFLogsPlugin\fflogs_parser_v8_v2.js
After deleting the file, retry the upload or live log. The plugin will download a fresh copy. If downloads continue to fail, check /xllog for the specific error message.
The plugin requires a valid ACT log directory that ends with FFXIVLogs and contains at least one .log file.Steps to resolve:
  1. Confirm ACT (Advanced Combat Tracker) is installed and has been run at least once with the FFXIV plugin enabled. ACT creates the FFXIVLogs directory and populates it with log files during play sessions.
  2. Check that the Log Directory field in the plugin points to a path ending in FFXIVLogs. The default auto-detected path is: 
    %APPDATA%\Advanced Combat Tracker\FFXIVLogs
  3. Open that directory in Windows Explorer and confirm .log files are present. If the directory is empty, start a play session with ACT running so it can record new log data.
  4. If your ACT logs are stored in a non-default location, update the Log Directory field in the plugin to point to the correct FFXIVLogs folder.
The plugin uploads each fight as a separate segment and retries failed segments up to three times with exponential backoff (1 s, 2 s, 4 s between attempts).Steps to resolve:
  1. Check your internet connection. A dropped connection mid-upload is the most common cause of segment upload failures.
  2. Watch /xllog for [Retry] entries — these show which segment failed and what error was returned.
  3. If the upload appears to complete but the report is missing fights or stuck in a processing state on fflogs.com, the terminate step may have failed. The plugin logs a warning when termination fails after all retries. In this case, open the report on fflogs.com directly — FFLogs may still be able to process the partial data.
  4. If the same log file fails to upload repeatedly, try uploading a shorter or more recent log file to rule out a file-specific issue.
After uploading a log, the parse viewer fetches fight rankings from the FFLogs API v2. If no percentiles appear, the report is likely still being processed by FFLogs.Steps to resolve:
  1. Wait one to two minutes after the upload completes, then click Refresh in the parse side panel. FFLogs processes reports asynchronously; large logs may take longer.
  2. If the exportedSegments count shown is 0, FFLogs has not yet finished indexing the report. This is normal immediately after upload.
  3. If percentiles still do not appear after several minutes, open the report on fflogs.com in your browser. If the report is visible there with rankings, the issue is specific to the plugin’s API query — check /xllog for GraphQL errors.
The parse viewer uses the FFLogs API v2 to fetch rankings. It requires a Client ID and Client Secret that are separate from your login credentials.Steps to resolve:
  1. Go to fflogs.com/api/clients and create a new API client if you do not already have one. Note the Client ID and Client Secret shown on that page — the secret is only displayed once.
  2. Open the Parse Viewer (click View Parses after any upload). The viewer shows a setup prompt with Client ID and Client Secret input fields. Paste both values and click Save & Connect.
  3. The credentials are saved to the plugin configuration automatically. The “API Setup Required” prompt will not appear again.
See configuration options for details on the ApiClientId and ApiClientSecret settings.
The plugin only persists credentials when the Remember me checkbox is enabled at login time.Steps to resolve:
  1. Open the login window, enter your credentials, and tick Remember me before clicking Login. The plugin will save your email and an encrypted copy of your password.
  2. On Linux / Wine, confirm that the plugin config directory is writable by the current user: 
    %APPDATA%\XIVLauncher\pluginConfigs\
    If the directory or FFLogsPlugin.json has restrictive permissions, the plugin will fail silently when trying to save. Check Wine drive mappings and folder permissions if this applies to your setup.
  3. Note that saved credentials are encrypted with a per-install key. Moving FFLogsPlugin.json to another machine or Wine prefix will cause decryption to fail and require re-login — this is expected behavior.
The region is set per-upload in the main window. If you uploaded with the wrong region, that report cannot be re-regionalized — the region is baked into the report at creation time on the FFLogs server.Steps to resolve:
  1. Change the Region dropdown in the plugin to the correct value matching your game server’s data center.
  2. Re-upload the log file. The new upload will create a fresh report under the correct region.
  3. If the incorrectly regionalized report is attached to a guild, you may want to delete it from fflogs.com to avoid polluting that guild’s ranking data.
See FFLogs server regions for the full list of regions and their corresponding data centers.

Build docs developers (and LLMs) love

Get started for freeTalk to us