godot-multiplayer

1# Godot Multiplayer (4.x high-level)
2 
3Connect peers, call functions remotely with `@rpc`, assign authority, and replicate state
4with `MultiplayerSpawner`/`MultiplayerSynchronizer`. Targets **Godot 4.7** (ENet). Treat
5all client input as untrusted; keep the server authoritative.
6 
7## When to use
8 
9- Use when adding networked multiplayer: hosting/joining over ENet, calling RPCs,
10  assigning per-node authority, or auto-spawning/syncing nodes across peers.
11 
12**When *not* to use:** local split-screen (no networking); raw TCP/UDP/WebSocket protocol
13work (low-level `PacketPeer`); HTTP requests. For save/persistence → `save-systems`.
14 
15## Core workflow
16 
171. **Create a peer** (`ENetMultiplayerPeer`), call `create_server(port, max)` or
18   `create_client(ip, port)`, and assign it to `multiplayer.multiplayer_peer`. The
19   server's unique ID is always `1`; clients get random positive IDs.
202. **Handle connection signals** on `multiplayer`: `peer_connected(id)`,
21   `peer_disconnected(id)`, `connected_to_server`, `connection_failed`,
22   `server_disconnected`.
233. **Define RPCs** with `@rpc(...)`. Call them on a `Callable` via `rpc()` (all peers) or
24   `rpc_id(peer_id)` (one peer). Inside, `multiplayer.get_remote_sender_id()` tells you who
25   sent it.
264. **Keep RPC signatures identical** on every peer that runs the script — Godot checksums
27   all `@rpc` methods in a script; a mismatch prints errors that can name an unrelated RPC.
28…