multiplayer-intent-replication-workflow

name	multiplayer-intent-replication-workflow
description	Operational workflow for routing player intent to authoritative commits and configuring replication so clients converge deterministically.
tier	operational
godot_version	4.6+
doc_anchors	["godot-docs/tutorials/networking/high_level_multiplayer.rst","godot-docs/classes/class_multiplayersynchronizer.rst","godot-docs/classes/class_scenereplicationconfig.rst","godot-docs/classes/class_multiplayerspawner.rst"]
tags	["multiplayer","replication","intent"]
depends_on	["godot-skills/godot-tertiary/networking-reliability-reconciliation-contract/SKILL.md","godot-skills/godot-operational/multiplayer-reconnect-runbook/SKILL.md"]

Multiplayer Intent Replication Workflow

Use When

• Implementing authoritative multiplayer state updates.
• Migrating from ad hoc RPCs to structured intent/commit flow.
• Investigating client divergence after replicated updates.

Outcomes

• Player actions are transmitted as intent, not direct client-side state writes.
• Authoritative commits are replicated through configured synchronization surfaces.
• Clients converge on consistent state after commit application.

Required Rules

• Treat client input as intent proposals to authority, not state mutations.
• Replicate committed state boundaries with explicit config and ownership.
• Keep replicated property sets minimal and deterministic.
• Separate transient presentation effects from authoritative replication channels.

Workflow

1. Define intent envelope and authoritative commit payload boundaries.
2. Route client actions to authority and validate request semantics.
3. Configure replication surfaces (MultiplayerSynchronizer and replication config).
4. Apply commits on clients in authoritative order and reconcile pending intent state.
5. Exercise reconnect/rejoin paths and verify convergence.

Validation

• Duplicate client intents do not double-apply commits.
• Replication config updates produce consistent state across peers.
• Rejoin/reconnect path converges to current authoritative commit boundary.

Failure Modes

• Clients mutate replicated gameplay state locally before authority commit.
• Replication includes unnecessary volatile fields and causes jitter/desync.
• Intent and presentation channels are mixed, obscuring reconciliation.

Local Doc Anchors

• godot-docs/tutorials/networking/high_level_multiplayer.rst
• godot-docs/classes/class_multiplayersynchronizer.rst
• godot-docs/classes/class_scenereplicationconfig.rst
• godot-docs/classes/class_multiplayerspawner.rst