Against "Simultaneous Logout Measures"

[Jijifli]

TEN MINUTES.

I'm leveling an alt on Mateus. I just got to Brayflox. The servers go down in 30 minutes. I am a dps.

I cannot do Brayflox. I cannot continue story.

So for me, an innocent person leveling something NOT on Balmung, it's not 10 minutes.

[alimdia]

I'm leveling an alt on Mateus. I just got to Brayflox. The servers go down in 30 minutes. I am a dps.

I cannot do Brayflox. I cannot continue story.

So for me, an innocent person leveling something NOT on Balmung, it's not 10 minutes.

I do like how posts like this keep getting ignored ^

People don't want to see how others are being affected negatively for way more than 10 mins, and they are gaining nothing from it either if they play in a server without queues.

[Issac]

I do like how posts like this keep getting ignored ^

People don't want to see how others are being affected negatively for way more than 10 mins, and they are gaining nothing from it either if they play in a server without queues.

Agreed. This is also what I keep trying to say. SE, either target your solution more responsibly or find another. This is ludicrous.

[HyperSMB]

Agreed. This is also what I keep trying to say. SE, either target your solution more responsibly or find another. This is ludicrous.

It is because it is a balance thing.

What is more important:

A) Kicking so thousands of people can log in when they get home with minimal delay.

or

B) Leaving it is as because we don't want to inconvience some DPS players.

It's annoying, it's a band-aid, but it is ultimately our fault for abusing an exploit (And by we I mean the community at large). I imagine it will be gone and done with in a few weeks backed by a patch to boot or ban AFK exploiters.

[Ayrie]

Agreed. This is also what I keep trying to say. SE, either target your solution more responsibly or find another. This is ludicrous.

This is why we cannot have nice things. Literally.. why... we can't have nice things.

A code rewrite, contrary to everyone's demands, would take months. Debugging the code to make sure you're not unintentionally breaking loads of other things simply does not happen overnight. And when you're talking about writing code that forcefully disconnects people due to arbitrary metrics like: how long they've been talking to an npc, or if they are trying to craft or not.

I can see half a dozen exploits to get around the proposed code fixes, anyways. Simply get a rapid fire controller and have it mash confirm... oh, look, I am no longer stuck in the same chat dialog for 30 hours, I am not actively chatting over and over with the same NPC. Code won't be able to detect that. And you wouldn't even need a controller to fix it.

Banning people trying to play your game, AFK or not, you don't pay their sub (stings when that crap goes the other way), is also the most wantonly destructive response they could have. They're bypassing the system because they want to play when they get home from work. Not sit in the queue for 4 hours before logging in and then going: oh my, time for bed, well this was fun! Do it again tomorrow!

Come on, I can tell many people here haven't played THAT game. THAT's the game Square is addressing... and a reboot at 2-4 in the afternoon is almost perfect, because now the people you all loathe so much cannot even swing by at lunch and jump back in and cause the same problems. A fresh boot right before east coast prime time ensures that the most slots are open and available for the most amount of people.

Also: if you are inconvenienced for a hour a day, its okay. I've been inconvenienced for 2-4 hours regularly since the launch of 4.0. And your "hour+" inconvenience is only what, truly 15 minutes? Come on guys. Save your hunt logs, save your crafting leveling, save some PotD, you know it is coming... PLAN ACCORDINGLY. The only way it becomes a 90 minute outage in your play cycle is if you are really crappy with time management, and probably could do with a little need to work on that part of your lives.

Trust me, given the time they had to implement the solution, this was, astoundingly, a great tactic by SE. A code fix would have been in place AFTER the need for it, plus likely would have been exploited quickly again, anyways, and this does help a MAJORITY of their player base that literally found 4.0 unplayable.

[Jijifli]

I do like how posts like this keep getting ignored ^

People don't want to see how others are being affected negatively for way more than 10 mins, and they are gaining nothing from it either if they play in a server without queues.

I do also want this to be looked at as if I am a new player. I end up in a complete restart on Mateus, meaning I don't have millions of end game things to do.

If I was just joining the game, I'd feel upset if I picked a dps, and because of it, got locked out of doing story for an hour because of queue, plus doing the dungeon, because everyone had to get kicked off. I'm working on this character so that my friends that come to play have a spot to go that isn't Balmung, and I'm thankful they don't play at this time because they'd feel upset having this happen to them.

Just do it to Balmung. It's wear most of the issue is anyways.

[Namahana]

My apologies. I didn't mean to slight any of the other servers. My FC / raid team / friends moved to Mateus and started our sister FC on Mateus. I also transferred all my toons to Mateus so we all are able to group together for instances. However, my main still resides on Balmung where as a dps, my q time is anywhere from 45 mins to 2 hours for the instances, which is the same q time sitting on the log in screen waiting to get on the game. I heal now (which I hate healing) so my instance q is not that long. I feel your pain Jijifli. Sooooo .. let me do another shout out to SE to please add more servers