October 5, 2026, 18:38 PDT: the shared supervisor is live on v6.7.22 with a five-second continuous empty-and-idle deployment wait. Rooms 1–3 are healthy and running v6.7.23; Room 4 is healthy on v6.7.22, waiting to update when empty. This is a dated observation, not a continuously updated deployment claim; see Live lobbies for current room versions.
.start, optional .wait, score processing and the configured numeric countdown retain their existing behavior.
This is an automatic-start pacing change, not a new command or a forced minimum break. A player explicitly requesting .start keeps its existing override behavior, subject to map, readiness and referee checks.
The referee API does not expose lazer's separate native Results state. It reports finished_play after gameplay, suppresses the intermediate Results transition, and reports idle or ready when the player returns. The bot uses that already-received post-game status as the hold signal; it does not inspect a player's screen or infer it from inactivity.
No additional API polling, recurring requests or account connections are added. Existing player-status events and the cached roster supply the information. See the official referee status mapping. Unknown states are not guessed to be results.
| Setting | Effective value in all four rooms | Purpose |
|---|---|---|
score_delay_seconds | 4 seconds | Initial wait before score fetching; absent scores can keep scoring active for up to 20 seconds after completion |
auto_start_seconds | 10 seconds | Ordinary idle/pre-countdown wait; Ready-based early starts may shorten it |
countdown_seconds | 10 seconds | Numeric countdown before gameplay; existing extensions can still apply |
start_wait_seconds | 10 seconds | Extra delay per eligible .wait request, once per player per map |
rating_window_seconds | 90 seconds | Feedback window, not a pause before the next match |
These are reviewed live operator values, not new immutable defaults. Universal settings override older values in individual room JSON files. The new hold postpones automatic timing while all gameplay players remain post-game; downloads, readiness, optional waits and safety checks can also extend a transition. Map duration settings are unrelated and unchanged.
789 offline tests passed, including solo/all-player holds, the actual finished_play → idle event sequence, release when one player returns, spectators/referees, departures, unknown states and absence of API calls. The immutable release is compatible with v6.7.22, and all four rooms passed the owner-approved duration guard.
The durable follow-on job submitted the guarded ordinary empty-safe rollout after successful v6.7.22 activation and healthy-worker checks. Actual worker observations confirm v6.7.23 in Rooms 1–3 at the dated review, while Room 4 remains queued until empty. Accepted deployment alone does not prove every room has updated; occupied rooms are not forced to close.
Includes earlier cumulative Jump and supervisor work. Collection, the separate research candidate database and live map catalogs are unchanged by this patch.
Release history · Match lifecycle · Readiness rules · Update safety · Live lobbies