edgegap-godot
Godot 4 + Edgegap: take a Godot multiplayer game (MultiplayerAPI, @rpc, ENetMultiplayerPeer, WebSocketMultiplayerPeer, MultiplayerSpawner, netfox) to dedicated servers and matchmaking, end to end. Load this before using any Edgegap MCP tool on a Godot project (project.godot, .gd, .tscn, export_presets.cfg). It has tested GDScript templates (a server lifecycle autoload that waits for the matched players and stops its own deployment, a matchmaker client and Find Match button), the Edgegap Godot plugin build (export, image, push from the editor), app version ports (UDP for ENet, WS + TLS Upgrade for web and wss), matchmaker config, and fixes for Godot pitfalls: empty server logs, export allowlists that drop new scripts, join validation that silently blocks matched players. Use when a Godot dev wants online play: "host my Godot game", "nobody should host", "Find Match button", "Godot web multiplayer", or is debugging Godot deployments, ports or matchmaking on Edgegap.
Target: Design & content creation. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Edgegap for Godot 4: dedicated servers + matchmaking
- How to work
- Phase 0: Understand the project
- Phase 1: Make the game dedicated-server ready
- Phase 2: Install the Edgegap plugin and connect
- Phase 3: Export, containerize, push
- Phase 4: App version and a direct deploy
- Phase 5: Matchmaker
Goal: a player clicks Find Match, the Edgegap matchmaker starts a headless Godot server near the matched players, every client joins it, the server starts the match when they're all in, and it stops its own deployment when the match is over. Done means that loop works with real exports, not that the scripts parse. Where this comes from: edgegap/game-sample-godot-arena-shooter (Godot 4.7.2, server-authoritative, WebSocketMultiplayerPeer on port 7000) ran end to end on Edgegap on 2026-10-20: two Windows clients pressed FIND MATCH, were matched onto the same deployment over wss:// (TLS Upgrade), played, and the deployment stopped itself. Its EDGEGAP.md is a working reference. On 2026-10-28 it moved to the Edgegap Godot plugin's build: its preset and the plugin's default Dockerfile, unchanged, ran in a local container and on an Edgegap deployment: two wss:// clients played a match and the deployment stopped itself. The templates in assets/godot/edgegap/ are that sample's server lifecycle and matchmaker client made game-agnostic. They were tested on 2026-10-20 with Godot 4.7.2 in a minimal project: a Linux dedicated server export in Docker, a fake matchmaker and two clients, with both E
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- edgegap/llm-agent-skills
- Source file
- skills/edgegap-godot/SKILL.md
- Fixed revision
- fd510ba826ea29ab359e70e185d2e650ef6827de
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: edgegap/llm-agent-skills · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-11T08:01:42.868Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
Apache-2.0. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.