I know that's your point Borr. And as always I'll grin and bear it and thank my lucky stars I made the right decisions which Turbine has not yet invalidated or weakened.
Yeah, I'm not in the "Just Get Rid of it Crowd". But, I am in favor of dropping it until the Grazing Hit flinch mechanic is removed. Because it adds nothing to the game currently, other then to cost us slightly more resources, or a lot of resources for those that had created builds that are specifically hit by this.
They certainly didn't lower Mob to-hit like they said would be the next step. I know, I know, they'll get to it soon(tm). But how much do you want to bet they'll work on the other part of their "plan" first, and raise Mob AC so that we finally start getting Grazing Hits on Mobs on decent warrior builds too and need to actually wait on out later attacks to guarantee a hit and can't jump all over the place using their own bodies against them like I usually do.
The high AC MOB will force me to "stand and deliver" if I only get Grazing Hits on te first or even second attack. That part I don't mind, bring them on. I'm not a gambling man, but I'm willing to bet that Turbine will raise Mob AC long before they lower MOB to-hit, like they said they would.
Certainly I'm not frothing at the mouth about it. But I have a question.
In Beta we all noticed two glaring mistakes right away.
One: Rogue's were getting Sneak Attack damage on Grazing Hits.
Two: We were flinching and being interrupted on Grazing Hits that did little to NO DAMAGE.
Well, I'm pretty sure Grazing Hits still cause interruptions and flinches.
How about the Rogue bug with Grazing Hits?
I'm pretty willing to bet that they fixed THAT rather quickly.
But the interruptions were too low a priority I'm sure.
They could at least acknowledge that it's a known issue or just say that's intended. Sure, I'll grumble, but I'd at least appreciate some word on this.
So, of course they aren't going to change this system. But I certainly ain't gonna give them any Kudos for it. Quite the opposite. I think whoever did the actual programming did a rather p1ss-poor job of it.