Square quit blaming 2002 on the user's internet connection and take responsibilty

[ApeKing]

Personally, I didn't have any 2002 errors since the post claiming that server side causes for this error were fixed, and I spent hours in queue every day since I only can play after work. I have fiber optic Internet connection (G-PON), pretty good router from UniFi and my PC is connected to the router by wire. I suggest to quit blaming Square Enix and take responsibility for the quality of your network equipment and Internet provider. Also, try rebooting all network equipment you have access to. I personally had issues with connection (before Endwalker) that were fixed by ONT box reboot.

How much do you guys get paid for this?

[not_sus]

How much do you guys get paid for this?

Negative amount, around -$78 per 6 months + additional retainer fee + optional items like fatter cat mount. I am regular player just as you, sharing my experience. I hope that my post will make you at least try to fix the problem on your end.

[ApeKing]

Negative amount, around -$78 per 6 months + additional retainer fee + optional items like fatter cat mount. I am regular player just as you, sharing my experience. I hope that my post will make you at least try to fix the problem on your end.

Oh you are just trolling. Ok continue on friend.

[not_sus]

Oh you are just trolling. Ok continue on friend.

I am genuinely not trolling. I am sorry that my post made you think so. I actually tried to formulate my sentences in a way that will not provoke emotional response and reach the rational mind, but I failed.

I used to have 2002 error every half an hour or so, and had to restart the client. But they seem to either fix the problem or significantly reduce the probability of it happening: for several days now I was able to join 2000-5000 person queue and start playing without single 2002 error.

Please at least try to diagnose problem on your end:
1. Reboot all network equipment
2. Try wired connection instead of Wi-Fi. If switching to wired connection will not cause 2002 errors, then at least you will know where the issue is and will be able to search for ways to fix it.
3. Try using different Internet provider. I would try tethered Internet connection through a phone. The 2002 experience may be actually worse though, since wireless network protocols are inherently less stable.

[ApeKing]

I am genuinely not trolling. I am sorry that my post made you think so. I actually tried to formulate my sentences in a way that will not provoke emotional response and reach the rational mind, but I failed.

I used to have 2002 error every half an hour or so, and had to restart the client. But they seem to either fix the problem or significantly reduce the probability of it happening: for several days now I was able to join 2000-5000 person queue and start playing without single 2002 error.

Please at least try to diagnose problem on your end:
1. Reboot all network equipment
2. Try wired connection instead of Wi-Fi. If switching to wired connection will not cause 2002 errors, then at least you will know where the issue is and will be able to search for ways to fix it.
3. Try using different Internet provider. I would try tethered Internet connection through a phone. The 2002 experience may be actually worse though, since wireless network protocols are inherently less stable.

Then you have not researched the current situation or are just ignoring it. Many people have tried diagnosing the issue already and have found nothing wrong on their end. Myself included. Not only that but plenty of evidence has already been provied by many users that the situation is not being caused on user side alone, or in many cases at ALL.

[DarkDepravity]

I am genuinely not trolling. I am sorry that my post made you think so. I actually tried to formulate my sentences in a way that will not provoke emotional response and reach the rational mind, but I failed.

I used to have 2002 error every half an hour or so, and had to restart the client. But they seem to either fix the problem or significantly reduce the probability of it happening: for several days now I was able to join 2000-5000 person queue and start playing without single 2002 error.

Please at least try to diagnose problem on your end:
1. Reboot all network equipment
2. Try wired connection instead of Wi-Fi. If switching to wired connection will not cause 2002 errors, then at least you will know where the issue is and will be able to search for ways to fix it.
3. Try using different Internet provider. I would try tethered Internet connection through a phone. The 2002 experience may be actually worse though, since wireless network protocols are inherently less stable.

The aggregated data thus far suggests an issue on the NTT backbone between several of their nodes in the US, one candidate being TX - CA (sacramento), so a different internet provider might indeed remedy the issue, just not for the reasons you assume. The traffic could potentially take a different route and thus not hit all the problematic NTT nodes. But it might also result in the precisely same thing depending on what routing agreements the ISPs have. Those who have VPN providers could try to find a different egress point. Personally I have been using PIAs California node today, and while the last stretch is NTT, I have about halved the # of NTT nodes I go via, and it has been rock stable, so it supports the general data available.



You can argue back and forth at what point it is no longer SEs responsibility, but considering the data thus far suggests the culprit being NTT and SE seeming to have an agreement with NTT. This is definitively in SEs court.


Edit: the downside for SE of having a 30+ years old franchise, literally generations of people with an interest in the franchise have had more than enough time to build up a lot of tech knowledge, also relating to issues such as these.



You are listing the (very good) 1st line suggestions for improving,but this is highly likely to be a 3rd line issue on the infrastructure end. The reason it works for a lot of people without a hitch is most likely because their ISPs routing agreements take different routes.

[not_sus]

The aggregated data thus far suggests an issue on the NTT backbone between several of their nodes in the US, one candidate being TX - CA (sacramento), so a different internet provider might indeed remedy the issue, just not for the reasons you assume. The traffic could potentially take a different route and thus not hit all the problematic NTT nodes. But it might also result in the precisely same thing depending on what routing agreements the ISPs have. Those who have VPN providers could try to find a different egress point. Personally I have been using PIAs California node today, and while the last stretch is NTT, I have about halved the # of NTT nodes I go via, and it has been rock stable, so it supports the general data available.



You can argue back and forth at what point it is no longer SEs responsibility, but considering the data thus far suggests the culprit being NTT and SE seeming to have an agreement with NTT. This is definitively in SEs court.


Edit: the downside for SE of having a 30+ years old franchise, literally generations of people with an interest in the franchise have had more than enough time to build up a lot of tech knowledge, also relating to issues such as these.



You are listing the (very good) 1st line suggestions for improving,but this is highly likely to be a 3rd line issue on the infrastructure end. The reason it works for a lot of people without a hitch is most likely because their ISPs routing agreements take different routes.

I don't care who to blame, since it is not productive. I worry that threads like this may result in people having a problem they can fix themselves would not even try. Using VPN with exit node in California is a good suggestion (I am in California myself, so this may be the reason I don't get network related 2002 errors).

Another thing that I noticed is that different regions have different number of servers. Japanese data centers have higher server count (11) than NA (8) and EU (6), this may also be the reason for 2002 fix not being as effective for players playing on Japanese data centers (I assume that more servers means more players connecting to lobby server).

[DarkDepravity]

I don't care who to blame, since it is not productive. I worry that threads like this may result in people having a problem they can fix themselves would not even try. Using VPN with exit node in California is a good suggestion (I am in California myself, so this may be the reason I don't get network related 2002 errors).

Another thing that I noticed is that different regions have different number of servers. Japanese data centers have higher server count (11) than NA (8) and EU (6), this may also be the reason for 2002 fix not being as effective for players playing on Japanese data centers (I assume that more servers means more players connecting to lobby server).

In this case it is not about "blame" as such, it is about determining the source of the problem, and wishing/attempting to see it remedied. As such, it is eminently productive to determine the culprits contributing to something being an issue.

[ApeKing]

I don't care who to blame, since it is not productive.

https://www.youtube.com/watch?v=C6U926lsM-w

[renachi]

I don't care who to blame, since it is not productive. I worry that threads like this may result in people having a problem they can fix themselves would not even try. Using VPN with exit node in California is a good suggestion (I am in California myself, so this may be the reason I don't get network related 2002 errors).

When a company "blames" something as the cause of a problem when it isnt the cause of the problem, the problem doesnt get fixed. The company has to understand their problem in order to fix the problem, and players have providd plenty of data as to the causes of the problems and they should be able to take steps to remedy them. The easiest would be that for this disconnect errors simply add in a couple of checks to see if the player's client started responding. For example when it would generate the 2002 and close the client, instaed check to see if the connection is there and then continue on in queue. For the error 90002, simply put a check right before booting the player to see if the client is responding and if so, reconnec them immediately. I just got booted out at the end of a cutscene just to have the game tell me my character wasnt properly logged out and it was going to log me out before I could log back in... when it should just reconned me to exactly where I was.
Their client has some bad design choices that are becoming major issues with the queues where they were just stupid annoyances before