Author
|
Topic: Problems with the New MTGO Beta Client
|
daner Member
|
posted July 16, 2014 03:37 PM
So before I set off to work I tried to log into my account. Ive used the beta before, and I use modo regularly....anyway, when trying to log on it said that my account no longer exists and that I needed to make a new account. Anyone else get this message/tried logging in? Id seriously hope my account didnt get axed...well, actually, I kinda do....bc there will be a massive lawsuit inbound.
|
oneofchaos Member
|
posted July 16, 2014 03:43 PM
quote: Originally posted by daner: So before I set off to work I tried to log into my account. Ive used the beta before, and I use modo regularly....anyway, when trying to log on it said that my account no longer exists and that I needed to make a new account. Anyone else get this message/tried logging in? Id seriously hope my account didnt get axed...well, actually, I kinda do....bc there will be a massive lawsuit inbound.
I wish WOTC would care more about modo and make it not a joke. If that means hire legit programmers, hire legit programmers.
|
caquaa Member
|
posted July 16, 2014 11:21 PM
likely user error. There are issues, but accounts haven't changed.
|
James_Hetfield2 Member
|
posted July 17, 2014 10:10 AM
Probably want to re-install the latest "new" client.My account still works fine. I'm getting use to the new client, though still not a fan. I'm a GUI programmer, hire me wizards!
|
daner Member
|
posted July 17, 2014 10:59 AM
Hours later I tried again....and I logged in. So it must have just been a bug.
|
dfitzg88 Member
|
posted July 17, 2014 11:09 AM
quote: Originally posted by daner: So before I set off to work I tried to log into my account. Ive used the beta before, and I use modo regularly....anyway, when trying to log on it said that my account no longer exists and that I needed to make a new account. Anyone else get this message/tried logging in? Id seriously hope my account didnt get axed...well, actually, I kinda do....bc there will be a massive lawsuit inbound.
your timing lines up too closely with the scheduled downtime on 7/16. It was probably a result of that.
| |