v6.6.23: Quieter lobby chat
Deployment status (October 1, 2026): validated and queued for normal empty-safe deployment. v6.6.22 is active at this review. These changes are upcoming, not yet live. Check Live lobbies or the current-version notice on the release index for deployment confirmation.
What changes
Shorter introductions. Welcome and mid-match messages are more compact. Familiar returning players no longer receive the same command tutorial on every rejoin. Custom supporter greetings and restored difficulty preferences remain.
Less frequent feedback prompts. Reminders wait for six completed maps and at least ten minutes between prompts. Any current lobby member rating one of the last three maps suppresses the reminder. Optional feedback hints avoid the twenty seconds after useful bot messages. .g and .b remain available after every completed map.
Website reminders without repetition. The forty-minute schedule stays unchanged and is not postponed by other bot messages. An unchanged group does not receive the same reminder repeatedly; newcomers make the next scheduled reminder useful again.
Concise style and source replies. Changes report the eligible-map count. Selecting an already-active style avoids an unnecessary pool rebuild. Existing queued maps stay unchanged; detailed help and pool queries remain available.
Quieter voting. Skip and replay votes announce their opening and outcome without reporting every intermediate vote. Difficulty votes introduce each direction once per voting window. Expired votes receive one concise outcome. Vote counting, thresholds, timing and permissions are unchanged.
Fewer repeated readiness explanations. An unchanged readiness problem is explained again only after five minutes, or when the map, roster or reason changes. Successful gameplay resets this episode. Countdown cancellation messages remain available.
PP achievements, requested command replies, and room closure and restart warnings remain. Map quality filters, style fallback rules and gameplay timing are unchanged by this update.
Deployment
This is one combined release using the normal empty-safe deployment policy. The one-time final-map deployment exception used for v6.6.22 does not carry forward.
See commands, map feedback, and release history.