Differences

This shows you the differences between two versions of the page.

--- moderation:players [2026/10/10 18:56] – Document v6.7.27-33, current rollout, map exclusions, DT refresh and queued staff moderation wikiadmin
+++ moderation:players [2026/10/10 19:39] (current) – Clarify persistent bans enforce only upon presence, with no pre-emptive commands on room creation wikiadmin
@@ Line 17: / Line 17: @@
 Use an exact username, including spaces, or an osu! user ID. The bot checks known names before interpreting a numeric-looking name as an ID. An absent player can be banned by ID or a known name. The saved name can resolve a later unban even after they have left. Kick requires the player to be in the selected room. An optional ban reason follows a literal ''|'' and is limited to 200 characters.
-===== Permissions and safety =====
+===== Room remakes and rejoining =====
+The bot remembers banned user IDs across room recreation, but **creating a new empty room sends no pre-emptive ban or kick commands**. It does not replay the stored ban list into each new room. Only after a banned player actually joins or is observed present does the bot request their removal from that room. If staff ban someone already present, removal is requested after the policy is saved.
+This is a persistent bot-enforced policy using kicks, not osu!'s room-specific native ban command. A newly created lobby has a new room ID; the saved policy still applies to all four project rooms until ''.unban'', but there is nothing to enforce while that player is absent. Banned players may therefore briefly appear during entry before their removal is confirmed.
+===== Access and enforcement safety =====
 Configured osu! moderators/admins and authorized Discord MOD/ADMIN roles have the same four commands. Wiki editing permissions confer no bot access. Bot, referee, administrator and moderator accounts cannot be kicked or banned through these commands. Ordinary players cannot invoke them.