The v7 pilot lets an independent operator run their own rooms with their own osu! account and local credentials, while downloading the owner's prepared map-selection catalogs. Public listing and shared feedback are optional. Contact the maintainer for access to the qualified private GitHub kit and the supported setup for your instance.

Use the supported Linux/Python/systemd environment from the kit. Ubuntu 24.04 with Python 3.12 has independent operator feedback; a compatible systemd-based LXC installation has been exercised. Verify the release asset and its checksums, not GitHub's Source ZIP. Keep the hosting account's OAuth credentials on that machine. Do not copy the owner's credentials or start a second controller on an account already hosting elsewhere.

Fresh installation defaults to one Standard Auto room. More rooms/presets need an explicit supported setup. Standard Auto, Standard fixed, Mania 4K and Mania 7K have owner-tuned public gameplay profiles; explicit saved host ranges/overrides take precedence. Existing installations keep their chosen titles and settings through ordinary compatible upgrades. Xikeon's dedicated dev12 helper intentionally applies the reviewed tuning while retaining their chosen titles and unrelated state; it is not a universal script for arbitrary hosts.

1. Download and verify the attached private release kit, then follow its installation guide for the intended instance and presets.
2. Import the full prepared selection catalogs, with the supplied trust/origin pins. There is no local research collector or model-analysis job to run.
3. Configure and authorize your own local OAuth client. On SSH installs follow the kit's loopback callback/tunnel instructions. Configuration success and completed sign-in are separate steps.
4. For optional hub participation, send the maintainer the requested hosting-account binding and public operator label, installation binding and separate listing/sharing consent. Redeem the bound invitation locally. Never post the invitation or credentials publicly.
5. Wait for the contribution grant before enabling shared uploads as instructed. Start the separate network agent only after configuration/enrollment is complete.
6. Check ownership and the exact version's admission instructions, then start once. Return the room links and redacted diagnostics. If startup is uncertain, retain state and report before retrying.

Play several maps with people other than the hosting account. Check titles, mode/keys, star range, queue, countdowns and completed map progression. Try .help, .queue, .g/.b, skip, Standard easier/harder, READY/unready/AFK with at least two players, and mid-match joins. Mark untested items as untested.

For a new good/bad vote, note its map ID, direction and time. After the normal approximately 30–60-minute upload window, return redacted capture/pending/accepted results so the maintainer can verify the hub acknowledgment. Local capture, upload acceptance, aggregate inclusion and active shared weighting are different stages.

Leave healthy rooms and their network agent running continuously. The first hour is a focused observation period, not a shutdown deadline. Send a brief daily uptime/match/error/feedback summary. Arrange a quiet upgrade window for shared-runtime changes; do not interrupt occupied rooms merely because a new release exists. Clean-stop evidence can wait for the next planned shutdown.

Upgrade the same installation through its exact qualified guide. Preserve OAuth, full catalogs, settings, titles, ratings, enrollment and sharing; reinstalling or recreating old votes is not a normal repair. If room ownership is uncertain, stop further startup attempts and use the maintainer's evidence-based recovery instructions. Process exit, an empty filtered room list or elapsed time is not proof of upstream closure.

Protected operator commands · Directory, feedback and privacy · What is downloaded · Release history