Just to add on to this. Because block is on the second roll, stacking parry or dodge reduces the chance to get a block, thereby reducing the value of mastery.
DR works by decreasing the percentage base of avoidance you get with higher actual rating. ie (random numbers) If you're sitting at 500 parry rating, adding 100 more parry would give you 1% more parry chance but if you're sitting at 1000 parry rating, adding 100 more parry would only give you .5% parry chance. This is the reason you attempt to even out your dodge and parry. Having the ratings close to each other will result in more net avoidance percentage than having one much higher than the other.
But are these real numbers or arbitrary ones? Somewhere I've read that the difference from stacking one stat over the other (i.e. parry for revenge) is below 1% net avoidance as compared to having them close to one another.
Between monk and warrior, which is better as the off tank?
If warrior, should it then be crit>mastery?
T16 4pc or 2pc? Thanks!
http://us.battle.net/wow/en/characte...nturion/simple Fury warrior (5.3) 13/13H , (5.4) 13/14H (retired)
What ever you're comfortable with, either a crit build, or a mastery build or like most warriors out there currently an avoidance build.If warrior, should it then be crit>mastery?
2p the 4p is pretty bad.T16 4pc or 2pc? Thanks!
Odeanathus is one of those people who get's a job driving the special bus just to make fun of the disabled kids....
I'm still no sure what to go for. I'm currently going with a mastery build and have 85% mastery. But when i go avoidance build i would still have 50% mastery but the parry and dodge went up good. I'm starting on HC this week or next week so should i go avoidance?
I'd also say I'd feel like a mastery build would be detrimental on a number of fights (while progressing at least, eg. Spoils) where the DPS you do is actually a huge benefit to the raid.
Last edited by Big Zazu; 2013-10-31 at 11:07 AM.
CPU: i5 3570k @ 4.5GHz | GPU: MSI GTX 970 Gaming 4G | RAM: Corsair Vengeance LP 1600 MHz | Case: NZXT H440 | Motherboard: Asus P8Z77-V LX | CPU Cooler: NZXT Kraken X61 | SSDs: Samsung 840 120GB / Samsung 840 Evo 250GB | HDD: Western Digital Caviar Green 1TB PSU: EVGA Supernova G2 750W w/ red sleeved cable kit Soundcard: Asus Xonar Essence STX w/ HD 598s
Thx for this, will check it out.
Perhaps it's just a WOL bug with the melee hit's not being counted or something but looking over my deaths overview I could not help but notice I was being crit over an over ???
Any one know why it would be registering all these crits? http://www.worldoflogs.com/reports/r.../1/#tab-deaths
As well if any of you have time to go over the parses and give some prot war specific tips on what I could do to improve then I would be much appreciative. It was our first night on him and was trying everything from swapping talents, glyphs to prioritizing S.block and sbarrier according to inc dmg... you know the "what works for our group" tuning but anything you see that I can do or am not doing and can help would be mucho appreciated! just a an FYI I'm starting as off tank, bringing adds to main pallie tank and taunting Garosh for his call and poping a cd rince repeat. in P2 we were taunting at 3-4 stacks as well ... empowere whirl with adds was generally the road block for us
Youtube Chan : http://www.youtube.com/user/eqbobyboucher
Armory : http://us.battle.net/wow/en/characte...Odina/advanced
It appears Blizzard made some changes in the combat log in 5.4.1. Certain abilities are showing as 0 damage on WoL even though the combat log records the event correctly. Exact cause hasn't been determined but my guess is they changed the event type on some abilities and also possibly added new flags that are throwing things off. Hopefully, the kinks will get worked out by next week. Until then, I wouldn't worry about it too much.
Hi guys, so I'm trying to clean out my deadly boss mods timers because it was starting to get annoying with so many timers covering my screen. So my question is, for example on Iron juggernaut dbm options, what is the difference between "ignite armor debuff" and "ignite armor cooldown". I have a hunch, but just wanted to make sure. Is the first one just showing the timer left on your debuff and the second one the cooldown until the next ability cast? I only want to see the timer for next ability cast, thanks!
Yea, that's correct. Debuff timer is fairly useless, I turn that off for every fight and just make a WA if I need to.