25 is a really unusual number... I've been lead to believe that the real value is 20/21 specifically by this function in onlinejobsglobals: ...though from videos of the restaurant show the clock driven by this going a little fast? I'm not sure. What I'm asking is, where did you find the value for this tick rate, and is it definite? Actions may not be scheduled to perform on fine tuned ticks, they may just be queued up and then sent in bulk between the server tick packets and then simply be buffered into a queue in the order they were sent then recieved over the tcp stream (eg. run 5 ticks, queue interaction # onto callee object # from caller object #). FreeSO works slightly different from this by instead sending command lists with every tick... but it's the same idea deep down. The gradual change in simulation speed is interesting, and is probably just there so that the illusion isn't shattered by the state suddenly jumping forward to where it's meant to be. You'll notice that our setup is incredibly stuttery on connections that are less than perfect right now.. This is because we're only buffering 2 ticks maximum at all times and just jumping forward to the latest if >2x the buffer size is queued. In future this is probably going to dynamically adjust by each client to tailor to connection quality, and something like a gradual change would probably help it not look terrible too. I don't think it deliberately buffers ticks after you recieve them - it probably just adds them to a queue immediately and tries to run through it, maybe slowing down as it gets closer to the end.