If the server is at the end of Montage1, it is at the 3rd second of Montage1; but the client has started playing the 1st second of Montage2 through GameplayAbility. If the client receives the server’s motion verification packet at this time, as long as it determines that the playback time difference exceeds the threshold, it will force SetPosition. However, it does not determine whether it is the same Montage.
In the above example, the client receives the server’s motion verification, and compares the client’s current Montage2 Position (3rd second) with the server’s Montage1 Position (1st second), which will cause the client’s Montage2 to be stopped directly. (Because Montage2 is only 2 seconds)
Is the official aware of this problem? Is there a subsequent repair plan?