Set up an authoritative matchmaker and realtime match handler using Nakama

domain: gaming · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. From the client SDK, call the matchmaker add method (e.g. AddMatchmakerAsync or add_matchmaker_async depending on SDK language) with minCount, maxCount, and a Lucene-like query plus string/numeric properties describing the player
  2. On the server, register a before-hook with nk.register_rt_before(fn, "MatchmakerAdd") to authoritatively override or validate cheat-prone properties like rank instead of trusting client-supplied values
  3. Set count_multiple so it evenly divides your desired match size, since matchmaker tickets never resolve if the pool can't be split evenly
  4. Implement the authoritative match handler server-side (Go, Lua, or TypeScript runtime) using MatchInit and the related match loop callbacks to run per-tick game logic
  5. Test matchmaking queries carefully in staging — a leftover wildcard query like "*" will match any opponent regardless of intended properties
  6. Deploy the server runtime module alongside the Nakama server and verify match creation end-to-end before opening matchmaking to real players

Known gotchas

Related routes

Set up server-side runtime logic and authenticate clients with Nakama
heroiclabs.com · 6 steps · unrated
Stand up a custom matchmaking function and director on Open Match in Kubernetes
open-match.dev · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans