Premoves taking up time

@ijh As many have mentioned, premoves don't take time. But after game is completed, we don't store clocks to full precision, so moves can show up later as 0.03s. There's a bug to fix this, prob in next couple of months. It only affects saves, not the clocks during the game.

One of the things @MoistvonLipwig mentioned earlier in the thread has me curious.

Is it actually possible for it to seem as though a premove was made, but not get credited for a premove, i.e., client-side you don't see a move from your opponent, you see the source and destination squares for the premove highlighted, but the move ends up taking time off your clock?

I have some vague intuition that the idea of a local OS/browser/machine issue could potentially cause some sort of delay like that, but I'm not sure I fully understand the mechanics of processing premoves enough to know for sure.

Otherwise, I guess the only way premoves would take time off your clock is if you exceeded your lag quota?

@isaacly If you could comment on that, it'd be greatly appreciated.

Thanks!

@a_pleasant_illusion

Otherwise, I guess the only way premoves would take time off your clock is if you exceeded your lag quota?

Essentially, yes. But if the timing is really close, it might be possible to release the mouse for premove and not get it counted as a premove if the opponent's move has already arrived but not yet been displayed. However if you see your premove shown on the board, and no opponent move, then your premove should get counted as a free move. The server indeed deducts this time against your lag quota.

It's unlikely this code acts differently in firefox vs chrome, but of course it's possible there's a bug we don't know about.

@isaacly Thanks. That makes sense.