Burning Crusade Classic Anniversary patch 2.5.6 was almost entirely intended to support critical service systems, but it also brought visible nameplate and raid-frame changes. The changes quickly prompted questions, so Blizzard explained why an old version of the game still receives interface updates and how players can adjust three of the new settings right now.
The blue post has two main points. Classic continues to use a technical foundation shared with modern World of Warcraft, which means it sometimes receives the same system-level interface updates. Blizzard also accepts that players need ways to adapt those elements to their own play. The chat commands available in patch 2.5.6 are an interim bridge to proper settings in the Options menu.
Why does Classic's interface change?
Every current version of Classic shares code with modern World of Warcraft. Blizzard says this connection gives Classic support for modern hardware, broader graphics and accessibility options, proper widescreen display, and Battle.net integration.
That shared foundation also means Classic's interface is not completely isolated from Retail development. Updating a common system can affect Classic even when the rules, content, and presentation of the game are otherwise intended to preserve the feel of an older era.
The history of raid frames illustrates the difference. The original version of The Burning Crusade only offered the interface that let players drag raid groups out into separate views. When WoW Classic launched in 2019, it included modern raid frames from the Battle for Azeroth era. Burning Crusade Classic Anniversary patch 2.5.5 then used The War Within-era frames, while 2.5.6 aligned them with the current Retail implementation in Midnight.
This is not a wholesale transfer of the Retail interface into Classic. It is a new version of a shared technical system, with the player-facing effects appearing in nameplates and raid frames.
Three settings are available through chat commands
Blizzard highlighted three settings that can be changed in 2.5.6 with a /script command. Each command should be entered in the in-game chat box exactly as shown.
- Show class colors on enemy nameplates:
/script C_CVar.SetCVar("nameplateShowClassColor", 1); - Show class colors on friendly player nameplates:
/script C_CVar.SetCVar("nameplateShowFriendlyClassColor", 1); - Disable the dispel-indicator overlay on raid frames:
/script C_CVar.SetCVar("raidFramesDispelIndicatorOverlay", 0);
The first two settings make player classes easier to distinguish by nameplate color. The third disables the dispel highlight on raid frames. Blizzard did not provide separate reversal commands or details about setting persistence in the same post, so neither should be inferred from these three lines.
The commands are not meant to be the final interface. Blizzard said it expected to expose the corresponding settings in the Options menu during the week after the post. That was a relative estimate rather than a commitment to a specific date.
Patch 1.15.9 brings Edit Mode to other Classic versions
The same interface direction is also coming to Classic Era, Season of Discovery, and Hardcore. Blizzard is planning patch 1.15.9 for the week of July 19, with deployment tied to each region's normal weekly maintenance. That wording does not establish one universal launch time or exact release date for every region.
The most visible addition in the patch is Edit Mode. It lets players arrange parts of the interface without relying on addons for the entire layout. The update is also intended to include nameplate and raid-frame changes similar to those already introduced in Burning Crusade Classic Anniversary 2.5.6.
This is a meaningful step for Classic, but it should be read narrowly. Blizzard announced Edit Mode and similar interface changes, not every Retail UI feature for every version of Classic.
Addons may need updates
The underlying interface changes also matter to addon authors. Blizzard warned that some addons may produce errors until their developers release compatible updates. It did not say that every addon will stop working.
The addon API in patch 1.15.9 is described as a very close match for the one in Burning Crusade Classic Anniversary 2.5.6. Blizzard is encouraging addon developers to test their work in 2.5.6 ahead of the 1.15.9 release. The qualification matters: the APIs are expected to match very closely, not guaranteed to be identical.
For players, the practical preparation is to check for updates to important addons before weekly maintenance and expect that some interface layouts may need adjustment. If an addon begins throwing errors, the first step is to look for a 2.5.6- or 1.15.9-compatible release from its author.
What should players watch next?
The immediate item to watch is the Options-menu implementation: whether all three settings are easy to find and behave like their chat-command counterparts. Attention then shifts to the regional rollout of patch 1.15.9, the behavior of Edit Mode in Classic, and addon updates.
Blizzard's explanation does not remove every point of friction created by an interface change, but it makes the direction clearer. The new frames are part of the shared codebase's development, while the customization controls are intended to become visible settings instead of commands players must remember.
Source and scope
This article is wow-anniversary.fi's own summary of Blizzard's official forum post. It is not a direct copy of the original post.