Deployment status (October 1, 2026): deployed; superseded by v6.7.1, which restores headless chat. The initial adoption completed through an operator-approved maintenance restart, with all old rooms confirmed closed before the four v6.7 lobbies reopened. Compatible future updates can now move through empty rooms independently. Use Live lobbies for current join links.

After the initial adoption, compatible updates can move through one lobby at a time. An empty room can receive an update while occupied siblings keep playing on their existing versions. Each lobby has its own worker process and pinned release; the supervisor and rooms can run different compatible versions.

The individual room must stay empty and idle for at least 30 seconds, including spectators. A player arriving before the room closes cancels that handoff and resumes the old room. The replacement receives a new room ID and join link. Use the site's Join a lobby menu to find the current room.

Candidate startup checks, a private readiness period, confirmed old-room closure, and version/schema compatibility checks protect the handoff. This is an update to an empty room, not a transfer of an active match.

Scope: compatible room commands, messages and map-selection code can roll independently. Shared account connections, supervisor/protocol changes, Python dependency changes and persistent database changes still require a coordinated upgrade. An incompatible candidate is refused while existing rooms remain running. Read How room updates work for the complete explanation.

This release includes the quieter-chat work previously staged as v6.6.23; that version is superseded rather than deployed separately.

• Shorter welcomes and mid-match introductions; familiar returning players do not receive the same command tutorial on every rejoin.
• Feedback prompts wait for six completed maps and at least ten minutes between prompts. Recent ratings suppress reminders, and optional prompts avoid the twenty seconds after useful bot messages. You can still use .g, .b or .ok after any completed map.
• Website reminders keep their configured schedule but do not repeat to an unchanged group of players.
• Skip and replay votes announce their opening and outcome without a message for every intermediate vote. Difficulty votes introduce each direction once per voting window.
• More compact style/source replies show the eligible-map count. Re-selecting an active Mania style avoids an unnecessary pool rebuild.
• Repeated readiness explanations wait five minutes unless the map, roster or reason changes. Countdown cancellation warnings remain available.

PP achievements, requested replies, custom supporter greetings and restored difficulty preferences remain available. These chat changes do not alter voting thresholds, map-quality filters, style fallback rules or gameplay timing.

A root-run read-only SQLite reader could briefly create support files that the bot could not access. The exact failure seen in room 2 was reproduced in isolation; a website status export overlapped the historical crash, although logs cannot prove its precise syscall timing.

The website and monitoring readers now access SQLite using the database owner's identity. This operational fix is already live and did not require a bot restart. The new dependency is included in website backups.

The deployed bot changes add bounded retries for connection setup and close failed connections. A failed download-availability cache read uses existing in-memory results and the osu! API path instead of terminating the lobby. Explicit unavailable-map and unavailable-set quarantine stays in force, including forced checks. Application writes are not automatically replayed.

The final bot release passed 402 offline tests, with 32 operations tests for the updated readers. Tests include real service-owner/WAL concurrency, visibility of uncheckpointed results, cache failure handling and preserved unavailable-map quarantine. Website publishers were checked under their real service restrictions.

See room updates, technical overview, player commands, and release history.