====== v6.7.2: Website and Discord reliability ======

**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.

===== Website and Discord =====
  * Restored current maps, upcoming maps, player counts and approximate live progress on [[status:start|Live lobbies]] and the site's lobby widgets. A fresh observation from each worker now feeds the website directly.
  * Fixed authentication failures that blocked room checks, bot replies and Discord ''.say'' messages. Shared OAuth tokens are reused and refreshes are coordinated; a definite authentication rejection gets one recovery attempt.
  * Fixed replies when a Discord control command targets a different room. A relay whose delivery cannot be confirmed now reports that to the operator instead of failing silently.
  * Fixed countdown cancellation and cleanup after a worker is retired.

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.

===== Updates wait for 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.

===== Validation and related changes =====
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 [[updates:v6_7_0|v6.7 features]] remain included: independent compatible room updates, quieter welcomes and voting messages, fewer repeated reminders and database reliability fixes. [[updates:v6_7_1|v6.7.1]] supplied the earlier headless-chat callback fix.

See [[wiki:room_updates|How room updates work]], [[status:start|Live lobbies]], and [[troubleshooting:start|Troubleshooting]].