
(08-18-2013, 07:04 AM)Nierfenhimer Wrote:I'm out of stuff to do, too.. I just finished Baccano! and already dreamed up a fanfic with my imagination for it, and I've got nothin'. This really feels like a reversed Sword Art Online (Season 1) plot.(08-18-2013, 06:36 AM)Kokobiri Tetebiri Wrote:Agreed. It would at least give people more play/test time (because, goddess knows, some of us actually are being good little testers, too X-D) while they work out the issue. Granted, it would probably resurface with quite a few people, but still, it'd be FAR less widespread than this. >_<(08-18-2013, 06:33 AM)Nierfenhimer Wrote:(08-18-2013, 06:28 AM)Kokobiri Tetebiri Wrote: In retrospect, I see three ways they could prevent this from happening again.
1. Add an AFK Timer (Which is needed in probably every MMO) before getting disconnected (WHICH WAS IN PHASE 3 BEFORE).
2. Restart the servers (duh).
3. Allow people to log in to characters that are still in the system by writing a new script or something. They're Square Enix, they should be able to develop something like that.
As for 1 and 3, that's actually news to me. I've never played a game that doesn't pester you after about 15 minutes of AFK'ing that it's gonna boot you. Likewise, the inability to log into a character already in-game is kind of silly. Just re-establish the connection to the character. No reason to force the player to wait to logout, just to log back into the same character.
As for 2... it does seem the most lucrative solution... especially since they supposedly conducted some manner of maintenance, which typically requires a restart to facilitate.
Just a lot of weirdness with this. Hopefully between now and this coming weekend (even more hopefully sooner).
I suppose 2 is a more instant and vulgar solution. But the option still stands. I would have done it in a management point of view the day it happened.