Table of Contents
Get unstuck
Choose the closest match to what you see in the lobby.
What happened?
- My command did nothing — check spelling, room mode, player eligibility, and votes.
- The map will not start — understand waiting, readiness, and interrupted countdowns.
- The next map is not my chosen style — find out when a preference takes effect.
- I keep seeing the same maps — understand a small pool and repeat selection.
A room closed or your invite stopped working?
Use Live lobbies or the Live lobbies sidebar for the current link. Replacing an empty room gives it a new room ID. Compatible v7 worker updates leave occupied siblings running after the new controller is activated; shared controller maintenance has a separate all-empty admission window. See How room updates work for what to expect. A closed room alone does not prove an update occurred; report unexpected closures with the room number and approximate time.
Just learning the controls?
Try practical session examples for ordinary situations such as a map being too hard or wanting another attempt. The command finder gives exact inputs and supported lobby modes.
Still need a hand?
Use Discord in the bar at the top, or type .discord in the lobby. Include the room number, approximate time and timezone, what you tried, and the visible response. Avoid posting credentials or private logs.
DT speed or language looks unexpected?
Mixed Standard DT is eligible automatically above an active star-window midpoint of 5.5★ on supported workers. .dt opts the room in, .nm opts it out; each item sets/restores its own mods. Mania does not use this mixed-DT feature. See DT rules.
.lang is personal guidance, not a shared-room language change or player-chat translation. .lang en or .lang off resets it to English-only. The website dropdown is independent. See language help.
Hosting diagnostics look contradictory?
A valid OAuth token does not mean startup ownership admission has run. A failed systemd unit does not necessarily mean room ownership is uncertain: inspect the authoritative journal/recovery summary and observation freshness. Keep state after uncertain startup or shutdown and ask the maintainer before retrying. For the distinct command/support fields and useful redacted reports, see operator diagnostics and host testing.