Files
sor/Client/context-files/scenes/ranked-play.scene.md
T

5.0 KiB

RankedPlay Scene

UI

  • Ranked lobby header (season, rank, queue health)
  • Loadout panel:
    • selected deck
    • selected archspirit
    • deck legality status for ranked ruleset
  • Queue actions:
    • Join Queue
    • Leave Queue
  • Matchmaking status panel:
    • elapsed queue time
    • estimated wait range
    • cancellation state
  • Lobby chat subsection:
    • ranked-only channel visibility while in this scene

Client

  • Load ranked eligibility and current competitive profile.
  • Prompt for deck selection + starting ArchSpirit before queueing.
  • Require valid deck + archspirit selection before enabling Join Queue.
  • Submit ranked queue request and transition to matchmaking state.
  • On match found, lock queue interactions and transition to gameplay scene with ranked ruleset payload.

Server

  • Return ranked season/profile data and queue eligibility.
  • Validate selected deck against ranked format/rules.
  • Enqueue/dequeue player for ranked matchmaking.
  • Emit match-found payload with authoritative match seed and ruleset.

Data Exchange

Client -> Server (RankedLobbyBootstrapRequest)

  • requestId, accountId, clientVersion

Server -> Client (RankedLobbyBootstrapResponse)

  • requestId, seasonSummary, rankedProfile, queueEligibility, formatId, rulesVersion

Client -> Server (RankedQueueJoinRequest)

  • requestId, deckId, archspiritId, formatId

Server -> Client (RankedQueueJoinResponse)

  • requestId, success, queueTicketId, estimatedWaitSeconds, errorCode

Client -> Server (RankedQueueLeaveRequest)

  • requestId, queueTicketId

Server -> Client (RankedQueueLeaveResponse)

  • requestId, success, errorCode

Server -> Client (RankedMatchFound)

  • requestId, queueTicketId, matchId, rulesetId, opponentSummary, acceptDeadlineUtc, gameServerEndpoint, matchToken

Matchmaking Handling (Design Draft)

Baseline Recommendation

  • Use skill rating (MMR) + rank tier as primary matching factors.
  • Use expanding search windows over time:
    • strict match window at queue start
    • gradually widen MMR/rank constraints each interval
  • Prioritize latency region compatibility.
  • Enforce anti-rematch cooldown (avoid immediate repeated same-opponent pairings when possible).

Queue Lifecycle

  1. Player joins queue with deckId + archspiritId locked.
  2. Server issues queueTicketId and tracks search window state.
  3. On candidate match, server validates both players still eligible/connected.
  4. Server emits RankedMatchFound with accept deadline.
  5. If accepted (or auto-accept policy), allocate match server and transition to gameplay.
  6. If declined/timeout/disconnect, apply policy (requeue/penalty) and notify client.

Matchmaking v1 Integration Spec

v1 Decisions (Locked)

  1. Accept flow: auto-accept (no ready-check popup) for fastest queue-to-match path.
  2. Queue type: solo queue only in v1.
  3. Deck/ArchSpirit lock: locked at queue join; changing either requires leaving queue.
  4. Placement: first 10 ranked matches per season are placement-calibrated.

v1 Search Window Expansion

  • 0s-30s: ±75 MMR, same rank tier bucket, same region preferred.
  • 31s-60s: ±125 MMR, adjacent rank tier allowed, same region strongly preferred.
  • 61s-120s: ±200 MMR, broader rank band, nearby low-latency regions allowed.
  • 121s+: ±300 MMR, widest v1 bounds, any allowed region under latency cap.

Region/Latency Policy

  • Preferred region from player profile/ping map.
  • Hard reject match candidates where predicted latency exceeds v1 cap (e.g. 140ms).
  • If no candidate under cap after 180s, notify client with option to keep waiting or cancel.

Anti-Rematch / Pairing Controls

  • Avoid same-opponent rematch within last 2 completed ranked games when alternatives exist.
  • Soft rule only (can be bypassed at high queue times to avoid deadlocks).

Dodge / Disconnect Policy (v1)

  • Since v1 is auto-accept, “dodge” is treated as disconnect/failure to load match.
  • First offense in rolling 24h: warning + immediate requeue allowed.
  • Repeated offenses: escalating queue lockouts (e.g. 2m, 5m, 15m).
  • Server records offense events for moderation review.

v1 Client Integration States

  • Idle
  • ValidatingLoadout
  • QueueJoining
  • InQueue
  • MatchAllocated
  • TransitionToGameplay
  • QueueError

v1 Server Event Contract Additions

Server -> Client (RankedQueueStatus)

  • requestId
  • queueTicketId
  • elapsedSeconds
  • searchWindowTier (T1/T2/T3/T4)
  • estimatedWaitSeconds
  • status (searching | allocating | requeue_required)

Server -> Client (RankedQueuePenalty)

  • requestId
  • penaltyType (warning | lockout)
  • lockoutSeconds (optional)
  • reasonCode

Telemetry / Audit Hooks (v1)

  • Queue enter/leave events with queueTicketId, deckId, archspiritId.
  • Match candidate evaluations (anonymized opponent id, accept/reject reason).
  • Final match allocation event with matchId, region, latency estimate.
  • Disconnect/penalty events with escalation tier.