Protection Warrior’s enormous Execute rework has lasted roughly long enough for everybody to update their spreadsheets. Blizzard has now rolled back the biggest parts of the Patch 12.1.5 PTR experiment, restoring Execute’s previous functionality and replacing the planned 100% damage increase with a much smaller 30% buff. The reason is more interesting than the reversal itself: Blizzard says the changes were not enough to accomplish what it actually wants from Protection Warrior, and the necessary work is now being pushed into Patch 12.2 and even 13.0 instead.

The original 12.1.5 PTR changes were unusually aggressive. Blizzard said Protection Warriors struggled to incorporate Execute into their rotation because of its high Rage cost, so the plan was to remove the ability’s optional extra Rage consumption entirely and increase its base damage by 100%. The idea was essentially to make every Execute hit as though the Warrior had committed the full additional Rage payment automatically.

That version is now gone.

The 100% Execute Buff Is Dead

In the September 15 PTR update, Blizzard crossed out both of the headline changes. Execute will once again use its previous Rage functionality, and the planned 100% damage increase has been replaced with 30% more damage.

Blizzard’s explanation is unusually candid. The developers say last week’s Execute adjustments “were not sufficient” to achieve their goals for Protection, and that the scope of the necessary changes is more appropriate for a major update rather than Patch 12.1.5. The team is therefore refocusing on Patch 12.2 and 13.0 for the bigger Protection Warrior work.

Which is a polite way of saying that making Execute substantially cheaper and twice as strong did not solve the actual problem.

Why Blizzard Tried the Change in the First Place

The original reasoning still matters because it tells us where Blizzard thinks Protection Warrior is currently awkward.

Execute is supposed to become an attractive button when enemies enter its health threshold. For Protection, however, Rage is also the resource keeping the Warrior alive and maintaining the rest of the rotation. Spending extra Rage on Execute can therefore feel considerably less exciting when that same resource is competing with defensive or rotational priorities.

Blizzard initially tried to solve that by simply removing the optional Rage component. In the first PTR notes, the developers explicitly said Protection Warriors were “hard-pressed” to fit Execute into the rotation because of its cost.

That was also why the Colossus Hero Talent tree was being adjusted around greater Rage efficiency. The initial PTR design gave Practiced Strikes an additional effect reducing the Rage cost of both Execute and Revenge by 10, reinforcing the idea that Colossus Protection should feel unusually efficient when spending Rage offensively.

The problem, apparently, is that this still did not produce the rotational identity Blizzard wants.

This Is Bigger Than One Ability

That is the most important part of the reversal.

If the problem were simply that Execute dealt too little damage, Blizzard could tune the percentage until the button became attractive. Instead, the team has concluded that the necessary Protection changes are broad enough to belong in major patches.

That suggests the discussion has moved beyond whether Execute should hit for 30%, 70% or 100% more damage.

Blizzard appears to be looking more fundamentally at how Protection spends Rage, how Execute competes with other buttons and how Hero Talents such as Colossus fit into that resource economy.

Patch 12.1.5 is therefore becoming a holding pattern rather than the finished answer.

Execute gets a straightforward damage increase.

The rotation stays mostly familiar.

The larger surgery waits for later.

Patch 12.2 Is Becoming Increasingly Important for Protection

The reference to both 12.2 and 13.0 is particularly interesting. Blizzard could simply have said the rework needed more time. Instead, the developers have already identified two future major-update windows for further Protection work.

That does not guarantee a complete specialization redesign in either patch. Blizzard has not announced new Protection talents or a replacement Rage system. But it does tell us the developers expect the solution to arrive in stages rather than through one PTR number change.

That approach is probably healthier than forcing an oversized redesign into 12.1.5 simply because the first experiment already reached the test realm.

PTR exists precisely so ideas can fail before they reach live servers.

Occasionally very loudly.

The PTR Is Doing Exactly What It Is Supposed to Do

There is always a temptation to treat PTR class changes as upcoming facts rather than experiments. Protection Warrior is a useful reminder that numbers appearing in development notes can disappear just as quickly.

One week ago, Protection Execute was losing its optional Rage cost and gaining 100% damage.

Now both changes have been abandoned.

The live direction for 12.1.5 is substantially simpler: the old functionality remains, and Execute deals 30% more damage.

For Protection Warrior players, that may feel less exciting than the original proposal. But Blizzard’s explanation is arguably more encouraging than quietly shipping a half-solution.

The developers tried to fix Execute.

They discovered Execute was not really the whole problem.

And instead of pretending otherwise, they have moved the bigger job to patches where they have room to do it properly.

Sometimes the most useful PTR change is the one that never leaves the PTR.

Post a Comment

Previous Post Next Post

Sponsores

Sponsores