Begin a remote game's placement phase: every human places their own ships on their own board at the same
time - no handoff, no "look away". done runs once the order is set, with the order play will take.
onTimerChange runs whenever the deadline below actually fires and changes state on its own - every other
state change in this module happens inside a function a dispatched/forwarded click calls directly, which the
server's own broadcast-after-dispatch already covers; the deadline is the one change that happens on a raw
timer with nothing else watching for it, so without this hook a client that lets it expire sees nothing at
all, even though the server's own state has already moved on.
A robot filling an empty remote seat (see server/gameplay.ts's startRoomGame) already has its fleet placed
by buildPlayers.ts, same as local play's own robots - it is seeded ready here immediately, never waiting on
a ready-up that nothing would ever drive, and never gets a placement panel of its own.
Begin a remote game's placement phase: every human places their own ships on their own board at the same time - no handoff, no "look away".
doneruns once the order is set, with the order play will take.onTimerChangeruns whenever the deadline below actually fires and changes state on its own - every other state change in this module happens inside a function a dispatched/forwarded click calls directly, which the server's own broadcast-after-dispatch already covers; the deadline is the one change that happens on a raw timer with nothing else watching for it, so without this hook a client that lets it expire sees nothing at all, even though the server's own state has already moved on. A robot filling an empty remote seat (see server/gameplay.ts's startRoomGame) already has its fleet placed by buildPlayers.ts, same as local play's own robots - it is seeded ready here immediately, never waiting on a ready-up that nothing would ever drive, and never gets a placement panel of its own.