Guide
Upload a WoW combat log
Drop WoWCombatLog.txt on the dashboard and get a CLA and an RPB for the raid night a few seconds later.
The whole workflow is sign in, drop the file, read the report. No addon, no Warcraft Logs account, and nothing to wait for. The file is on the logger's machine already.
What you need
- A Logbreakdown account: sign in with Discord and request access. The beta is closed and changes often. Reading a report needs no account, only uploading does.
WoWCombatLog.txtfrom the game's Logs folder, written with advanced combat logging on. The logging guide covers both.
1. Open the dashboard
Sign in and you land on the dashboard. The New breakdown box at the top takes the file. Three fields above it are optional, and all of them can be changed after the upload.
| Field | What it does |
|---|---|
| Title | The heading of the report and the title of the Discord post. Left empty, the report is named after the instances found in the log, like MH, BT. |
| Raid team | Which of your teams the night belongs to. A team carries the Discord webhook, so pick one if you want the link posted. Teams are set up under Raid teams. |
| Visibility | Hidden, the default, means anyone with the link can read it and nobody else finds it. Public also lets search engines in. Private is only you. More under sharing. |
2. Drop the file in
Drag WoWCombatLog.txt onto the box, or click it and pick the file. The upload starts at once, and the box shows three stages:
- Uploading, with a percentage. This is your connection and the file size, nothing else.
- Building CLA and RPB. Parsing a full night takes a couple of seconds.
- Saving the report. Then it opens.
If the team has a Discord webhook, the link is posted as the report opens.
A night with more than one raid
Many guilds run Gruul, Magtheridon and Karazhan on the same evening, or Hyjal and Black Temple. Logbreakdown finds every instance in the file and makes one report per raid, plus a page for the whole night with a switch between them at the top. The dashboard lists the instances with their own links.
When the team's Discord setting is Ask me after upload, the last step asks whether Discord gets one message for the night or one per raid. Not posting at all is a choice too.
Limits during the beta
| File size | Up to 500 MB. A full night is well under that. |
| Uploads | 5 an hour and 15 a week per account, including files that are not a combat log. Three raid nights a week fit with room to spare. |
| The same file twice | Recognised by its content and not parsed again. It does not count towards the limit. |
| One at a time | The machine parses one log at a time. A second upload while that is running is asked to wait a minute. |
If the upload fails
| Message | What it means |
|---|---|
| File is too small to be a combat log | Logging was not on. Type /combatlog before the first pull next time. |
| This is not a WoW combat log | The file is not a combat log. Drop WoWCombatLog.txt from the game's Logs folder, not a screenshot or a random text file. |
| This is not a TBC Classic combat log | Retail, Classic Era and other expansions are not supported. Anniversary TBC realms are. |
| This file has no combat events | The header is there but nothing was fought. Logging may have been turned on after the raid, or the file was emptied. |
| Another log is being parsed | Someone else is uploading. Wait a minute and drop the file again. |
| Sign in first | The session ran out. Sign in again and drop the file again. |
| Upload limit | One of the limits above. The hourly one clears itself. |
| Could not reach the data service | The parser is down. Try again in a few minutes. If it stays down, use Report a problem in the account menu. |
| The report opens, but Gear is empty | Advanced combat logging was off. It is a one-time setting, turn it on. |
Logbreakdown parses TBC Classic logs, Anniversary realms included. A file from Retail or Classic Era is not supported.
Next: share the report.