Important Information Regarding North American Data Center Relocation

[Ama_Hamada]

It's not about "OMG my ping is 100 when it was 20 UNPLAYABLE I WANT MY MONEY BACK" (and for those who genuinely think that way - get a grip). It's about how they could have made it equal for everyone that the data center is officially supposed to serve. If they had said "we're moving the NA data center to better accommodate Oceanic players" then I would have been understandingeven though it sucks for me. But this was supposed to make it better just for NA. That being the case, then taking a page from Riot's book and moving to Chicago or Dallas would have been more in line with those objectives. Moving to Cali just flip-flops who gets shafted.

I'm sorry that you have to play with 200+ ping, but your acceptance of it is not a reason for the rest of us to shush. My friend is now playing with 150 and spikes into ~190, and while it IS PLAYABLE, it is NOT ENJOYABLE. We all deserved better and SE let us down.

Agreed, I only said that because it can make some aspects unplayable (people dying before Lustrate heals someone) this has more to do with the coding, not the ms increase, it is just the increase makes the faulty coding more noticeable.

FINAL FANTASY XIV was designed to be played in an environment featuring ping times of 200 – 220 milliseconds or less. Even if players experience an increase in ping times due to the data center relocation, as long as their times remain below 200 ms, then they may rest easy, for there should be no discernable difference in gameplay.

We expect that the players most likely to experience a significant increase in ping times will be those in Europe playing on an NA data center World. We will be working hard to minimize the anticipated increases, but there is the chance that based on their location, some players may be more severely affected by this relocation than others.

Here is what I want to point out and how I feel not enough research was given. It increased the east coast enough where it effected rotations, in south America it changed the game to unplayable. So SE is not aware of the time tight rotations people do to know or not if 30 ms >100 ms = means some jobs are no longer possible to optimize? So how can he say as long as it is under 200 ms it is fine and have "no discernable difference in gameplay" when 30ms to 100 is effecting rotations? They do not know the bad coding effects things that much. Some people are going to say it is fine, because they do not know to notice (or care) of the clipping that can happen esp trying to double weave in 100 ms. After the second ogcd, the follow up GCD will be clipped slightly doing that with that ping. MCH and NIN (as far as i know ) REALLY suffer from this.

This is more trying to tell SE it does effect us since they clearly did not know, based on what I quoted, and hope they really take a look at coding for SB. (and maybe move the servers to Texas for 5.0)



"with WTFast I was able do a wildfire rotation without any clipping. Not only did I see it not clip but it was quite clear when I had 2 sec left on wildfire letting me to pull down gauss and put in an extra ws" With my normal speed I clipped an ocd and even though I did fit everything in the wildfire, it blew up after the last ws, meaning I could not put in a gauss off ws like I could with WTFast. 70 ping to 120 ping is very noticeable with this game and makes the statement 'no discernable difference in gameplay' a false one. To me that means the game needs to be coded better. I am not paying 9.99 on top of my sub and overpriced retainers over game shortcomings, please improve the coding"

As for the PC not detecting it I was told it wouldn't because how its run through wt's vpn