I made a Broken Priest... Shelving my Tank

[Gàldin-yojamba]

@Purplelime-frostmourne

Tell us about the warrior bugs the OP mentions yet doesn’t describe then, as far as I can see there aren’t any.

@Aizensama-faerlina

So after testing, retesting and having others test. The DR tables are completely wrong not just for Warriors but perhaps every class. The source info for patches and how Stun DR was implemented here

I have a thread on warrior charge which has it’s own Stun table actually DRing every other stun which wasn’t added until patch 4.06

However ALL PROC stuns are incorrectly having DR for any Class/Spec that utilizes them.

Edit - I would like to also add that how the stuns function is also wrong, many are experiencing delays where the stun happens but the mob/player can actually attack after the stun and even run away before it lands. This isn’t spell batching.

Currently Mace stun, Revenge stun, Blackout stun etc… etc…are having diminishing effects!! If you get the lucky RNG of back to back stuns they will DR and that isn’t how it works. Proc stuns are full duration stuns. If you get a 3 sec Proc the next Proc needs to be 3 secs! This is how it works since they are considered Proc’s!!!

In Patch 1.9 ( 1-03-2006) The Stun effect’s duration no longer diminishes or is diminished by controlled stun abilities and spells. for the following abilities.

• Improved starfire
• Improved concussive shot
• Impact
• Seal of justice
• Blackout
• Mace specialization
• Pyroclasm
• Improved Revenge

So this 1.12 client is just beyond bugged and completely wrong on how most talents actually function. I just don’t get it

@Aizensama-faerlina

Edit - Confirmed bug so if we can get some clarification please and thanks from a Blue. Finally found when Charge stun was changed to share DR’s!!!

Patch 4.0.6 Ability Warrior Charge now shares diminishing returns with stun effects.

This is when Charge was changed for everyone but Prot Warbringer talent allowed for Charge to remain OFF the DR stun table!!

I remember charge and intercept have their own DR table. For some reason Charge stun currently DR’s other stuns doesn’t make much sense. Then that means any warrior that Charge will Dr the 5 sec stuns and everyone gets charged by a warrior.

This seems like current DR tables from Retail not Vanilla. Or am I missing something.

Currently this means any Charge will DR a HOJ, Rogue stun etc… Making their big stuns worthless. That isn’t right! I know we have all separate DR tables in Vanilla which is what made stuns so unforgiving and allowed class gameplay to function.

However this is a huge problem with control for PvE stopping mobs that get away or pull Aggro. It really minimizes peoples roles when charge can DR other CC then it causes a wipe.

If 2 warriors charge you that means your main stun is DRed. That isn’t right.

@Zaim-thalnos

If u are using a gear with +%hit and you die, you lose the %hit of the gear, you have to drop the gear and put it again to work again. This bug occur many times with mask of the unforgiven and wyrmhide spaulders. Every death i have to fix it.

@Nephelina-stormrage

Charge / Intercept seem extremely buggy/different compared to what they were in vanilla.

Warriors charge slower if they are affected by a movement speed debuff. It wasn’t like this in classic. This is probably due to forgetting to put in the “suppress movement speed debuffs while charging” line in the charge/intercept code.

Additionally Charge/Intercept don’t charge up cliffs like it did in Vanilla.

Anyone seen any other charge/intercept bugs other than these two?

@Corpseten-runetotem

There’s a bug where if you ever change your target to something that didn’t dodge your attack, or clear your target, your ability to use Overpower gets disabled. So after one of your attacks gets dodged, you have 1 shot to change to exactly that target.

@Ekbert-sargeras

There is a famous bug that was discovered in WotLK where if you’re dual-wielding and have an on-next-swing attack like Heroic Strike or Cleave queued, any off-hand swings that land during that time will not suffer the dual-wield miss penalty:

Offhand swings that land while HS or Cleave is queued do not suffer the dual wield miss penalty. They’re treated as if you were single wielding when the swing lands.

We’ve been anecdotally hearing about people noticing reduced off-hand misses with HS queued for a while now, so we decided to test it properly. We performed two tests using the exact same gear and talents; one where we just auto-attacked the target without queuing HS or Cleave at all, and another test where we used Heroic Strike as much as possible. If the ‘bug’ exists, then we should see considerable reduction to miss chance in the second test.

Player: 305 weapon skill, +7% hit
Target: Servant of Razelikh (level 57)

Base miss chance: 5% + (57*5 - 305) * 0.1% = 3%
DW miss chance: 3% * 0.8 + 20% = 22.4%
Expected miss chance: 22.4% - 7% = 15.4%

White attacks (no HS queued)
Total: 3812

• Hit: 60.55% ±1.55% (2308)
• Crit: 18.47% ±1.23% (704)
• Miss: 15.42% ±1.15% (588)
• Parry: 1.23% ±0.35% (47)
• Dodge: 3.36% ±0.57% (128)
• Block: 0.97% ±0.31% (37)

White attacks (HS queued whenever possible)
Toal: 2339

• Hit: 64.34% ±1.94% (1505)
• Crit: 20.35% ±1.63% (476)
• Miss: 9.28% ±1.18% (217)
• Parry: 1.58% ±0.51% (37)
• Dodge: 2.74% ±0.66% (64)
• Block: 1.71% ±0.53% (40)

As can be seen by the results of the second test, the bug is clearly present.

-magey & the Fight Club team

@Ekbert-sargeras

There is a famous bug that was discovered in WotLK where if you’re dual-wielding and have an on-next-swing attack like Heroic Strike or Cleave queued, any off-hand swings that land during that time will not suffer the dual-wield miss penalty:

Offhand swings that land while HS or Cleave is queued do not suffer the dual wield miss penalty. They’re treated as if you were single wielding when the swing lands.

We’ve been anecdotally hearing about people noticing reduced off-hand misses with HS queued for a while now, so we decided to test it properly. We performed two tests using the exact same gear and talents; one where we just auto-attacked the target without queuing HS or Cleave at all, and another test where we used Heroic Strike as much as possible. If the ‘bug’ exists, then we should see considerable reduction to miss chance in the second test.

Player: 305 weapon skill, +7% hit
Target: Servant of Razelikh (level 57)

Base miss chance: 5% + (57*5 - 305) * 0.1% = 3%
DW miss chance: 3% * 0.8 + 20% = 22.4%
Expected miss chance: 22.4% - 7% = 15.4%

White attacks (no HS queued)
Total: 3812

• Hit: 60.55% ±1.55% (2308)
• Crit: 18.47% ±1.23% (704)
• Miss: 15.42% ±1.15% (588)
• Parry: 1.23% ±0.35% (47)
• Dodge: 3.36% ±0.57% (128)
• Block: 0.97% ±0.31% (37)

White attacks (HS queued whenever possible)
Toal: 2339

• Hit: 64.34% ±1.94% (1505)
• Crit: 20.35% ±1.63% (476)
• Miss: 9.28% ±1.18% (217)
• Parry: 1.58% ±0.51% (37)
• Dodge: 2.74% ±0.66% (64)
• Block: 1.71% ±0.53% (40)

As can be seen by the results of the second test, the bug is clearly present.

-magey & the Fight Club team

Just to name a ‘few’ of the bugs affecting warrior gameplay.