Simply because behavior is “expected” doesn’t mean it isn’t a bug.
It might not be a bug, but, given how poorly TBCC is being handled, it is just as likely to be a bug they simply cannot fix.
2 Likes
It is the juxtaposition of “actually correct” with “otherwise expected” that gets me. If we were just reproducing a bug because that’s how it was, ie Classic #nochanges, then “actually correct” would suffice alone. “Otherwise expected” means stuff that may not actually be correct behavior, but falls in line with what the Devs would expect (vision, intent, meta tweaks, etc) for this period of time, and gets blessed anyway.
I can’t say for sure from their list whether the 2.2 change to Ferals was a bug or intended or simply overlooked, but what I can say is that Blizzard chose to lump together warts-n-all with tweaks they expect into the same bucket of “Not-A-Bug” and called it a day. This can be due to laziness, apathy, difficulty in addressing it, whatever, but ultimately it only matters that Blizzard blessed the status quo.
1 Like
Yup.
It doesn’t, however, make me think their pants aren’t on fire
1 Like
Heh, well my position on that is “oh well” since Blizzard gets to do what Blizzard does and can hide behind the EULA all day. Even if I catch Blizzard in an outright lie, pants ablaze, they can still just ignore it and well… I guess catharsis for me for solving it?.. but oh well in the end.
I play to Tank, it is the one thing in this game that I truly enjoy above all other activities, so my tolerance for other nonsense going sideways is pretty high if it doesn’t impact Tanking.
PS - And if I can’t enjoy Tanking in this game, I just quit. That’s the ease of it all. Video games are fun.
1 Like
Yup. I generally don’t care.
It just lets me be judgy.
2 Likes
I laughed way too hard at this.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.