Guide

Enable advanced combat logging in WoW TBC Classic

Turn on advanced combat logging once, type /combatlog before the first pull, and find WoWCombatLog.txt afterwards.

Logbreakdown reads the combat log the game writes to disk. There is nothing to install. Two things have to be on before the first pull: advanced combat logging, a setting you turn on once, and logging itself, which the game forgets every time you log out.

1. Turn on advanced combat logging

With this on, the game writes a line at every boss pull with what each raider is wearing, down to enchants and gems, their talents, and the buffs they have up. That line is what the Gear tab and the flask and food columns are built from.

The quickest way is the chat box. Paste this and press Enter:

/console advancedCombatLogging 1

The same switch is in the options: press Esc, open Options, find Network (under System in the classic options window, under Gameplay in the newer one) and tick Advanced Combat Logging. It is saved with your other settings and stays on.

With it off, the log still holds every hit and heal, so the RPB works. The CLA has nothing to check gear or buffs at pull against: the Gear tab comes out empty and the consumable columns show a dash.

2. Start logging before the first pull

Advanced logging on its own writes nothing. Logging starts when you type this in chat:

/combatlog

The chat window answers Combat logging enabled. Type it again to stop. The game does not remember it between sessions, so it has to be typed every raid night, after you are in and before the first boss. If you relog or the game crashes during the raid, type it again.

Addons that switch logging on when you zone into a raid exist, and they work fine with Logbreakdown. What matters is that the file is being written while you raid.

3. Find the file

The game appends everything to one text file in the Logs folder of the client you play on.

Client	Path
TBC Anniversary, Windows	`C:\Program Files (x86)\World of Warcraft\_anniversary_\Logs\WoWCombatLog.txt`
TBC Anniversary, Mac	`/Applications/World of Warcraft/_anniversary_/Logs/WoWCombatLog.txt`
Original TBC Classic client	The same, in `_classic_` instead of `_anniversary_`.

A full raid night is usually somewhere between 100 and 300 megabytes. That is normal, and the upload expects it.

Before every raid

Empty the file first. The game keeps appending. After a few weeks the file holds a month of raids and dungeons, and the report would show all of it. Delete or move WoWCombatLog.txt before the raid, and the upload is one night.
One logger is enough. Logbreakdown reads one file per night. Pick a raider who is in for every pull, and a second one as backup.
Watch for the chat line. If you did not see Combat logging enabled, nothing is being written.

If something is missing

What you see	Why
The Gear tab is empty and every flask column is a dash	Advanced combat logging was off. Turn it on once and it stays on.
The file is a few kilobytes	`/combatlog` was never typed, or was typed twice and switched logging off again.
The upload says the file is too small to be a combat log	Same as above.
The report has raids you did not run tonight	The file holds older nights too. Empty it before the next raid.

Next: upload the file.