Oh bravo on this change, totally worth your time screwing the players who hate daze ![:clap:](https://d38bqls1q93fod.cloudfront.net/en/wow/images/emoji/twitter/clap.png?v=6" ":clap:")
1 Like
I would wait and see if it were unintended,Just like all the other unintended features they slipped into with out notice.
They are acting like a beta bug is mission critical and demanding immediate feedback on when a BETA bug is going to be fixed. Judging by these posts and the other topics made by him I would not expect a rational conversation.
How about telling them to leave the Water Striders alone while we’re at it? a “free” equipment doesn’t make up for the wasted time farming the rep for those mounts.
6 Likes
Bet us noticing was what was really not intended. The whole intent of mount equipment is to make mounts worse and to make getting from point A to point B on them harder. I put real money on people pro-mount equipment and pro-strider nerf wishing they had things back how they are now within a year.
7 Likes
FLYING KODO!! It’s all I’d ever use.
Feel free to remain outraged.
Taken at their word… they were probably adding/replacing code that determines if a rider gets dazed/dismounted, and they ‘forgot’ (deliberately or negligently) to account for absorbs.
Which means that the baseline chance of getting dazed/dismounted has almost CERTAINLY gone up.
Mark my words… After 8.2, absorbs / tank-spec / barding / no-daze equip are going to be more essential than ever. At every level and everywhere in the game.
4 Likes
WarcraftDevs Retweeted Wowhead
This change was not intended. We’re investigating the issue and plan to fix it in the Rise of Azshara PTR as soon as possible.
End Tweet.
It this is the case then fine. But I just don’t believe these guys anymore.
2 Likes
This, lets all abandon this retail trash until Blizzard decides to imporve their design philosophy to fix all these inconsistencies and design problems on their end.
I would rather take the bugs and no flying in classic, but gain good game design over this trash rng loot piniata that is BFA. Sick of your bullshiyte Blizzard.
Can someone tell me who in the world is doing this? It seems like there a guy with nothing to do and afraid to be fired. So he keeps coming up with stuff to keep a job. Mount, daze and what next no jumping allowed. Just move him to somewhere else in the game. He really not helping.
Btw: a shield is doing it job if stopping something. You are breaking so many laws of physic it not funny anymore. A flying mount born into the region cannot fly? What? Kind of thing.
Mate, chill out. It was a bug.
I got a bridge to sell ya.
1 Like
It’s adorable you think they care enough about what people like you think to lie, mate.
I recognize corporate PR spin when I see it. ![:wink:](https://d38bqls1q93fod.cloudfront.net/en/wow/images/emoji/twitter/wink.png?v=6" ":wink:")
And no they don’t care what >I< think. If they notice me at all I’m one of MANY in their “lost cause” bucket, and too much effort for them to bother winning me back.
And it’s not like people didn’t start reporting this problem on the PTR like WEEKS ago. It took it showing up on Wowhead to get Blizzard to finally go “Oh! huh. we’ll look into fixing that”
1 Like
Seeing as how it only started a couple days ago after the most recent update to the ptr, this is false.
Reread until you understand.
“only started a couple of days ago” according to what?
Because it’s been broken for me since I first tried the 8.2 PTR, and I reported the problem back then.
Since no one started reporting it until the most recent build update, which was less than a week ago…?
I noticed and reported it on the PTR nearly 3 weeks ago.
And then again over a week ago on the forums as well.
2 Likes
I can read your post history. You reported it a week ago on the dot. And nothing before that.
This was a totally new discovery in the discords ~4 days ago.
So, again, ?..
cool. thank you