How to Enable Combat Logging in WoW Midnight (/combatlog, 2026)

Your raid leader says "I'll check the logs." Your M+ group says "link logs." That one guy in trade chat says "post your parse or shut up." And you're sitting there thinking: what logs? Where are these logs? Is this something I should have been doing this whole time?

Yeah. It is. But nobody ever showed you how, because every guide assumes you already know.

Let me fix that. In about 60 seconds you'll have combat logging enabled — and unlike most guides written before patch 12.0, this one accounts for what actually changed in Midnight: the addon shakeup that broke half your UI, the auto-logger addons that still work, and a known healing-data bug worth knowing about before you trust your numbers.

Whether you're prepping for Voidspire, pushing keys in the Season 1 dungeon pool, or just tired of saying "I don't have logs" when your guild asks — this is the setup.

---

What Is a Combat Log?

Every time you fight something in WoW, the game can record every single event that happens: every ability cast, every damage number, every heal, every buff, every death, every interrupt. All of it, for every player, with millisecond timestamps.

This record is your combat log — a text file called WoWCombatLog.txt that WoW writes to your hard drive while you play.

It's the raw data behind every WarcraftLogs parse, every DPS ranking, every wipe analysis, and every "why did I die?" answer. Without it, none of those tools work. With it, you can see everything that happened in a fight — not just what you remember, but what actually occurred.

The catch: WoW doesn't record it by default. You have to turn it on.

---

What Changed in Midnight (Patch 12.0)

If you logged in The War Within and you're coming back for Midnight, two things matter for combat logging:

1. The Secret Values addon shakeup didn't touch combat logs. Patch 12.0's new Secret Values system gutted in-game addons that read live combat data — WeakAuras for combat, most cooldown trackers, custom proc alerts. The combat log file that WoW writes to disk is completely unaffected. WarcraftLogs, WowCoach, and any tool that parses WoWCombatLog.txt work exactly as they did before.

2. There's a known healing-data bug. Since Midnight launched, healing events in the advanced combat log are coming in lower than the in-game UI shows for some specs (Mistweaver and Holy Paladin most reported). DPS and tank data log correctly. This affects every parser that reads the file — WCL, WowCoach, all of it — because the data is missing at the source. Blizzard hasn't acknowledged it yet as of April 2026. Don't panic if your healer numbers look light; it's not your setup.

Everything in this guide still works. You just want to know about the bug before you trust raw healing parses for HPS rankings this season.

---

Step 1: Enable Advanced Combat Logging

Before you start recording, flip this setting so your logs capture everything.

1. Open System menu (Escape → System)
2. Click Network
3. Check the box that says Advanced Combat Logging

That's it. This setting persists across sessions — set it once and forget it.

What "advanced" means: Standard combat logging records the basics. Advanced combat logging adds positioning data, absorb amounts, and other details that analysis tools need to give you accurate results. Every combat log site — WarcraftLogs, WowCoach, all of them — wants advanced logging enabled. There's no reason not to use it.

Prefer a slash command? Type this in chat: /console advancedCombatLogging 1 Same result, saves you three clicks.

---

Step 2: Start Recording

Here's the part that trips everyone up: the setting above doesn't start logging. It just configures the format. You need to actually tell WoW to start writing the file.

Type this in chat:

/combatlog

You'll see a message: "Combat logging enabled."

That's it. WoW is now recording everything. Every ability, every damage event, every heal, every death — all being written to a file on your hard drive in real time.

Important: You need to type /combatlog every time you log in or reload your UI. WoW doesn't remember that you were logging. This is the single most common reason people think they have logs and don't.

---

Step 3: Make It Automatic (So You Never Forget)

Typing /combatlog every session gets old fast. Here are two ways to make it automatic:

Option A: A Simple Macro

Create a macro with this command and put it on your action bar:

/combatlog

Click it once when you log in. If logging is already on, it toggles off — so only click it once. Not glamorous, but it works.

Option B: Use an Auto-Logger Addon (Recommended)

The cleanest solution is an addon that runs /combatlog for you whenever you zone into the right content. Two options that are actively maintained for Midnight (12.0):

• AutoCombatLogger — the most established option, maintained by Talryn since Cataclysm and updated to 12.0.2 for Midnight (Voidspire and the Eco-Dome Al'dani / Floodgate dungeons added). You can configure logging per raid name, raid size, and difficulty separately — log Voidspire Mythic but not LFR, log your M+ pushes but not Delves. Settings live under /acl or Interface Options.
• RaidLogAuto — lightweight alternative if you just want "on when I enter a raid, off when I leave." No per-difficulty config, no UI to learn.

One important catch: these addons toggle /combatlog for you, but they do not flip the Advanced Combat Logging cvar. You still need to do Step 1 once (the System → Network checkbox). After that, the addon handles everything.

This combination — Advanced enabled once, AutoCombatLogger handling the rest — is what most serious raiders run in Midnight. You never think about it again.

Option C: Skip All of This

If you install the WowCoach Desktop App, it handles everything. It detects when WoW is running, watches your log folder, and uploads your logs automatically when your M+ or raid session ends. You still need combat logging enabled in-game (Option A or B above), but the Desktop App eliminates the entire "find the file, open a website, upload it" workflow.

More on that in a minute.

Where Is Your Combat Log File?

Once logging is enabled, WoW writes to this location:

World of Warcraft\_retail_\Logs\WoWCombatLog.txt

On most Windows installs, the full path is:

C:\Program Files (x86)\World of Warcraft\_retail_\Logs\WoWCombatLog.txt

A few things to know about this file:

• It grows fast. A full raid night can produce a 500MB+ log file. A busy M+ session, 100-200MB.
• It doesn't reset automatically. WoW appends to the same file until you delete it or rename it. After a few weeks of logging, you might have a multi-gigabyte file.
• Delete it periodically. Or at least before each raid night, rename or delete the old file so you get a clean log. Most upload tools handle large files fine, but there's no reason to carry around three weeks of data.

Classic WoW players: Your log is in _classic_\Logs\ or _classic_era_\Logs\ instead of _retail_\Logs\. Same filename, different folder.

---

Now What? What Do You Do With a Combat Log?

You've got logging enabled. You ran a dungeon or raided for the night. You have a WoWCombatLog.txt file sitting on your hard drive. Now the interesting part.

A raw combat log is a wall of text — millions of lines of comma-separated data that no human should try to read directly. You need a tool to parse it. (Curious what's actually inside? The combat log basics primer walks through the format and what each line means.)

Option 1: Upload to WowCoach

Drag your WoWCombatLog.txt file onto the WowCoach upload page and it gets parsed in seconds. You'll see:

• Every fight in your session broken out — boss encounters, trash pulls, M+ runs, all of it
• Damage and healing breakdowns by player and ability
• Death recaps showing the exact sequence of damage that killed each player, including which defensive cooldowns they had available
• M+ run timelines with pull-by-pull breakdowns

And then you can do something no spreadsheet will ever give you: ask questions in plain English.

"Why did we wipe on pull 7?" "What killed the tank?" "Am I using my defensives enough?" Coach Clutch reads every event in your log and answers like a raid leader who actually looked at the data — not "do better on mechanics," but specific, timestamped, actionable feedback. (New here? Meet Coach Clutch.)

Option 2: Upload to WarcraftLogs

WarcraftLogs is the industry standard. Upload your log file through their uploader client, and you'll get detailed breakdowns, parse percentiles, and rankings. It's powerful — and complex. If you've never used it before, expect to spend some time learning the interface. (If you're wondering how the tools compare, I wrote a full breakdown of WarcraftLogs vs WoWAnalyzer vs WowCoach.)

Option 3: Use the WowCoach Desktop App

This is the "I don't want to think about any of this" option.

Download the Desktop App, sign in with Battle.net, and play WoW. The app watches your log file in real time and uploads automatically when your M+ key or raid session ends. Your reports appear on WowCoach ready to review — no manual upload, no file hunting, no alt-tabbing.

Pro subscribers get live analysis: each boss pull uploads as it ends, so you can check your wipe analysis between pulls instead of waiting until tomorrow.

---

Troubleshooting

"I uploaded my log but there's nothing in it." You forgot to type /combatlog before pulling. The advanced logging setting alone doesn't start recording — you need to explicitly start the log. Use an auto-logger addon to avoid this.

"My log file is huge and upload is slow." Delete or rename your WoWCombatLog.txt before each session so you start fresh. A single raid night's log uploads in seconds. Three weeks of accumulated data takes longer.

"I can't find the Logs folder." Make sure you've typed /combatlog at least once — WoW creates the Logs folder the first time you enable logging. If it still doesn't exist, check that WoW is installed where you think it is. Open the Battle.net launcher, click the gear icon on WoW, and "Show in Explorer" to find your install directory.

"Do I need to log every session?" Only if you want to analyze it. Most players log raids and M+ keys but skip open-world content. An auto-logger addon handles this perfectly — it only records inside instanced content.

---

What to Log in Midnight Season 1

Once logging is on, the content actually worth uploading this season:

Raids (opened March 17, 2026):

• Voidspire — 6 bosses, the main progression raid. Log every difficulty you progress on. (Pre-prep checklist.)
• Dreamrift — 1 boss, Crucible-style side raid. Worth logging for ranking pushes.

Mythic+ Season 1 dungeon pool (the 8 that count for KSM):

The 4 new Midnight dungeons:

• Windrunner Spire
• Maisara Caverns
• Magisters' Terrace
• Nexus-Point Xenas

The 4 returning legacy dungeons:

• Algeth'ar Academy
• Seat of the Triumvirate
• Skyreach
• Pit of Saron

Skip logging: delves, world quests, queued content (LFR is fine to log, but parses are noisy). AutoCombatLogger lets you whitelist instanced content only, which is the right setting for almost everyone.

The Season 1 push window closes June 23, 2026. Every key you don't log is a key you can't review.

---

The 30-Second Version

1. System → Network → Check "Advanced Combat Logging" (one-time)
2. Type /combatlog in chat (every session, or use an auto-logger addon)
3. Upload WoWCombatLog.txt to WowCoach or WarcraftLogs after your session
4. Or install the Desktop App and never think about step 3 again

That's it. Two minutes of setup and you'll never have to say "I don't have logs" again.

Your logs are talking. Your deaths, your DPS, your missed kicks, your unused defensives — it's all in there. The only question is whether you're going to listen.

---

Frequently Asked Questions

Does combat logging affect my FPS? No. The performance impact is negligible — WoW is writing a text file to disk, which your SSD handles without breaking a sweat. You won't notice any difference in FPS or latency.

Does combat logging work in Classic WoW? Yes. The /combatlog command works in Classic, Classic Era, and Season of Discovery. The log file is in the _classic_ or _classic_era_ folder instead of _retail_. Advanced Combat Logging is available in the same Network settings.

Can other players see that I'm logging? No. Combat logging is entirely local and invisible to other players. There's no indicator, no notification, nothing. Log freely.

Do I need to stop logging manually? Typing /combatlog again toggles it off, but there's no real reason to stop manually. Logging ends automatically when you log out. If you're using an auto-logger addon, it handles start and stop for you.

What's the difference between WoW's combat log and the built-in damage meter? WoW's built-in damage meter (added in 12.0, Options → Gameplay Enhancements → Damage Meter) shows you real-time DPS/HPS during combat. The combat log is a raw data file written to your hard drive that contains every event — far more detail than the in-game meter shows. External tools like WowCoach and WarcraftLogs read this file to provide analysis that goes way beyond what any in-game display can show: full death recaps, cooldown tracking, rotation analysis, and AI-powered insights.

Did the Midnight addon shakeup (Secret Values) break combat logging? No. The Secret Values system that broke WeakAuras and most combat-tracking addons only restricts what addons can read from the live game API. The combat log file is written by the game itself, not by any addon, so it's completely unaffected. Every parser that reads WoWCombatLog.txt works exactly as before — and AutoCombatLogger, which only toggles the /combatlog command, is one of the addons that survived the patch unchanged.

Why are my healing numbers lower in the log than in-game? There's a known bug in Midnight where some healing events aren't being written to the advanced combat log — Mistweaver and Holy Paladin are the most reported. DPS and tank data log correctly. This isn't a setup issue on your end; the data is missing at the game-engine level, so every parsing site sees the same gap. Blizzard hasn't acknowledged it as of April 2026. Keep logging — the bug will get fixed and old logs will still be useful — but don't read too much into healer HPS rankings this season until it's resolved.

Does AutoCombatLogger turn on Advanced Combat Logging too? No. AutoCombatLogger only toggles the /combatlog command for you when you zone in and out of content. The Advanced Combat Logging cvar is a separate one-time setting (Step 1 above). Set it once via the System → Network checkbox or /console advancedCombatLogging 1, install AutoCombatLogger, and you're done forever.

Stay clutch.

---

Coach Clutch is the AI coaching engine behind WowCoach.gg. Upload your combat logs at wowcoach.gg/upload for instant analysis, or download the Desktop App to skip manual uploads entirely.