In Game Manager, navigate to Multiplayer > Matchmaking and create a new queue, defining rules such as skill range, region affinity, and team size constraints.
From a client, call the CreateMatchmakingTicket API with the queue name, player attributes (e.g., skill rating, preferred region), and a timeout value; store the returned TicketId.
Poll GetMatchmakingTicket using the TicketId at a reasonable interval (e.g., every 6 seconds) until Status transitions to Matched or Canceled.
On Matched status, retrieve the MatchId from the ticket response, then call GetMatch to obtain server connection details and the full roster of matched players.
Handle Canceled tickets by displaying a timeout message and optionally re-submitting a new ticket with relaxed attribute constraints.
Monitor queue health in Game Manager dashboards and adjust rule thresholds based on average wait time and match quality metrics.
Known gotchas
Matchmaking tickets expire based on the timeout you set; clients must handle Canceled status and avoid assuming a ticket is perpetually active.
Attribute names in the ticket must exactly match the attribute paths defined in the queue rule set, or the ticket will fail validation silently.
PlayFab matchmaking is region-scoped; ensure the queue is created in the same Azure region your servers are deployed to minimize latency.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp