Against "Simultaneous Logout Measures"

[awbalto]

So this fix "helped" to get in the game at around 6pm BST but if you dare to get a 90k or anything else that would disconnect you after that time, have fun in a queue of 2000 people -_-

[Rasylia]

Stuff

Edited cause i completely missed something.

However, there isn't much you can do at that point, since it IS conviniently made for NA players, not EU players.

But, as its not prime time for NA, the ques wont be bad after the boot. High, yes, but quickly gone too. So, overall, its not any different than for any NA player who is online at that moment.

[Nezerius]

Your post is nonsense, as the Big Boot(y) happens during the day, not in the prime time.

Just to point out that their post isn't nonsense, the player you're quoting is using EU times.
While it's true that the server logout happens at noon PDT, that's 9pm in central Europe, for EU players that play on the NA servers.

[Rasylia]

Thanks for pointing it out, as i seem to have completely missed that part. I edited my post.

However, there isn't much you can do at that point, since it IS conviniently made for NA players, not EU players.

But, as its not prime time for NA, the ques wont be bad after the boot. High, yes, but quickly gone too. So, overall, its not any different than for any NA player who is online at that moment.

[Hasrat]

I've never had problems with queues, but even I look at that situation with little sympathy. Your 2 hour window of play time is mildly interrupted, so you can't do party content? As I understand it, for a great many players, getting online at all in a two hour window was nearly impossible for a while there.

After the relatively short roulette queue I just had, I still feel that this has been a net benefit for everyone.

[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.

[Val-K]

Your 2 hour window of play time is mildly interrupted

The lockout is right in the middle of my prime time (8pm). You have to interrupt your instance queueing about 20 min prior to the lock out so we don't get caught inside. So for those with limited play time, 30 min is not trivial. I would see no problem if that was a one off, but with no permanent solution on the horizon it could last a while.

I still don't understand why they blanket lockout all the servers and not the specific ones with problem.

I'm glad my lost time and inconvenience are helping others to login in their own server .. but I chose my server specifically to do not have these problems and you would excuse me if i feel a "little bit" annoyed by all this.

Quite frankly, if this continue too long i will have no other option than to transfer to another data centre for a more convenient lockout time.

[Lexia]

Guess one can never truly leave Balmung, You can take the person out of Balmung but not Balmung out of the person. The game will be forever haunted by it.

[Ayrie]

I still don't understand why they blanket lockout all the servers and not the specific ones with problem.

Quite frankly, if this continue too long i will have no other option than to transfer to another data centre for a more convenient lockout time.

The first bit there... that is actually a legitimate complaint! But here's the problem Square is likely facing:

Each server cluster probably runs off of the SAME code. Each shared data center resource has the SAME code. The beauty of that is that when you do a new code deploy, you can have an automated service go out and push the SAME code to every node, and the update takes minutes instead of hours.

If they were to "make a code exception" for server-specific restarts... that would clutter the process, and invite a WHOLE LOT of human error into a process that is probably completely automated. Trust me, human error and servers are about as healthy of a mix as electricity and water.

Bottom line: they probably don't want their code to have exceptions, keep it all standardized for future development cycles, and to keep the disruptions congruent across the population. Besides, everyone is treated fairly, read as: the same. Isn't that what everyone is about these days? Fair treatment and equal access (to getting unceremoniously booted every day ).

It is rough, but fighting the same tired argument without any context as to why they do what they do... or why they didn't do it differently. Well... that just sounds pointless. And I know one of their engineers/sys admins aren't about to come out here and explain to us WHY.

[Val-K]

The first bit there... that is actually a legitimate complaint! But here's the problem Square is likely facing:

Each server cluster probably runs off of the SAME code. Each shared data center resource has the SAME code. The beauty of that is that when you do a new code deploy, you can have an automated service go out and push the SAME code to every node, and the update takes minutes instead of hours.

If they were to "make a code exception" for server-specific restarts... that would clutter the process, and invite a WHOLE LOT of human error into a process that is probably completely automated. Trust me, human error and servers are about as healthy of a mix as electricity and water.

Thank you ... at last i can understand some of the decisions