it's not a lag issue -- the current move time storage doesn't have a 0ms time, it only has .1s. So 0 is rounded up to .1s. We previously then replaced .1s with 0s, but that code is now removed, so you're seeing the time we stored.
We're adding more accurate times very soon, which is why this code is changing.
We're adding more accurate times very soon, which is why this code is changing.