[Feedback] Data Center Travel Changes

[Qorani]

Then surely a fair amount of the issues that you cited are either nonexistent or significantly reduced at the moment?

Also, to not post twice regarding your previous discussion about queues on savage patch day. Despite all of the extended queues for DC travel, throughout the day as I hopped from DC to DC delivering gear, and even during peak hours going to Dynamis, my login queue when I got there was never more than 30-40 people. On day one of savage, during peak hours. If anything you said about "you should have expected high queues" is accurate, that means that they moved all of the login queues to DC travel queues that we're actively crashing and throwing errors. Even if it was intentional for them to shift the queues to DC travel, errors and bugs are not intended.

Not even to mention the issue of still having to pick a non-crowded server to jump to when you start to DC travel being potentially locked to DC travel players for long periods of time when you get there. I tried to go to Primal during the middle of the day today, when congestion was reasonably at its lowest, and still couldn't get in.

Stop defending the problem and start proposing a solution that people can agree on.

[ObscuraFi]

Then surely a fair amount of the issues that you cited are either nonexistent or significantly reduced at the moment?

Significantly reduced. Bozja is hit or miss depending on the day, market is slowly building up but not main data center level yet, other areas such as queue's are better, casual pvp is popping. Instead of PF being blank or having 2-3 listings we have 6 Extreme pf's and 27 Savage PF's currently.

As for the queue system during peak, JP twitter already stated that these errors are not problematic. There is no mention of them even trying to fix it.
https://x.com/FF_XIV_JP/status/1818498557399466211
"About data center travel congestion
Since patch 7.05, the number of users using Data Center Travel has increased significantly, and we apologize for the inconvenience caused by the congestion.
If the estimated travel time displayed when selecting the DC/world to move to is "Expected to take a long time due to congestion", the wait time for data center travel may exceed 1 hour because it is extremely crowded, or Errors may occur due to timeouts.
Even if the client closes due to an error while waiting for your turn after applying for a move, the data center travel process itself will proceed without any problems, so we apologize for the inconvenience, but please wait for a while. Please restart the client after that.
Please note that if the character selection screen is displayed at the data center before the move, it means that the application has not been completed, so please apply again."

They just released a known issue after patch 7.05 lodestone that made no mention of the login errors. That has to be something they can't fix.

And there is no solution to be agreed on. Yoshi P flat out said he wanted to get rid of discrepancies between the worlds and data centers. Data Center Travel creates discrepancies from how the community uses it when it's completely free and not restricted. Even if they disabled PF/DF use, disabled MB use, you still mess up the logins on that world and create barren social areas from where you left that Yoshi P said they do consider. Places like Uldah/New Gridania/Limsa they want populated for newer players. Your presence on another DC is problematic in itself if its not for a really short time period. They implemented it, the community segregated and messed up the health balance of the worlds, and now it has to be taken away if Square doesn't want to invest 3 years of development time just to possibly find a different solution. Development time that could be spent on other things that are more valuable in the day to day of the player base. No world/DC including Dynamis is going to be opened up without restriction because the community will flood it and create another Aether. This isn't the negotiation stage, this is the head of the ship already decided the direction of the feature and you have to deal with it.