Concrete proof finally provided that the 2002 error has NOTHING is server side issue

[NanaWiloh]

The claim being made is that 2002 is caused by the servers and has nothing to do with user connections.

However various anecdotes show that users with strong connections to the servers don't get 2002. I'm one of them.

This would support the "user connection" issue.

The queue may well be forcing a refresh every 15 minutes, but if you have a good connection to the servers then that refresh won't cause a 2002.

I looked at the doc the person who did it is saying there is no packet loss. But their saying it cause they themsleves have no packet loss. Their data does not apply to everyone only to them and should be ignored. To everyone only two people can determine if packet loss is your issue..You and SE!!!

[KarstenS]

The queue may well be forcing a refresh every 15 minutes, but if you have a good connection to the servers then that refresh won't cause a 2002.

Depends on the time.

Most of the day I get through the queue without 2002.

But on friday, I queued up during primetime and had 5x 2002 till I got into the game.

So I think the FIN packet happens because of the 21k (earlier 17k) mark.

As hard as it is, I think the system should make a difference between ppl, that are already in queue and ppl, that want to enter the queue.

Maybe using different ports could separate them.

[Yeol]

mid-queue Error 2002 is a combination of several questionable decisions made in the networking implementation of the FFXIV client and server

the tl;dr, here you go: The game client is voluntarily closing a healthy connection every 15 minutes, forcing you to (invisibly) re-connect to the server as though you had just pressed the ‘Start’ button. When this happens, if the login server arbitrarily decides not to let you in, you will see Error 2002 and have to close the client. Even if you have perfect network conditions in your home you will still get Error 2002 randomly and there’s nothing you can do to prevent it.

Questionable decisions indeed.

[RyuDragnier]

Questionable decisions indeed.

Well then the following is a good thing.

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 to be restored. If you are able to get back online and reconnect to the lobby server quickly, you will be able to queue up again from the middle of the queue. After a certain amount of time, the connection will be completely lost, and you will have to join the end of the queue.

Keep in mind I play on PS4, and so it takes around 1-3 minutes for me to get back into the queue. Every time it has saved my spot when I get the error.

[Yeol]

Well then the following is a good thing.

I wouldn't call this good. The few seconds to a minute are RNG. Sometimes you're lucky to get back to the middle of the queue, other times you're not. Let's hope we get a real fix for this.

[Hustensaft]

Well then the following is a good thing.

Keep in mind I play on PS4, and so it takes around 1-3 minutes for me to get back into the queue. Every time it has saved my spot when I get the error.

If you can manually reconnect and keep your spot in the queue, this means the server holds your spot, but at the same time told your client to disconnect or your client disconnected. The proper solution should be, that as long as the server holds your spot, the client should be able to reconnect automatically.

Same on PC. If you have two instances of the game running at character select, the first in queue, the second as backup. If the first 2002s, you can immediately requeue on the 2nd and keep your spot. What you can do manually, the client should to automatically.

Blaming the users internet connection is flawed on so many levels. Their piss poor queue implementation should be fixed, and should ideally account for paket loss.

[Rufalus]

My connection is stable enough that I never get kicked from the actual game, but the login queue can still kick me. If I'm in a very long queue then the chance of being kicked becomes very high. At some point in the multi hour wait it will decide to kick me while my internet is still working fine.

This is especially bad on patches that make housing plots available for purchase at the same time that the servers come online. All the plots are bought by lucky people who get in on first attempt while the unlucky are still having to re enter password, restart the game and restart queue until the queue stops kicking them.

Why does the application need to force close anyway. Other mmos I've played do not make you open the launcher again and start from the beginning in the case of an error connecting to your character.

[Ranhansha]

Does this mean Yoshi-P lied to us?

[Vukimukinukiduki]

I think devs just can't fix this, my profession lies far from programming, but I have feeling that part of code responsible for dropping connection and other things with 2002 error is patched so many times that they can't do something about it, if they would do than they gonna broke another thing.

[Rinhi]

The claim being made is that 2002 is caused by the servers and has nothing to do with user connections.

However various anecdotes show that users with strong connections to the servers don't get 2002. I'm one of them.

This would support the "user connection" issue.

The queue may well be forcing a refresh every 15 minutes, but if you have a good connection to the servers then that refresh won't cause a 2002.

I live like, an hour away from the EU servers and still get 2002 issues trying to connect the few times I tried and yes, my connection is stable