PoolRotater Wiki

Your guide to automatic osu! multiplayer

User Tools

Site Tools


wiki:match_lifecycle

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
wiki:match_lifecycle [2026/10/06 00:48] – Document scheduled v6.7.23 results intermission and refresh dated rollout status wikiadminwiki:match_lifecycle [2026/10/06 01:39] (current) – Document deployed v6.7.22, v6.7.23 rollout and persistent monitoring-path correction wikiadmin
Line 32: Line 32:
 Each mixed-DT Standard item requires its verified DT settings; the following NoMod item restores the configured normal mods. Mania converts require verified converted keys and difficulty. Returned settings/rating mismatches or uncertain transitions hold the start and schedule safe recovery rather than starting an unsafe map. A player's DT opt-out does not interrupt a running match. See [[wiki:mixed_dt|mixed DT]] and [[wiki:converts|converts]]. Each mixed-DT Standard item requires its verified DT settings; the following NoMod item restores the configured normal mods. Mania converts require verified converted keys and difficulty. Returned settings/rating mismatches or uncertain transitions hold the start and schedule safe recovery rather than starting an unsafe map. A player's DT opt-out does not interrupt a running match. See [[wiki:mixed_dt|mixed DT]] and [[wiki:converts|converts]].
  
-===== Pending results-screen intermission: v6.7.23 ===== +===== Results-screen intermission: v6.7.23 ===== 
-**Scheduled, not live at the October 5, 2026, 17:47 PDT review.** Once this update reaches a room, automatic timing pauses while its lone player, or every active gameplay player, remains post-game viewing results. When anyone returns to Idle or Ready, the ordinary pre-countdown wait starts fresh. Spectators and the referee do not count.+**Rolling out:** v6.7.23 was verified live in Rooms 1–3 on October 5, 2026, at 18:38 PDT; Room 4 was still waiting empty on v6.7.22. In a room running v6.7.23, automatic timing pauses while its lone player, or every active gameplay player, remains post-game viewing results. When anyone returns to Idle or Ready, the ordinary pre-countdown wait starts fresh. Spectators and the referee do not count.
  
 Existing readiness requirements and Ready-based early starts remain: returning to Idle does not automatically make you Ready. Explicit ''.start'', ''.wait'', score-fetch delay and the numeric countdown retain their existing behavior. The bot uses already-received referee status events, with no additional API polling. [[updates:v6_7_23|Release notes and protocol details]]. Existing readiness requirements and Ready-based early starts remain: returning to Idle does not automatically make you Ready. Explicit ''.start'', ''.wait'', score-fetch delay and the numeric countdown retain their existing behavior. The bot uses already-received referee status events, with no additional API polling. [[updates:v6_7_23|Release notes and protocol details]].
  
wiki/match_lifecycle.txt · Last modified: by wikiadmin

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki