edgegap-threejs

Topics in the source

• Edgegap for Three.js and other browser games: one Node.js server per match
• How to work
• Phase 0: Understand the game
• Phase 1: Authoritative server, local
• Phase 2: Browser client
• Phase 3: Image, app version, one direct deployment
• Phase 4: Matchmaker
• Phase 5: End-to-end test and hand-off

Goal: a browser game where each match runs on its own authoritative Node.js server on Edgegap, near its players. Players click Find match, the page asks Edgegap's matchmaker for a ticket through the official Edgegap JS SDK (@edgegap/sdk), the matchmaker starts a server and returns wss:// .pr.edgegap.net: , everyone plays, and the server stops its own deployment when the match is over. Done means real clients played a whole match on one Edgegap deployment that then stopped itself, not that the image builds. Verified on Edgegap on 2026-10-22 with netcode-sample-threejs-minigames: five Three.js games (top-down shooter, kart racer, 2v2 soccer with matchmaker teams, light cycles, sumo brawler) from one image, one app version per game and one matchmaker with a profile per game. Headless players queued through the matchmaker landed on one deployment per game, played full matches over wss with TLS Upgrade, and every deployment stopped itself about 17 s after its match; deployments whose matched players never connected stopped after 120 s; a direct deployment (no matchmaker) did the same. The templates in assets/ are that repo's shared files plus a skeleton game. Not run on Edgegap: Babylon

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