2002 completely a problem with the game itself?

[NanaWiloh]

There is a post on the mainpage regrading the 2002 issue. The client dropping the connection is a problem and packet loss is the primary one. The person who posted that data tested only their connection for packet loss. There only two people who can tell if packet loss is your issue or not...you and SE.

[Arazehl]

My disconnects (2002's) are more random, not every 15 mins. The queue refreshes itself every 30 seconds to a minute when it let's the next 100 people into the game. I babysit the queue to make sure if I am disconnected, that I log right back in before that next refresh and in doing so I usually retain my place in queue prior to receiving the error.

So my question is if the limit is reached past the 17,000 allotted before one gets the 2002 error, is it better for the world servers at over 17,000 to crash instead of the log in server and everyone get knocked out of game, forcing a even a greater queue time of three times the queue's previous numbers? Are there people asking them to let the game crash for those that are in game so you don't get the 2002 error anymore?

[Larirawiel]

My disconnects (2002's) are more random, not every 15 mins.

The 2002 error CAN happen every 15 minutes. But it can also be that it will not happen for a couple of hours. There are two conditions that must be met: the 15 minutes disconnect AND the lobby server is full at this time. Then you will get the 2002 error ... even when your internet connection is perfect without any packet loss.

Cheers

[Seraphor]

Several multi-hour queues with no 2002's here.

Yes there's an issue with the queue refreshing itself, but if you have a good connection to the server tgat won't result in a 2002.

[PredatoryCatgirl]

if you have a good connection to the server

The issue being that there are enough intermediaries between you and the server that this is completely out of your control. You can only change your connection speed and whether you use a hardline or wifi. If there's a node somewhere in the middle screwing up...