Observed this in Spearhead but also occurs in GM and mods that use animateDoor for vehicle hatches and the like.

I'm not sure if it's a bug or if 'as designed' but either way it leads to undesirable results.

The problem is the 'animateDoor' script command seems to have very low network priority, where it can take upwards of 6-10 seconds for the script command to take effect over the network.

This is noticeble in the following scenario:
Self-hosted server, and a client (running on same PC)
Vehicle with the previously mentioned hatch animateDoor usage
Client enters the vehicle as a driver therefore making the vehicle local to them.
Server Client stays outside and observes
Client turns out from the driver position, this will be animated with animateDoor. On their end the hatch opens as per expected and works correctly.
On the server end the unit is turned out, but the hatch remains closed. This stays this way for multiple seconds before the command 'catches up' and the hatch opens as per normal.

If animateDoor is remoteExec or otherwise run locally (like a client entering another clients vehicle, and turning out themselves) the command behaves as expected