Another embarrassing bug
Lol man you dev guys and gals need to get it together, you do know that the perspective from our side is you guys aren’t up-to par have you guys learned anything from your past failures? From here it ...
Forum Discussion
"Bevel_Lemelisk;c-1899484" wrote:
I think the point of the OP is these are happening way too often. Even the post about the failed GAC said they "hoped" the fix would work but did not test it. "oops". It is that attitude and lack of respect for the product that is frustrating the user base. Whether it is a minor glitch or a major game crash they need to take a look at their processes and figure out what is going wrong. I know there is pressure to push these things out. Especially when the user base screams they want to know what is coming and then as soon as you announce anything they scream when is it coming. I know me personally would rather be yelled at for taking to long then having it not work. For CG lately it seems to be both.
This is the June 10th list of hotfixes for World of Warcraft: https://worldofwarcraft.com/en-us/news/22933417
The words, "fixed a bug" are in that list 33 times, with "resolved an issue" appearing an additional seven.
Bugs happen in continuously supported games. They get resolved. It's how the development cycle works.
The GAC collapse was embarrassing, sure. But this? This is trivia. This is a routine bug. As long as it gets resolved before TB, it affects literally nothing.
