The original four owner lobbies keep their modes, commands and staff controls. Independently operated rooms use another operator's osu! account, configuration and moderation policy. Community Lobbies on the homepage, Live Lobbies page and sidebar displays consenting remote hosts with the same map-card components used for owner rooms. Owner room counts do not silently include those hosts. Stale, revoked or unavailable listings lose their join links.

Map art and song duration come from the central public display index. Existing dev9/dev10 hosts do not need to rebuild databases or restart simply for those compatible website improvements. Cover links use the official osu! asset location, with a neutral fallback when metadata or an image is unavailable.

The new v2 public contract carries relevant room settings, current playing-player observations when known, and the participant count recorded at match start. These are distinct from the number of people in the room, which can include spectators. Unknown counts are not invented.

Song progress is labeled Estimated and uses an actual match-start observation bound to the same room, map and match, with duration adjusted for the active clock rate. Timing clears or hides after completion, abort, map changes, expired observations or missing evidence. A map-selection timestamp is not a playing-song clock. The v2 hub is qualified and staged, not activated; richer remote settings/timing require both the new client and coordinated hub activation. Real remote progress accuracy still needs observation.

Private rooms, passwords, credentials, chat, individual player identities and administrative settings are not published. Public listing requires the existing consent and freshness checks; hub outages or malformed community data leave owner displays independent.

The central service collects metadata and score evidence and runs map analysis. Operators obtain complete prepared selection catalogs, including the information needed for their supported modes. Signed catalog metadata and hashes establish integrity before activation. Research databases and display-only website metadata are separate from selection catalogs.

If the hub is unavailable, rooms can continue with their last verified local catalogs and feedback snapshot; unavailable updates are not silently treated as verified. Network recovery and local gameplay remain separate responsibilities.

Enrollment does not automatically publish a host's rooms, upload historical opinions or grant feedback contribution rights. Public listing consent, rating capture/sharing, the central contribution grant, historical seeding and shared weighting are distinct choices. Player feedback is committed locally first. Retries are deduplicated; an accepted upload alone does not establish aggregate inclusion or active shared weighting.

Shared selection reads verified snapshots only when explicitly selected. Local/independent weighting remains the default. Private diagnostics report progress without publishing raw player chat, vote bodies or credentials. Both retained votes from the independent host have been accepted centrally. Snapshot inclusion and active shared-weighting gameplay remain separate checks; receipt of an upload is not proof that an operator is using it to select maps.

Contact the maintainer for the qualified private kit, supported setup and a bound enrollment invitation if desired. Keep osu! authorization local. Same-topology upgrades preserve compatible state; adding rooms requires a reviewed setup rather than editing protected ownership files or running two supervisors on one hosting account. The latest qualified private dev11 kit retains supported stopped configuration and clearer diagnostics, and includes the chat maintenance/message-deferral repair plus narrow deferral of undispatched player-profile and score reads. Actual joining players and READY state remain recorded while profile data is unknown; the existing scoring timeout and cursor remain intact. Existing operators follow its state-preserving upgrade guide after resolving old-room ownership. Keep the current installation, OAuth, catalogs, titles, local votes, enrollment and sharing settings; no repeated enrollment or vote recreation is needed.

Project moderation bans are operator-local; they are neither osu!-wide sanctions nor an automatically shared network ban list.

v7 foundation · Current pilot notes · Choose an owner lobby · Player feedback