The thread is about his warrior being broken somehow then he used priests bugged shield as some sort of justification for his complaints about his own class.
We know priests shields are bugged, that has nothing to do with OP sucking at warrior, especially when warriors are beating priests with bugged shields.
4 Likes
I was going to level my shaman next, but i think i may jump on your bandwagon.
I dont not wish to exploit certain bugs for my own personal gain, but there just has to be some synergy with having a fury warrior tank sit/stand spam for free enrage/blood craze procs, while taking zero damage off the shield, and maintaining high rage gen from dw while enraged white damage - especially if you add the hs/cleave while dw bug (no penalty to hit).
If a paladin can stream to 10k+ people how to ânot exploit a bugâ in regards to sit/stand spam for free soc procs, anyone can do it.
2 Likes
âWaaaaaaahhhhhhâ. OP - September 2019
3 Likes
The gall of making it personal instead of fixing what is bugged and broken
Just sad really.
How about we just try and make the game actually be all it can be and fix it for everyone to enjoy! Thanks!
3 Likes
I wouldnât be too confident there OP, this is Blizzard were talking about.
Improved Power Word: Shield Rank 3
Requires Priest (Discipline)
Increases the damage absorbed by your Power Word: Shield by 15%.
The âbugâ is with this, and melee crits not reducing the damage from the improved shield.
2 Likes
Dude, we know.
He made a thread complaining about his warrior being bugged and useless, it has nothing to do with priests shield bug.
He just randomly brought it up mid thread. Itâs a seperate problem (if his original âproblemâ is even real in the first place).
^
2 Likes
GĂ ldin:
Improved Power Word: Shield Rank 3
Requires Priest (Discipline)
Increases the damage absorbed by your Power Word: Shield by 15%.
The âbugâ is with this, and melee crits not reducing the damage from the improved shield.
Sweeet 2 more levels then more OPness.
Actually the thread is about âDid you reroll because your class is buggedâ Itâs clearly a question the OP.
There I highlighted the topic for you.
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
Hunters have rerolled cause of their bugs, Rogues have rerolled cause of their bugs⊠etc etcâŠ
Simple discussion on did you reroll too? What bugs caused you to stop playing your class/spec?
/discuss
1 Like
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.
7 Likes
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.
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
1 Like
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.
4 Likes
Complains that the OP is complaining
3/3 this is a troll ez report
3 Likes
I know right moving on with the discussion and just reporting the blatant agenda to derail a thread.
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.
3 Likes
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
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
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.
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.
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?
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.
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
Base miss chance: 5% + (57*5 - 305) * 0.1% = 3%3% * 0.8 + 20% = 22.4%22.4% - 7% = 15.4%
White attacks (no HS queued)
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)
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
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
Base miss chance: 5% + (57*5 - 305) * 0.1% = 3%3% * 0.8 + 20% = 22.4%22.4% - 7% = 15.4%
White attacks (no HS queued)
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)
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.
4 Likes
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
2 Likes
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.
2 Likes
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.
1 Like
Aizensama:
What are you guys doing?
Playing my resto shaman and leveling a druid tank alt.
2 Likes
How do you like Druid? I kinda want to make an odd ball spec and do Boomkin.
