godot-adapt-single-to-multiplayer

NEVER Do (Expert Multiplayer Rules)

Security & Authority

• NEVER trust client-reported state — Clients own their 'Input', NOT their 'Position' or 'Health'. Server must validate every coordinate and health change.
• NEVER use gettree() groups for authority checks — Use ismultiplayer_authority(). Group registration is non-deterministic in high-latency joins.
• NEVER allow unrestricted RPC rates — A malicious client can call a 'FireWeapon' RPC 10,000 times per second. Always implement rate-limiting (netrpcrate_limiter.gd).

Movement & Lag

• NEVER skip Client-Side Prediction — Movement without prediction feels 'heavy' and unresponsive. Predict movement locally, then correct only on server disagreement.
• NEVER sync peers at 60Hz — Sending entire state every frame will saturate client bandwidth. Use a lower tick-rate (20-30Hz) and interpolate between packets.
• NEVER snap peer positions — Abrupt position updates cause 'jitter'. Store a buffer of past states and lerp between them with a 100ms delay.

Bandwidth & Sync

• NEVER sync 'Full Floats' if possible — Quantize Vector3 data (truncating decimals) to save 50%+ bandwidth. Use MultiplayerSynchronizer with delta-sync enabled.
• NEVER ignore 'Late Joiners' — Players who join mid-game won't see existing environmental changes. Broadcast a full world-state 'Snapshot' on peer connection.
• NEVER test on 0ms ping — Everything works on localhost. Use a simulator (netlatencysimulator.gd) with 150ms ping to identify sync bugs.

Available Scripts

MANDATORY: Architecture decision tree first, then golden-path scripts. Deep latency workflows → [references/latency-testing.md](references/latency-testing.md).

Authority / transport bridges

[multiplayersync.gd](scripts/multiplayersync.gd)

MANDATORY when adding MultiplayerSynchronizer interpolation for remote peers. Trigger: authority owns transforms; non-authority interpolates.

[rpcbridge.gd](scripts/rpcbridge.gd)

MANDATORY signal→RPC bridge. Trigger: gameplay emits local signals; bridge validates authority and fans out RPCs.

Prediction / lag / lobby

[netpredictionreconciliation.gd](scripts/netpredictionreconciliation.gd)

CharacterBody prediction + input-buffer replay for server reconciliation.

[netsnapshotinterpolation.gd](scripts/netsnapshotinterpolation.gd)

Snapshot interpolation / jitter buffers for remote peers.

[netauthservervalidator.gd](scripts/netauthservervalidator.gd)

Authoritative validation (position, speed, actions).

[netrpcratelimiter.gd](scripts/netrpcratelimiter.gd)

RPC flood / macro protection.

[netinterestmanagement.gd](scripts/netinterestmanagement.gd)

Distance-based visibility to cut bandwidth.

[netdeltacompressionsync.gd](scripts/netdeltacompressionsync.gd)

Quantization + significance checks for delta sync.

[netlagcompensation.gd](scripts/netlagcompensation.gd)

Server-side rewind for hit registration.

[netlobbylatejoinsync.gd](scripts/netlobbylatejoinsync.gd)

Late-joiner world snapshot bootstrap.

Diagnostics

[netlatencysimulator.gd](scripts/netlatencysimulator.gd)

MANDATORY before ship — see [references/latency-testing.md](references/latency-testing.md).

[netdebugoverlaymonitor.gd](scripts/netdebugoverlaymonitor.gd)

RTT / loss / jitter overlay.

[netupnpdiscoverylogic.gd](scripts/netupnpdiscoverylogic.gd)

UPNP port mapping for listen-server / P2P hosts.

Architecture Patterns

Migration golden path (no inline host/join tutorials)

1. Separate input (client) from simulation (authority).
2. Set multiplayer_authority per player node; clients send intents only.
3. MANDATORY multiplayer_sync.gd for property replication / remote interpolation.
4. MANDATORY rpc_bridge.gd for gameplay events that cross the wire.
5. Add prediction / lag compensation scripts only for the genres that need them.
6. Validate with latency-testing reference + netlatencysimulator.gd at ~150 ms RTT.

Expert insights (WHY — keep in body)

• Client prediction — WHY: without local sim, RTT doubles perceived input lag. Replay buffered inputs after server correction ([netpredictionreconciliation.gd](scripts/netpredictionreconciliation.gd)).
• Interpolation buffer — WHY: raw sync packets jitter; lerp between snapshots with ~100 ms delay ([netsnapshotinterpolation.gd](scripts/netsnapshotinterpolation.gd)).
• Hit rewind — WHY: clients fire at past world state; server rewinds RIDs via PhysicsServer3D before raycast ([netlagcompensation.gd](scripts/netlagcompensation.gd)).
• Input send rate — WHY: 60 Hz input RPCs saturate uplink; batch at 20–30 Hz with significance checks ([netdeltacompressionsync.gd](scripts/netdeltacompressionsync.gd)).

Decision Tree: Which Architecture?

Advanced Networking Topics

Peer-to-Peer NAT Traversal (Hole Punching)

In P2P architectures, clients often sit behind firewalls. UPNP (Universal Plug and Play) is the first line of defense, allowing the game to request port forwarding from the router automatically using netupnpdiscovery_logic.gd.

For cases where UPNP fails:

• STUN/TURN: Use a STUN server to discover public IP/port pairings.
• Relay Servers: If direct connection is impossible, fallback to a relay server (TURN) to bridge the two peers.

Network Profiling & Visualization

Visualizing the packet timeline is critical for debugging jitter. Propose an overlay that graphs:

• Packet Arrival: A scrolling timeline showing when packets arrive relative to physics frames.
• Buffer Health: A visualization of the interpolation jitter buffer size.
• RTT (Round Trip Time): Real-time graph of latency spikes.

Deep recipes (on demand)

Reference

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

Official Documentation

• High-level multiplayer — RPC modes, authority, and peer lifecycle you must retrofit before any gameplay state leaves the single-player path.
• Networking — Transport map (ENet / WebSocket / WebRTC) so host/join choices match platform and NAT constraints.
• MultiplayerSynchronizer — Property replication, delta sync, and visibility filters that replace ad-hoc position RPCs.
• MultiplayerSpawner — Spawn/despawn replication when late joiners need the same scene graph as the host.
• SceneMultiplayer — Default MultiplayerAPI implementation: root path, auth callbacks, and RPC routing under SceneTree.
• ENetMultiplayerPeer — UDP host/client peer used by most LAN and dedicated-server ports of single-player games.
• MultiplayerAPI — multiplayer singleton surface: peer IDs, signals, and rpc / rpcid entry points.
• MultiplayerPeer — Transfer modes and connection status shared by every concrete peer backend.
• UPNP — Automatic port mapping for listen-server / P2P hosts behind consumer routers.
• WebRTC — Browser-friendly P2P path when ENet UDP cannot punch through firewalls alone.
• Node — setmultiplayerauthority / ismultiplayer_authority ownership rules for input vs state.
• PhysicsServer3D — Direct RID transforms for server-side hit rewind without SceneTree side effects.

Related Skills

Prerequisites

• godot-input-handling — Split InputMap reads from simulation so clients send intents and the authority owns outcomes.
• godot-signal-architecture — Local signal graphs that rpc_bridge.gd can wrap without coupling gameplay to transport.
• godot-autoload-architecture — Session/lobby Autoloads that outlive scene changes during host/join flow.

Complements

• godot-multiplayer-networking — Broader RPC, lobby, and ENet tuning once the single-player→online migration shape is fixed.
• godot-characterbody-2d — Deterministic moveandslide steps reused by client prediction and reconciliation buffers.
• godot-physics-3d — Body/shape setup that lag-compensation rewind and hit validation query against.
• godot-raycasting-queries — Server-side ray/shape queries for authoritative shots after state rewind.
• godot-debugging-profiling — RTT/jitter overlays and remote debug habits that catch sync bugs localhost never shows.
• godot-export-builds — Headless/dedicated-server export presets and CLI flags for real multi-instance tests.
• godot-server-architecture — PhysicsServer/RID patterns and headless host scaffolding used by rewind and dedicated peers.

Downstream / consumers

• godot-genre-shooter-fps — Hitscan/projectile feel that depends on prediction + lag compensation from this skill.
• godot-genre-battle-royale — Large-peer interest management and late-join snapshots at BR scale.
• godot-monte-carlo-balancer — Retune economy/TTK after netcode changes alter effective weapon timings.
• godot-performance-optimization — Cap replication rate and cull interest when bandwidth/CPU budgets break under peer load.

Master

• godot-master — Library router and mirrored module entry for this Domain Skill.