mcpbeat

Godot Multiplayer Networking

thedivergentai/godot-multiplayer-networking

Expert multiplayer for desync, rollback, dedicated --headless servers, interest culling, and bandwidth spikes: ENet/WebRTC choice, authority, secure RPCs, client prediction/reconcile, and adaptive sync. Trigger on rubber-banding, cheat-able clients, peer floods, late join, or profiler Network spikes — not only greenfield online games. Keywords: multiplayer, RPC, ENetMultiplayerPeer, MultiplayerSynchronizer, authority, client prediction, rollback, interest management, headless, desync.

14k tokens
context cost
the whole folder, loaded on every use
25
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
451
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/thedivergentai/GD-Agentic-Skills --skill godot-multiplayer-networking

The instruction itself

21 sections, as written by the author

Godot 4.7 Baseline

  • Expert patterns in this skill target Godot 4.7+ (stable, 2026-06-18).
  • Consult the Godot 4.7 migration guide when upgrading projects from 4.6.
  • NEVER assume 4.6 defaults (stretch mode, audio area_mask, RichTextLabel percent flags) without checking 4.7 migration notes.

Multiplayer Networking

Server authority, prediction/reconcile, secure RPCs, and interest culling — not a high-level multiplayer tutorial.

NEVER Do (Expert Networking Rules)

Core Architecture

  • NEVER use Reliable for high-frequency data (Position/Movement) — Reliable packets block all following packets until acknowledged (Head-of-Line blocking). Use UnreliableOrdered.
  • NEVER trust the client for shared state (Health/Money/Inventory) — Clients should only suggest actions. The Server MUST validate and broadcast the result.
  • NEVER hardcode the Server IP — Always allow for discovery (net_lan_discovery.gd) or pass the IP via CLI/UI.

Performance & Bandwidth

  • NEVER send the same data every frame — Use net_adaptive_sync_throttle.gd to only send updates when state changes significantly or at fixed Hz intervals (e.g., 20Hz).
  • NEVER use JSON for high-speed synchronization — String serialization is massive over the wire. Use bit-packing (net_packet_bit_packer.gd) to keep packets under 100 bytes.
  • NEVER broadcast to all peers if it's not needed — In large worlds, use Interest Management (net_visibility_grid_culling.gd). A player in the forest doesn't need the position of a player in the city.

Security

  • NEVER allow unlimited RPC calls per second — An attacker can flood the server with 1,000 "Attack" RPCs to crash the game. Use net_packet_rate_limiter.gd.
  • NEVER expose PeerIDs to the end-user — PeerIDs are internal. Always map them to persistent UserIDs (net_custom_id_mapper.gd) from a database.
  • NEVER run a dedicated server with a GUI enabled — Use --headless (net_headless_server_auto_start.gd) to save resources and ensure stability.

Decision Tree (transport / authority / sync Hz)

| Question | Prefer | Script |

|----------|--------|--------|

| Desktop/console LAN or dedicated UDP | ENet | MANDATORY net_enet_expert_config.gd |

| Browser / NAT-hostile peers | WebRTC (or WebSocket fallback) | Official Docs + peer wrappers; still use secure RPC scripts |

| Who owns gameplay truth? | Server-authoritative | MANDATORY server_authoritative_controller.gd |

| Dedicated host without GUI | --headless | MANDATORY net_headless_server_auto_start.gd / server_dedicated_host.gd |

| Position @ 10–20 Hz, not every frame | Adaptive throttle | MANDATORY net_adaptive_sync_throttle.gd |

> Do NOT Load lobby/RPC beginner recipes from memory — use the golden path below and open only matching scripts.

Golden Path

  • Host / dedicated → server_dedicated_host.gd + net_headless_server_auto_start.gd; clients → client_network_setup.gd.
  • Secure RPC → secured_rpc_pattern.gd + net_packet_rate_limiter.gd + secure_variable_synchronizer.gd.
  • Prediction / reconcile → client_prediction_synchronizer.gd + net_anti_desync_reconciler.gd; fighting/rollback → net_rollback_helper.gd.
  • Interest culling → net_visibility_grid_culling.gd before broadcasting positions.

Available Scripts

Transport & host

  • net_enet_expert_config.gd — channels, compression, bandwidth.
  • net_headless_server_auto_start.gd — CLI/--headless detect.
  • server_dedicated_host.gd — dedicated host bootstrap.
  • client_network_setup.gd — client peer join.
  • net_lan_discovery.gd — UDP LAN discovery.
  • network_error_handler.gd — disconnect/error routing.
  • packet_peer_latency_test.gd — latency probes.
  • net_heartbeat_monitor.gd — RTT/jitter.

Authority, RPC, sync

  • server_authoritative_controller.gd — server validates actions.
  • secured_rpc_pattern.gd — safe RPC annotations/patterns.
  • secure_variable_synchronizer.gd — server-owned vars.
  • net_packet_rate_limiter.gd — flood protection.
  • net_packet_bit_packer.gd — compact payloads (no JSON on hot path).
  • net_adaptive_sync_throttle.gd — Hz / change-threshold sync.
  • game_state_sync_manager.gd — snapshot/state sync.
  • multiplayer_spawner_manager.gd — spawn authority.
  • network_input_synchronizer.gd — input frames to server.
  • networked_interpolator.gd — remote entity smoothing.
  • net_custom_id_mapper.gd — UserID ↔ PeerID.

Desync / rollback / interest

  • client_prediction_synchronizer.gd — predict + correct.
  • net_anti_desync_reconciler.gd — forced correction.
  • net_rollback_helper.gd — snapshot re-sim helper.
  • net_visibility_grid_culling.gd — interest management.

Expert Pointers

  • Position/movement: UnreliableOrdered + throttle — never reliable every frame.
  • Clients suggest; server validates and broadcasts results.
  • Large worlds: cull with visibility grid before adding more sync Hz.

Deep dives (on demand)

  • RPC modes, lobby handshake, puppet interpolation → rpc-lobby-and-sync.md
  • Delta-compression + network simulator concepts live in that reference (LLM-ignorance: unreliable vs reliable HoL blocking is NOT generic knowledge).

Reference

> Progressive disclosure: open Official Documentation links only when researching a specific API; load Related Skills when routing to a peer domain — do not preload the whole lattice.

Official Documentation

  • High-level multiplayer — RPC modes, authority, and peer lifecycle for host/join lobbies and server-validated actions.
  • Networking — Transport map (ENet / WebSocket / WebRTC / HTTP) so peer choice matches platform and NAT constraints.
  • MultiplayerAPImultiplayer singleton: peer IDs, connection signals, and rpc / rpc_id entry points.
  • MultiplayerPeer — Transfer modes (reliable / unreliable / unordered) and connection status shared by every backend.
  • ENetMultiplayerPeer — UDP host/client peer used for LAN, dedicated servers, and most action games.
  • SceneMultiplayer — Default MultiplayerAPI: root path, auth callbacks, and scene-tree RPC routing.
  • MultiplayerSpawner — Spawn/despawn replication so late joiners share the same networked scene graph.
  • MultiplayerSynchronizer — Property replication, on-change deltas, and visibility filters that replace ad-hoc position RPCs.
  • Nodeset_multiplayer_authority / is_multiplayer_authority ownership rules for input vs shared state.
  • PacketPeerUDP — Raw UDP send/receive for LAN discovery broadcasts outside the high-level multiplayer peer.
  • WebRTC — Browser-friendly P2P path when ENet UDP cannot punch through firewalls alone.
  • Command line tutorial--headless and CLI flags for dedicated-server launches and multi-instance tests.
Prerequisites
  • godot-project-foundations — Project layout, Autoloads, and export/feature flags that host/join and dedicated-server builds depend on.
  • godot-gdscript-mastery — Typed @rpc annotations, Callables, and PackedByteArray patterns used by secure RPCs and bit-packers.
  • godot-input-handling — Split InputMap reads from simulation so clients send intents and the authority owns outcomes.
Complements
Downstream / consumers
Master
  • godot-master — Library router and mirrored module entry; open when discovering which Domain Skill owns a cross-cutting networking concern.

How to use it

Copy the folder

Take thedivergentai/godot-multiplayer-networking from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.