I thought I would write a few thoughts on my experiences this lovely October patch day because my realm is not up yet and I am bored. I guess my first thought is on the admission by Blizzard that there are some balance issues with some talents and those were excluded from this patch, unlikely to return until closer to, or the day of Wrath's release. I am disappointed by this. That means that either a) they are pushing an unfinished patch or b) they intentionally held back this information until well into the patching process, knowing the fans would be furious. The first denotes a significant amount of proof that things have changed at Blizzard since the merger, and the second shows a great lack of respect for their customers.
My day, odd as it was, started at about 5 am my time, which is to say Central. I had taken a nap, and slept longer than planned, missing the entirety of the few hours before the realms went down. I went ahead with my plan and blew away my install of WoW after backing up a few of my favorite folders, and began the process of installing the client from scratch, since my client felt really sluggish of late. I went through the entire patching system all the way up to 3.0.2, and, knowing the beta realms were down, I decided to launch my beta client since I had word through Twitter that those were still up. I got about as far as 2 or 3 seconds after click and I got an error message saying there was an error in one of my beta files. I have since narrowed this down to the Wrath beta looking for files that are not there.
The likely culprit is that during the install of 3.0.2, the patch asks if it can move my install to Public folders, cause Vista's User Access Controls or some such don't like it in the Program Files. I think this is bogus, but I did it anyway. Now, though, there was a problem. I run over and begin downloading the beta client again, and load up the beta and live forums to look for an answer. 503 Service Unavailable. Uggh. So I go out for a bit while my client downloads, and come back to the beta installer saying it cannot install since I already run a WoW.exe that is in the 3.0.2 generation. /facepalm. The servers are slowly coming back up now, and I am dreading seeing what patch changes didn't make it, and worried what we will all come to see, some day, that this is not the Blizzard we are looking for.
My day, odd as it was, started at about 5 am my time, which is to say Central. I had taken a nap, and slept longer than planned, missing the entirety of the few hours before the realms went down. I went ahead with my plan and blew away my install of WoW after backing up a few of my favorite folders, and began the process of installing the client from scratch, since my client felt really sluggish of late. I went through the entire patching system all the way up to 3.0.2, and, knowing the beta realms were down, I decided to launch my beta client since I had word through Twitter that those were still up. I got about as far as 2 or 3 seconds after click and I got an error message saying there was an error in one of my beta files. I have since narrowed this down to the Wrath beta looking for files that are not there.
The likely culprit is that during the install of 3.0.2, the patch asks if it can move my install to Public folders, cause Vista's User Access Controls or some such don't like it in the Program Files. I think this is bogus, but I did it anyway. Now, though, there was a problem. I run over and begin downloading the beta client again, and load up the beta and live forums to look for an answer. 503 Service Unavailable. Uggh. So I go out for a bit while my client downloads, and come back to the beta installer saying it cannot install since I already run a WoW.exe that is in the 3.0.2 generation. /facepalm. The servers are slowly coming back up now, and I am dreading seeing what patch changes didn't make it, and worried what we will all come to see, some day, that this is not the Blizzard we are looking for.
Reference Links
Leave a comment