Results 1 to 5 of 5
  1. #1
    Player
    Yimiko's Avatar
    Join Date
    Aug 2014
    Location
    Uldah, monk first.
    Posts
    62
    Character
    Yimiko Hojo
    World
    Balmung
    Main Class
    Paladin Lv 90

    stating the obvious

    Error 2002 90k 5003 whatever the number there's a bigger issue that is clearly within their power to fix. The game should not handle these issues with a crash to desktop. It should not forcibly shut itself down and make you enter your login information over and over again. This is just poor design. It always has been. it's a massive QoL failing, and it's time to fix that.

    Every single time we are bumped form the queue because your program shuts itself down, we try logging in again. Every single time the program closes to desktop, we put our login info again and ping the login servers. This is /creating/ a pile on of login attempts that might as well be a DDOS. it is causing your servers to be less stable. Just make the client stop closing to desktop already. There's no need for that.
    (2)

  2. #2
    Player
    NightPort's Avatar
    Join Date
    Dec 2021
    Location
    Gridania
    Posts
    39
    Character
    Merlin Caledonensis
    World
    Midgardsormr
    Main Class
    Red Mage Lv 90
    Quote Originally Posted by Yimiko View Post
    Error 2002 90k 5003 whatever the number there's a bigger issue that is clearly within their power to fix. The game should not handle these issues with a crash to desktop. It should not forcibly shut itself down and make you enter your login information over and over again. This is just poor design. It always has been. it's a massive QoL failing, and it's time to fix that.

    Every single time we are bumped form the queue because your program shuts itself down, we try logging in again. Every single time the program closes to desktop, we put our login info again and ping the login servers. This is /creating/ a pile on of login attempts that might as well be a DDOS. it is causing your servers to be less stable. Just make the client stop closing to desktop already. There's no need for that.
    I've been saying this for a while now. I never understood why the launcher needs to shut down every time I hit play. Why not keep it up and logged in. Keeps from stressing the servers in situations like we are experiencing right now.
    (2)

  3. #3
    Player
    Yuletide's Avatar
    Join Date
    May 2020
    Location
    Gridania
    Posts
    55
    Character
    Yule Xiv
    World
    Gilgamesh
    Main Class
    Sage Lv 90
    Quote Originally Posted by NightPort View Post
    Keeps from stressing the servers in situations like we are experiencing right now.
    That would add more stress to the servers to keep you logged in. It would also produce far more errors.
    (0)

  4. #4
    Player
    NightPort's Avatar
    Join Date
    Dec 2021
    Location
    Gridania
    Posts
    39
    Character
    Merlin Caledonensis
    World
    Midgardsormr
    Main Class
    Red Mage Lv 90
    Quote Originally Posted by Yuletide View Post
    That would add more stress to the servers to keep you logged in. It would also produce far more errors.
    eh, not really. The launcher doesn't necessarily have to do much. Though I understand what you are saying in the traditional sense of launchers. Most games launchers shut down after you hit that good ole play button. But companies could, to a degree, learn from Blizzard here because their Battle.net system only closes when you tell it to.
    (0)

  5. #5
    Player
    Brandter's Avatar
    Join Date
    Sep 2021
    Posts
    34
    Character
    Mr Captain
    World
    Odin
    Main Class
    Warrior Lv 62
    Read the news on lodestone before making new threads.
    ■ Error 2002 While Waiting in Login Queues

    In regards to Error 2002 that occurs during login queues, outside of causes related to unstable connections, we have confirmed a bug. This bug was part of a login-related program created back in FFXIV version 1.0, and thanks to the reports and tests carried out by many of our players, we were able to identify the cause of the problem. We apologize for not being able to identify the issue on our end and thank you all for submitting detailed reports regarding this matter.

    Although the code for fixing this bug is already prepared, applying the fix will require patching the game client, which will be addressed in Patch 6.01, scheduled for Tuesday, December 21. As this issue occurs while waiting in the queue for a very long time, we considered releasing the patch ahead of schedule, but in the end decided to include it in Patch 6.01, as there is already a lot of new code in the pipeline for the patch and interrupting the process of verifying them may lead to other bugs. We apologize for the inconvenience and ask for your patience a bit longer.
    (0)