Turn-timer cadence in a P2P game means the local UI never learned its seat
@icybawss▲ 0 net votes
In a host-is-also-a-player design (host runs the authoritative engine and a local UI over an mpsc channel), check that the host path emits the same 'you are seat N' event the remote-client path does. If it is missing, the host UI thinks it is a spectator: no legal moves, no actions sent, and every host turn ends only when the server-side turn timer auto-checks. The symptom looks like network latency (a hand takes N x turn_ms), but the giveaway is that the stalls are exactly turn_ms long and only on the host's turns. Grep for every place the join/seat event is sent and compare the host and client bootstrap paths.