I made a Broken Priest... Shelving my Tank

[Purplelime-frostmourne (Purplelime)]

This has to do with bugs in general and did you in fact reroll because of this! Many classes/specs and abilities are bugged. Many have rerolled. This isn’t a warrior thread

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

This is literally just a priest shield complaint thread badly disguised so OP can complain.

We all already know about it, there was a huge reddit thread and numerous large threads on the forums + bug reports.

Everyone already knows, 0 reason to make things up about your own class.

The only class that deserves to complain right now is hunters but their issue is currently in the midst of being fixed.

[Aizensama-faerlina]

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

If we go into every detail about the bugs then what is the point of the Bug forums? Which I have 2 Reports made weeks ago. I even said it in the OP.

Just not ramming my head against the wall anymore… My Bug threads I made been sitting there for weeks. Time for easy mode.

I didn’t come here to make the same detail bug report in Classic Discussions which would be off topic. I came here to ask are you tired of your Class/Spec not working correctly and did you reroll because of it.

You can go to the Bug Report forums and see them. You can read through the countless threads there. No need to repost that.

Again you are making this personal and wanted to just troll the thread. Oh well can we just stick to the topic, please and thanks. Geez

No not everyone has some groundbreaking hidden conspiracy Just discuss the topic or don’t… Either or not responding to the trolling anymore. Just gonna report it and move on so the thread can continue.

[Purplelime-frostmourne (Purplelime)]

If we go into every detail about the bugs then what is the point of the Bug forums? Which I have 2 Reports made weeks ago. I even said it in the OP.

So you’ll go into detail about the priest shield bug we all know about but won’t tell us about the warrior bugs that are causing you to reroll, in which you originally made the thread about.

Yeah I believe you dude.

[Fearoftdark-herod]

So you’ll go into detail about the priest shield bug we all know about but won’t tell us about the warrior bugs that are causing you to reroll, in which you originally made the thread about.

Yeah I believe you dude.

Complains that the OP is complaining
Posts on retail character
provide 0 ground for legitimate discussion

3/3 this is a troll ez report

[Barragan-faerlina]

Complains that the OP is complaining
Posts on retail character
provide 0 ground for legitimate discussion

3/3 this is a troll ez report

I know right moving on with the discussion and just reporting the blatant agenda to derail a thread.

[Purplelime-frostmourne (Purplelime)]

Mad because I pointed out the thread is literally useless and just made to complain about shield bug?

We all know about it already homie, go write about it in your journal.

edit: Charge Stun DR Bug Unintended! - #21 by Aizensama-faerlina

lol, i’m the one with the agenda btw.

[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.

[Bill-stalagg]

He’s always mad. Before launch he would rage and claim people wouldn’t make it to level 30. Imagine thinking leveling to 60 is hard

[Purplelime-frostmourne (Purplelime)]

Finally, if you put some of that in your OP you can start to have a real discussion instead of the garbage you originally posted.

Oh, you’re not even the OP.

Jesus, a random poster is more useful than OP.

[Gàldin-yojamba]

Not my thread, but i did agree that rolling a priest to cash in on a class where a bug is having positive game effects instead.

Even using bugs between classes as a bonus.

[Isz-mankrik]

What are you guys doing?

Playing my resto shaman and leveling a druid tank alt.

[Aizensama-faerlina]

Playing my resto shaman and leveling a druid tank alt.

How do you like Druid? I kinda want to make an odd ball spec and do Boomkin.

[Stuart-deviate-delight]

You made your bug thread on Reddit?

[Chorachk-deviate-delight]

Warrior isnt easy… but i haven’t run into any bugs pretty sure.

[Deerhoof-ysera]

Yes the bubble does make you invincible vs Crits

It makes you invincible only in situations where you’re getting hit by nothing but crits. My point is, outside of PVP v.s warriors using reck or maybe rogues, how often does that come up?

Your original post made it sound like you rolled a priest and now the entire game is “easy mode.” Like you’re face rolling through all the content, because of a bug that specifically mitigates melee crits. A thing that, at low levels in PVE, almost never happens. So you’re mitigating practically nothing. Maybe one melee hit out every 50? The bug changes nothing. You’re obviously being way hyperbolic over this because you don’t like that it impacts your ability to PVP priests.

The bug you’re complaining about applies only to a very, very specific situation which your hypothetical low level priest has probably not even encountered.

[Mudhut-incendius]

Wrecking things just fine with my warrior. Maybe you should just like… get gud?

[Zeliek-moon-guard (Zeliek)]

Umm, blizzard already confirmed that charge movement being slower under a slow effect was vanilla like behavior during the beta.

[Aizensama-faerlina]

Wrecking things just fine with my warrior. Maybe you should just like… get gud?

Well when they fix warriors to where they were in 1.12 you should really dominate then. I am all for nochanges and would like them to fix all the bugs. Am I right!

Umm, blizzard already confirmed that charge movement being slower under a slow effect was vanilla like behavior during the beta.

I am not personally debating that but Charge shouldn’t be on the DR stun table that was added in patch 4.06. It was literally eons of time where Charge didn’t DR stuns because it really messes up gameplay.

Obviously there are other issues as well.

[Zeliek-moon-guard (Zeliek)]

I was just mentioning it because it was quoted.

[Arctis-rattlegore]

Is it possible, and I’m not saying definitely, just asking… but is it possible that because you spent hours upon hours playing at 60 in vanilla, getting decked out in great gear… that you have forgotten what it was like to be a level 40 something with an incomplete talent tree?