Amazon Evade Bug

[Ruvanal]

Kind of difficult to accept desynch, and the known problems it carry on BNet and Lan/TCP-IP games, at Ping 10. And even then, I am writting over several hours sessions testing what I wrote.

There are two primary ways to get desynch. The first is the more familiar problems that come from high ping levels; greatly delayed commands or commands completely lost. The second method of getting desynch is when the client processes an action in an entirely different manner than the server and this is completely independent of the ping between the client and the server.

Look at it this way, character is doing a 'slow attack sequence' on a monster (Zeal, Fend or just plain old very slow weapon). Part way through the attack the server calculates that the player is hit and goes into GH animation (get-hit or 'stun'); the client on the other hand does not process it in this way and continues to display the attack going off. With an attack that is being handled by a continuos holding down of the mouse button, the client will not send another attack until the previous is finished. When it does send the packet for the next attack the server may instead be showing that the player is still in GH animation and discard the command. By the time that the server is completed with the GH animation and ready to allow the start of another attack sequence, the client will be in the process of displaying an attack that is not really happening and will not be attempting to send any attack initiation packets. Meanwhile on the server side the game is treating the character as just standing there and the monster are free to continue having 'free' attacks on the player since the player is not actually attacking the monsters to cause them anything like their own GH animations. Since they have ample time for 'free' attacks there is a good chance to have the character back in GH or BL animation at he time the client is going to auto send another attack initiation packet. At no time is there any concern with the ping delay in this.

This is what I consider the most major 'bug' with the 1.10 game at this point. The Client and Server sides of the game are not actually 'playing' the same game. There are several points where this coming from to causes these problems.

First, I have observed that the pathing routines and speed processing of movement between the two is different to a considerable degree in many cases. This will leave the player at time attacking the wrong area because the server has the monster positioned in a very different manner than what the client displayed it at. The speed issue is most apparent if you really pay attention to the barbarian Whirlwind skill, the client is processing the movement along a leg of the WW at a faster rate than the server does and the server will not allow the initiation of the next leg (even on the client side) until it completes the leg it is working on. This is those very annoying pauses that can be seen with the skill in SP mode.

Second the two sides do not appear to be using the same criteria for determining if a hit occurs and the threshold points at which the GH and BL (or amazon D/A/E) should be getting used at. This can quickly lead to the client and server processing the combat in widely different manners.

Third is tied in with the first and is what whyBish brought up. The game is not correctly considering the weapon lengths when the attacks are started. This may in fact just be some bad positioning disagreement between the to sides, but it is hard to tell until the first part of the problem is corrected.