Godot multiplayer authority
Clarifies which player or server may change shared game state. It helps prevent invalid attacks, duplicate rewards and incomplete worlds when someone joins an ongoing match.
godot-multiplayer-authority
See how it helpsWhen is it useful?
Use when client requests could improperly change shared game state.
What does it help you do?
- Assigns authority per action, field and entity lifecycle.
- Validates commands rather than trusting an RPC annotation.
- Separates reliable events from replicated state and handles disconnection.
Try asking this
In our cooperative dungeon, let two players open the same reward chest. Validate distance and ownership on the authority, then test a repeated request and a late join; the chest stays open and its reward is granted only once.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
Godot — multiplayer authority
Use when adding Godot RPCs, replicated nodes, ownership or reconnect behavior.
Version and project gate
Inspect project.godot, config/features, .tscn and .tres files, export_presets.cfg without credentials, input actions, autoloads, renderer, physics backend and installed Godot executable. Distinguish Godot 3 from 4 before selecting APIs. Never turn a task into an engine upgrade without the user’s intent. Read the version-matching official reference when an API decision depends on it.
Work
Map peer authority for every action and state field. Validate commands on the authority side, establish spawn/despawn ownership and distinguish reliable events from replicated current state. Pin RPC paths and signatures to the installed release. Treat disconnect and late join as explicit transitions.
Deliver
A peer/authority table and a minimal two-peer scenario with validation and lifecycle handling. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
An RPC annotation is not authorization; a client-reported position or reward needs game-rule validation.
Acceptance scenario
Join a running level, disconnect during an action and submit an invalid or duplicated command without corrupting authoritative state. Follow the project’s execution and verification permissions. If execution or a target device is unavailable, provide the reproduction steps and name the remaining uncertainty; do not mark it passed.
Scope and sources
This skill belongs to Rune. Agent selection is restricted by Orqestria’s assigned-agent policy, including forced skill selection; instruction text alone is not an access control. These are original task workflows researched from official documentation, not a copied or endorsed vendor skill.
Included files 1
SKILL.md