Excessive wait times for Data Center Travel

[Bitter_Blossom]

Date & Time: 31st of July 2024 01:05 AM CET
Frequency: Twice
World name: Cerberus
Character name: Bitter Blossom

I was Datacenter Transferring my character from Shiva Back to Cerberus at 1 am and it took 20 Minutes to resolve. When I transferred my character to Shiva, I accepted the long wait time because of the new system and because it was 7pm so many people logged in. But now I doubt these times can be the intended queue time. Especially at 1 AM.

[raventhor0]

I'm having similar issues. I datacenter traveled to help with que times for alliance raids. Seems after the data center travel restriction changes my server had a drastic drop in que times. Last night I was able to que for an alliance raid in about 5-10 minutes but I was sitting in que for about 40 minutes today before i made the decision to transfer. My server is also considered congested now as well even though it's on the newest north American data center. Well I had to afk and the auto logout system did it's thing. Now I can't seem to log back in. I just get an error stating the world is congested and then the game force quits on me. Logged back in again to attempt to return to my own server however I encountered a slightly different but similar error about the server being congested and after about 3 attempts the game force quit on me each time. I can't even log into another character because when I change data centers from the main menu it automatically returns to my character attempting to transfer data centers. I literally can't log in to play right now. I feel it would have been better if they just kept the restrictions they had prior for a while. Only reason I can think on why they changed it is for people to meet up with their static who might be on different data centers, but those people could have easily transferred to a lower population data center to meet up instead unless there were other issues regarding data center travel I'm unaware of.

[stu4355226]

If it's untransferable and users have to wait until the server is not congested, it should not let users travel to that particular world/DC. I believe there is a certain lag between the UI and actual server showing which world is congested and not, and it accidentally lets users travel to the world that is no longer available.

Short note to devs: Please add proper stress tests to your services.

[Eisweyr]

Perfectly stuck in a loop as well. Can't change characters/dc. Cant go home. Can't load the game. Complete Game Crash 2021 or 505 after 5-10m.

Please either force load the characters to their desired DC if you allowed them to transfer
Or just load them back to home.

[OliviaFalls]

Go reset your password, that force quit me out of that loop & allowed me to get back on & change dc & login on a diff character

[Curanthir]

Im 90% sure this is caused by the new update to DC travel. The lodestone post says any standard world in a DC with any congested worlds in the same DC has greatly reduced ability for DC travel. Even Dynamis has a couple congested worlds sometimes. The congestion status changes throughout the day, and may even be changing as you are travelling, possibly causing the crashes and failures.

This is really the worst possible way to try to force everyone to stay home, it wasted 2/3 of my static's first raid day just trying to get our people onto a single DC to raid. DC travel worked fine in EW and if you transferred during down time, you could get in easily. This new system is causing 20 minute plus wait times in the middle of the lowest population downtimes even.

It's a total disaster, and the worst part is that it was intentional on SE's part.

Please revert the DC travel changes SE, either fully un-restrict it or change it back to chaos/dynamis/OCE only again, anything but this artificially limited and slowed down system.