567cc33576
The host sent the overworld clock's rate even while /time pause held it (ServerClockInstance.packNetworkState sends 0 when paused), so a guest's day kept running. A guest also moved its clock by the rounded rate each client tick and never caught up when the server's game-time sync moved game_time on, so a guest whose game lagged fell behind for good. ClientClockManager.tick advances the clock by the game time passed, with its partial tick; the guest now does the same. lan_e2e.py time: the paused clock and a guest stalled for 4 seconds. Part of #848 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>