WoW Patch 10.2 Combat Log Change: How Blizzard Stopped Overlays

Key Takeaways

• In Dragonflight Patch 10.2 (November 7, 2023), Blizzard changed how World of Warcraft writes combat log data: all events are stored in memory during combat and written to disk only when combat ends.
• The trigger was a Reddit-demonstrated overlay tool that read the live combat log file during live raid pulls to display player positions, debuff assignments, and mechanic safe zones in real time.
• Blizzard cited EULA Section 1-C and framed the change as a protection for Season 3 raiding in Amirdrassil.
• Warcraft Logs is not affected — it processes data after combat ends, exactly when the file is now written.
• A historical parallel: Blizzard broke the AVR (Augmented Virtual Reality) addon in Wrath of the Lich King's Icecrown Citadel tier (~2010) with a targeted API change — the first time the game was modified specifically to stop an overlay tool.

This article covers the mechanism Blizzard changed, the incident that triggered it, and the practical impact on raiders and log parsers.

What Changed in Patch 10.2

World of Warcraft's Advanced Combat Log is the opt-in setting (System → Network → Advanced Combat Logging) that enables detailed per-event logging for tools like Warcraft Logs. Before Patch 10.2, the game wrote combat events to the WoWCombatLog.txt file in real time; each event was appended to disk as it occurred during combat.

With Patch 10.2, Blizzard reversed that write behavior. Combat log data is now held in memory for the entire duration of a combat session and written to disk in a single batch when combat ends. From a Warcraft Logs user's perspective, the log file is complete and functional after every pull. An external program polling that file during active combat sees the previous pull's data — nothing from the current pull exists on disk yet.

The Tool That Triggered the Change

The Patch 10.2 change was a direct response to a tool demonstrated by Reddit user u/Shamzaa in r/CompetitiveWoW. The tool read the live WoWCombatLog.txt file during live raid pulls and rendered a real-time radar overlay on a separate screen showing player positions, debuff assignments, and mechanic safe zones. In effect, it converted the combat log stream into a live instruction display for boss mechanics — eliminating the execution challenge those mechanics exist to test.

Blizzard's public statement cited EULA Section 1-C, which prohibits external programs that modify or interrupt the game session in unauthorized ways. The statement explicitly distinguished the overlay from Warcraft Logs: post-combat parsers that upload data after combat ends are not covered by the change, since they operate on already-finalized log data rather than the live stream.

Historical Precedent: The AVR Addon

The Patch 10.2 combat log change follows a precedent from Wrath of the Lich King. During the Icecrown Citadel raid tier in 2010, an in-game addon called AVR (Augmented Virtual Reality) used the WoW API to project visual markers directly onto the 3D game world, showing safe positioning zones for boss mechanics. Blizzard silently hotfixed the API it relied on — no patch notes, no warning — and AVR stopped working overnight.

Both responses share the same principle: Blizzard modifies game behavior when a third-party tool replaces player skill with an automated real-time display. The AVR case targeted an in-game addon; the Patch 10.2 change targets an external program. The outcome is the same — the tool stops working because the data stream it depends on is no longer accessible in real time.

Known Limitations of the New System

The deferred write approach introduces a narrow limitation: combat log data stored in memory is lost if the game crashes or the player reloads the UI during an active combat session. The log for that pull is discarded on crash; only completed pulls produce a file entry.

A separate issue surfaced during Patch 10.2 PTR testing: events in the written file could appear out of order relative to combat sequence. All events retain their original timestamps, so parsers that sort by timestamp during upload process the log accurately. No data is lost; only the on-disk ordering may differ from combat sequence.

📌 If you upload a log and see events out of sequence in Warcraft Logs, sort by the timestamp column before sharing a parse link : the data is complete; only the file ordering is non-sequential.

Impact on Raiders and Parsers

For players using Warcraft Logs, the workflow is unchanged: enable Advanced Combat Logging, run pulls, and upload after the session. The file now writes at combat end rather than in real time, but the upload process and resulting data are identical. Players looking to run Amirdrassil with a carry will log and parse under the same system — Blizzard's change left post-combat parse tools completely untouched.

Players who used third-party overlay programs for raid encounters can no longer use them as live displays. Programs that read the combat log file during active combat will find the file unchanged until combat ends, making the overlay non-functional at the moment it would matter most.

✏️ The deferred write also means your parser only sees completed pulls. If you want to capture a wipe-heavy progression night accurately, let each pull fully reset to out-of-combat before closing the session — reloading mid-combat discards that pull's in-memory data.

Last reviewed 2026-06-12 against Patch 10.2 Guardians of the Dream — Maintained by WowCarry's WoW team.

FAQ

What exactly did Blizzard change about the combat log in Patch 10.2?

Blizzard changed World of Warcraft so that combat log events are stored in memory during a combat session and written to the WoWCombatLog.txt file only when combat ends. Previously, events were written to disk in real time as they occurred.

Why did Blizzard make this change?

An external overlay tool demonstrated on Reddit read the live combat log file during raid pulls to display player positions and mechanic safe zones in real time. Blizzard cited EULA Section 1-C and made the change to protect competitive integrity in Season 3 raiding for Amirdrassil.

Does this affect Warcraft Logs?

No. Warcraft Logs uploads and processes data after combat ends, exactly when the log file is now written. The upload workflow is unchanged, and post-combat analysis remains fully functional.

Can combat log data be lost with this system?

Yes, in one scenario: a game crash or UI reload during active combat discards the in-memory log for that pull. Completed combat sessions are written to disk as normal. The PTR issue of events appearing out of order (with timestamps intact) is a separate behavior difference that parsers handle transparently.

Was this Blizzard's first response to an overlay tool?

No. During Wrath of the Lich King's Icecrown Citadel tier (~2010), Blizzard silently patched the API used by the AVR (Augmented Virtual Reality) addon, which projected visual safe-zone markers directly into the game world for boss mechanics. The Patch 10.2 combat log change follows the same pattern — the game is modified specifically to break a tool that replaces mechanical skill with an automated display.

Was this change tested on the PTR before it went live?

Yes. The change appeared on the Patch 10.2 PTR before going live on November 7, 2023. A PTR bug caused events to appear out of order in the written file; all timestamps were preserved, and parsers that sort by timestamp are not affected. The ordering issue was documented and acknowledged before live release.

What is the Advanced Combat Logging setting?

Advanced Combat Logging is an opt-in setting under System → Network in the WoW interface. Enabling it causes the game to write detailed event data to the combat log file (spell IDs, GUIDs, target information) that parsers like Warcraft Logs use to generate performance breakdowns. It must be enabled before a pull for that pull's data to appear in the log.