Combat Logs

Where the log is, and how to make one

Forever beta

World of Warcraft/_forever_/Logs/WoWCombatLog-*.txt

Live Classic

World of Warcraft/_classic_/Logs/WoWCombatLog-*.txt

Start and stop logging

Type /combatlog in the game. It writes until you type it again or log out.

Turn on the detail

Advanced Combat Logging in System › Network. Without it there is no health, no position, no power and no level in the log, so deaths, replay and the boss-HP check have nothing to read.

A log is plain text the game writes. This page never sends it anywhere: there is no upload endpoint on this site.

On a Mac, following a live log needs one extra step. World of Warcraft installs into /Applications, and browsers refuse to hand a page any folder in there — Chrome says it “contains system files”. Opening a log is unaffected: choose or drop the file and it reads normally. Only Follow, which re-reads the file as the game writes it, needs the folder, so point it at a copy of Logs somewhere like Documents.

Every network request this page ever makes

• Its own code — this page, logs.css, the ui/*.js files, worker.js and the core/*.js parser, from wowdata.app.
• Spell data — data/spells.js and, when a session runs, data/simspells.js, generated from the Forever client. Same origin, loaded once.
• Spell icons — one image per ability a table shows, from wowdata.app. A missing one falls back to the question mark and is not asked for again.
• Web fonts — the stylesheet and font files from Google Fonts. That is the only request to anything that is not wowdata.app, and it carries no part of your log.

That is the whole list. The combat log itself is never sent anywhere — there is no upload endpoint on this site, no analytics call on this page, and no API behind any button here. Exporting a report writes a file to your disk; it does not post one. After the first visit the page and its code are cached by a service worker and it opens with no network at all.