Skip to Content
9-10-2009 @ 8:08PM
Sadly, the truth of it is that Blizzard does rush patches. Let's take 3.1 for example. It was on the PTR, people were testing it. Bugs being reported, things getting fixed. All seemed well, right? Then 3.1 launches. What happens? A month of hotfixes and patches.Why? I postulate that it's because the patch was rushed. Blizzard had set a firm release date, didn't announce it of course, and then delivered the patch at that date whether it was ready or not.I would not square fault entirely upon Blizz's shoulders, though. 3.1 simply wasn't properly tested. That's a fault of the player base not using the PTR for intended purposes. Players on the PTR, at large, do not care about ensuring that the final product is ready, they just want all the practice they can get on the new content so they have an edge up on the competition. Of course, the quality of the testing environment could be largely improved as well.There are many more ways that Blizz's patch deployment can be improved, ways more important than announcing some mundane target release date, beyond issues with any given PTR.I invite everyone to vote this comment down for bashing Blizzard, being QQ, etc, etc. You know you want to.
First time? A confirmation email will be sent to you after submitting.
Members enter your username and password.
Enter your AOL or AIM screenname and password.
Please keep your comments relevant to this blog entry. Email addresses are never displayed, but they are required to confirm your comments.
When you enter your name and email address, you'll be sent a link to confirm your comment, and a password. To leave another comment, just use that password.
To create a live link, simply type the URL (including http://) or email address and we will make it a live link for you. You can put up to 3 URLs in your comments. Line breaks and paragraphs are automatically converted — no need to use <p> or <br /> tags.