Backed by: @pithy-sh/matchmaking. Scopes: matchmaking:queues:read · matchmaking:queues:moderate.
What it shows
Matchmaking is the capability it reads, and the reference has the routes behind every read and act here.
Who is waiting to be matched, the rooms open, and the invites nobody has answered, read live from your Worker. Two kinds appear in the rail beside Ratings when your Worker composes matchmaking, at whatever path you mounted it: Matchmaking and Invites.
Matchmaking lists every game your config declares. Each row carries how many players make a match, and whether its queue and its room codes are open. Its filters, Open queue and Room codes, each on or off, narrow the games read. The overview is how the filter panel works.
The record is one game. How many make a match, the rating pool it buckets on or that it matches by region alone, whether its queue and room codes are open, and how long a player waits before it matches them with anyone. Under those come two sections. Waiting is its queue, as the game’s queue object answers: each player, their region, their skill and band, or Unrated, and how long they have waited. Open rooms is its rooms, a page at a time: each room’s code, occupancy against capacity, host, uses left, when it opened and when it expires.
Invites lists every pending invite, newest first, a page at a time. Each row carries who sent it, to whom, and how long it has waited. Game is sent to your Worker, so it answers over every pending invite, and offers the game keys the invites read carry, as you named them. Older than 1, 7, 30 or 90 days narrows this page only. The record is that invite: its game, who sent it, to whom, when, how long it has waited, and its status.
Never a friend list. No read here reaches the friend graph, which belongs to your players.
Dropping a player and canceling an invite
Two acts: drop a player from a game’s queue, and cancel a pending invite. Each one previews exactly what it will change, asks for a reason, and confirms once.
| Act | What it does |
|---|---|
| Drop from the queue | On a game’s record. You choose the player from those its queue lists. They leave the queue at once and are told your reason, so write it for them |
| Cancel the invite | On an invite’s record. Both players are told, and it can no longer be accepted |
What is shown after an act is your Worker’s answer. A game’s queue and rooms read again after a drop, and the invites read again after a cancel; a canceled invite stays open in the record, drawn as your Worker answered.
Each opening of an act mints one idempotency key, and every press of that opening sends it. A press whose answer was lost and is pressed again acts once, and says nothing changed a second time. Once a drop has been sent, the question keeps the player it named; to drop someone else, cancel it and ask again.
A refusal your Worker names stays in the question, with what you typed, so you can fix it and press again: the invite is gone or no longer pending, the player is not waiting, the game is not configured, or the key was spent on another act.
Each act is written to the dashboard’s own audit record: who did it, the reason, and whether it changed anything. A drop names the game and the player; a cancel names the invite and its game, never who sent it or to whom.
On every plan, and on Team
The reads render on every plan. Seeing the queues, the open rooms and the pending invites costs nothing.
The two acts are Team. Below it they are drawn locked, saying what Team buys.
Two scopes, a read and a write
matchmaking:queues:read is every read here, and it is a read, so it is in the default grant. A connection without it sees the panes refuse by name and send nothing. Scopes has how to add one to a connection made before it existed.
matchmaking:queues:moderate is both acts, and it is a write, so it is never in the default grant. A connection without it shows the acts unavailable, with the scope they need.
It keeps nothing
Opening a room, sending an invite and joining a queue are not buttons here. Those belong to your game.
Nothing here is kept. Games, queues, rooms and invites are fetched from your Worker for this screen and held in no Pithy table.