I tried doing some test tonight after forgetting how to juke and getting dropped by Deadvulcano. GG anyways
My sample sizes are just too small to really conclude anything. Speced Arcane and spammed Frostfire bolt, testing the miss is class specific theory. 20.8% miss with 0 hit, but again the sample is small.
I opened a ticket this time instead of a bug report but ran out of room quickly trying to explain everything. But at least I'll get a written response this time.
I can confirm everything is fine outside of a BG. Frost mage (0 hit ratting) with 250 sheep casts on a PvE lvl 20 mob was 17 misses (6.8% miss) I assume that will go to 6 with a larger sample. So it is for sure a BG problem.
Has anyone gone Arcane with 6% hit and notice their sheeps hit just fine?
It's off-spec spells that are glitched. Sheep is arcane.
I tried doing some test tonight after forgetting how to juke and getting dropped by Deadvulcano. GG anyways
My sample sizes are just too small to really conclude anything. Speced Arcane and spammed Frostfire bolt, testing the miss is class specific theory. 20.8% miss with 0 hit, but again the sample is small.
I opened a ticket this time instead of a bug report but ran out of room quickly trying to explain everything. But at least I'll get a written response this time.
I can confirm everything is fine outside of a BG. Frost mage (0 hit ratting) with 250 sheep casts on a PvE lvl 20 mob was 17 misses (6.8% miss) I assume that will go to 6 with a larger sample. So it is for sure a BG problem.
Has anyone gone Arcane with 6% hit and notice their sheeps hit just fine?
It's off-spec spells that are glitched. Sheep is arcane.
It is not off spec spells that are affected but base spells. Spells you have when you do not chose a spec. That means for an arcane/any mage sheep is affected and for a frost/any mage frost nova, but not pet freeze. Paladins for example have the same problem with their "Hammer of Justice" you just don't hear them complaining, because they are still op. It seems like deadvulcano said and my own experience confirms this: All base spells ( Sheep, frost nova, arcane explosion and frostfire bolt) are treated as if we are level 20 and enemy's are level 24. That's why we have about a 20% miss rate. 26% against 24 minus about 6 % from your regular hitcap.
It is not off spec spells that are affected but base spells. Spells you have when you do not chose a spec. That means for an arcane/any mage sheep is affected and for a frost/any mage frost nova, but not pet freeze. Paladins for example have the same problem with their "Hammer of Justice" you just don't hear them complaining, because they are still op. It seems like deadvulcano said and my own experience confirms this: All base spells ( Sheep, frost nova, arcane explosion and frostfire bolt) are treated as if we are level 20 and enemy's are level 24. That's why we have about a 20% miss rate. 26% against 24 minus about 6 % from your regular hitcap.
unhappy with the answer, I click need more helpHowever, with the implementation of our 5.2 battle-ground scaling, only specialization spells always hit while non-specialization spells frequently miss.
Using a character at the bottom of the Battleground bracket as you are, makes the spell hit scaling problem more pronounced. It is more pronounced because a level 20 needs 26% spell hit to hit a level 24 under normal conditions.
so i'm guessing spell hit will be fixed in the next major patch.I did some digging into this for you and it looks like we’ve had a few reports from other players about this same issue. As that's the case, we have our QA team currently looking in to it. What I can do for you is forward your information up to them so that they have more data to go by. It definitely never hurts to have too much info! =)
What happens from here is they will continue to gather information, try to replicate the problem, and then if they can do that, they will get the issue up to our developers to be further worked on and finally fixed.
I know that this is not the quick fix that you were looking for, but every report that we send to the QA team helps them identify the cause, and once that is pinned down, a fix can be coded and put into play. It may take some time, since you can’t rush code repair lest you trigger a whole new chain of unwanted effects, but the goal is to get these repaired as quickly as possible. Getting us this information will help us get this resolved and out of the realm for everyone.
On the other hand, focusing on low lvl pvp issues has never been something bliz has taken very seriously so we might not see any change to this issue for a very long time.