#0 - March 23, 2009, 9:10 p.m.
So how about you fix this pronto blizzmen. This is ridiculous.
Q u o t e:
As someone said:
WHY? This makes no sense.
Q u o t e:
Seems complicated and pointless. we want simplicity blizz.
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?
Q u o t e:
Fixed.
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?
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.
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.
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.
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...
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?