Table of Contents

v7.2.0 — native Catch

Owner pilot live — October 20, 2026 UTC: Lobby 1 Catch started at 02:12:51 UTC on v7.2.0, native NM, initial 3.00–4.00★. Map, queue, artwork, website and Discord connection are verified. No Catch gameplay has been exercised yet. Live Lobbies gives the current room link after future maintenance.

Optional native osu!catch joins the existing distributed PoolRotater engine. The first owner pilot uses Lobby 1, NM, a fixed initial 3.00–4.00★ range and Ranked/Approved charts. Read the Catch guide and check the current rooms.

The first retained-Discord startup was repaired before room creation. v7.2.1 makes that correction reusable and preserves completed Catch transactions across upgrades. Use the latest installer for new Catch setups.

What is included

The recent v7.1.20 room-handoff and player-name repairs remain included. Existing rooms, operator settings, OAuth, Discord identities, enrollment, sharing choices and boot/update preferences are preserved.

Updates and rollback

Installing the version does not add a room to another host. The reviewed direct upgrade predecessor is v7.1.20; older hosts complete their existing update chain first. Shared-controller changes use the established empty/drained maintenance process. Compatible later worker-only releases can still update an individual empty room.

After Catch has initialized, rollback removes its room configuration while retaining the compatible controller/hub and its history, opinions and pending contributions. Old code cannot safely read that new state, so it is not silently restored over it. Use the release's Native Catch operator guide; do not delete databases or repeat uncertain room creation.

Validation

Full-catalog selection and identity checks, older-reader compatibility, affected runtime tests, current website rendering and protected installed donor workflows qualify the implementation. Donor rooms use an invented provider and do not prove real osu! gameplay. Live pilot startup and any subsequently exercised gameplay are recorded separately; a running room alone is not a completed gameplay test.

Verified installer and release evidence · All updates

The retained owner setup exposed a duplicate public Discord status-channel mapping before any room was created. Lobby 1’s existing public panel route was restored; the running pilot is healthy. The installable correction and controller-lineage rollback checks are being qualified for v7.2.1 before automatic channel promotion. Existing Standard/Mania hosts remain on their current signed release until that promotion.