godot-multiplayer-networking — Claude Code skill: Godot netcode

What godot-multiplayer-networking does

The skill covers the networking layer of a Godot project: ENet versus WebRTC, server authority, secure RPCs, client prediction with reconciliation, interest management and adaptive sync. It ships as a set of scripts grouped by job — transport and host, authority and sync, desync and rollback. A decision tree picks the transport: ENet for LAN and dedicated UDP, WebRTC or a WebSocket fallback for browsers and NAT-hostile peers.

The rules are blunt. Position and movement must not ride a reliable channel, because one unacknowledged packet blocks everything behind it — use UnreliableOrdered with throttling instead. Clients suggest actions, the server validates and broadcasts the result. In large worlds, cull positions through a visibility grid before raising sync frequency. JSON on the hot path is out: string serialization bloats packets, so bit-packing takes over.

Security gets its own section. A packet rate limiter keeps an attacker from flooding the server with RPC calls, and PeerIDs stay internal — they map to persistent UserID values from a database. Dedicated servers run with --headless to skip the GUI. This assumes you already have a Godot project; the skill targets a specific networking problem such as rubber-banding, late join or Network spikes in the profiler, not a greenfield game.