scenario-godot-multiplayer
FeaturedUse when a Godot 4 game goes online or co-op: host and join with ENet, WebSocket for a web build, RPCs (@rpc, rpc_id, any_peer), MultiplayerSpawner and MultiplayerSynchronizer, player authority, lobbies and login, a dedicated or headless server export, lag, rubber-banding, prediction or netfox, cheating, bandwidth, Steam, Nakama or WebRTC. Symptoms: players do not appear on the client, 'rpc node checksum failed', 'node not found' on an RPC, desync, the server build is huge, a client never connects.
Install
Quality Score: 96/100
Skill Content
Details
- Author
- scenario-labs
- Repository
- scenario-labs/skills
- Created
- 3 months ago
- Last Updated
- yesterday
- Language
- Python
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
godot-multiplayer-engineer
Builds Godot 4 networking: MultiplayerAPI, scene replication, ENet/WebRTC transport, RPCs and authority models. Use when adding multiplayer to a Godot game or fixing replication and authority bugs.
godot-multiplayer-engineer
Builds Godot 4 networking: MultiplayerAPI, scene replication, ENet/WebRTC transport, RPCs and authority models. Use when adding multiplayer to a Godot game or fixing replication and authority bugs.
multiplayer-networking
Designing networked gameplay - authority model, state replication, client prediction and reconciliation, latency compensation, bandwidth budgeting, and handling disconnects. Use when adding multiplayer, when networked movement or combat feels wrong, when players desynchronise, or when deciding between listen server, dedicated server and peer-to-peer.