I doubt SE will fix it… honestly a lot of the problems could be solved with a change in one simple section of their code… when people get kicked randomly for the 2002 bug, give them more time to get back into queue before they lose their place in line. Several times I’ve been queued for multiple hours, got a random kick followed by being unable to reconnect to the data center for several attempts and then finally reconnecting to find myself back at the end of the line.
I can forgive technical problems, poor coding is another thing.
I highly doubt it's that simpleI doubt SE will fix it… honestly a lot of the problems could be solved with a change in one simple section of their code… when people get kicked randomly for the 2002 bug, give them more time to get back into queue before they lose their place in line. Several times I’ve been queued for multiple hours, got a random kick followed by being unable to reconnect to the data center for several attempts and then finally reconnecting to find myself back at the end of the line.
I can forgive technical problems, poor coding is another thing.
As a coder, I can tell you it’s much easier that you would think. Names/addresses are kept in a floating database and checked against a server clock, if x amount of time has passed since last contact then the entry is removed from its position in the list. Increase the value of x to accommodate the current known issue and most people will be able to resume their positions in line.
I hear SE is hiring, go help them out.As a coder, I can tell you it’s much easier that you would think. Names/addresses are kept in a floating database and checked against a server clock, if x amount of time has passed since last contact then the entry is removed from its position in the list. Increase the value of x to accommodate the current known issue and most people will be able to resume their positions in line.
The thing that annoys me about the 2002 bug is that only people coming into the end of the queue should really be getting it…
Databases like the ones used for the queue are built to a precise size, they assume a maximum load and build the database to fit what they feel is going to be the worst case scenario for a given dataset… in this case the maximum number of people trying to break down their doors at one time. So a number is set, in this case right around the 17,000 mark. Good even number that divides by 8.
Now once the database is full, anyone coming in at the end would get an error, thus the 2002. The real issue is the people getting kicked while already in queue. Either they should be getting a different error or the server is just having some kind of memory leak and randomly kicking people after a certain period of time. I would love to see the actual logs on this.
As a player i can tell u its much lmao.
I cant count the times i've read that type o'stuff, it almost feels like copy paste.
I wonder, if there are so many great super coders out there...why do we still have those problems?
But eh Sgt Smart, maybe u can get over urself and help them out by just sending them some Email with ur easy peasy solution?
Otherwise its just what others do...runnin ur mouth.
Of course, only if u consider this worth ur time.
Thanks in advance.
Greetz,
Mörser out
Toxic much?
100%. From a software engineer stand point that have worked on multiple illegal mmo servers, this is one of the worst networking I have seen used. There are so many things that they could have done to make everything much better or that should have already been in.I doubt SE will fix it… honestly a lot of the problems could be solved with a change in one simple section of their code… when people get kicked randomly for the 2002 bug, give them more time to get back into queue before they lose their place in line. Several times I’ve been queued for multiple hours, got a random kick followed by being unable to reconnect to the data center for several attempts and then finally reconnecting to find myself back at the end of the line.
I can forgive technical problems, poor coding is another thing.
For instance, losing connection in a game if it wasn't done through a proper shutdown method can be considered as a saved spot in queue for x time - which they don't even do. Random crash! back to a 5 hour wait to get in game - but only after if I make it in time after the 50 error 2002's on a stable connection.
Other than that, there should be no reason to have a limit of "17k" connections hitting the login server - if something like that is occurring, then that's some bad code and design. Then again, if you want the most out of any mmo, you should just drop using any form of game engine and code the game from scratch with tools alongside - you end up with better performance overall by doing things correctly for an mmo.
This is certainly not the worst launch I have seen. It is annoying, yes, but far from the worst.
I just hope a lot of these people who feel so Sqenix has really damaged them and now say they are cancelling the sub really do it. Less people playing, more chances of getting in these days.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.