Can we please, have a modernization for the servers. (Specifically, tick/refreshrate)

[Jeeqbit]

We're talking about the tick rate of ffxiv servers... i mean, the rate of information being updated

Alright but that assumes everything is single-threaded, which it very well could be. There would have to be a main server loop and that could refresh at any interval they want, but we can't see their code and to what extent they actually do operations side-by-side.

Using a single thread is something from prehistoric times. It's 2023 and it would be surprising if they didn't use multiple threads. But I can't see their code, so.

What bothers me about your response is the ignorance that you think you know what you're talking about.

Because I do know what I'm talking about. There is a such thing as threads (where operations happen side-by-side) and we can't necessarily see whether they make use of them or how they have gone about any of this, but I made an extremely clear example of a loop in my previous posts that is visible at hunts in particular as well as an example that can be reproduced of the difference between Sidewinder and Bloodletter.

If what you said was true it would apply to all MMORPG's we play. So you're empirically just wrong.

I remember ping affecting me in other games actually, but maybe that is when ping is 200-300 ms and maybe when internet wires weren't as good as they are now. I also agreed that other games don't suffer these animation delays.

This has almost nothing to do with ping. Besides the fact i have a 20 ping im in Austria/Europe.

I don't think I've quite played at a ping that low so maybe it is harder for me to distinguish. I wasn't saying there isn't a refresh rate either. I just find the animation delay to be the more significant issue ie. difference between Sidewinder and Bloodletter.

All the other issues with snapshotting and movement, I just don't find to be a big deal to me at all and don't cause me any problems even at 200 ping.

Because your client only gets the ACTUAL position every 0,3 seconds.

Now let's say this is the case and it affects casts. Someone said they have to move by 75% of the cast bar. A refresh rate of 300 ms out of an average cast of 3 seconds (3000ms) is 10%, not 25%. You would have to have 450 ping to need to move by 75% of the cast bar. Even so, that's normally plenty of time with legacy movement.

Let's apply this logic to an interrupt. If a cast is 3 seconds (3000ms), you would have to use the interrupt by 90% of the cast bar in order to guarantee it registers, which isn't much of a problem. But that isn't the only factor, because there is ping (let's assume the ping is 200ms) and an animation delay (let's assume this is 300ms because I don't know the delay for this specifically). Now you have to use it by 75% of the cast bar. Which is tighter but still doable.