[Feedback] Data Center Travel Changes

[Sove92]

We live in a time where SE self-DoS's their own service, and it's not even a server struggle, like back in EW launch. And even in those EW days, you could at least get in queue...

Now it's simply because of an arbitrary decision that has nothing to do with actual server load.

[Roehann]

We live in a time where SE self-DoS's their own service, and it's not even a server struggle, like back in EW launch. And even in those EW days, you could at least get in queue...

Now it's simply because of an arbitrary decision that has nothing to do with actual server load.

Agreed! I am stuck in limbo myself.. Can't log into any server, any world, not even my home world.. Got caught in a data center transfer... SE if you aren't going to let us travel, then just stop us at the door, don't let us get away from home and THEN shut us down..

[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.

[CuteBucket]

Logged in to start savage raiding with my static earlier. We can't. We started our static in early Endwalker and have people from three different datacenters in our team. We were prepared to be on Dynamis to raid, we go there often anyway, but today we can't even do that. Everyone who wasn't already on the server from last night can't get on. It's been almost an hour and no one has been able to get to Dynamis to start raiding.

After the trashfire that was the Dawntrail MSQ, raiding with my friends and the social community scene of the game were the only things keeping me from unsubbing. If this isn't fixed VERY SOON, then that's it, I'm done, I'm out. The story went to shit and I can't even play the game with my friends anymore.

[xoci]

I (and many other people) went about static hunting for this savage tier under the assumption that world and data center travel would work like it has up to 7.01, and formed groups consisting of players from different data centers. However, the newly implemented world/dc travel changes make it really difficult, if not impossible for these cross dc raid groups to actually meet up to raid.

I understand that the changes are intended to even out player population, but this should have had at least several weeks prior notice before implementation so people would know to form groups consisting only of people from the same data center, and definitely should not have been spontaneously implemented the same patch as savage release.

(on a different note, i asked a friend on primal to make my raid gear for this tier and now i cant go pick it up!)

[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.

[xoci]

-

Funny thing, I was gonna meet up with my friend to pick up gear on Dynamis, only to end up trapped in the rift between dcs. as for raid alts, unfortunately you have to drag that alt through all of msq which, at this point, is Really Freaking Long. I have an existing alt in Endwalker, but there's no way in hell I'm gonna be able to finish all of Dawntrail in the 20 hours I have until my static meets.

Anyway my main issue is the fact that this came out of literally nowhere. If I knew they were gonna do this ahead of time, I would have just joined an aether-specific static to begin with... Decisions like these have to be communicated well in advance, especially when it comes to game content that people literally make plans for months ahead of time.

[VoidsentStatus]

If I knew they were gonna do this ahead of time, I would have just joined an aether-specific static to begin with... Decisions like these have to be communicated well in advance, especially when it comes to game content that people literally make plans for months ahead of time.

Agreed. Though a part of me thinks that the original limitation was a test. And they probably liked what they saw over the few weeks they had it in place and didn't want to remove it but knew a complete shut out like before was likely going to be too much outrage so they decided to replace it with a nerfed version. The fact the new announcement has no planned end date/time, tells me that they wanted something like this permanently. They're going to work out as many kinks as they can in the current system and prob keep it if I had to guess.

[xoci]

Honestly the changes in general are also Pretty Bad, but they'd have been taken with a lot less abject vitriol if they had been communicated properly.

DC travel is the kind of thing where, once you open Pandora's Box, there's no way to put it back without completely alienating a large part of the current population that joined the game after DC travel was implemented. People have built communities in game that rely on DC travel and it's weirdo behavior to go "okay screw your friend on another DC that doesn't want to play this game without their friends."

[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