October 7, 2026, 13:18 PDT: Rooms 1, 3 and 4 are healthy and running v6.7.26. Room 2 is healthy on v6.7.25, with v6.7.26 queued for its next empty-and-idle window. The shared supervisor remains on v6.7.22; its account connections stayed running during the worker updates. This is a dated observation; see Live lobbies for current room versions.

• Fixed a room crash when a difficulty change made an already queued DT map ineligible and a player then used .skip.
• Before promoting a queued replacement, the bot checks that its variant still satisfies the current mod and difficulty rules. An obsolete variant is discarded and the bot tries another queued map or a newly selected eligible map.
• Queued DT charts receive a fresh source-revision check before promotion. Unavailable or changed charts are passed over safely.

For example, a 7.39-star DT map queued before .easier could remain visible after the pool moved to 4.80–5.50 stars. Previously, skipping into that map raised an error and stopped the room controller. From v6.7.26, the skip rejects that stale DT replacement and continues looking for an eligible map.

The existing skip vote threshold and eight-second vote window remain. Playlist synchronization, download checks and per-map mod validation remain enforced. If no replacement is available, the bot reports Pool exhausted. and keeps the current map.

Room 1 was restored with the fixed worker after the old, empty room was safely replaced. Rooms 2–4 kept their controllers and account connections during that recovery. The remaining compatible updates use the normal empty-room handoff; an occupied room waits rather than removing its players.

All 803 offline regression tests passed, including seven new queued-variant skip cases. Read-only checks against the production catalogs passed for all four room configurations. No live player command or test match was required, and no mutable player database was replaced.

Skip · Queues and future picks · Room updates · Release history