This is an old revision of the document!
Table of Contents
v7.0: Independently operated lobbies
| Status | Pilot foundation; the owner's live implementation is cumulative v7.0.1 dev10 |
|---|---|
| Behavior reference | v7 pilot architecture · reviewed 2026-10-14 |
More people can host
The v7 pilot lets independent operators run their own lobbies with their own osu! accounts and local credentials. The owner's VPS supplies prepared selection catalogs and an authenticated central hub. It does not take possession of other operators' osu! credentials.
Prepared maps, not a collector on every host
Collection and analysis remain central. Operators download complete prepared Standard, Mania 4K and Mania 7K catalogs, verified through signed metadata and integrity checks. They do not need to rebuild research databases. A hub interruption does not require discarding the last verified local catalogs or feedback snapshot.
Optional community participation
Hub enrollment, public directory listing, sharing feedback and choosing shared feedback for selection are separate operator decisions. Enrollment alone does not grant permission to contribute ratings. The owner's four rooms remain distinct from community-operated rooms.
The website now presents consenting community rooms on the homepage, Live Lobbies page and sidebar using shared lobby cards. Art and duration are resolved centrally for existing dev9/dev10 hosts. Host attribution and owner-only controls/totals remain explicit, and stale or revoked joins are withdrawn. Rich settings and Estimated song progress require the new v2 client plus hub activation; that hub change is qualified but remains staged. An empty community section does not mean the owner's rooms are offline.
What players keep
Existing map preferences, chat commands, skip and difficulty voting, countdowns, personal language guidance, feedback and Discord controls remain the foundation. v7 is not a replacement set of gameplay commands. Read the cumulative v7.0.1 pilot notes for the qualified repairs and current availability.
Pilot limits
This is a qualified pilot, not a claim that all planned distributed-host features are finished. Installed migration, catalog and outage scenarios have technical qualification; two independent-host votes have been centrally accepted, while active shared-weighting gameplay and real remote progress accuracy remain separate acceptance tasks. Older development milestones are not release dates.
How community hosting works · Release history · Live owner lobbies