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.

The Upload a Log tab processes a completed ACT log file and submits every raid encounter it contains to FFLogs as a single report. The plugin runs the official FFLogs parser bundle (embedded via a V8 JavaScript engine — no Node.js required) to discover fights, produce per-fight data tables, and upload each fight as its own report segment. Large log files with many encounters are fully supported.
1

Open the Upload a Log tab

Run /fflogsuploader to open the plugin. Log in if prompted. Click the Upload a Log tab at the top of the window.
2

Select the log file

The path field is pre-populated with the most recently modified .log file in your saved log directory. To change it, click Browse and select any .log file.
If you browse to a directory instead of a file, the plugin automatically selects the most recently modified .log file in that directory.
3

Choose guild, region, and visibility

Configure the upload destination using the dropdowns:
  • Guild: select a guild from the list or keep it as Personal Logs.
  • Region: choose the data center region that matches your home world (NA, EU, JP, or OC). Only visible for personal log uploads.
  • Visibility: controls who can see the report on FFLogs. Private is the default; change to Public or Unlisted if needed.
Optionally enter a description in the text field below.
4

Click "Go!"

Click the Go! button in the bottom-right corner. The button changes to Processing… while the upload is running.The plugin performs the following steps automatically:
  1. Creates a report on FFLogs using your credentials.
  2. Scans the log file (pass one) to discover all raid encounters and their time windows.
  3. Replays each raid (pass two) in isolation so the parser produces a slim, per-fight master table scoped only to that encounter’s actors and abilities — matching what the official FFLogs uploader sends.
  4. Uploads each fight segment along with its master table.
  5. Terminates the report, making it available on FFLogs.
5

Note the report code

When the upload finishes, the status area shows:
Upload complete! Report: aBcDeFgH
The report code links to https://www.fflogs.com/reports/{code}.
6

View parses

A View Parses button appears below the status message. Click it to open the Parse Viewer with the uploaded report pre-loaded. See Viewing parses for details on the parse viewer.
Processing time scales with log file size. A log file covering a full raid session with multiple wipes can take 30–60 seconds. The Go! button stays disabled during processing.

​
How the parser works

The plugin uses an embedded V8 JavaScript engine (Microsoft ClearScript) to run the official FFLogs parser bundle directly — no separate Node.js process or external tool is needed. The parser bundle is downloaded from FFLogs on first use and cached at: 
%APPDATA%\XIVLauncher\pluginConfigs\FFLogsPlugin\fflogs_parser_v8_v2.js
The cache is valid for 24 hours. If the cached file is missing, too small, or older than 24 hours, the plugin downloads a fresh copy automatically before starting the upload.

Build docs developers (and LLMs) love

Get started for freeTalk to us