Skip to Content

WoW Insider has the latest on the Mists of Pandaria!
  • bluespacecow
  • Member Since Feb 20th, 2010

Are you bluespacecow? If So, Login Here.

BlogComments
Joystiq1 Comment
WoW65 Comments

Recent Comments:

Beta Testing 101: Addons and the Mists of Pandaria beta {WoW}

Mar 29th 2012 9:13AM Just to reiterate here :

Addon developers need your help in getting their addons ready for MoP.

There have been a ton of Lua API changes already with this latest patch for the beta (the one that just got pushed recently build 15508)

They are going to need your help in diagnosing/trouble shooting their addons.

The work you do will help them get their addons ready for the eventual patch day addon meltdown. You can help make patch day less of a nightmare for everyone.

So once addons get enabled for the beta find out from your favourite authors how they prefer bugs to be submitted. Some will have a ticket database. Help them out for the good of your fellow wow player :D

Pandaren lore and what we know so far {WoW}

Mar 22nd 2012 6:43PM "lets wait and see how long it'll see before a Pandaren joins an traditionally evil organisation" clock."

This just in. Panda enrolls in law school intending to seek employment with the IRS.

News at 11

Patch 4.3.3 will break the current 64-bit WoW client {WoW}

Feb 27th 2012 10:28PM That still wouldn't fix this patching issue.

It breaks because it doesn't expect to find a wow-64.exe and freaks out. Switching to the 32 bit option won't magically fix this as it won't delete wow-64.exe

The support article is only formalizing a known technical issue with the 64 bit client that's existed since the 2nd build come up on the 4.3.3 PTR

Patch 4.3.3 will break the current 64-bit WoW client {WoW}

Feb 27th 2012 12:24PM Adam , Adam , Adam.

You've fallen into the same trap that MMO Champion fall into.

They as well as you are assuming that because the support article doesn't mention any way of updating the 64 bit client that it's evidence of Blizzard dropping the 64 bit client.

This could not be further from the truth.

The support article is regarding a known patching issue with the 64 bit client.

That's it.

If you had a look in the PTR discussion forums you would of seen this sticky :

http://us.battle.net/wow/en/forum/topic/3881708285

Which has currently updated links for 64 bit clients for Mac and PC for the current build on the PTR. 4.3.3 build 15354

The support article is merely formalizing a known issue that effected the 64 bit client on the 4.3.2 PTR

Patch 4.3.3 will break the current 64-bit WoW client {WoW}

Feb 27th 2012 12:16PM It's actually because the update system freaks out when it sees wow-64.exe in the wow folder.

It will throw up an internal error and may cause you launcher to attempt to repair all your data.

Simple fix - put out a launcher update that expects wow-64.exe to be in the wow folder and update around it.

I suspect the reason why they haven't fixed it is not because it's too hard. Rather because they're not sure how they want to do it.

Patch 4.3.3 will break the current 64-bit WoW client {WoW}

Feb 27th 2012 12:13PM Why ?

For every build that's come out on the 4.3.3 PTR there's been a 64 bit client build as well.

This support article means absolutely nothing for the future of the 64 bit client.

If the patch went live right now it wouldn't take Blizzard that long to put up a new 64 bit client. Baring unforeseen circumstances possibly in the area of a few hours.

Patch 4.3.3 will break the current 64-bit WoW client {WoW}

Feb 27th 2012 12:10PM Client's built with the LAA flag turned on by default now.

Has been for a while actually.

Tuesday Morning Post: Extended downtime is back edition {WoW}

Jan 17th 2012 12:05PM It's hard to express tone in the written word.

I guess I should of added this to my post : My questions are more in the spirit of understanding why wow insider got it wrong and what can be done in the future to improve their accuracy.

Again the service status post was updated before wow insider made their post.

Tuesday Morning Post: Extended downtime is back edition {WoW}

Jan 17th 2012 11:04AM It's hard to express tone in the written word.

I guess I should of added this to my post : My questions are more in the spirit of understanding why wow insider got it wrong and what can be done in the future to improve their accuracy.

Again the service status post was updated before wow insider made their post.

Tuesday Morning Post: Extended downtime is back edition {WoW}

Jan 17th 2012 10:30AM http://us.battle.net/wow/en/forum/topic/3881884586

Posted 11.36 PM 16 Jan.

Do you double check the service status forum before posting your post ?

When you post a blog post here does it go immediately up or does it go in a queue ? Does it get checked by someone else ?

And are the times listed for posted listed in Pacific Time , Central Time or Eastern coast time ?