This is an old revision of the document!
Room flow and recovery
Use .settings and Live lobbies to understand the current room before changing it. The public dashboard is observed data and may lag the bot; the in-room response is authoritative for an immediate command.
| Command | Role | Effect |
|---|---|---|
.start | Moderator or admin | Starts the match through the privileged path; admin use also clears single-player start/download holds. |
.abort | Moderator or admin | Aborts the current match; the bot marks it as an explicit abort. |
.forceskip | Moderator or admin | Forces a skip without waiting for the ordinary skip vote. |
.softrestart | Moderator or admin | Requests a supervised soft restart. Expect a brief interruption and check the room afterward. |
.hardrestart [maps] | Admin | Recreates the room immediately, or queues it after 1–100 maps; 0 means immediate. |
.close | Admin | Closes this lobby. |
.closewhenempty / .closewhenempty cancel | Admin | Arms closure when non-referee players leave, or cancels it. |
.shutdown all / .shutdown <room> | Discord ADMIN only | Requests system-level shutdown through the control path. Use only for an intentional outage. |
For a stuck countdown, check countdown troubleshooting and active player readiness. Use .abort for an in-progress match that must stop; use .forceskip to advance the map. Restart and close commands interrupt players, so communicate the reason in the room when possible. The bot can reject or defer actions while recovering; recheck before retrying.
A short recovery check: inspect .settings and .queue, try the least disruptive control that addresses the symptom, then confirm the next map or countdown. If the room remains unhealthy, ask an administrator or VPS operator to inspect service logs. Tuning covers settings that affect future picks rather than the current match.
| Behavior reference | v6.6.17 · reviewed 2026-09-29 |
|---|
Safety recovery versus ordinary preference changes
Normal source/style/difficulty preferences preserve the visible queue. Mixed-DT opt-out or invalid chart/settings verification can instead rebuild unsafe unplayed entries while protecting a running match. Do not use forced starts to work around a verification hold; inspect the returned error and current pool first. Compatible room updates wait for an empty, idle gate and do not require clearing players or restarting the shared service. See DT, converts and updates.