[Feedback] Data Center Travel Changes

[Vstarstruck]

If the server transfer cant be done and congested why not let us not do a request? or if in a request, let us cancel? let me play my other characters plz, not the one locked in the server transfer.

also I thought all the warnings said going to OCE/ Bismarck was supposed to be fine, it worked fine since DT released, why is it broke now?

Maybe SE servers cant handle savage release so close to new expansion? i doono but this is the first time I was stuck like this. Least have a way to cancel requests so we are not stuck, or block server requests if it is overwhelmed.

like I said in my other thread, they should at the very least allow us to withdrawal the request, not stuck loading time and time again, even if i try go on a different server with a different character. its like SE never thinks about backup plans

[Jlato]

My main lives on Aether, but the rest of my raid group lives on Crystal. For at least a year now, I've been traveling to Crystal to raid with my friends with zero repercussions. The queues have never been bad like this.

When Aether was WAY too packed for me to even login on Dawntrail's launch, I played on Dynamis to alleviate congestion on my own home DC. I don't use AFK macros as to not take up precious server space when I'm not playing. I'm playing my part and doing everything "right" to help alleviate congestion, and I'm still being punished. I'm now trapped in a data center transfer queue and can't even play the damn game because the transfer keeps erroring out and I have to start it over in hopes that this time will be the one. If I have to do this several times a week during the raid season I think I'm actually going to lose my damn mind. I can't even play the game with my siblings who live on Crystal because they're too afraid of traveling to Dynamis after hearing my horror stories.

Screw me for having friends on other data centers, I guess? Everyone always pisses and moans about how all the PFs for actual content are on Aether, but maybe I should just stay home and stop trying to branch out if it's going to be this much of a hassle just to play the game on other DCs.

Also, please stop making excuses for SE and blaming the players for something that is absolutely not their fault. This is no longer the era of small indie developer of a game with 300,000 active players.

[Eisweyr]

Tried to visit my friends on Primal from Aether.
Let's me pick Excal to move to, I choose to DC transer.
Now Im stuck in a loop of trying to transfer to Primal - get a 2021 or 505
Complete crash, while I have to input an OTP each time
Only to be stuck back into an unending ability to DC transfer.

Please either force load the person into the DC-
Since you were so kind to let them choose to DC Travel-
Or send them home

[Taytay]

It's broken. DC travel wasn't ready.

Put me back in DC travel jail. I can't get out of this stupid queue.

[Eskat]

Yeah, I've been stuck trying to DC travel queue, I can't get out of DC travel queue. I've been here for over an hour, getting booted every 2-15 minutes. It's frankly kinda terrifying to not even be able to say "never mind" and back out. I just want to play the game with my friends. I'm not trying to go to a big venue, or a crowded server, I'm just trying to get to Maduin in Dynamis, it's normally a ghost town. This really feels like Square just did not realize what bottlenecking the servers like this would do. It's not like we ever evenly distributed across all the servers, but this really does not feel like it has made it any better.

[Zandeth]

Went to do content with my friend on Dynamis, and now am locked out of the game as I sit in a cycle of unknown wait times and error code crashes trying to get back home.

[VoidsentStatus]

.

I'm going to assume within a few days if not tomorrow that they increase the cap on Dynamis for travelers because it's a hard lockout system currently. Once Dynamis can be where people meet up for raid, over half of the complaints are going to disappear. They probably underestimated how many ppl would end up using Dynamis and set the cap too low. Don't know how high they'll raise it though because eventually they wouldn't want Dynamis to turn into Aether 2.0 permanently. Safest route is to use Dynamis for rn after the cap is pushed up and afterward to just create alts on each data center if you wanted to raid with a multi-dc static. Run the raid on the data center of the most people, and then run it again on alts for the people that didn't get loot on their main after. Either that or only choose from your main data center when filling slots.

[Silaryn]

They literally talked about shutting off cross data center on stream as one of the solutions if things came down to it because at the end of the day, breaking up statics and venues is better having 75% of your region with no access to current raid tier PF content. If people actually handled the responsibility of data center travel properly and just visited other worlds instead of staying there all day and doing everything from there content wise, we wouldn't have been in this situation. Aether had 3-5k logins at Dawntrail with cross data center disabled. Their servers would've been massacred if it was triple by travel. They need to shut off people grouping up and have them spread out for hardware stability and overall content health.

This is an insane take. Imagine thinking that splitting up friend groups is a good thing.

[scatteringmyashes]

My static has people on three different data centers. Two of them took an hour to get over to Dynamis (where we planned to gather) and the others still haven't even gotten over. It's frustrating to know that we probably won't be able to raid tonight and I just hope this gets reversed before the week's out.

[Cat1234567890]

Some of you sound like genuinely miserable, friendless people. God forbid people have made friends and relationships with people cross server and want to travel for raiding. This was the worst time and worst way to implement these arbitrary population restrictions. It’s like absolutely no thoughts went into this before implementing it.