Queued, not live at the October 10, 2026 review. This cumulative update waits for the existing v6.7.32 rollout, then for all four rooms to be empty and idle for at least 30 seconds before a coordinated supervisor upgrade. Players will not be removed to install it.

Owners and moderators can use these in lobby chat or the authorized staff Discord control channel:

Exact usernames may contain spaces; numeric osu! IDs also work. Offline bans require an ID or a username known to the bot. Bot, referee, admin and moderator accounts are protected. Ordinary players cannot use these controls.

Bans survive bot restarts and room recreation. They are enforced by automatic removal on entry, not an osu!-wide account ban or an irreversible native referee room ban. Banned users cannot issue player commands or contribute gameplay votes. Unbanning lets them rejoin normally.

Ban changes are saved before removal and retained in an audit trail; workers serialize writes to prevent lost changes. Uncertain kicks are not blindly repeated. Invalid policy updates retain the last valid list and refuse new moderation changes. Implementation did not kick or ban any player.

Room-remake clarification: Creating a new empty lobby sends no pre-emptive ban or kick commands and does not replay the stored ban list. The persistent user-ID policy is checked when a banned player joins or is observed present; only then is removal requested from that room. Banning someone already present also requests removal after saving. This is bot-enforced kicking, not native room banning, and the policy remains across all four project rooms until .unban.

All 863 offline tests passed; real-configuration offline checks passed for all four rooms. The update preserves map catalogues, duration preferences and the five-second wait for ordinary compatible per-room updates. The shared Discord permission change is why this release needs coordinated maintenance.

Kick and ban handbook · Permissions · Update policy · Release history