atmos

Atmos is authoritative simulation and often performance-sensitive.

Ownership

Locate the existing simulation owner. Keep gas, fire, pressure, pipe networks, and device behavior on the server. Shared should contain only required components, enums, contracts, and UI messages. Client should render overlays and UI from replicated or explicit state.

Data and units

Use existing units, gas identifiers, GasMixture patterns, device components, and alarm flows. Do not create parallel gas containers or convert units ad hoc. Keep device tuning prototype-driven when content authors need control.

Performance

Avoid allocations, LINQ, repeated global queries, and broad per-tile work in update loops. Reuse buffers and existing batching. Review how often a device or tile update runs before adding work.

UI and resources

Keep server simulation separate from BUI and XAML. Validate every UI request on the server. Update prototypes, UI, locale, overlays, and sprite states together.

Verification

Test pressure boundaries, disconnected networks, deletion, anchoring, power loss, multiple gases, fire interaction, and malformed device settings when relevant. Run focused build/tests and YAML validation for touched prototypes.