Absorbs to No Longer Prevent Daze (EDIT: APPARENTLY A BUG)

[Jops-zuljin]

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, ?..

I was talking about it at least 15 days ago, maybe more.

https://us.forums.blizzard.com/en/wow/t/water-strider-discussion/148759/5039

What are the odds that blizzard would accidentally create two bugs that do exactly the same thing a few weeks apart? Do you think they’re really that incompetent?

I still think it was intentional, until they changed their mind.

[Morgueart-kul-tiras (Morgueart)]

The only fix is just to revert it back to normal.

So your saying it was intentional? That this was an unintended change as a result of other changes and the fix is a simple as flipping a switch on and off.

I have some Arizona beachfront property you’d just love, and it’s cheap.

By the way is it fixed yet? hahaa

[Tatertot-darkspear (Tatertot)]

Do you think they’re really that incompetent?

Well…hmmmm…they…sorta…oh hell…

[Gladewiing-aggramar (Gladewiing)]

How is that saying intentional? Or me saying it would be an easy fix? You are assuming a lot of things from just one sentence. I think its an unintended bug from the mount equipment. They now have to figure out which partvfo the new system caused the bug and then fix it. Assuming that this was the cause of the bug and not something else.

[Morgueart-kul-tiras (Morgueart)]

How is that saying intentional? Or me saying it would be an easy fix?

The only fix is just to revert it back to normal.

You made it sound like blizz deserves a pass on this and that all they have to do is change it back. Now you are saying it was maybe this maybe that, I’m just glad blizzard got busted again trying to pass poorly designed systems off, you know kinda like legion’s scaling fiasco where Ion admits they tried to hide it.

[Eret-hyjal (Eret)]

That has… Daze… And no barding. Lol

I’m just glad blizzard got busted again trying to pass poorly designed systems off

you mean in a test environment where stuff breaks all the time? I suggest you loosen that tin foil hat a bit

[Kaiburner-nagrand]

@Drezwazluz-aegwynn

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, ?..

I guess you aren’t so good at reading Jops’ post history after all.

(7 days ago, GD)

Water Strider Discussion

Then get informed: Mount Equip buff lamely breaks on even slight falling damage. Water Strider’s does not. MANY mounts (between a third and half) are unable to go from swimming to water walking 8.2 will daze & dismount more players than ever in both the new AND the OLD zones There. Now you know that “nothing’s changed” is false.

(7 days ago, GD)

Water Strider Water Walking Passive - Removed

Except forgetting will be hard. Mount equipment water walking is seriously interior to the water striders… And daze/dismount problems are being ramped up to force many of us to switch to no-daze.

(8 days ago, GD)

Water Strider Water Walking Passive - Removed

Great! So you’ve been using water walking potions instead of the mount you hate, right? Because unless you’re always in TANK spec, that’s how it’s gonna be for you from now on if you don’t want to be dazed & dismounted every few feet.

(8 days ago, GD)

Water Strider Discussion

Correction: Blizzard HAS ALREADY MADE anti-daze AND safe-fall necessary in the new zones being tested on the PTR. AND they’ve disabled the no-daze/dismount protection offered by other abilities (like Warlock’s [Demon Skin] talent), not just in the new zone, but in old zones on the PTR as well.

(9 days ago, GD)

Water Strider Discussion

If you hate them that much, why aren’t you using water walking potions? In fact, you should start getting used to them now, because after 8.2 drops, you’re gonna need them. Why? Because you’re gonna get dismounted so hard so often that you’ll give up water walking mount equipment as fast as possible, and replace it with no-daze. So instead of ALL your mounts having water walking, or SOME. You’ll have NONE.

(10 days ago, GD)

Water Strider Water Walking Passive - Removed

The only way one can “act like nothing changed” is if the changes that Blizzard is making with 8.2 are LIMITED to Najzatar/Mechagon and you never go there. If you spend any serious time in the new zones and/or if the changes coming with the new zones affect older zones… you will be dismounted so much more often that NO-DAZE will be practically mandatory until we unlock flying. And afterwards, SAFE-FALL will be needed because we’re going to get dismounted while flying a lot more often too. Wa…

(10 days ago, GD)

Clarity please on Water Strider

They’re converting “Lifetime free” to “Next One is free”. It’s a rip off. And, as has been pointed out… if you’re doing the new zones, you will almost absolutely positively need either NO-DAZE or SAFE-FALL because of how they’ve changed things. So in a nutshell, no one doing ‘current’ outdoor pve content will have water walking equipment slotted. “One free” means nothing if it’s useless. We ‘gain’ the freedom to choose how we deal with a brand new impediment. We ‘lose’ the ability to …

(13 days ago, PTR)
https://us.forums.blizzard.com/en/wow/t/water-walking-equipment-doesnt-work/156463/78
(14 days ago, PTR)
https://us.forums.blizzard.com/en/wow/t/water-walking-equipment-doesnt-work/156463/71
(14 days ago, PTR)
https://us.forums.blizzard.com/en/wow/t/water-walking-equipment-doesnt-work/156463/67

[Gladewiing-aggramar (Gladewiing)]

Because all they have to do is change it back. Simple does not always equal easy. Why does everything have to be a conspiracy about Blizzard being shady? Why aren’t the blizz devs allowed to make mistakes? They are human too you know. Lets get honest for a moment, does it really matter if the change was intentional or not? If it was and they decided to call it a mistake because of the player outrage does it really matter, its getting changed back. Unless you played on the PTR it didn’t even affect you at all.

[Jops-zuljin]

LOL! Thanks Kaiburner! I feel like I’m walking through a hall of mirrors… is there an echo echo echo in here here here ?

I can read your post history. You reported it a week ago on the dot. And nothing before that.

AND ALSO fwiw… this post you’re referring to?
https://us.forums.blizzard.com/en/wow/t/warlocks-demon-skin-nerfed-in-8-2/172491

was listed as “8d” old when I linked it… so I dunno what planet you’re on, but we have 7 day weeks on this one.

[Jops-zuljin]

Why aren’t the blizz devs allowed to make mistakes?

Mistakes in software development are SO common that professional programmers and companies that depend on them come up with complicated policies and practices to catch “code changes” that don’t match “change requests” before users see them.

It’s far more likely that this ‘problem’ was the result of a badly considered or badly worded CHANGE REQUEST than it was a programmer bug that just escaped 1 or more levels of testing and review before landing on the PTR.

does it really matter if the change was intentional or not?

Schrödinger’s Code Change… is the cat in the box deliberate or not. Won’t know until we can open the box. And we can’t. So it doesn’t. /snirk

If it was and they decided to call it a mistake because of the player outrage does it really matter, its getting changed back.

Yes it matters. Because badly considered changes that end up getting rolled back due to mass outrage reflect badly on the company, it erodes loyalty, it shakes off subscriptions and trains us to flip our lids every time we see anything we don’t like … in the hopes that it’s another “whoops, thought we could get away with that” stoppable change.

Whomever is making the design decisions for WoW needs to retire and hand the reigns over to someone whose vision for the game is better than: “hey let’s break and re-set some of these ugly old mended bones from way back, and not give the patient sufficient pain killer while we do it.”

[Gladewiing-aggramar (Gladewiing)]

It’s far more likely that this ‘problem’ was the result of a badly considered or badly worded CHANGE REQUEST than it was a programmer bug that just escaped 1 or more levels of testing and review before landing on the PTR.

You know this for a fact do you? You don’t though you are just assuming it. According to Occam’s Razor (spelling?) though it was indeed a bug.

Yes it matters. Because badly considered changes that end up getting rolled back due to mass outrage reflect badly on the company, it erodes loyalty, it shakes off subscriptions and trains us to flip our lids every time we see anything we don’t like … in the hopes that it’s another “whoops, thought we could get away with that” stoppable change.

I don’t think that matters anyway when you have a playerbase like this one. I have been silently reading the forums since late Cata and there is always someone who jumps on Blizzard’s case for every change. Every. Single. Time. I’m not saying Blizzard is perfect they have made plenty of mistakes over the years. I wish pathfinder didn’t take so long. I just don’t think this is that big of a deal.

[Jops-zuljin]

You know this for a fact do you? You don’t though you are just assuming it. According to Occam’s Razor (spelling?) though it was indeed a bug.

For a ‘bug’ to get deployed to PTR multiple people have to screw up. PTR isn’t an ‘alpha build’.

For a bad design decision to get deployed to the PTR, it only requires one person to screw up.

Which assumes more?

[Gladewiing-aggramar (Gladewiing)]

For a ‘bug’ to get deployed to PTR multiple people have to screw up.

For a bad design decision to get deployed to the PTR, it only requires one person to screw up.

Which assumes more?

The first one because that is exactly what Blizzard themselves stated. You are assuming they are lying and being shady. I think you underestimate how hard it can be to find bugs with only a few dozen people or so, compared to thousands if not hundreds of thousands playing the PTR.

[Kaimasutra-amanthul]

LOL! Thanks Kaiburner! I feel like I’m walking through a hall of mirrors… is there an echo echo echo in here here here ?

I asked Kasim and co, and none of us can work out what could have given you that impression.

Don’t you find it annoying when the forums randomly swap you to a different character, or when you have to swap because the character you’re on has run out of likes to give your favourite posters?

[Jops-zuljin]

The first one because that is exactly what Blizzard themselves stated. You are assuming they are lying and being shady. I think you underestimate how hard it can be to find bugs with only a few dozen people or so, compared to thousands if not hundreds of thousands playing the PTR.

I’ve spent years working in software development, I know that things can slip through. But seriously, if the software engineer went this far off spec and the original intent was to respect absorbs? They needs disciplinary action for failing to adequately test side conditions for his/her own code.

And Kaivax only tells us what he’s told. Probably doesn’t even know if “not working as intended” meant “not working as ORIGINALLY intended” or “not working as intended NOW that we’ve changed our minds because of backlash”

And I honestly don’t care. I’m glad they recognize that it’s wildly unpopular and they’re changing it, whatever their original intent was.

[Gladewiing-aggramar (Gladewiing)]

And I honestly don’t care. I’m glad they recognize that it’s wildly unpopular and they’re changing it, whatever their original intent was.

That’s all I really wanted, because it honestly doesn’t matter because it’s getting changed back. Not like anyone can prove it wasn’t an unintentional bug anyway.

[Drezwazluz-aegwynn (Drezwazluz)]

I guess you aren’t so good at reading Jops’ post history after all.

The first one of these to even specifically imply a change was 8 days ago, today. The others are complaining about the mount equipment.

was listed as “8d” old when I linked it… so I dunno what planet you’re on, but we have 7 day weeks on this one.

Because at the time I posted that, it was not 8 days…?

What are the odds that blizzard would accidentally create two bugs that do exactly the same thing a few weeks apart? Do you think they’re really that incompetent?

See now I’m just questioning you. Because this was not reported in Black Harvest until, again, the most recent ptr build, 4 days (now 5) ago. Before that, it was never mentioned.

[Jops-zuljin]

Because at the time I posted that, it was not 8 days…?

Probably because it was after midnight in my timezone when I posted, and before midnight in yours when you read my post. Whatever.

The first one of these to even specifically imply a change was 8 days ago, today. The others are complaining about the mount equipment.

19 days ago I posted
https://us.forums.blizzard.com/en/wow/t/water-strider-discussion/148759/4726:

Even with my innate no-daze protection with Warlock [Demon Skin] … I’m getting dismounted -WAAAAY- more often than ever before.

Demon Skin isn’t functionally different than other absorbs, so while I didn’t test “Resounding Protection” or “Prydaz”, it’s very likely they all were broken in the same PTR patch.

So regardless of whether anyone reported it to the black harvest discord or not… the problem has been around for nearly 3 weeks. I saw it. I reported it on the PTR at least twice. I talked about it on the forums.

This isn’t something that’s been around for “less than a week”.

[Nyaria-argent-dawn (Nyariá)]

People are way overthinking this…

Conspiracy theory’s galore.

[Morgueart-kul-tiras (Morgueart)]

Why does everything have to be a conspiracy about Blizzard being shady?

Because the modern wow team is shady, there are so many issues that Ion has outright lied about let alone the half truths and lawyerspeak to hide the true meaning of what is being said.

If it was and they decided to call it a mistake because of the player outrage does it really matter

Sure does matter. Do i want to do business with the guy who lies and has to be caught lying or do I want to do business with an etical truth teller?

Unless you played on the PTR it didn’t even affect you at all.

We as a playerbase are making a preemptive strike because issues like scaling in legion where openly admitted to that they used deceit by not telling the playerbase whats up.

This time we have our eyes open and there will be no prepurchase records set next xpac. Very few will prepurchase after how hard we have been taken advantage of since wod.

If your strategy is to try and make money on a crap product by hiding what it really is , good luck in your long term success.