Square Enix 2002 is related to your AFK timer. Data confirming this issue.

This is a repost of one I made on the technical forums. The servers appear to place you on the datacenter when you enter the queue. You are not physically loaded into the server until there is room hence the queue.

IN July 2021 a 30min AFK timer was added to FF14. This AFK timer is triggered when the client does not receive client side input from the user for 30 minutes. The reason this error was not discovered since June is because we have not had queues that last longer then 30 minutes.

If I am wrong then I am wrong but this should be VERY VERY easily reproducible.

Quote:

---

I have been trying to time this issue and it appears to be occurring every 30 minutes atleast on my side.

Connected to the login server in queue at 7:18pm(CST) and immediately got a 2002 disconnect error at 7:48pm (CST). This exact 30 minutes lines up with the AFK timer implemented in June 2021.

Is there any connection here at all?

Update: Confirmed

Reconnected to server login queue at 7:50pm (CST)
Kicked out of the server queue EXACTLY at 8:20pm

---

Logged in again at 8:22pm and my next 2002 error should be at 8:52pm(CST) if I am still in queue

I've had multiple 2002's only a few minutes apart over the past few days, so going with no on this one.

feeling low on your post count?

so, now, in your opinion... they are policing your login...

just a thought... check any of the sleep timers for your OS? bothered focusing your login queue windows and clicking? moving the mouse?

or are you just recommending they remove the AFK timer in game so you dont have to log out and can stay in all night?

your "explanation" doesnt consider 2002 errors earlier than 30 minutes... or longer...
also does not address other errors that pop up while in queue

Quote:

---

Originally Posted by Puremallace

This is a repost of one I made on the technical forums. The servers appear to place you on the datacenter when you enter the queue. You are not physically loaded into the server until there is room hence the queue.

IN July 2021 a 30min AFK timer was added to FF14. This AFK timer is triggered when the client does not receive client side input from the user for 30 minutes. The reason this error was not discovered since June is because we have not had queues that last longer then 30 minutes.

If I am wrong then I am wrong but this should be VERY VERY easily reproducible.



Logged in again at 8:22pm and my next 2002 error should be at 8:52pm(CST) if I am still in queue

---

I believe you may be stupid.

Quote:

---

Originally Posted by Darthgummibear

I've had multiple 2002's only a few minutes apart over the past few days, so going with no on this one.

---

There is no way this is this predictable down to the second without it being related to something occurring server side that has jack squat to do with chips. 2002 could just be a generic error it gives when the client is disconnected from the server but not that the server capacity is higher to hold more people in queue that could be why the 30min timer is now visible.


All I know is this is reproducible.

I had the game sitting in queue for over 2 hours straight unattended the other day without issue, so I'm gonna say you're simply wrong.

Quote:

---

Originally Posted by Chooty

I had the game sitting in queue for over 2 hours straight unattended the other day without issue, so I'm gonna say you're simply wrong.

---

Welp I do not know then. This MMO makes no sense than.

Quote:

---

Originally Posted by Puremallace

Welp I do not know then. This MMO makes no sense than.

---

They already said why 2002 happens, nothing to do with AFK timer. Happens due to the load of the login server.

If you posted this in Technical...where it and every thread about this issue factually belongs......then why are you posting it again here in General?

People have already established the likely circumstances around the error using network diagnostic tools;

Quote:

---

The main problem with error 2002 is that every 15 minutes the client closes its connection to the lobby server and opens a new one. When this happens, there's a race condition between your connection closing and somebody else taking your slot before the new connection opens. Unless there's an open slot within the 17,000 concurrent character limit the lobby server will immediately close your new connection and your client will crash with error 2002.

This means that every 15 minutes, you have a chance of getting a 2002 error while waiting in queue, which is ridiculous. You can get your spot back by getting back into the queue within 5ish minutes, but to do this there needs to be an open slot for you (probably vacated by somebody else's client doing a connection refresh) when you hit the Start button to get to the character select screen.

The somewhat nice thing about this though, is that the behavior is predictable. So it's only possible (minus packet loss, etc) to crash once every 15 minutes from when you reach the Character Selection screen in the game. So you can go afk and set a timer to come back and check if you've crashed.

---

onyxia deep breaths more