6acf7fb6ab
Each step waited a fixed 2.5 s. When the machine is loaded the vanilla server stalls for longer than that (CI on #1571 and #1585: after Bob's trip to the Nether, vanilla's `tp Bob 4.5 -60 0.5` from the console ran a step late), so its packets were filed under the next step and the transcripts differed although both servers sent the same. A step now ends once the server has done its work: - the console's own `time query gametime` comes back, so the step's console commands have run (the console runs its queue in order); - LocatorBarClient's new `sync NAME` runs `time query gametime` as that player and waits for the reply (not recorded), so that player's commands have run and every packet sent before the reply is recorded; - the server's game time has advanced STEP_TICKS (40) more ticks, then each player sends its position reminder and syncs once more. game_time() moves out of settle() in test_dedicated_server_parity.py so both use it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>