Colyseus synchronized state
Separates lasting match facts from brief effects. It helps new players reconstruct the current world while private fields and event listeners stay within their intended visibility and lifetime.
colyseus-schema-state
See how it helpsWhen is it useful?
Use it when adding synchronized entities, private fields or client listeners that must survive reconnects correctly.
What does it help you do?
- Matches Schema syntax to installed package versions.
- Separates transient events from coalesced replicated field changes.
- Defines stable entity keys, private visibility and callback cleanup.
Try asking this
A spectator joins our arena after a tower has fallen. Replicate the destroyed tower and current scores, but do not replay every old explosion as new damage. Keep private hands hidden and verify leaving and rejoining does not duplicate state-change callbacks.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
Colyseus — schema state
Use when changing Colyseus Schema state, client callbacks, visibility or patch bandwidth.
Version and project gate
Inspect Server, client SDK and @colyseus/schema versions, TypeScript/decorator configuration, room registrations, auth hooks, patch/simulation rates, transport, deployment topology and persistence adapters. The 0.17 reconnection lifecycle must not be assumed for older versions. 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
Pin schema syntax to the installed package. Distinguish transient events from current replicated fields because a patch interval may coalesce intermediate mutations. Design stable entity keys and per-client visibility. Register and dispose client callbacks with room ownership.
Deliver
A state/visibility map and synchronized client view with explicit event-versus-state semantics. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
Do not encode every transient hit by repeatedly mutating a field whose intermediate values may never reach the client.
Acceptance scenario
Join after several state changes, remove an entity, hide private state from another player and reconnect with a full snapshot. 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 Relay. 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