Packet loss...attempting to reconnect

[Snorky]

This is all well and good for when you initially log into the data center. I can understand that and it makes sense. What I refuse to accept though is when I have already been in the queue for hours and it randomly 2002's me and closes the client. It's bad programming and needs to be fixed yesterday.

It's nothing of the sort

[Cadmar]

It's nothing of the sort

Then do tell. Why exactly does it kick someone who is already IN the queue OUT of the queue?

[AngelCheese77]

Here just solved 99% of the current rage from 2002 error. STOP CLOSING THE CLIENT for god sake. What is so hard about this?

ok cool get a packet loss that causes the client to desync from the login queue. Ok add a message that literally says that and says attempting to reconnect.

Closing the entire client and requiring people to try and login as soon as possible is just insane.

You are LITERALLY FORCING people to stay at their computers to watch a queue and if it disconnects quickly log back in. We cannot do ANYTHING ELSE!

I can tell you it doesn't work for me. When I get a 2002 it closes the client, and when I log back in I can never connect to my data center for hours.

[Alxyzntlct]

I've been experimenting with the entire connection / disconnecting / internet connectivity issue, and I have to say, what I'm seeing is, well... insane.

Some context first: I work remotely so I've invested in a solid internet connection. At any time during my normal workday, I can have multiple chat programs, a persistent email app, literally dozens of internet pages, a 2nd computer on the internet, do online calls (slack, zoom, etc.), and stream either music or a movie in the background without issue. I use wifi for my laptop, but my desktop has a direct wired connection so that it's stable.

However, as soon as I try to connect to FFXIV, if I have anything more than just a couple internet pages open (aka most of what I just listed above), I get the 2002 error. I can't stream, can't have email open, effectively anything else internet related going on or even attempting to hit a data center results in a 2002.

If I get into the queue, I've found that I can then start streaming something, for a little while, but if I have to pause or select something new, aka something that takes up more bandwidth, it'll crash out the game with the 2002. And then if I try to reconnect quickly to hit the 1minute timer, it won't let me and will instead just keep hitting me with 2002 errors. And it won't stop with the errors until I reset/refresh my entire connection, by which point I'll have lost my spot in the queue.

However, for the last couple of nights I've had no issues, as long as I have absolutely nothing else connecting to the internet. I've been patiently waiting through 2-3hr+ queues (I've been playing later to try to accommodate, which has sucked on other levels), but no 2002 errors during login or while playing the game. Only thing connecting was FFXIV.

So, this all essentially tells me the following: The bandwidth requirement for SE's launcher to do the connect check is INSANELY SENSITIVE.

Probably one of, if not the worst, system I've ever seen in my 40+ years of life and working with technology. I'm actually legit impressed considering they're not some little indie company and an actual mega-corporation, lol

Welp, since I just lost my place in the queue after having wasted an hour, now I need to get back on track to my chores and maybe try again later today...

Edit: Adjusting some details above due to Catwho's thoughtful addition below

[Catwho]

It's probably not bandwidth, but a QoS issue. if you're using a fancy enough router, you can adjust it to prioritize QoS and limit bandwidth hogging applications - you can even tell the router to give priority to your gaming computer over everything else in the house if your router has that capability.

XIV sips data, and the connection to the queue server is just a small echolocation, a few packets. If those packets are lost or delayed, it's enough to cause the 2002.

[Alxyzntlct]

It's probably not bandwidth, but a QoS issue. if you're using a fancy enough router, you can adjust it to prioritize QoS and limit bandwidth hogging applications - you can even tell the router to give priority to your gaming computer over everything else in the house if your router has that capability.

XIV sips data, and the connection to the queue server is just a small echolocation, a few packets. If those packets are lost or delayed, it's enough to cause the 2002.

Oh, interesting. That's cool to know, I appreciate the info!

Alas, I just checked and my router apparently isn't one of those nicer ones... Oh well. At the very least I know how to consistently get the game to work, despite it being a tiresome and frustrating process. At this point I'm finding more and more reasons to do other stuff than play the game, if only out of necessity, lol

[PangTong]

How is that everyone's connection sucks ONLY when they're in the queue, but once they get in the game, it's fine? I get disconnected from the queue probably once every 1-2 hours, but almost never get disconnected from within the game even if playing for 10-12 hours straight.

Why does the queue not have any kind of handling for minor packet loss, like the game obviously has? And failing that, WHY does the game close completely when you get disconnected, forcing you to restart the client and re-authenticate, greatly increasing the chance that you will miss the reconnection timer and be kicked to the back? Why is the grace period only "a few tens of seconds"?

To say that this is just player hardware fault and there's nothing they can do is insulting. If there's a reason why they can't make the obvious improvements everyone is suggesting, then explain those reasons. Why does the game not automatically attempt to reconnect? Why does it close completely? Can you fix that? If not, why not? Don't hit us with this "stop using wifi, dummy" and leaving it at that when literally everyone is getting this problem.

[Kes13a]

Here just solved 99% of the current rage from 2002 error. STOP CLOSING THE CLIENT for god sake. What is so hard about this?

ok cool get a packet loss that causes the client to desync from the login queue. Ok add a message that literally says that and says attempting to reconnect.

Closing the entire client and requiring people to try and login as soon as possible is just insane.

You are LITERALLY FORCING people to stay at their computers to watch a queue and if it disconnects quickly log back in. We cannot do ANYTHING ELSE!

didnt you recently "solve" the issue by saying it was the game server AFK kick mechanism, that was causing the login server disconnects?

[Snorky]

■ Current Congestion Situation

It has been eight days since the start of Early Access, but we are still experiencing congestion and apologize for the inconvenience associated with this. Likewise, we continue to see large numbers of players accessing the game over the weekend, although the peak numbers are slightly lower than last weekend and players logging in are gradually dispersing into the other time slots. In addition, the queue lengths and wait times are conversely tending to increase because of the progress made in our resolutions for each error and our raising of the login queue cap. We will continue our efforts to expedite the processing of logins and the stabilization of queues, and we appreciate your understanding and cooperation on this matter.

■ Error 2002 Related to Login Queues

As we mentioned in our previous announcement (https://sqex.to/eUgyp), there are two causes of Error 2002.

Occurrence of Error 2002 When the No. of Players Waiting in the Queue per Logical Data Centre Exceeds 17,000

This processing is carried out to prevent the login server from going down if the queue becomes too long. The error occurs when the queue has reached the maximum number of people and a player attempts to newly join it. After opening the launcher, entering one’s ID, password, and one-time password, and then proceeding to the character selection screen, an error message is displayed when attempting to log in. When that happens, it may look like as if a problem has occurred because the client shuts down completely. In reality, however, access is not possible due to the cap on the number of players that can join the queue. We are very sorry but, in this case, we would appreciate that you give it some time and try again later.

Please note that we were able to successfully raise this cap on the queues as a result of deploying our backup development machines to the lobby servers on December 7. This means that the error is less likely to occur even within peak hours, with the exception of those times when access is at its highest. On the other hand, this has resulted in longer queues due to the increase in the number of players who can wait for access. Your understanding on this point would be much appreciated.

Error 2002 Occurrence From Issues With the Player's Internet Connection

Currently, most of the reports we have been receiving about Error 2002 are to do with this issue. The reason for this is that, as a result of longer queues and more time spent in the queue, there is an increased likelihood of issues occurring in relation to the player’s internet connection. In most cases, this is considered to be caused by packet loss on the internet route or instability from the Wi-Fi connection in the player's internet environment.

Even if you are temporarily disconnected due to Error 2002 at times of such instability, the lobby server will continue to wait for a few tens of seconds to a minute for your connection

[Tsukino]

I've been complaining about this one for 8+ years now and it just doesn't seem to be going away.

The most frustrating part is that it doesn't have anything to do with any connections/routing or the servers. It cannot and would not be fixed by any of the additional hardware they've said they need to get but couldn't. It's just the way the client is written to completely close down when that error is encountered, and it should be fairly simple to just kick you back to the title screen to select "Start" again instead. This would also make the whole "tens of seconds" grace period for the lobby server actually useful.

In fact, a friend of mine recently reminded me that if you lose connection normally from within the game (i.e. if your connection to the Internet is down), you get kicked back to the title screen. From there, if you select "Start" while the connection is still down the client closes, but if you wait until the connection is good at the title screen, you can hit Start and get back in without the client closing and having to log back in all over again. All of the pieces are clearly there, it's just badly designed.