Quote from Watermelon
There is only one left on the list.

Quote from Torr Samaho
After respawning the player is prevented to move for a fixed amount of tics. Server and client both start to count this time directly after spawning the player, but since the spawning on the client is delayed by the ping, the player was allowed to move on the server while the client was still thinking it may not move yet. To account for this I increased the non-movement time on the server by the client's ping (which seemed to fix the problems for me) and now also made the client not send any movement requests while it locally still thinks it is not allowed to move (which seems improve the situation for you).

Quote from Watermelon
So far the following are the only things required for meeting the competitive standards from ZD/Oda:

- ssg (easily modifiable through decorate [check])

Quote from unknownna
I think that this is caused by the teleport/spawn/respawn prediction in Zandronum.

Quote from unknownna
On a side note, I noticed that the client prediction for doors was a lot better in ZDaemon. You don't jitter there compared to Zandronum.

Quote from Doom source code

        // don't move for a bit
        if (thing->player)
            thing->reactiontime = 18;

Quote from Torr Samaho
To keep things synchronized the client will wait for exactly 18 tics before it allows movement while the server waits for 18 tics + the player's ping. So on the client it should look like exactly an 18 tic delay.

Quote
Wouldn't this caused an increased delay for higher ping players? Shouldn't the client be waiting for 18 - ping and the server waiting for 18?