Animation lock is ping-dependent, as time spent before the server response is ignore

Date & Time: The past several years of play
Frequency: Every weaponskill and ability cast
World name: All
Class/Level: All Disciples of War and Disciples of Magic, Level 1-90
Party or solo: Either
In-game time: N/A
Area and coordinates: N/A

This issue impacts the moment-to-moment gameplay on average-to-high latency, resulting in artificially sluggish combat as every action's animation lock is extended by twice the connection delay.

Some jobs, such as Machinist, simply cannot be played optimally on average to high latencies as a result - while a player with low latency has plenty of time to weave two charges of Ricochet and Gauss Round between their GCD actions, a player with high latency will only be able to execute these skills extremely slowly, fitting no more than one off-GCD cast.

Unfortunately, because this issue is ping-dependent, I believe it's likely to have flown under the radar of the development team until now - while it's an egregious and relatively well-known problem in the EU and NA regions, to the point of third-party tools being developed to address it, the JP region is geographically small enough for the latency to never exceed a critical point.

The issue in more detail:

Upon using any action, the game will normally apply about a half second of animation lock, preventing you from using another action for a brief moment. When the server processes that action, it responds with the total appropriate animation lock for that SPECIFIC action.

The problem arises with how the game seems to be handling this response.
At current, the game DOES NOT TAKE INTO ACCOUNT how long it took for the response to arrive after the action was used. This effectively lengthens the intended animation lock by the given player's latency.

As a result, on connections with even just around ~100ms latency, every action will take a full fifth of a second longer to fully execute. This interferes significantly with gameplay, making some move combinations impossible for some players without delaying their next GCD cast.

As an example, let's say a certain action is intended to have 600ms of animation lock.
With 20ms latency to the server, it will take around 40ms total after the action is performed until the game client receives the intended duration of the animation lock from the server - 20ms there, 20ms back.

By the time the server response arrives, the character has already spent 40ms in animation lock. Because the game erroneously does not subtract these 40ms from the intended 600ms, the total animation lock lasts for 640ms.

However, on a high latency connection, this becomes a lot more egregious - a player with a latency of 150ms will find each action taking a full third of a second longer than intended. 150ms as the game communicates the action to the server, 150ms as the server responds, and then the FULL 600ms of communicated animation lock, totalling a 50% longer downtime of nearly a full second.

The player with 640ms animation lock might still be able to use their following actions normally, but the player that - for the same action - is stuck with 900ms of animation lock might run into various issues. Primarily, they'll likely lack time to weave more than one oGCD action between each cast, even at a normal skill speed appropriate for their played job.

As mentioned before, especially in the EU and NA regions where continental distances between players and servers are likely to be much longer than within Japan, this has been known and debated for a while, resulting in the development of third party tools that directly rewrite the information received from the server to correct for the delay, in an effort to work around this bug.

But ideally, none of that should be necessary.
All it'd take to address this issue is to properly subtract the time between the action and the arrival of the server response from the communicated animation lock.

In case this summary did not contain enough information, here are some other occasions where this issue has been discussed, unfortunately so far never as a proper bug report:

https://forum.square-enix.com/ffxiv/...tions-normally.

https://twitter.com/perchbird_/statu...34091780186120

https://old.reddit.com/r/ffxivdiscus...nimation_lock/

https://old.reddit.com/r/ffxivdiscus...on_tools_like/

https://github.com/Soreepeong/XivAle...-timing-helper

Personally I see this on jobs I play such as dancer where I can not press the next actions until the server responds.
This is a difficult problem to solve, but I hope a better solution can be achieved.
Some of this has to do with anti-cheat measures to force the client to wait until the server says it is OK to resend the next command.

What really needs to be resolved is the lag issues, which have been reported in other threads, and I believe this will also resolve these issues.

But, even if the client was able to send data to the server without waiting for the response... the client would eventually get queued up with many packets to send the server and will be playing "catchup" so some of these measure are also to assist with stability issues. How many packets can the client queue up, or how many packets can the server handle if it receives a "burst" of queued up packets?

This happens a lot with me, and the only thing I can to as accept it as it is, the game is still playable but there will be issues with DPS and being able to perform "rotations" optimally.
Personally I accept it as there are times some routes in the internet can be flakey or inconsistent with response times do to the very nature of the internet and data packet congestion.

Ultimately I believe the server lag needs to be addressed, which is very difficult to identify the root cause, but I believe it is being looked into.
With issues in the housing system now though, attention appears to be spread out in the dev team to address other issues as well.

Here are a couple threads that are in a response to the latency issues.


You have not provided a system report so we can not see which client you are using but here are some related threads.
Please do specify your platform, as some bugs like this can be platform specific at times, if not provided this may be moved to "not enough information."

Please also search a little to see if the bug (or similar) has been previously reported before posting a new one, this helps alleviate the load on the community team whom review these.

PS4 (accepted for review bugs)
https://forum.square-enix.com/ffxiv/...in-Aglaia-Raid

Windows 10 (accepted for review bugs)
https://forum.square-enix.com/ffxiv/...ed-after-patch

With the above information, there are a few things that can be tried.
Without stating this information it is difficult to know where the issue is.

Have you disabled any firewalls or antivirus software? These can "shim" between the game and the internet and inspect packets causing a delay.
Have you contacted your ISP to see if there is anything that can be done on their end?

Please provide details if your ISP, it is difficult to see if there is a pattern without this information.
It is possible the route from your ISP is where the issue is, and that information is necessary to proceed with an investigation.

Please also provide your "system information" to see what drivers are being utilized.
There are a LOT of different PC configurations (if your platform is PC) that can have a variety of compatibility issues.

Are there any programs running in the background that are utilizing internet bandwidth?

Sorry to say all this above would be covered if you used the template to report your bug.

https://forum.square-enix.com/ffxiv/threads/65378

Yes it is time consuming to fill out, and the information is most likely somewhere on the server (server knows what client you use) but this is a burden for the team confirming these bugs to have to dig up, but please help them out and provide as much detail as you can, it will speed up the investigation.

Neola, this is a very well-known issue among high-end FFXIV players to the extent that some even go to third-party tools that directly rectify the issue described - and the problem goes away. While it's against forum rules to discuss third party or ToS breaking tools, there is a lot of research on this specific issue and it is completely game dependent. It is not ISP related. It is not "other software running on the computer" related. It is not FFXIV server related. That is a fact.

If one is just complaining, then you can withhold any information you see fit.

If one is asking for help, one should provide information requested by the people being asked. Even if one feels they 'know it's not useful'.

Humor us.

Quote:

---

Originally Posted by Breakbeat

If one is just complaining, then you can withhold any information you see fit.

If one is asking for help, one should provide information requested by the people being asked. Even if one feels they 'know it's not useful'.

Humor us.

---

You're right, of course. Since this issue is known widely enough that I'm confident it's not a "me" problem, I initially skipped the step of providing information on my specific setup - since reducing my personal latency would not address the wider problem for everyone else affected. As far as I can see, the problem isn't that latency exists, it's how it's being handled by the animation lock system.

In any case, here goes:

Platform: Windows PC
ISP: Vodafone Germany
Type of Internet Connection: CATV
Internet Connection Speed: 500Mbit/s

- Disabling my firewall and antivirus did not affect the issue
- My ISP (Vodafone Germany) stated they were unable to help with specific software. If it helps, this problem is unique to FFXIV, I have not encountered anything of the like on high-latency connections in other games.

The issue is most egregious when playing on a data center far from where I live, such as playing with friends on another continent.
Again, it's not simply an issue of the latency itself - though this has effects on e.g. the timing of AoE indicators, these are unavoidable, whereas the animation lock handling is absolutely a fixable issue.

In addition to people in the threads I linked in the first post, several of my friends have reported being stuck with the same problem.
Some of them have used tools like XIVAlexander to address it, in the exact way stated, and the problem went away.

I'd also like to clarify my perspective on some of the points stated here:

Quote:

---

Originally Posted by neola

What really needs to be resolved is the lag issues, which have been reported in other threads, and I believe this will also resolve these issues.

---

As stated, I'm certain that even on higher latencies, this problem can be addressed - it's exacerbated by lag, but not inevitably caused by it, and to a degree it affects connections of any latency.

Quote:

---

Originally Posted by neola

But, even if the client was able to send data to the server without waiting for the response...

---

Yes, absolutely. This isn't the proposed solution - instead, after getting the response, the client must take into account how long the response took to receive.
By subtracting the wait time from the communicated animation lock, the actual animation lock of the character will be equal for players of any latency.

Quote:

---

Originally Posted by neola

This happens a lot with me, and the only thing I can to as accept it as it is, the game is still playable but there will be issues with DPS and being able to perform "rotations" optimally.

---

Yeah, I thoroughly agree - it's a very unfortunate state of things.

Quote:

---

Originally Posted by neola

Personally I accept it as there are times some routes in the internet can be flakey or inconsistent with response times do to the very nature of the internet and data packet congestion.

Ultimately I believe the server lag needs to be addressed, which is very difficult to identify the root cause, but I believe it is being looked into.

---

Since this issue has - from what I'm hearing, though I can personally vouch for having this exact issue since post-Stormblood - existed for about as long as the game itself has, I don't believe that it's tied to any current Endwalker-specific lag issues.

While the bug is networking-related, I'm trying to relay that (unlike many networking issues) it's categorically not related to any given player's individual hardware situation.
This is a problem that exists in the netcode itself, verified independently by several groups of players over the years, and so far not addressed.

Because the animation lock problem disproportionately impacts high-latency connections, the development team may not be fully aware of the extent of it.
(I'm fairly confident that most software engineers would be fairly disturbed to hear about it, at that...)
But addressing the issue would go a long way towards reducing the sluggishness of play on high latencies, and players that use tools like XIVAlexander to artificially implement the suggested fix have reported results to that effect.

While I'm a complete stranger to you, having explained the situation as best I could, I ask that you trust my judgement this far - I posted in the Bug Reports subforum rather than the Tech Support one because this is a bug inherent to the game, affects all players bar none (though unequally), and can't simply be addressed on my (or any other player's) end, short of resorting to potentially disallowed third-party tools that I'd prefer to avoid.

I have no more direct way of ensuring that word of it reaches the people that can actually fix the problem at the root than by posting here.
But the problem can be fixed. In the end, it's more of an issue of developer awareness than a technical hurdle.

I'll cooperate any way I can.
In return, please take into account that this bug is neither unavoidable, nor will it go away on its own even once the server-side lag issues you mentioned are resolved.

Quote:

---

Originally Posted by hyperion995

Neola, this is a very well-known issue among high-end FFXIV players to the extent that some even go to third-party tools that directly rectify the issue described - and the problem goes away. While it's against forum rules to discuss third party or ToS breaking tools, there is a lot of research on this specific issue and it is completely game dependent. It is not ISP related. It is not "other software running on the computer" related. It is not FFXIV server related. That is a fact.

---

Hyperion has the right of it here.
Let me know if there are further steps I can take to help prove that this is not a personal issue - though originally, I'd hoped that everyone else's talk of it outside these forums would be proof enough.
I was amazed when I found no actual bug reports on it in this specific subforum - conversely, you'll find the bug routinely acknowledged by players in the General Discussions section. The aforementioned tools are commonly brought up, by name, as life-savers for circumventing the bug. But they shouldn't have to.

Surely, the devs look through commonly used plugins and third party tools and look through places like Balance discord to track these sorts of things? I sincerely doubt they dont know about this issue, and if they dont...thats not a good sign of their awareness of the community and how people play the game.

That said, I hope they see this and fix it. People shouldnt be using third party tools to level the playing field. Incidentally, in addition to ping affecting animation lock, your FPS also changes your effective GCD...and as such third party tools exist to fix your FPS at a level that shortens your GCD the most. Outside of extreme cases, players SHOULD NOT have an insurmountable gameplay advantage by having a more expensive graphics card or living closer to the server, especially when both can and are fixed by third party tools.

This is an incredibly important bug that makes the game feel worse to play and I really hope SE notice and address it ASAP.

This server response delay is the difference between someone being able to double weave (or even triple weave) and considerably destroys DPS making content harder than it needs to be

This is now under investigation on the JP side as there is now a public announcement, plus a thread collecting tracert information.
However, this topic is for those living in Japan only at the moment.
This should begin to help pinpoint the lag issues for players, if it is client based lag it should also be identified.

It has also been said that this is also being tested on the development servers, but no major lag issues are showing up so the investigation is proceeding to ask players (in Japan) to submit tracert, ISP, and residing city to further expand the investigation. Please be assured there is an investigation underway to pinpoint lag issues.

Japan residents may assist by submitting your information, even if connecting to the NA datacenter (such as myself) may aid in the investigation efforts.
I believe only submit your information if you are experiencing lag or server disconnection issues as well, so no need to participate if you are not experiencing these issues.

The topic collecting information (this is for Japan residents only)
https://forum.square-enix.com/ffxiv/threads/461702

The announcement regarding this (Japanese)
https://jp.finalfantasyxiv.com/lodes...4ce11d545b48cb

Quote:

---

Originally Posted by neola

This is now under investigation on the JP side as there is now a public announcement, plus a thread collecting tracert information.
However, this topic is for those living in Japan only at the moment.
This should begin to help pinpoint the lag issues for players, if it is client based lag it should also be identified.

It has also been said that this is also being tested on the development servers, but no major lag issues are showing up so the investigation is proceeding to ask players (in Japan) to submit tracert, ISP, and residing city to further expand the investigation. Please be assured there is an investigation underway to pinpoint lag issues.

Japan residents may assist by submitting your information, even if connecting to the NA datacenter (such as myself) may aid in the investigation efforts.
I believe only submit your information if you are experiencing lag or server disconnection issues as well, so no need to participate if you are not experiencing these issues.

The topic collecting information (this is for Japan residents only)
https://forum.square-enix.com/ffxiv/threads/461702

The announcement regarding this (Japanese)
https://jp.finalfantasyxiv.com/lodes...4ce11d545b48cb

---

This is a different issue. Ping affecting animation lock is not the same as packet loss-related lag.

Quote:

---

Originally Posted by neola

This is now under investigation on the JP side as there is now a public announcement, plus a thread collecting tracert information.
However, this topic is for those living in Japan only at the moment.
This should begin to help pinpoint the lag issues for players, if it is client based lag it should also be identified.

It has also been said that this is also being tested on the development servers, but no major lag issues are showing up so the investigation is proceeding to ask players (in Japan) to submit tracert, ISP, and residing city to further expand the investigation. Please be assured there is an investigation underway to pinpoint lag issues.

Japan residents may assist by submitting your information, even if connecting to the NA datacenter (such as myself) may aid in the investigation efforts.
I believe only submit your information if you are experiencing lag or server disconnection issues as well, so no need to participate if you are not experiencing these issues.

The topic collecting information (this is for Japan residents only)
https://forum.square-enix.com/ffxiv/threads/461702

The announcement regarding this (Japanese)
https://jp.finalfantasyxiv.com/lodes...4ce11d545b48cb

---

Seconding what geebster said, I'm afraid there's a misunderstanding here. I've tried to explain the bug in further detail after your first response. Please keep that information in mind.

Taking into account the above responses, and an "animation lock" please understand that this may be a "feature" rather than a bug, and is working as intended.
It may be an unwanted "feature" but may still be a "feature" that is working as intended and server response is necessary.

While this "animation lock" could be removed and the delay removed, it is very possible there are technical reasons behind why this is in place.
Many players use methods to reroute their internet packet data to lower the delay, such proxy servers or VPNs, I hear, can reduce latency.
Using such a service is in no violation of the terms of service as this is just a way to control how your data packets are routed to the server (and back).

Let me give one example, in the game FFXI there is also an animation lock on some abilities. At one point the development team removed the the animation lock for these abilities but by doing so introduced a whole new set of bugs and ways to exploit the system. Please consider that this may also be the case here. This may very well be a feature in place to prevent other bugs from happening.

What would happen if the client did not wait for the server's response and kept sending data?
Is there some data in the response packet that needs to be inserted into the next packet sent to the server?
Can this be exploited in some way or introduce system instability? We don't know without testing.
If the server is all of a sudden hit with a burst of delayed packets, will that cause server instability?

From a technical stand point it is possible that these limits are in place to prevent specific bugs, unwanted stability, or exploits from being introduced into game play.
While this animation lock could be altered or removed, it is very possible it is not as easy at thought.

In the regards to this, I believe the development team has decided to put their efforts towards pinpointing the source of the lag and packet loss issues and in doing so should ultimately improve game play in this respect.

Personally I just did a tracert myself and have a 120ms ping to the server, is that high? I don't know, but the game is perfectly playable without issues. I have not experienced any disconnections lately personally, but there are now issues locally in Japan that are concerning players, hence the announcement above.

In all the content that I do I have never experienced lack of DPS causing issues to meet a DPS check due to lag.
I honestly believe the game is balanced in such a way that a high latency player can still provide enough DPS to clear contents without issue.
Perhaps a player may do more DPS with a lower latency, but that is the nature of the internet and this game.

If this is to be investigated further other information needs to be provided.
As stated above, if other players know that the a packet is sent to the server and takes 50ms then the client must wait for the response then unlock the action, how do we know this is how it functions?
This testing needs to be able to be reproducible in a development environment so steps to reproduce it need to be clearly provided.

Software such as a packet sniffer WireShark can be used to see the timing of the packets to and from the server, however, the contents of these packets are difficult to understand except to the development team.
We need detailed information about the contents of these packets to investigate this properly ourself, which might not be feasible and confirmation would be difficult.
Reproduction of the claims on other internet sites would have to be possible as well.
If you "feel" you get less combos and DPS in we need a way to analyze these, which no one but the development team knows best and possesses the right tools to do this properly while balancing the game.

Although information may have been posted elsewhere, these forums is where the development team looks for bug reports and the steps to reproduce and verify these bugs.

The steps, software used, how we know that the animation lock works the way it does, etc, needs to be provided here to aid in an investigation, if this is not working as intended.
Concrete steps to reproduce, verify the issue, and reproduce it is very important otherwise it would be difficult to proceed and actually say there is a flaw that needs to be confirmed and fixed.

However, if this is working as intended, then an official answer from the development team or community team is needed.
We honestly don't know if this issue is intended behavior or not.

It appears the development team has made the decision to trace down the lag and packet loss issues, as eliminating these issues would also reduce the "animation lock" timing issues as well.
As stated in the very first post, when the connection shows lag (ping-dependent) the "animation lock" timing is affected. Therefore I do believe the lag and packet loss issues are very much related to this.

If this is rather a request to alter or remove the "animation lock" from the game as it is considered a bug, then this is a completely different subject, in my personal opinion.

What would be best if there was confirmation from the development team or community team confirming the observed behavior.
Until that time we do not know if this is intended behavior or not.

Use of a third-party tool, if available, would not be recommended as it may cause difficult to track down issues or server and/or system instability effecting everyone's game play.
We have no way to test and verify if a third-party tool would cause harm to the game or other player's experience without proper official testing.

In the mean time, the use of a proxy or VPN server may reduce latency in order to improve game play.

Quote:

---

Originally Posted by neola

Taking into account the above responses, and an "animation lock" please understand that this may be a "feature" rather than a bug, and is working as intended.
It may be an unwanted "feature" but may still be a "feature" that is working as intended and server response is necessary.

While this "animation lock" could be removed and the delay removed, it is very possible there are technical reasons behind why this is in place.

---

The problem isn't that animation lock exists. The problem is that connection speed is affecting it in a broken way. This is a problem with the programming of the game client, not the server or the individual player connections.

Quote:

---

Originally Posted by neola

Many players use methods to reroute their internet packet data to lower the delay, such proxy servers or VPNs, I hear, can reduce latency.
Using such a service is in no violation of the terms of service as this is just a way to control how your data packets are routed to the server (and back).

Let me give one example, in the game FFXI there is also an animation lock on some abilities. At one point the development team removed the the animation lock for these abilities but by doing so introduced a whole new set of bugs and ways to exploit the system. Please consider that this may also be the case here. This may very well be a feature in place to prevent other bugs from happening.

---

This is missing the point. Nobody is talking about removing animation delay entirely. I'm no longer sure you read any of our explanations of the issue at all.

Quote:

---

Originally Posted by neola

In the regards to this, I believe the development team has decided to put their efforts towards pinpointing the source of the lag and packet loss issues and in doing so should ultimately improve game play in this respect. [...] It appears the development team has made the decision to trace down the lag and packet loss issues, as eliminating these issues would also reduce the "animation lock" timing issues as well.

---

Fixing the temporary lag issues WILL NOT fix the issue described in this thread. It has existed before the current connection problems, and it will exist after they're gone unless it's directly adressed.

Quote:

---

Originally Posted by neola

As stated in the very first post, when the connection shows lag (ping-dependent) the "animation lock" timing is affected. Therefore I do believe the lag and packet loss issues are very much related to this.

---

You're mistaken. They are all network-related issues, and this bug affects higher latencies stronger than lower latencies, but it exists for connections of ALL speeds.

Quote:

---

Originally Posted by neola

If this is rather a request to alter or remove the "animation lock" from the game as it is considered a bug, then this is a completely different subject, in my personal opinion.

---

It's not! It is not! That was never the issue!
The bug is that the duration of the animation lock is applied improperly and unevenly.

For example, you mentioned having a ping of 120ms (where ping generally measures round trip time, meaning it takes ~60ms to reach the server and another ~60ms for the response to reach your game client).
In your case, an ability that's meant to have 500ms of animation lock would erroneously have roughly 620ms of effective delay, about 25% longer than intended.
That same ability, for a player with a delay of 50ms, would have 550ms of animation lock instead, purely because that delay is not taken into account when the information received from the server is applied.

In the correct implementation, the game would:
1) register your use of the action, communicate that action to the server, and lock your character until a response is received
2) receive the server response, with the information that your action has 500ms of intended animation lock, roughly 120ms
3) reduce the 500ms by the time your character has already been locked, i.e. the 120ms that elapsed between 1) and 2)
4) apply that remaining animation lock of 380ms to your character, resulting in a total lock of the intended 500ms. The first 120ms before the server confirms the total duration, the rest after. Seamless.

Currently, the game already does step 1 and 2, but not step 3.
After receiving the response, it naively applies the full duration received from the server, regardless of how long it took for that information to arrive.
As a result, the animation lock lasts longer than intended by the server on all player connections.

As I understand it, existing third-party tools get around this bug by intercepting and rewriting the information received from the server to implement this fix artificially.
But they shouldn't have to. This is an honest mistake in how the game client handles the response.