edgegap-matchmaking

Topics in the source

• Matchmaking for games on Edgegap
• Step 1: decide who owns matchmaking
• Step 2: design the profile
• Step 3: place servers near the players
• Step 4: backfill (join in progress)
• Step 5: ship the config
• What was verified
• Troubleshooting

Edgegap starts a server near a group of players and returns an address. Matchmaking is everything before that: who plays together, when a partial match is good enough, where the server goes, and what happens when someone leaves. This skill is the design layer, the same for every engine. Done means the developer knows who owns matchmaking, the config or allocator matches the game's real rules, players are placed by measured latency or IP, and, when the game needs it, a running server takes new players through backfill. The client code that sends tickets lives in the engine skills, and the backend code that calls the Deploy API lives in edgegap-deployments-api. Load those for the code; come back here for the decisions. Edgegap ships the matchmaker clients as SDKs: the Unity SDK (sdk-unity-sessions-matchmaker-server-browser) and the JavaScript/TypeScript SDK @edgegap/sdk (browser clients, and Node, Bun or Deno servers: groups and parties, page-reload resume, ARBITRIUM/MM parsing, backfill with ServerAgent), and the Edgegap SDK for Unreal Engine (UE 5.0-5.8, beta: beacons, groups, a server-side check that admits only players with a ticket for that server, MM readers, self-stop; steps i

This is an excerpt. Refer to the complete source and its current requirements.