Is melee hit cap really 9%?
 

So I, and basically everyone else, thought the hit cap for ranged attacks and non-dual-wielding melee attacks was 9%.
There is a post in hunter forum found here with some pretty convincing tests showing that it is actually 8%.
Since this relates to other classes as well, I thought it might be a better idea to have a thread on main page for everyone else to see.
Feel free to add any data (dummy vs bosses, white hit vs yellow hits, etc) so that we can confirm or deny that 8% is the new hit cap for physical dps.

Similar data in the druid forum here, with some discussion farther down: http://elitistjerks.com/f73/t36999-f...p2/#post988344

I glanced through the hunter thread, too, and the sample set of people with 8.x% hit and not missing against actual bosses is starting to get to the point where it's hardly believable that the problem is just a flaw in the boss level target dummy mechanics.

Wild speculation here, but perhaps when they removed the inherent 1% resist chance for spells, they lowered the ranged/melee hit cap as well. The data in the hunter thread is indeed convincing; as it is I'll be aiming for 263 hit until someone somewhere reports a miss with over 8% hit.

Paladins have (in various tests) gotten from 1% "ghost hit" (that's what we've been calling it) to 4%.

For some Paladins in raids (not just against test dummies) they're not missing at 8%, but miss if they go lower. Some don't miss at around 6%, some at 5%. It's quite confusing to our class community.

We'd been wondering if there issues when they removed the +hit talents - possibly people who had it before 3.0 still are gaining it. There had been debate if it was from Ret aura.

Seeing various threads along the same lines for multiple classes, I'm inclined to believe hit has changed for +3s.

The question is - did Blizzard intend this or is it in error? DPS was balanced around their assumptions. If we all had 1% (or more) free hit during balance and they fix it later, what does this do to melee DPS?

Similarly, if there was a 1% change to the "generic" physical miss rate, was there any change to the dual wield miss rate? If not, this would be a small buff to arms warriors/druids/hunters, but won't do anything for rogues, and enhance shaman whose specials will be capped anyway, from needing lots of hit for other things. Not sure how it'll affect fury warriors; with the extra 5% miss on specials, I don't know if they actively ensure soft hit cap anymore or not.

There are some data supporting that 8% is hit cap for not just white attacks, but yellow attacks as well.
It means mut rogues and enhance shaman lose value on their hit rating past 8%, as opposed to 9% before. Unlike arms warrior, druid, and hunters, they still gain some benefit from hit rating past cap, but those stats are better allocated somewhere else (feel free to correct me if I'm wrong, but I'm just saying this still has quite an impact on rogues and enhance shamans as well).
What I really like to see is some data from fury warriors w/ TG. Are their specials capped at 13 or 14%? Are their white hits capped at 27% or 28%? (Only if I had a warrior)

Im currently testing this now, as a Draenei Death Knight, on the Heroic dummy in Ironforge. Im using 7.3% hit, with the additional 1% racial. It was either this, or be slightly under the new theorized cap, so I went with slightly over.

So far, Im at 600 white swings, 300 specials, and 0 misses. Ill update again at 1000 white swings, which should be enough to have atleast one miss, if the cap hasnt changed.

The white hit cap for a TG should be 19% (DW malus) + 5% base miss + 5% TG miss + 3% each lvl above + 1% boss -
so 33% overall or 32% when the cap has changed.

But keep in mind that every point of hit beyond 14% (or 13%) is kind of wasted.

Yesterday I did some testing on the heroic dummy, here are my results:



No hit on gear and currently specced as resto.

Titan's Grip - Spell - World of Warcraft

Correct me if I'm wrong, but according to that tooltip it doesn't affect white hits, only abilites (special attacks)...

Call me a doubter on this notion but running 10.09% as a TG warrior on monday I was seeing misses. If the 8% was correct then I should never see a miss as 8%(proposed base miss %) + 5% = 13% which I have with 10.09% + 3% from talents = 13.09%.

WWS I'm basing this off...
Wow Web Stats

I don't doubt your numbers, I'm just wondering if this is a real change, how exactly Blizzard implements Titan's Grip miss rate. It's not necessarily the case that they coded in (making up variable names, whee) "TG_Special_Miss_Rate = Melee_Miss_Rate + 5", and changing Melee_Miss_Rate automatically updates TG_Special_Miss_Rate. If melee miss rate was hard coded at 9%, and TG special miss rate was hard coded at 14%, reducing the value of the former wouldn't have any effect on the latter if they overlooked it when making the change.

While interesting, this doesn't affect raiding Enhance shaman very much because even after the yellow cap, +hit is still the best stat until the spell hit cap.

With 0 hit and normal Ret raiding spec, with max weapon skill and 0 hit rating after 2000 attacks I had a 6.5% miss rate.

Since other classes are seeing ghost hit like Shadow Priests, the only way I can make sense is the hit cap is lower and/or hidden hit is being banked into talents.


My wild ass guess for Ret Pallies is the hit cap for 2H melee is 8% and 1.5% hit is being banked in some Ret aura talent.

I know that there are few tests w/ hunters w/ no gear or no talents, and they all seem to agree on 8% hit, for both the hunter and the pet.
Is there any data with naked, no talent pallies, or any other classes?
There seems to be valid point about some hit baked into talents, if pallies are really seeing different miss rate depending on a person or spec. Seeing actual numbers would be great, or just link to other posts (so far I've only seen druid and hunter ones).

As for TG, how does it compared to say when you don't have TG.
Do warriors still get 9% hit cap without TG, or is TG hard coded as 14% miss on yellow attacks?

Whether it is intended or not is unclear, and we probably won't know until next minor content patch.
I doubt they can hot fix this even if it is unintended.