Skip to content
SkillModel-led2,526 tokens in use

godot-multiplayer

Builds Godot 4.7 high-level multiplayer with ENet, @rpc, authority, MultiplayerSpawner and MultiplayerSynchronizer, tested with two headless instances.

9,684 stars on the repository Apache License 2.0gamedev-skills/awesome-gamedev-agent-skills · skills/godot/godot-multiplayer
npx skills add gamedev-skills/awesome-gamedev-agent-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing godot-multiplayer costs

102tokens idle
2,526tokens in use
4,092tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetectedwrites filesdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter8/15
  • Structure23/25
  • Examples12/15
  • Output15/15
  • Size15/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 51
  • Writes files−8

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 51

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity92
  • Maintenance96
  • Community60
  • Maturity24
  • Momentum40

This skill guides an agent through Godot 4.7 high-level multiplayer: creating an ENet host or client, handling connection signals, defining @rpc methods, assigning per-node authority and replicating state with MultiplayerSpawner and MultiplayerSynchronizer. It treats all client input as untrusted and keeps the server authoritative.

It includes patterns for hosting and joining, client-to-server RPCs with validation, per-player authority, a synchronizer configured entirely from code, and host or join from command-line arguments. A two-instance headless smoke test starts a server and a client and checks both logs for the handshake and for error lines.

What You Get

  • A core workflow from creating the peer to server validation and a two-instance smoke test
  • GDScript patterns for host and join, RPCs, per-node authority, a code-configured synchronizer and command-line host or join
  • A shell recipe that runs a server and a client headless and greps both logs for errors and handshake lines
  • A gotcha list for RPC modes, checksum mismatches, node path mismatches, untrusted clients and Android permissions

Common Use Cases

  • Adding host and join to a Godot co-op game over LAN or the internet
  • Fixing an RPC that is rejected or a spawned node that is missing on clients
  • Giving each player authority over their own avatar while the server validates actions
  • Checking that a networked build starts and connects before asking a person to test it

What Makes It Unique

Most multiplayer guides stop at the API. This skill adds a runnable two-process check using command-line user arguments, with a pass condition read from the logs, and falls back to asking the user for logs when no Godot binary exists. It also explains the default authority RPC mode trap, where a server call to a client-owned node is dropped.

Under The Hood

The agent loads the SKILL.md and, when needed, a reference on RPC arguments, spawn functions, visibility filters, authentication and a lobby skeleton. For the smoke test it runs commands in your project: it starts a headless Godot server in the background and a headless client, both wrapped in timeouts, with logs written to files and searched with grep. The server listens on a local port and the client connects to the loopback address, so it uses the local network. The skill also has the agent edit GDScript to read host and join arguments. It makes no calls to outside services.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers