Also, I know there is a lot of controversy saying this, but fixing a bug is not a nerf. It’s making something work as originally intended and all it does it show how flawed the spec is. So instead of asking for the bug to be reimplented, maybe it’s time to look elsewhere in the spec to see where there could be improvements made (this is directed towards Blizzard, of course, even though I know they won’t ever read it).
The patch notes literally say “Serpentstalker’s Trickery no longer triggers Wild Spirits (Night Fae Ability) twice.” Sounds like an unintended mechanic, which sounds a lot like a bug to me.
And I’ve seen a lot of MM hunters asking for it to be reverted. So maybe you aren’t, but there are people asking for it.
The balance this expansion has been so bad it’s funny. Calling 9.0.5 a ‘patch’ is hilarious, considering it should have been done in tuning passes across the weekly resets.
For years, Blizzard has been consistently using language like “Fixed an issue with” or “as intended” or “now correctly applies” etc. to denote a bug fix. That language is conspicuously absent in this case. From that perspective, it does not at all sound like a bug fix. Sounds more like an intentional nerf.
Blizzard never said, or even implied it was a bug. The player base did based on the fix to Animal Companion / Stomp / Wild Spirits interaction.
Really? Which part of that sentence implies it was unintended?
Hmmm, not seeing anything about it being unintended.
Yeah… still not seeing how it was implied to be unintentional.
I mean this is how they word bug fixes
Notice the “Fixed an issue” part? I mean it’s all throughout the patch notes.
Fixed an issue that caused Storm, Earth and Fire’s cast to sometimes break nearby enemies’ Stealth.
Fixed an issue that caused Xuen, the White Tiger to be able to target enemies in Stealth.
Fixed an issue that caused Tiger Palm to grant an additional stack of Mark of the Crane when Storm, Earth and Fire is active.
Fixed an issue that allowed Mark of the Crane to be maintained permanently at maximum stacks while fighting a single target.
Fixed an issue that could prevent Storm, Earth, and Fire spirits from using Fists of Fury, Rising Sun Kick, and Whirling Dragon Punch (Talent).
Fixed an issue that allowed Storm, Earth and Fire spirits to continue channeling Fists of Fury after the Monk’s Fists of Fury channel ended.
Fixed an issue that could cause Spinning Crane Kick’s damage to not be properly increased by Mark of the Crane if targets die with the Monk’s mark active.
Changing how something works doesn’t automatically mean it was a bug or not intentional.
The entire sentence, specifically the middle part.
Even after reading your entire post, I still feel it was a bug fix rather than whatever it is you are trying to make it out to be. Interpretation is everything. Just because they didn’t use the wording that you associate with “bug” or “fixed an issue” doesn’t mean it can’t be interpreted as such. You’re lying to yourself if the wording they used “Serpentstalker’s Trickery no longer triggers Wild Spirits (Night Fae Ability) twice" doesn’t sound like a bug fix or an unintentional way of how interactions work.
If you look in the sentence it literally says “no longer” as in it was doing something before that Blizzard deemed incorrect for the item. If it was intended they wouldn’t have even touched it. Clearly there was an issue with the item causing something to happen twice instead of once. This conclusion leads to a bug fix, fixing something that wasn’t intended.
I’m sorry, but you can do all the arguing you want here, this was a bug clear as day, and Blizzard fixed the bug reverting it back to its original intended design.
Blizzard could have easily worded it as “Fixed an issue causing Serpentstalker’s Trickery to cause Wild Spirits (Night Fae Ability) to trigger twice” and it means the exact same thing.
It’s called a change. Not all changes are bug fixes, otherwise you may as well chalk WoW up as the buggiest game in history because they’ve been changing how things work for more than 16 years now.
Right, but nothing in their own wording suggests that the way SST worked was not originally intended.
lol no. It doesn’t sound like a bug fix. It sounds like they decided to change how SST interacts with WS.
They didn’t say “Fixed an issue that caused the Serpent Sting fired from using Serpentstalkers Trickery to proc Wild Spirits twice.” Because that would sound like a bug fix.
They also didn’t say “Changed the way Serpentstalkers Trickery interacts with Wild Spirits so Wild Spirits is only proced once as intended.”
You talk about interpretation but you really, really, really have to go through some incredible mental gymnastics to get to
sounding like a bug and not just a change. Again, not all changes are bugs.
I mean, it was fixing a bug. The same patch they revamped Serpentstalker’s Trickery during the beta, they also fixed the Stomp double-proc, so it was pretty clearly unintended behavior. They very specifically set out to make it 1 action = 1 proc. We let them know about it repeatedly during the last few months of the beta, but Blizzard being Blizzard, were completely unaware of it.
The issue isn’t so much that they fixed the bug. If it’s unintended behavior, it’s unintended. The issues is that they fixed a major bug we were tuned around, and didn’t compensate with a buff to base damage.
It’s basically the same issue Windwalkers are having, they fixed a bunch of major bugs that were propping up the spec and didn’t compensate on the spec aura, so now the spec is riding the bottom of the rankings with all 3 hunter specs.
ok…ill do this once more only…all ppl need to do is read…it is in english…
Wild Spirits “…While the Wild Spirits are active, each damaging ability you or your pet use against a target in the area…” Serpentstalker’s Trickery "
Aimed Shot also fires a Serpent Sting at the primary target."
SO following the basic logic, each attack is a proc, the legendary states that it ALSO FIRES therefore meaning that its another attack, if that was not the case it would say APPLY ss, so implying that it would proc wild spirit, if that was not enough the patch didnt stated BUG FIX like it was stated with the monk ww…english is not even my 1st language you guys should learn it…
To me, it doesn’t read like a bug fix given the timeline of events and the actual wording used.
Regardless, whether it’s a bug fix or not really has little bearing on the matter. The end result is MM ate a huge nerf, when it was the only one of our three specs doing well at all for PVE. We’re now in a position where we will likely have to wait for 9.1 to release before we see any further changes.
Since 9.1 isn’t yet at the PTR, at the earliest I suspect we see it on the PTR next Tuesday (the 23rd). We could hope maybe for about 4 - 5 weeks of PTR I would guess. So anywhere between 6 or seven weeks total (assuming it goes on PTR next Tuesday) without any fixes to the class while we have all 3 of our specs at or very close to the bottom. Over a month and a half.
And that’s assuming it’s next Tuesday or they buff us. So. Yes, people are upset. No, it really doesn’t matter whether this was meant to be a straight nerf or a bug fix because the end result hurts the entire hunter population regardless.
i mean blizzard has the same tools we have to check the dps…actually they have better tools…so if do this kinda change is either gross stupidity or lack of common sense
Or likely they have their own reasons for wanting it nerfed. Regardless, it doesn’t make a lot of sense one way or the other given the end result is the class as a whole is pretty dumpstered atm.
in any case, the lack of foresight is amazing, and it seems to always struck hunters mercilessly and without fail, im yet to se a mage get nerfed for 4 years