Animation Lock: Why don't you like it?

[Issachar]

1.0 WS processing:
[START] Click WS -> instruction sent to server -> damage algorithm processed and damage dealt -> server instruction sent back -> WS animation activates and log updated [END]

This is why animation lock sucks.

2.0/ARR WS processing:
[START] Click WS -> clientside sees if conditions are met -> WS animation activates [END]

Meanwhile, behind the scenes...

(if clientside conditions are met) -> instruction sent to server -> damage algorithm processed and damage dealt -> server instruction sent back -> log updated [END]


These two paths happen simultaneously when the button is clicked. Combine it with a non-locking animation, and it just works out much better than before.

If ARR were to use animation locks combined with the branching process tree that they introduced, it'd still work much better than 1.0's.