Getting frustrating at the 2002 and losing queue position

[Hauntedd]

On a direct ethernet fiber DSL connection, extremely stable. Was in Q from 3500 for the last hour and half and kicked out around 400 with 2002. Back to 3586 again....

You really need to fix this Square. I can handle waiting in line but being booted back to the end of the line after this error is terrible service on your part.

I have been playing MMO's since UO and I have seen many poor launches, this would have been a pretty reasonable expansion launch if not for all these errors causing people to have to wait hours and hours again. An I cannot recall seeing anything in any MMO where people consistently get errors and are kicked out to the back of the line, so I don't but any excuses, especially this wifi excuse you keep going with as many of us have posted we are on direct ethernet connections and still getting this frequently.

[ibiteyourankle]

On a direct ethernet fiber DSL connection, extremely stable

It's not your connection and I don't know where you are getting information that it's a wifi issue with the 2002 errors. You can read the information here: https://na.finalfantasyxiv.com/lodes...9cad782363f25b

FFXIV’s Error 2002 message pops up if the game’s login server is dealing with high amounts of players or if the player amount in a single login queue for a specific data sails past 17,000 players, though Yoshida has confirmed that the team is deploying an update to increase that number to 21,000.

[Grayjack]

Tell me about it, got to 74 in the queue after 2 hours only to 2002 and get kicked back to 4500.

[Yahallo]

It's not your connection and I don't know where you are getting information that it's a wifi issue with the 2002 errors. You can read the information here: https://na.finalfantasyxiv.com/lodes...9cad782363f25b

No, Yoshi P stated that switching to a wired connection instead of a wifi connection can possibly mitigate the issue. However the fundamental problem is the massive number of players. The fix to increase the login server limit from 17000 to 21000 has already been implemented.

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

https://na.finalfantasyxiv.com/lodes...9264ac9f24986f

Also, in the announcement you linked:

"The other occurs when your internet connection experiences packet loss or a period of network instability, causing the server connection to be momentarily disconnected. At the moment, we are seeing more cases caused by this."

The 2002 during queue is caused by connection issues which can stem from the large number of players trying to log in as traffic has a huge effect on connection.

[SquashBuggy]

No, Yoshi P stated that switching to a wired connection instead of a wifi connection can possibly mitigate the issue. However the fundamental problem is the massive number of players. The fix to increase the login server limit from 17000 to 21000 has already been implemented.

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

https://na.finalfantasyxiv.com/lodes...9264ac9f24986f

Also, in the announcement you linked:

"The other occurs when your internet connection experiences packet loss or a period of network instability, causing the server connection to be momentarily disconnected. At the moment, we are seeing more cases caused by this."

The 2002 during queue is caused by connection issues which can stem from the large number of players trying to log in as traffic has a huge effect on connection.

there is no way this is wifi related like they said in the message from Yoshi. My PC has a wired connection and while it isn't as bad as it was before, i am still getting 2002 errors when in the queue after a couple hours. Starts out almost 5k people in the queue, and i get a 2002 after a coupel hours when it was down to around 2,300. Logged back in as fast as i could and back at the end of the line around 4000. Not sure what the time limit is since that post was really vague about it, but they really need to increase it.

[Hauntedd]

It's not your connection and I don't know where you are getting information that it's a wifi issue with the 2002 errors. You can read the information here: https://na.finalfantasyxiv.com/lodes...9cad782363f25b

As someone else already posted just after your post, the exact post you linked notes wifi as a factor, if you look at the original post on the 2002 error that SE did it was also list as an excuse. While its possible wifi could play a part for someone who has poor wifi, the majority of people posting are direct connected, which supports this isn't really a problem with people's wifi, this is on SE's side in fully in their court to fix. It feels like they are trying to pass some of the blame onto the customer and it does not come across well.

[Yahallo]

there is no way this is wifi related like they said in the message from Yoshi. My PC has a wired connection and while it isn't as bad as it was before, i am still getting 2002 errors when in the queue after a couple hours. Starts out almost 5k people in the queue, and i get a 2002 after a coupel hours when it was down to around 2,300. Logged back in as fast as i could and back at the end of the line around 4000. Not sure what the time limit is since that post was really vague about it, but they really need to increase it.

It's more that wifi can be an issue, but it is not the only possible issue. That is what the announcement is saying.

As someone else already posted just after your post, the exact post you linked notes wifi as a factor, if you look at the original post on the 2002 error that SE did it was also list as an excuse. While its possible wifi could play a part for someone who has poor wifi, the majority of people posting are direct connected, which supports this isn't really a problem with people's wifi, this is on SE's side in fully in their court to fix. It feels like they are trying to pass some of the blame onto the customer and it does not come across well.

I wouldn't say they are passing it off to the costumer; if anyone is getting passed to, it is the ISP's. Which isn't too far-fetched considering ISP's often don't route things rather well. I remember Comcast routing my connection through some very questionable paths. SE can't really do much to make the ISP's fix anything either.

[ibiteyourankle]

The 2002 error is not due to the client's end FOR THE MOST PART. It's the overload of the server's "number crunching" capacity and connection priority.

Even if you have a super duper connection and not on wifi, you still might/will experience the problem because every connection has some sort of packet loss. Direct connect just has a lower amount. If the number of hops from you to the data center is high, you will most likely experience more 2002 disconnections. This is because every hop you do, you lose some packets and your client side needs to resend. So, math wise (below are arbitrary numbers):

• Let's say you have 10 hops from you to the server and you lose 1 packet for each hop. That's 10 re-request that needs to be done.

Now for those that have more than 50 hops....you can see what is going on. This is usually not a factor if things are running normally because the packets travel super fast (unless you have 200+ MS latency...then it's partly you), but, with how overloaded the servers are...it does become a big factor.

If you want to check how many hops you have, just do a tracert to the servers. Remember, each hop has a packet loss of some sort. Each packet loss needs a resend of the packet. Each send and send back (round trip) is dictated by your latency (i.e. ping in ms). If you put it all together:

• High packet loss due to a lot of client to server hops causes 2002

• High latency (that's why wifi is not a good idea because it adds more to the latency) causes 2002

• A lot of hops plus high latency...feels bad, man

[Sndman22]

Im tired of people making excuses for them They continued to sell tickets to a concert that was sold out with no more room 3 months ago. They knew that they could not fix the problem 3 months ago with the global chip shortage. But hey they appoligized and continued to sell tickets. I tried to unsub but unfortunately i still have 20 days left. I have never seen anything this bad. My only hope for playing the game will be to log on at 3am est for next month or longer. 1

[MaraSuttle]

I feel your pain , sat in queue for 1.5 hours this morning , got in the game , did a few quests and got DC'ed during a cut scene after 20 mins of play (errors below) and was in a 6800 + queue. Sat in queue for almost 2 hours, down to 3200ish , walked away for no more than 7 mins , come back and I'm 2002 and lost my place in line and back over 6700 .

the worst is you cant even queue and walk away to even change out a load of laundry or grab a snack without the fear you will lose your place in line .