Blizzard gave Dracthyr players a long-requested option, but the argument never really stopped

When Blizzard first previewed Battle Visage for Patch 12.0.5, it pitched the feature as a toggle for Evokers that would automatically swap them back into Visage form whenever they were not using abilities that require their draconic body. Blizzard also warned right away that the feature had technical hurdles, especially around camera movement while switching between forms. That sounded like the setup for a pretty straightforward quality-of-life win. It has not stayed that simple.

By the time Blizzard made Battle Visage testable in the PTR notes from March 25, the studio had already spelled out a long list of abilities that still force a shift back into Dracthyr form, including Deep Breath, Fire Breath, Eternity Surge, Upheaval, Hover, Rescue, Zephyr, Verdant Embrace, and Soar. Blizzard also said it had added visual treatment changes for some abilities and a camera-height override to reduce jarring transitions, which tells you the team knew the presentation side of this feature could get messy fast.

The core complaint is getting more specific now

The main PTR feedback thread is not arguing that Battle Visage is a bad idea. It is arguing that Blizzard made the exceptions list too broad for the feature to feel transformative in real play. In the thread “Battle Visage Feedback - Way Too Broad A Spell List,” players push Blizzard to narrow that list and specifically question why abilities like Hover, Dream Breath, Fire Breath, and Eternity Surge still force Dracthyr form so often. The original poster even points out that Disintegrate is not on the forced-shift list despite being a breath-style spell, which is exactly the kind of inconsistency players latch onto when a cosmetic-quality feature starts feeling arbitrary.

That feedback thread has also clearly grown legs. It has spilled across multiple forum pages, which is a decent sign the topic is not just one annoyed Evoker posting into the void. On top of that, related discussions keep spinning up around it, including “Battle Visage. Disintegrate. You cowards :p” on the Evoker forum and newer complaint threads that focus on specific ability interactions instead of the feature in general.

Hover is quickly becoming the “this misses the point” example

The newest version of the debate seems to be settling on Hover as the most obvious problem. In the April 3 Evoker thread “Hover not working with Battle Visage feels off,” a Devastation player argues that Hover is one of the spec’s most-used abilities in raid and Mythic+, not some niche dragon-fantasy button, so forcing Dracthyr form during Hover makes Battle Visage feel much less impactful in actual combat. That is a strong criticism because it shifts the conversation away from aesthetics alone and into gameplay rhythm. If a heavily used rotational or movement tool keeps breaking the Visage loop, then the feature stops feeling like a broad combat-form option and starts feeling like a partial novelty.

The forum activity supports that idea too. As of April 5, the Evoker class board showed “Hover not working with Battle Visage feels off” with replies and views already stacking up, while separate Battle Visage discussion threads were still active on the same board. That does not mean the whole Evoker community agrees on one solution, but it does show the subject is still hot enough to keep generating fresh sub-arguments instead of fading out after the first PTR week.

The deeper fight is still about Dracthyr identity

That is why the older “Combat Visage is controversial for a reason” thread still matters. That post argues the backlash is not just about one toggle or one spell list. It says some Dracthyr players feel Blizzard keeps investing in ways to avoid dragon form instead of putting more support into dragon form itself, including better transmog options and a more clearly cosmetic relationship between Visage and baseline Dracthyr play. The post explicitly says many players chose Dracthyr because they actually like the scaled dragon-body fantasy, not because they wanted to spend more time looking like “half elves with horns.”

That is the real reason this PTR feature keeps starting arguments. Battle Visage is a good option for players who want to see their Visage and transmogs more often, but some of the pushback is coming from players who think Blizzard is still answering the wrong question. They do not necessarily hate the feature. They hate the idea that it could become Blizzard’s answer to long-running complaints about Dracthyr visuals, armor support, and race fantasy.

This now looks like a feature Blizzard may need to refine more than once

The interesting part is that Blizzard already framed Battle Visage as work in progress, both when it first previewed the feature on March 12 and when it added camera-adjustment caveats to the March 25 PTR notes. So the current backlash does not automatically mean the system is doomed. It does, however, suggest Blizzard may have underestimated how quickly players would move from “finally, a Visage toggle” to “okay, now why does it still break on half my kit?”

Right now, Battle Visage still looks like a feature players want. The problem is that the current PTR version is turning into a negotiation over what “combat visage” is supposed to mean in practice. If Blizzard narrows the forced-shift list and smooths out the obvious pain points like Hover, this probably ends as a popular quality-of-life win. If not, it is going to keep feeling like Blizzard handed Evokers a cool option and then stapled too many caveats to it. 

1 Comments

  1. can they PLEASE listen to the evoker mains for just this one time

    ReplyDelete

Post a Comment

Previous Post Next Post

Sponsores

Sponsores