Comment by Geige
on 2021-03-17T20:43:42-05:00
Wonder how all of these abilities got broken for invis pots all of a sudden
Comment by Zygos
on 2021-03-17T20:45:32-05:00
Wonder how all of these abilities got broken for invis pots all of a sudden
It could have been something as dumb as “fixing” the BE males face that caused it.
Comment by Segano
on 2021-03-17T20:48:46-05:00
This is the 3rd day in a row with invis pots fixes. So weird.
Comment by Avalith
on 2021-03-17T21:02:46-05:00
Removed
Comment by Novackl
on 2021-03-17T21:03:25-05:00
<3 perculia <3
Comment by Jerhomie
on 2021-03-17T21:07:34-05:00
The Mole Machine for the Warlords of Draenor Alliance quest “Mole Machine, Go Home” will now allow smaller races to interact with it.
I hope it’s not just smaller races, I submitted a bug report a few days ago on my Kul Tiran shaman.
Comment by deathlavitz
on 2021-03-17T21:12:31-05:00
Wonder how all of these abilities got broken for invis pots all of a sudden
15+ years of code on a single game engine can cause some very undesired effects.
Comment by Donawen
on 2021-03-17T21:25:59-05:00
But no comment/hotfix on Sacred Covenant being bugged for those swapping to Venthyr making it literally impossible to get Soulbinds. Super cool.
Comment by the9tail
on 2021-03-17T21:37:02-05:00
The Mole Machine for the Warlords of Draenor Alliance quest “Mole Machine, Go Home” will now allow smaller races to interact with it.
I hope it’s not just smaller races, I submitted a bug report a few days ago on my Kul Tiran shaman.
Smol is relative
Comment by Transfat
on 2021-03-17T23:55:20-05:00
Wonder how all of these abilities got broken for invis pots all of a sudden
I would venture a guess that the initial bug report that was causing something to break invis made them realize that whatever the error in logic was could cause other things to break invisibility as well so now they are finding alot of other things from that initial bug report.
Comment by mtmf
on 2021-03-18T00:13:00-05:00
The thing is, the problem wasn’t there before. They changed something in this patch that created the problem and now, instead of searching for the core issue and fixing it, they are putting a band-aid on each spell and hoping we won’t find new ones that cause the same issue.
That’s such a terrible development practice. If they don’t work to find the real problem this will keep coming back in future patches.
Comment by TOMRUS
on 2021-03-18T00:46:09-05:00
Another day without hunter buffs, sad…
Comment by jkowalke
on 2021-03-18T01:04:00-05:00
Part of me really wants to understand how the game is architected from a code perspective. Then another part of me shudders at what that might look like after 15 years.
Comment by sotaba
on 2021-03-18T01:17:54-05:00
Nice hunter buffs!.. oh wait :X
Comment by Dabraxus
on 2021-03-18T01:40:55-05:00
Part of me really wants to understand how the game is architected from a code perspective. Then another part of me shudders at what that might look like after 15 years.
“Oh, something we did broke invis pots!”
“But we didn’t touch any of the affected abilities tho, didn’t we?”
“No.. mhm”
“Let’s just add some exceptions to each ability we find that causes the invis effect to break!”
“But that’s not good software engineering..”
“But we’re not getting paid enough to invest time on a wild bug hunt for some side-effect… sod off!”
Comment by Psyshadowxx
on 2021-03-18T01:41:38-05:00
Wonder how all of these abilities got broken for invis pots all of a sudden
We’re talking about the same small indie company that broke the game so bad adding 4 extra backpack slots that they had to roll back an entire patch. I wouldn’t go too far down that rabbit hole.
Uh, what…?
Comment by xenolithix
on 2021-03-18T01:57:05-05:00
Part of me really wants to understand how the game is architected from a code perspective. Then another part of me shudders at what that might look like after 15 years.
It’s referred to fairly often by former and current Blizzard staff as essentially being spaghetti code. Which is hardly surprising. Hell, think about it; when they first started working on the game, it was 1999! When they first announced it, even, Windows XP was literally a month old.
Comment by Chungtao
on 2021-03-18T02:28:12-05:00
Wonder how all of these abilities got broken for invis pots all of a sudden
I would assume they tried to fix the cheese that involved using invis pots to evade the Prideful mob.
In case they “fixed” the invisibility spell itself, and not the mob’s behaviour, it caused many abilities and buffs written inside Blizz Spaghetti to misbehave and break everything.
Comment by Torguish
on 2021-03-18T02:44:43-05:00
Wonder how all of these abilities got broken for invis pots all of a sudden
15+ years of code on a single game engine can cause some very undesired effects.
In legion we had a start of a patch where Wake of Ashes on retribution paladin did 0 damage and instead gave you archeology levels. 😀
Comment by NierielNora
on 2021-03-18T02:49:40-05:00
That’s why code needs automated testing. Then you have a state before and after and can check for side effects. While this does not catch all side effects, it avoids fixing the same bugs over and over again.
The biggest issue Blizzard has, is data integrity. Some entry level employer adds a new quest, has a settings dialog with hundreds of unexplained settings, the whole dialog doesn’t check anything for consistency or if it actually makes sense, this whole thing gets shipped as is, and then it blows up. Followed by a hotfix, and a note that always reads like this “make quest work for allied race …” – and then you just know, oh yeah, they forgot to check this for this new race. And it has to be done manually for every race combined with every quest. That’s how this company works. And when the next holiday comes along, they make a hotfix because they “forgot” to adjust the level squish for the holiday quests. Well this battleground brawl bug 2 days ago was exactly that category — for a billion dollar company this just cannot happen.
Sometimes I think the whole company employs 2 developers, that work 24/7. While Blizzard thinks to lay off 50% of the staff. For efficiency. Looking what they have done in the last 3 months for patch 9.0.5 it’s literally nothing. That’s pretty much what you expect from 2 employees over 3 months work. That have to do everything. Under pressure, without the time the fix a problem, just the time to remove the symptoms.
If I had something to say in that company, I would run a team of 10 people and clean this codebase up within 1 year. With full testing capability and everything. Make it “bug free”. And with bug free I mean all -known- bugs removed. For a billion dollar company that’s something they have the money for. Uncontrolled greed is the cancer of modern economy. Just my two cents.
Leave a Reply