edgegap-manus

Topics in the source

• Edgegap for Manus games: dedicated servers + matchmaking
• How to work
• Phase 0: Understand the game
• Phase 1: Authoritative game server, local
• Phase 2: Steam sign-in and the matchmaking backend
• Phase 3: Image, registry, one Edgegap deployment
• Phase 4: Matchmaker
• Phase 5: End-to-end test and hand-off

Goal: a player signs in with Steam on the Manus site, clicks Find Match, the Manus backend gets them a seat on an Edgegap server near them, the browser connects over wss, the server runs the game, and the server stops its own deployment when the match is over. Done means two real players did that on the published site, not that the code compiles. Why this shape, so you can defend it when the developer asks for shortcuts: The backend creates tickets, not the browser. The matchmaker Auth Token is client-safe by design, but keeping it on the backend lets the backend tie every ticket to a verified Steam account, stop duplicates and enforce parties. It also means no allowedcorsorigins. Steam IDs come only from the backend session. A Steam ID in a request body is a claim anyone can type. The join token is what lets a player in. Signed by the backend, bound to the Steam ID, the ticket and the deployment, valid 60 s, single use. The server holds only the public key, so a leaked image or env var can't mint tokens. The server is authoritative. Browser code is readable by anyone. Rules, scores and timers that stay in the browser can be changed from the console. This skill's templates were tes

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