Reviewed October 10, 2026: Rooms 3 and 4 are running v6.7.32; Rooms 1 and 2 remain on v6.7.30 with cumulative v6.7.32 queued for their empty-and-idle handoff. See Live lobbies for current versions.

An operator can now exclude an exact broken chart through an external policy file without preparing another code release. Standard, DT, Mania, style fallback, replay and direct playlist writes use the same beatmap-ID policy.

The local file is checked about every two seconds, with no osu! API requests for watching it. Excluded unplayed entries are safely replaced or removed between matches after a server room audit. A running map or countdown is not interrupted. If no safe replacement exists, an excluded current map cannot start.

Malformed or missing updates retain the last valid list. A worker starting with an unreadable configured policy cannot select maps until the policy is valid. Removing an exclusion does not erase a separate download quarantine or restore rows previously removed from its catalogue.

The policy initially carries the 11 existing exact-chart exclusions. Historical ratings and research data are untouched. A future catalogue rebuild cannot bypass the runtime list, but export-time exclusion checks remain a separate pipeline responsibility.

All 839 offline regression tests passed, with duration settings and catalogues preserved.

Player reporting and operator policy · Room updates · Release history