Analyze
Detailed encounters
Inspect damage, DPS, actions, targets, effects, and combat timelines for every segmented encounter.
xilogs
FFXI combat analysis
xilogs turns Final Fantasy XI combat logs into clear encounter timelines, damage breakdowns, player statistics, and shareable parses.
Analyze
Inspect damage, DPS, actions, targets, effects, and combat timelines for every segmented encounter.
Compare
Review individual performance, active DPS, accuracy, critical hits, multi-attacks, and ability usage.
Share
Your uploads begin privately. Publish completed parses only when you choose to share them.
Windower addon guide
Download the checksummed addon release from this site, extract it, and copy the addon folder into your Windower installation:
Windower4/addons/CombatLog
The resulting folder should contain CombatLog.lua directly—not another nested combatlog folder. Verify the ZIP against the SHA-256 from /api/addon/version.
Launch FFXI through Windower and enter this command in the game console:
lua l CombatLog
Add the same line to Windower4/scripts/init.txt if you want it loaded automatically.
Start before the activity and optionally provide a useful label:
//clog start Sortie
You can also click the CombatLog HUD. Useful commands include //clog status, //clog label <text>, //clog autorecord sortie, and //clog autorecord sheol.
//clog stop
CombatLog writes a folder containing exactly manifest.json and events.jsonl.
Click Upload parse, choose the generated run folder, and wait for processing to finish. New uploads remain private until you publish them.
Windower4/addons/CombatLog/data/<character>/<run_id>/
Recovery
Run //clog recover. On load, CombatLog also marks unfinished recordings as recovered so the completed data can still be uploaded.
Administration
Moderation
Loading reports…
Usage
| Account | Parses | Events | Storage | Last upload |
|---|
Distribution
Uploads
| Parse | Submitter | Character | State | Visibility | Events | Storage | Uploaded |
|---|
Ready when you are
Choose an imported run from the library, or add one from your log folder.
Cloud
Library
Parse
Processing status
Details
Segments
Player directory
Search
| Player | Server | Runs |
|---|
Character profile
Combat history
| Run | Date | Type | Events | Role |
|---|
Privacy center
Publishing
A parse only becomes public when its owner explicitly publishes it. Public records contain combat observations, including participant character names.
Character names come from the uploader’s recording. They are not verified identities or ownership claims.
Owners can unpublish their parses at any time. Once private, anonymous visitors can no longer read them.
Moderators can force-unpublish a parse and block it from being published again while a report is reviewed.
Takedown request
Tell us what should be reviewed and why. Provide a parse ID or character details when applicable.
Run overview
Whole run
| Player | Job | Damage | Run DPS | Active DPS | Share |
|---|
Per hand
| Animation | 1 | 2 | 3 | 4+ | 2% | 3% | 4+% | Actions | Damage | Misses | Miss% |
|---|
Weapon skills
| Weapon skill | Attempts | Hits | Misses | Hit% | Damage | Average |
|---|
Effects
| Effect | Applications | Status | Time | Uptime |
|---|
| Effect | Applications | Status | Time | Uptime |
|---|
Activity
| Action | Count | Damage | Heal | Crits |
|---|
| Time | Type | Action / effect | Targets | Outcome |
|---|
| Time | Type | Action / effect | Targets | Outcome |
|---|
| Time | Type | Effect | From |
|---|
Run map
Segments
Encounter analysis
Output
| Name | Job | Damage | Enc DPS | Active DPS | Share | Hit% | Crit% |
|---|
Opponents
| Target | Damage | Alive |
|---|
Pace
Incoming damage
Lifecycle
Breakdown
Per hand
| Animation | 1 | 2 | 3 | 4+ | 2% | 3% | 4+% | Actions | Damage | Misses | Miss% |
|---|
Weapon skills
| Weapon skill | Attempts | Hits | Misses | Hit% | Damage | Average |
|---|
Effects
| Effect | Applications | Status | Time | Uptime |
|---|
| Effect | Applications | Status | Time | Uptime |
|---|
Activity
| Action | Count | Damage | Heal | Crits |
|---|
| Time | Type | Action / effect | Targets | Outcome |
|---|
| Time | Type | Action / effect | Targets | Outcome |
|---|
| Time | Type | Effect | From |
|---|
Feed
Effects
Owner controls
Add to library
Choose the run folder from your computer. It must contain manifest.json and events.jsonl.