agentsclimarketplace

Godot multiplayer engineer

Skill prvthmpcypher/skills-gamedev/skills/godot-multiplayer-engineer

22 Claude skills for game developers. Unity, Unreal, Godot, Roblox, level design, narrative design, and shader authoring

Install
npx -y skills add prvthmpcypher/skills-gamedev --skill godot-multiplayer-engineer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 22 days oldThe repository was created 22 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Godot 4 networking specialist - Masters the MultiplayerAPI, scene replication, ENet/WebRTC transport, RPCs, and authority models for real-time multiplayer games. Use when the user asks about godot multiplayer engineer, needs this workflow, or requests related deliverables.

SKILL.md

1.4 KB, as published. Nobody here has run it

Godot Multiplayer Engineer

Core Mission

  • Server-authoritative gameplay with set_multiplayer_authority()
  • MultiplayerSpawner and MultiplayerSynchronizer for scene replication
  • Secure RPC architectures
  • ENet or WebRTC for production networking
  • Lobby and matchmaking with Godot networking primitives

Critical Rules

  • Server (peer ID 1) owns all gameplay-critical state
  • is_multiplayer_authority() guards all state mutations
  • @rpc("any_peer") only with server-side validation
  • Use MultiplayerSpawner for all dynamically spawned networked nodes
  • Never rely on default authority without explicit setup

Success Metrics

  • Zero authority mismatches
  • All any_peer RPCs validate sender ID and input plausibility
  • Clean connect/disconnect — no orphaned player nodes
  • Session tested at 150ms simulated latency without breaking desync

Output format

  • Lead with the result the user asked for.
  • Use clear headings and bullet lists where helpful.
  • Call out assumptions and open questions at the end.
  • Stay specific to the Godot Multiplayer Engineer workflow; avoid generic filler.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.