メニュー
Architecture guide for networking in Space Station 14 — Lidgren integration, NetManager abstraction, message system, game state synchronization, PVS, network events, and component networking
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | ss14-netcode |
| description | Architecture guide for networking in Space Station 14 — Lidgren integration, NetManager abstraction, message system, game state synchronization, PVS, network events, and component networking |
| metadata | {"source_skill":"../../../.agents/skills/ss14-netcode/SKILL.md"} |
Canonical source skill file: ../../../.agents/skills/ss14-netcode/SKILL.md.
Use that file as the entrypoint and load resources from the same source skill directory.
Gives a complete practical analysis of the AtmosSystem API in Space Station 14: what methods to use for what, which of them are fresh and safe, which ones are legacy/limited, and how to correctly combine calls in gameplay, devices and map-level logic.
Parses the AtmosSystem architecture in Space Station 14 at the server/shared/client level: processing cycle, tile state, invalidations, connection with DeltaPressure and overlay synchronization. Use it when you need to understand how the system actually works, where it is safe to expand, and how not to break the performance/consistency of the atmosphere.
Gives a practical catalog of the AudioSystem API in Space Station 14: when to use the Play/Set/Stop/Resolve methods, how to work with predicted audio and filters, and how to use OpenAL EFX (auxiliary/effect/preset) without common mistakes.
Explains the AudioSystem architecture in Space Station 14 at the shared/server/client and OpenAL levels: audio entity lifecycle, PVS filtering, occlusion, streaming and EFX chain. Use when you need to understand the internal design of a system before expanding or debugging.
SS14 Database System Guide (PostgreSQL and SQLite)
A practical documentation standard in Space Station 14 for C#, SWSL, YAML and FTL: how to write `<summary>`, when to add explanatory comments, how to document partial systems, and how to avoid noisy documentation. Use it when writing, refactoring and reviewing documentation in code, prototypes and localization.
