How is it a self fixing issue when they are suspending it until further notice ? They are delaying the "big boom", nothing else.Money that comes out of the Yearly budget to fix a self-fixing issue.
Imagine having to rent a bunch of servers on a short-term lease and only getting two days of use out of them and hiring a bunch of network engineers to install and format them across 3 physical locations for again an issue that will fade in like one or two days. its not chump change
But what about the people stuck on other DCs?tbf what could they of done not release it? There is no point in building a system that could handle 15k requests a minute when in normal use it wouldn't see numbers that high. just need to wait for the player base to get the novelty out of their system anything breaks when you push it past its limits.
At the least they should've planned something for that. I imagine they could've made it so that if they had to turn the feature off that they could have also made it so that people stuck on foreign DCs could return to their own still.
That means you can't use it again until things get fixed. Which means no new travel requests, which means less and less server load the more people get through. I hope you can manage to understand the rest.
Why did I know that this was gonna be a shitshow lol
just chill out and have some patience, you not going to starve to death on the other DC.
I imagine there are some technical limitations that stop them from just booting you back to your home DC. I imagine there are checks and balances between the DCs when you are sent back to avoid any weirdness.But what about the people stuck on other DCs?
At the least they should've planned something for that. I imagine they could've made it so that if they had to turn the feature off that they could have also made it so that people stuck on foreign DCs could return to their own still.
Yes, this was predictable.
No, it's not SE's fault. It's players fault for using it at the same time. Why would you use Data Center Travel right after the patch release when you know a lot of other people will be?
It's like logging in when an expansion release and not expecting a queue. Duh. What did you expect?
In other news, there is no technical debt from 1.0.
"We don't have ... a technological issue that was carried over from 1.0, because ARR was meant to kind of discard what we had from 1.0 and rebuild it from the engine."
https://youtu.be/ge32wNPaJKk?t=560
Yes, lets blame the players for using the only advertised feature of this patch.Yes, this was predictable.
No, it's not SE's fault. It's players fault for using it at the same time. Why would you use Data Center Travel right after the patch release when you know a lot of other people will be?
It's like logging in when an expansion release and not expecting a queue. Duh. What did you expect?
You'd expect long queue times, not the entire system shutting down. Imagine players wanting to use a feature of a game they pay for.Yes, this was predictable.
No, it's not SE's fault. It's players fault for using it at the same time. Why would you use Data Center Travel right after the patch release when you know a lot of other people will be?
It's like logging in when an expansion release and not expecting a queue. Duh. What did you expect?
In other news, there is no technical debt from 1.0.
"We don't have ... a technological issue that was carried over from 1.0, because ARR was meant to kind of discard what we had from 1.0 and rebuild it from the engine."
https://youtu.be/ge32wNPaJKk?t=560
It's not like this feature wasn't released in 6.18 specifically so its issues, like these ones, can be sorted out in time for 6.2. It's better to have the system stress tested during content drought than when new major content releases.
This feature was originally intended to launch in the 5.5x patches, exactly so the devteam can iron out the kinks in time for EW launch. That didn't work as planned due to lack of hardware.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.