PoolRotater Wiki

Your guide to automatic osu! multiplayer

User Tools

Site Tools


updates:v7_3_5

Differences

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

Link to this comparison view

updates:v7_3_5 [2026/10/27 00:25] – v7.3.5 published ruleset preferences and update recovery wikidocsupdates:v7_3_5 [2026/10/27 00:28] (current) – document first-transition refresh limitation wikidocs
Line 12: Line 12:
   * A proven controller failure after the affected rooms have closed can be retried by the staged update timer. Unknown ownership, partial transactions and unproven failures remain held for review.   * A proven controller failure after the affected rooms have closed can be retried by the staged update timer. Unknown ownership, partial transactions and unproven failures remain held for review.
   * Existing configurations, room intent, OAuth authorization, enrollment, catalogs, ratings and statistics are preserved. The preference database schema remains compatible with supported hosts on different versions.   * Existing configurations, room intent, OAuth authorization, enrollment, catalogs, ratings and statistics are preserved. The preference database schema remains compatible with supported hosts on different versions.
 +
 +**First-transition limitation:** The scheduled-refresh fence takes effect after v7.3.5 is running. An outgoing v7.3.3 or v7.3.4 worker does not yet have it, so a scheduled room refresh during this upgrade can still make the drain stop for review. A hold is not an installed update; retain state and use supported recovery. Occupied rooms are not force-closed.
  
 The signed feed offers this controller update to supported v7.3.3 and v7.3.4 installations. Rooms drain independently at safe empty boundaries; the controller update waits for all required rooms and bookings to clear. Deliberately stopped slots remain stopped. A host with an uncertain operation retains its state for review. The signed feed offers this controller update to supported v7.3.3 and v7.3.4 installations. Rooms drain independently at safe empty boundaries; the controller update waits for all required rooms and bookings to clear. Deliberately stopped slots remain stopped. A host with an uncertain operation retains its state for review.
updates/v7_3_5.txt · Last modified: by wikidocs

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki