devs attitude to players

[Masked]

*snip*

Do a pathway. Even a -t shows the issue.

The issue isn't their data server, it's the buffer from their center --> primary servers.

You don't actually experience the latency issues UNTIL you're in an instance.

.300 is fine UNTIL you hit an instance where the .300 is added due to the fact that you're not actually instanced on the data center.

Now you have .600 ON TOP OF human response times...That's a no bueno...Especially for Titan.

I can actually show this perfectly via Twitch...I'll CLEARLY be out of the AOE/Landslide for 200-300ms and then boom, blown off the platform. -- I'm on F/O.

There's absolutely no reason for instancing not to have been ported to that data center and if they are, the .300ms tracer, isn't cutting it.

Yeah it is. But masked is being a bit misleading, unintentionally of course.
It is only illegal to selectively throttle a specific protocol, like say bit torrent, at the ISP level, while allowing all other protocols to pass with no throttling.
They can however throttle all traffic equally and be within the law. Its much like racial or gender discrimination, but for internet traffic.
Comcast lost a big case over throttling Bit Torrent, and lieing about it.

They purposefully throttled network traffic based on the packet ROT.

FFXIV is still a packet-transfer.

I wouldn't say I was being misleading as opposed to pushing a technicality.

Throttling is throttling regardless of individual service.

[Dragonskin]

Do a pathway. Even a -t shows the issue.

The issue isn't their data server, it's the buffer from their center --> primary servers.

You don't actually experience the latency issues UNTIL you're in an instance.

.300 is fine UNTIL you hit an instance where the .300 is added due to the fact that you're not actually instanced on the data center.

Now you have .600 ON TOP OF human response times...That's a no bueno...Especially for Titan.

I can actually show this perfectly via Twitch...I'll CLEARLY be out of the AOE/Landslide for 200-300ms and then boom, blown off the platform. -- I'm on F/O.

There's absolutely no reason for instancing not to have been ported to that data center and if they are, the .300ms tracer, isn't cutting it.

Right, and I'm not saying people that are talking about having issues are lying either. I have experienced it, but it's not consistant. For Tracert to be 100% accurate you should be hitting the same server every time. Do we know that when we go into an instance that we are going to the same server every time? I don't think we do even if you hit E or your region language as preferred.