Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Implement [multiplayer action] in [game] using the existing networking model. Define its legal preconditions, required identity and ownership checks, and the authoritative result. The client should request the action; validate consequential values at the intended authority boundary.
If immediate local feedback is needed, distinguish prediction from accepted state and explain how disagreements are reconciled. Replicate only the information each recipient needs. Handle repeated, delayed, or obsolete requests according to the action policy.
Verify a valid action, a disallowed action, repetition, delay, and the result seen by another player. Check the authoritative record as well as the visible animation. Report the rules, evidence, and remaining network assumptions.Make this prompt yours
Replace bracketed fields with your goal, current behavior, and relevant evidence. Keep requirements that affect the task. Check the result against the acceptance criteria you supplied.
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
- Epic Games — server authority and state replication
- Unity — client prediction, rollback, and correction
Documentation links checked .
Editorial review · October 28, 2026
Supported: Original action template grounded in server authority and prediction. Its validation, recipient privacy, repetition, and delay tests are proposed requirements.