Na server upgrade = Simultaneous Logout Measures

[Freyar]

It is actually more than ten minutes, just not literally. You never know how long duties or whatever you're doing will take, so you have to stop doing whatever you were doing/gonna do way ahead of time, everyday.

So you stop queueing, do something else for 30 minutes, wait the ten minutes, then log back in.

[Kit-Kat]

oh please. if you see the hour warning and decide to jump in a duty thats on you. a dungeon will never take more than 40 minutes (unless complete and utter failures in the group). if you see the 1hr warning you'd just not do EX trials.

Add queues into that. I personally don't have a problem since I got friends to insta queue with, I'm just seeing both sides of this matter. I don't mind taking breaks if that means more people get to play the game, but I also see why people get upset when they get punished for something that has nothing to do with them on different servers.

[Catwho]

This is the only thing that they can do without extensively reprogramming the afk-checker to boot people mid-craft or while checking retainers, which they may also be doing, but would be a client side change and not a server side thing.

On a normal server after a massive world boot, the login queue is reasonable and everyone just shrugs and treats it like another 90002. We're back in within ten minutes.

[Kyouki]

You do realize that this is data center wide, yes? What happens to the lobby server if all these booted ppl try to log on at the same time?

What happens if you just waited an hour in your queue? You finally log on, just to get booted and you end up in another queue?

Think about this...

[RukiaFae]

Add queues into that. I personally don't have a problem since I got friends to insta queue with, I'm just seeing both sides of this matter. I don't mind taking breaks if that means more people get to play the game, but I also see why people get upset when they get punished for something that has nothing to do with them on different servers.

This is true. I was just thinking about that. I hope that don't do it the evenings. I would never play a dps. I only have two good hours to play. If you get the notice there is no point in trying to queue for a dugeon that night as dps because by the time you get into the dungeon the game will kick and if you wait until after the kick to queue it will be time to get off.

[HakaseNyan]

The anti-AFK logout has an extremely weak implementation. You can do a whole lot of things to prevent being logged out. Once you hit the AFK timer, the client tries to initiate the logout timer - as if you were out in the field away from an aetheryte. I'm not sure why they took this route. A more appropriate measure would be forcing a logout the moment the AFK timer is triggered, and exclude only if the player is in a duty-queue. I cannot think of any other instances where a player's client would be idle for 30 minutes straight.

[AziraSyuren]

wat

This is such a heavy-handed and excessive solution that it's almost hilarious.

I hope this doesn't happen during prime time. I'd be fine with it if it happened during 12 PM (EST) or whatever, but if you get booted "randomly" at 4 PM, that's just... awful.

[Kyouki]

wat

This is such a heavy-handed and excessive solution that it's almost hilarious.

I hope this doesn't happen during prime time. I'd be fine with it if it happened during 12 PM (EST) or whatever, but if you get booted "randomly" at 4 PM, that's just... awful.

Ehm... There is not only NA prime... there is also EU prime... 4pm EST would hit EU prime. 12am EST would be "ok" for EST and GMT... But then it would hit PST... There is no way that everybody will be ok with this. They are going to punish ppl for something that isn't their fault.

[Celef]

oh please. if you see the hour warning and decide to jump in a duty thats on you. a dungeon will never take more than 40 minutes (unless complete and utter failures in the group). if you see the 1hr warning you'd just not do EX trials.

Sure but as a DPS you are screwed to join the duty.

Plus, with all the players trying to log in we'll probably kill the login server....

[Vallamaria]

I'm sure you're an expert on server infrastructure and maintenance and can explain to us exactly how the new server location is the cause of the measures in question, not shitty player exploitation to remain clogging the queue even while AFK.

Pretty sure that the point they were trying to get at is that one would assume there wouldn't be such big problems happening when the servers supposedly received n upgrade. Doubly so given the launch of Heavensward wasn't anywhere near as bad as things are right now with Stormblood. Even though back then it was still on the older data center. So one would be inclined to naturally assume that the upgraded servers should be more up to the task of handling the increased server loads in the new expansion.