Roles and command access
| Role | What it can do | Where checked |
|---|---|---|
| Active gameplay player | Shared votes, session controls, and Mania style changes | Current lobby player list; spectators do not gain these controls |
| osu! moderator | Normal room flow and selected live settings | Configured moderator account; admins inherit these rights |
| osu! administrator | Moderator controls plus access, policy, title, and room shutdown controls | Configured admin account |
| Authorized Discord MOD or ADMIN | Corresponding staff controls routed to a room | Discord control role and channel; some commands are Discord-only |
| Wiki editor or maintainer | Edit permitted wiki pages | DokuWiki ACL; separate from bot access |
The command prefix is a dot in the current rooms. .help2 exposes the current bot's role-specific help. Most staff settings are saved to room or shared configuration; a reply ending in “live only; JSON save failed” means the setting changed in memory but persistence failed. Recheck .settings and ask an operator to investigate before relying on it after restart.
A spectator cannot change a Mania style unless also a moderator. Standard player selection and votes follow their own command rules; see player commands. A Discord MOD/ADMIN actor is separate from an osu! account; reports and shutdown have channel-specific checks. See Discord control.
Never treat a wiki page as an authorization source. If a command is ignored, verify the room, account, and current .help2 response before escalating. Command troubleshooting explains throttling and disabled public commands.
| Behavior reference | v6.6.17 · reviewed 2026-09-29 |
|---|