Colyseus diagnostics
Connects disconnects and lag to actual room, transport and server measurements. It checks how rooms end during deployment instead of treating a reachable server as proof of a healthy match.
colyseus-diagnostics-delivery
See how it helpsWhen is it useful?
Use it when rooms accumulate, players disconnect or a multiplayer deployment behaves differently from local testing.
What does it help you do?
- Measures room counts, patch size and tick duration.
- Correlates disconnects with deployment transport and proxy settings.
- Defines draining and room disposal before server restart.
Try asking this
Players disconnect from our card battler during releases. Trace one room through the proxy and transport, measure tick and patch sizes, and define graceful draining. Verify ongoing matches receive the intended ending or reconnect path rather than silently losing their last result.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
Colyseus — diagnostics delivery
Use when diagnosing Colyseus room leaks, bandwidth, disconnects or multiplayer deployment failures.
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
Measure active rooms, clients, tick duration, patch size and lifecycle counts against a reproducible scenario. Pin transport/proxy settings to the deployed topology. Correlate disconnects without recording auth tokens. Define draining, room disposal and bounded recovery before rollout.
Deliver
A room lifecycle/bandwidth evidence record and operational handover for the actual deployment. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
Do not claim scale from a single local room or reconnect uncertain durable operations by blindly repeating them.
Acceptance scenario
Create and dispose rooms repeatedly, interrupt transport, restart a server and report the actual limits exercised. 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