Getting frustrating at the 2002 and losing queue position

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

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