Imagine a player who lives right next door to the servers.
Any time you spent waiting for the server's response, is simply additional animation lock time. The server's response contains additional animation lock data, which the game client then applies again, at the time of the game receiving that information. Then, you must wait for the server's response. So, when you press an action in game, you are automatically put into animation lock by the game itself. The further away you are from the servers, and the longer and more complicated the electrical "route" taken by those information packets, the more of a delay there is between you pressing a button in-game and then seeing the result. It takes time for the information sent by the game client to reach the server, it takes time for the server to process that information, and it takes time for the server's reply to make its way back to your computer. So, how does latency come into it? Well, receiving information from the server is not instantaneous. This is called "clipping" your GCD, and it causes all sorts of problems regarding your character's DPS output and how their cooldowns align. If your character is still in animation lock when your GCD spin is ready, you cannot use your next GCD until the animation lock is over. using off-global cooldown abilities during the wait time between GCD spins. This has consequences on the act of "weaving" i.e. What does this mean for gameplay? Characters cannot use any actions until their current animation lock has expired.
This new animation lock value is typically around 600ms, but some actions have more. The game client takes the animation lock value given by the server and applies it AGAIN to your character, overwriting any time remaining on the initial 500ms. This information from the server also contains animation lock data for the skill that was used. This information travels to the server, where the server processes it, and sends information back to the client to let it know things like the damage of the attack. The client also sends information to the game server, to let it know the client has used that action. half a second of animation lock to your character, which prevents you from using any other actions. In Final Fantasy XIV, when you press an instant-cast action, the game client (on your local hardware), applies 500 milliseconds (ms) i.e. Yoshida's response seems to indicate that he doesn't really quite understand the issue on a crucial level, so I'm going to explain how animation lock works in Final Fantasy XIV and give Yoshida the information he requested.
0 kommentar(er)
