PoolRotater Wiki

Your guide to automatic osu! multiplayer

User Tools

Site Tools

You are here: PoolRotater Wiki » How the bot works » Queues and future picks
wiki:queues

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
wiki:queues [2026/10/07 20:18] – Normalize v6.7.26 documentation review references wikiadminwiki:queues [2026/10/10 18:56] (current) – Document v6.7.27-33, current rollout, map exclusions, DT refresh and queued staff moderation wikiadmin
Line 5: Line 5:
 ^ Availability | All lobbies | ^ Availability | All lobbies |
 ^ Documentation status | Current behavior | ^ Documentation status | Current behavior |
-^ Behavior reference | v6.7.26 · reviewed 2026-10-07 |+^ Behavior reference | Queue safety through v6.7.32 · reviewed 2026-10-10; check room version |
  
  
Line 31: Line 31:
  
 ===== DT and verification safety exceptions ===== ===== DT and verification safety exceptions =====
 +From [[updates:v6_7_30|v6.7.30]], catalogue age past 30 days alone no longer expires all DT eligibility; invalid per-map revision/checksum or source/calculator evidence still does. From [[updates:v6_7_32|v6.7.32]], [[wiki:map_exclusions|hot-loaded exclusions]] are another safety exception: excluded unplayed items are removed/replaced after a between-match audit, while running gameplay/countdowns remain protected. An excluded current item cannot start if no safe replacement exists. Replay cannot bypass exclusions.
 +
 Normal preference changes preserve existing entries, but safety checks are different. From [[updates:v6_7_26|v6.7.26]], ''.skip'' revalidates a queued variant before promotion. A DT map outside the newly selected difficulty range, or otherwise no longer eligible under the current rules, is discarded and another eligible replacement is selected. A fresh DT source-revision check also rejects changed charts. This exception prevents stale queued DT maps from crashing the room after a difficulty change; it does not make every preference change rebuild the visible queue. Standard ''.dt'' enables future mixed-DT selection without converting the visible queue into DT. ''.nm'', automatic DT disabling or expired verification can remove future unplayed DT entries; an upcoming DT current item can be replaced by a newly eligible NoMod pick. A running DT match finishes normally. The bot does not relabel the same chart NoMod while retaining its DT stars. Normal preference changes preserve existing entries, but safety checks are different. From [[updates:v6_7_26|v6.7.26]], ''.skip'' revalidates a queued variant before promotion. A DT map outside the newly selected difficulty range, or otherwise no longer eligible under the current rules, is discarded and another eligible replacement is selected. A fresh DT source-revision check also rejects changed charts. This exception prevents stale queued DT maps from crashing the room after a difficulty change; it does not make every preference change rebuild the visible queue. Standard ''.dt'' enables future mixed-DT selection without converting the visible queue into DT. ''.nm'', automatic DT disabling or expired verification can remove future unplayed DT entries; an upcoming DT current item can be replaced by a newly eligible NoMod pick. A running DT match finishes normally. The bot does not relabel the same chart NoMod while retaining its DT stars.
  
wiki/queues.txt · Last modified: by wikiadmin
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki