On GOD this should be up there too. Alas. Legit have to make a brand new battle.net account to fix this bug. Which isn't really a fix, is it?Edit: Wowhead, you gotta' change the patch timestamp on the right of comments. It still says 12.0.7.I forgive u tho <3
They don't even test their sht anymore, let alone QA to find fringe bugs, hahaha, what a circus
lol, i'm glad i left this sinking boat months ago. Good luck to you all. Btw CoA is pretty fun
also...
Wow amazing so many testings. Didn’t even play the dungeons.
How about QAing your own patch being a top priority. The whole "Quality patches " hasnt happened a single time yet since that statement. Thanks Holly.
Imagine expecting a major patch to function properly
Bugs in a WoW patch? Say it ain't so!
Not a good sign after the last bugfest patch. How will they apologise this time? :\(maybe ask the Chinese devs if we can have that crab? ;p)
A patch shouldn't release THIS many with bugs immediately.Fire Holly Longdale and get someone in charge who isn't just going to machine gun out vibe coded slop at record speeds.
We are the testers, why waste ressources...
Remember when we used to get an extra days of gameplay aslong there was a big issue, that was pretty cool.
A bug on a Patch launch! Say it isn't so! (:
Microslop Blizz(t)ard Beta-tainment developers of World of Bugcraft: Mid-Development spent lots of time testing Patch 12.1: The Curse of No AI Tokens before deploying to the PTR Stage 2 aka Paid Tester Realm yesterday I see.
