Deployment status (October 1, 2026): all four lobbies reopened on v6.7.2. The rooms were already confirmed closed before deployment; this patch did not remove players to install an update.
.say messages. Shared OAuth tokens are reused and refreshes are coordinated; a definite authentication rejection gets one recovery attempt.A room whose worker stops reporting is shown as unavailable until fresh data returns. A confirmed closed room is offline. The website does not treat either condition as proof that an open room has zero players.
Compatible updates still require the affected room to be empty and idle for at least 30 seconds. A player arriving before closure cancels the handoff. Infrastructure closure now also rejects an occupied room or an unknown roster. Players are not kicked to make automatic updates happen. Shared-service and database changes still require coordinated maintenance; they do not bypass these occupancy requirements.
During the earlier coordinated maintenance closures, osu! emitted player-kicked events as rooms closed. These were actual removals caused by room closure, not a separate automatic kick policy. This patch was installed only after the four rooms had already been closed through Discord commands.
Passed 428 offline tests, including real worker-process Discord relays, website output without legacy hub logs, concurrent OAuth refresh, stale observations, occupied-room refusal and a player arriving during an update.
All v6.7 features remain included: independent compatible room updates, quieter welcomes and voting messages, fewer repeated reminders and database reliability fixes. v6.7.1 supplied the earlier headless-chat callback fix.
See How room updates work, Live lobbies, and Troubleshooting.