What is the core principle of the starwards-colyseus skill?

The core principle is that the server state is the single source of truth; commands modify this authoritative state, and clients receive automatic patches to their local state mirrors.

What is the difference between JSON Pointer and Typed Commands?

JSON Pointers provide a dynamic way to update properties without extra server code, ideal for GM tools, while Typed Commands offer better performance and type safety for high-frequency game actions.

Why does the @gameField decorator need to be placed last?

TypeScript decorators execute from bottom to top. Placing @gameField last ensures it wraps the final property correctly so Colyseus can register it for schema synchronization.

How does Starwards handle precision loss in multiplayer sync?

Starwards uses float32 for network efficiency, which can cause minor precision loss compared to 64-bit JavaScript numbers. It recommends using toBeCloseTo() in tests to account for these variations.

Starwards Colyseus Multiplayer

Name: Starwards Colyseus Multiplayer
Author: starwards

bystarwards

•

Game Development

Implements authoritative multiplayer state synchronization patterns using Colyseus for the Starwards spaceship simulator.

About

This skill provides specialized guidance for managing real-time multiplayer synchronization within the Starwards ecosystem using the Colyseus v0.15 framework. It establishes a 'state as source of truth' architecture where the server remains authoritative while clients receive automatic updates. Developers can leverage this skill to correctly implement the @gameField decorator, manage complex room architectures (Admin, Space, and Ship rooms), and handle client-to-server communication via JSON Pointers and typed commands. It specifically addresses common synchronization pitfalls such as decorator execution order, collection initialization, and floating-point precision issues in networked environments.

Key Features

Authoritative server-side state management and schema design
Multi-room architecture patterns for different gameplay scales
Multiplayer testing strategies using ShipTestHarness and MultiClientDriver
Dual command patterns using JSON Pointers and typed StateCommands
Correct implementation of @gameField decorators for property synchronization
38 GitHub stars

Use Cases

Debugging real-time state replication issues between game clients and servers
Implementing low-latency player commands with server-side validation
Synchronizing complex spaceship systems like shields and reactors across multiple stations

About

Key Features

Authoritative server-side state management and schema design
Multi-room architecture patterns for different gameplay scales
Multiplayer testing strategies using ShipTestHarness and MultiClientDriver
Dual command patterns using JSON Pointers and typed StateCommands
Correct implementation of @gameField decorators for property synchronization
38 GitHub stars

Use Cases

Debugging real-time state replication issues between game clients and servers
Implementing low-latency player commands with server-side validation
Synchronizing complex spaceship systems like shields and reactors across multiple stations