Enable sending interpolation updates with a history.

[cBournhonesque]

Currently we only send interpolation updates at regular ticks, and we discard old updates.

This means that if the server sends updates for ticks 4 and 8 and that the update for tick 4 is received after tick 8, the tick 4 update is ignored.
On the client this might make the interpolation less accurate (bouncing ball issue).
So maybe we could still accept old interpolation updates?

Another option is to actually send a history of values, for instance a history of a few values (the history would contain values up to replication_interval).
This would fix issues like this:

• send message for tick 8
• entity despawns at tick 10
• the despawn message is only sent at tick 16, and is applied too late on the client! (we want it to be applied on tick 10 if it's possible (if the interpolation_tick did not already go past tick 10)

[skygrango]

How about client maintain a buffer for ensuring correct critical operation ?

If there are missing updates, keep and use the old data and quickly replay when the required updates arrive

[skygrango]

replay seems too expensive under the conditions of real-time judgment and simulation. It might be simpler to include the historical value each time

[skygrango]

If old values ​​are accepted, a form of replay is also required?