just also fix the bug of no lucky hit from bladedancer
Bug or not they should have disclosed they intended to “fix” it in the patch notes. Now poison rogues are sitting with an awful build mid season just after the devs promised on last campfire not to introduce game breaking changes mid season and better communication with the community blah blah blah
They did promise to never introduce changes that would break builds during the season again. They have flat out lied to the community. They lost all the credibility that existed with me. Even with a heads up, we could have maybe come to some kind of resolution evolving into another build. But to drop this without notification is nothing short of betrayal to their paying customers. Makes my Poison Tank build unplayable now.
That’s the part that is pissing a lot of folks off.
They seem to have zero awareness or just don’t give a toss. There was a major uproar the last time they did this to a class mid-season, which triggered an apology and the above statement, yet here we are again…
It’s comically embarrassing.
they fixed a bug for barb before, put it in notes and tried to boldly explain it.
Now they don’t have the ball lol.
Had they actually put in the effort and said in patch 1.1, yeah this is unintended. We are fixing it. Okay cool.
Hell, had they mentioned this 2 weeks ago in the 1.1.1 patchnotes, then people wouldn’t have minded as much. They could still switch around.
We are half-way through and I only found out because suddenly the entire Icy Alchemist aspect has become pointless.
They wanted rogues to play Basic Attacks, so I made a puncture with Pestilent Point and ice alchemist for AOE/CC. Which was satisfying, as the rapid explosions from the procs were nice and meaty sound design (like the explosions from shadow imbuement) and it did damage.
hell, if it was overtuned, I rather them nerf it than this. ALLOW PLAYERS FUN.
If it was a bug, it was a fun bug. Maybe make it a feature… Rework the aspect into something interesting.
This is Twisted Blades all over again.
Exactly this. I didn’t even play poison pre season and decided to give it a try S1. I am level 98 stuck with my best roll aspects on damage over time gears. I also have to redo my Paragon now. I always thought it was only bugged on certain skill. I didn’t know it was bugged on all skills. They should had put that in the patch note so I could had prepared.
Yup, as a casual player who is only level 63 and full poison l, this is crap. I need to farm more gear (when i can find the timr) and play a broken build thats not fun until then.
Ive pretty much given up on this season at this point and probably wont play again till maybe next season
Fixing a bug is not the same as “introducing changes”.
there is a section “bug fixing” in the patch note while there’s nothing mentioned about TB/ BV fixing
Yes, Blizzard has been doing undocumented bug fixes forever. Or, possibly, the bug was fixed without them explicitly trying because they fixed other bugs. I’m kind of leaning towards that because it looks like when they fixed the taunt bug for pvp they broke thew malignant heart trap taunt. That made for a fun half hour or so until I found a new gem to replace mine.
It 100% is if the build is only playable because of the “bug”.
The build is absolutely playable. And despite what people think fixing a bug is not the same as making an intended change to break builds.
Imbuements have like 3% up time. They are crazy levels of useless typically. Poison imbuement, although it did relatively low damage due to speed, allowing it to be used every pack to apply poison for things like “damage reduced by poisoned enemies” actually allowed rogues to somewhat survive in melee. Without that, well…
Just cuz you think “herp derp slightly less damage, it’s fine” doesn’t mean that is the reality of the situation.
video game dev is the only aspect of software development where it’s totally accepted by a huge number of users that there are bugs.
imagine this happening on paypal or venmo. people will go nuts.
Same problem here… It’s broken now… One more aspect “fixed” and thrown in the trash…
If it didn’t work as intended, now it doesn’t work at all…
You could argue that was FTX as well…I suppose people did go nuts there in the end.
This was the same conclusion I came to yesterday. While I do appreciate them trying to address things in a rapid manner it does seem to result in unintended consequences, whether it be fixing or breaking things, for good or ill. This may also be a result of rushed development and lack of resources to run QA on changes that are pushed out.
Bigger company also means greater disconnections and less efficient communications. Its just what it is.