ETA on Mac Issue fix?

#0 - March 23, 2009, 9:10 p.m.
Blizzard Post
I don't want to make a Battle.net account, and I shouldn't have to in order to play a game I pay MONTHLY to play.

So how about you fix this pronto blizzmen. This is ridiculous.
#15 - March 23, 2009, 9:35 p.m.
Blizzard Post
Our database administrators are currently looking into this issue, however we do not yet have an ETA.

Do keep in mind that you will eventually be required to merge your World of Warcraft accounts with a Battle.net account. You can do so now by following the instructions provided here: http://forums.worldofwarcraft.com/thread.html?topicId=15864256387&sid=1

Edit: This issue should now be resolved. See here for more information: http://forums.worldofwarcraft.com/thread.html?topicId=15864259214&sid=1
#23 - March 23, 2009, 9:41 p.m.
Blizzard Post
Q u o t e:


As someone said:

WHY? This makes no sense.

Battle.net accounts provide the frame work for many features to come. The frame work has to precede the functionality.
#30 - March 23, 2009, 9:43 p.m.
Blizzard Post
Q u o t e:
Seems complicated and pointless. we want simplicity blizz.

I have full faith in you to figure out how to make a Battle.net account in about three minutes that will be your single source of operation control for all things Blizzard.
#34 - March 23, 2009, 9:45 p.m.
Blizzard Post
Q u o t e:


An even better question is why we weren't warned that this was coming and had things explained a bit.

Or did I miss some announcement?

Merging your WoW account isn't required right now. Consider the current optional implementation of this feature a warning.
#38 - March 23, 2009, 9:47 p.m.
Blizzard Post
Q u o t e:

Fixed.

That's not true. The current issue affecting Mac users isn't intentional.
#46 - March 23, 2009, 9:50 p.m.
Blizzard Post
Q u o t e:



Question then. Why force us to merge? I am fine with the way it is. I see no current use or benifit from doing this and until you put in some features, its just extra junk to do.


Put in things that are useful, then merge.

More to the point, if this is so needed, why dont Blizz just merge all accounts in to Battle?

The frame work we're creating internally to allow Battle.net accounts access to all of the upcoming features requires that they be the sole source for logging into Blizzard games. Automatically morphing WoW accounts into Battle.net accounts does not work from a technical standpoint.
#49 - March 23, 2009, 9:52 p.m.
Blizzard Post
Q u o t e:

Issue is Blizz didn't mention that merging your account was something you had to have done by this afternoon in order to be able to continue logging in. Once you know about it, yes, it's pretty easy.

We didn't mention it because it's a technical bug. We're working to fix it.
#97 - March 23, 2009, 10:39 p.m.
Blizzard Post
Q u o t e:


And read my edit: without changing the root cause, the next time they b0rk something, there may not be a user workaround, forcing thousands to be left in the wind due to them not simply having a test plan that encompasses all of their user base.

You're talking about this incident. I'm talking about the cause of this incident, and many other incidents past and present.

Quality assurance cannot always reproduce every potential issue that could arise when releasing a new feature, as was the case here, and the reason this login issue did not start until days after the Battle.net Account System was released.

Edit: To quote Tigerclaw from Technical Support:

Q u o t e:
Apologies to everyone affected by the handshaking issue today. Some bits of information to help clarify what went on.

- a server config change was made sometime after noon PST to enable our automatic playerbase survey, which normally takes place during logon. This is normally a routine process and not required to take place during downtime or maintenance. Unfortunately an error occurred in the setup process leading to the behavior experienced on the Mac client.

- it affected my account too which wasn't yet migrated..

- there was no intent or desire to force migration to Battle.net accounts today or even this week.

- it was a bit of a fluke that converting an account to battle.net form did allow some users to get around the server glitch. The reason this worked - as far as I can tell - is because we're not yet doing surveys on the new account system, only on the classic account system. Since the config error had to do with survey activation, it only affected the classic accounts where surveys went live.

- by about 2PM PST this was resolved as far as we can tell and classic accounts should be logging in correctly once again.

Long term we will be migrating all users to the new single account system on battle.net, but that day will be telegraphed well in advance and there will be lots more information available when that comes around. Just wanted to reinforce that today's outage was a simple setup error and did not represent any intent to force a migration before its time.

You can read it here: http://forums.worldofwarcraft.com/thread.html?topicId=15864259214&sid=1
#102 - March 23, 2009, 10:54 p.m.
Blizzard Post
Q u o t e:
And here's the question: will this prevent us from then continuing to transfer our kids' old toons from our accounts to their accounts? Will character transfer be limited to accounts within the same merged bnet account? If so, we'd have to choose right now which toons we'd want to transfer, and take care of it before merging.

If we instead opted to put us all into a single bnet account to avoid the issue, will the new system allow five people to simultaneously log into the same bnet account and play five different WoW accounts? I suppose I should have asked that question first...

You can play separate WoW accounts from the same Battle.net account at the same time. If a child with a WoW account on your Battle.net account wants to login though, your authenticator will be required to do so.

The rules for the paid character transfer system are otherwise unchanged. Account transfers do not require that both the destination and source accounts exist on the same Battle.net account. All current restrictions still apply.

Q u o t e:
What can't I do on my Mac right now? What am I going to have to do at a later date? Will someone tell me when that later date is?

It is better explained here: http://forums.worldofwarcraft.com/thread.html?topicId=15864259214&sid=1

The issue should now be resolved. There shouldn't be anything abnormal you can't do on your Mac. At a later date you will be required to create a Battle.net account and merge your WoW account(s) to it. That date has not been provided, but we will give advanced warning ahead of time. You can read about it here: http://forums.worldofwarcraft.com/thread.html?topicId=15864259214&sid=1