Run any Skill in Manus with one click

ss14-pvs

Stars2

Forks12

UpdatedApril 21, 2026 at 17:03

Work with SS14 PVS, visibility, network interest, PVS filters, PVS override behavior, visibility-dependent audio or popups, zoom PVS scale, or systems that behave differently when entities leave PVS.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

ss14-art

ss14-art/open-space

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	ss14-pvs
description	Work with SS14 PVS, visibility, network interest, PVS filters, PVS override behavior, visibility-dependent audio or popups, zoom PVS scale, or systems that behave differently when entities leave PVS.

SS14 PVS

Use this skill when a change depends on which clients can see, hear, or receive an entity.

PVS is a networking and relevance boundary, not just a visual effect. Keep filters narrow, avoid leaking hidden information, and remember that clients may not know about entities outside their PVS.

Workflow

Decide what must be relevant.

World feedback for nearby players should usually use PVS filters or PVS-scoped helpers.
Admin, ghost, camera, or debug visibility may require explicit override behavior.
UI or client code must tolerate entities leaving PVS or arriving later.

Keep network interest narrow.

Prefer Filter.Pvs(...), Filter.PvsExcept(...), and existing audio/popup helpers over broadcasting to all players.
Do not use global filters for local world feedback unless the feature truly is global.
Be cautious with PVS overrides; remove or scope them when the special view ends.

Do not assume the client has every entity.

Client code should handle missing entities, nullspace, and stale entity references.
Avoid client decisions that require hidden server-only or out-of-PVS entities unless a deliberate message/state path provides the data.

Coordinate with prediction and feedback.

Predicted local feedback may happen before server PVS feedback.
Avoid duplicate popups or sounds when both local prediction and PVS broadcasts exist.

Validate visibility behavior.

Test with another client or call out when multi-client verification was not possible.
For admin/debug visibility, check cleanup paths as carefully as setup paths.

Reference Map

../ss14-netcode/SKILL.md
../ss14-prediction/SKILL.md
../ss14-audio/SKILL.md
../ss14-debugging-workflow/SKILL.md

Good File Anchors

Content.Server/**/Pvs*.cs
Content.Server/**/PvsOverride*.cs
Content.Client/**/ContentEye*.cs
Content.Server/**/Filter*.cs
Content.Client/**/Overlay*.cs

Common Pitfalls

Broadcasting feedback globally when PVS or station/PVS filters are enough.
Assuming a client can resolve an entity that may have left PVS.
Leaving PVS overrides active after an admin camera, ghost, or debug view closes.
Treating PVS as security for data that should never be sent.

More from this repository

same repository

ss14-upstream-maintenance

ss14-art/open-space

Safely maintain a forked SS14 codebase with minimal upstream churn. Use when deciding whether to edit upstream files, when extending behavior in `_OpenSpace`, when preserving path similarity, or when avoiding unnecessary changes to RobustToolbox and offs content.

2026-05-112

ss14-atmos

ss14-art/open-space

Work with SS14 atmospherics, gases, gas mixtures, fire, pressure, pipes, vents, pumps, scrubbers, air alarms, atmos overlays, and atmos-related prototypes or UI.

2026-04-212

ss14-audio

ss14-art/open-space

Work with SS14 audio systems, sound specifiers, sound collections, ambient or lobby music, jukeboxes, predicted sound feedback, or audio assets under `Resources/Audio` and `Resources/Prototypes/SoundCollections`.

2026-04-212

ss14-databases-migrations

ss14-art/open-space

Work with SS14 server database models, EF Core DbContexts, SQLite/Postgres migrations, persistence services, admin/player data storage, and schema compatibility.

2026-04-212

ss14-npc-ai

ss14-art/open-space

Work with SS14 NPC systems, HTN behavior, pathfinding, steering, AI debug overlays, mindless mobs, hostile or friendly mob behavior, and NPC-related prototypes.

2026-04-212

ss14-sprite-overlays-shaders

ss14-art/open-space

Work with SS14 sprites, RSI metadata, sprite layers, overlays, custom visualizers, shaders, lighting-like client effects, and visual assets under `Resources/Textures` or client visual systems.

2026-04-212

name	ss14-pvs
description	Work with SS14 PVS, visibility, network interest, PVS filters, PVS override behavior, visibility-dependent audio or popups, zoom PVS scale, or systems that behave differently when entities leave PVS.

SS14 PVS

Use this skill when a change depends on which clients can see, hear, or receive an entity.

PVS is a networking and relevance boundary, not just a visual effect. Keep filters narrow, avoid leaking hidden information, and remember that clients may not know about entities outside their PVS.

Workflow

Decide what must be relevant.

World feedback for nearby players should usually use PVS filters or PVS-scoped helpers.
Admin, ghost, camera, or debug visibility may require explicit override behavior.
UI or client code must tolerate entities leaving PVS or arriving later.

Keep network interest narrow.

Prefer Filter.Pvs(...), Filter.PvsExcept(...), and existing audio/popup helpers over broadcasting to all players.
Do not use global filters for local world feedback unless the feature truly is global.
Be cautious with PVS overrides; remove or scope them when the special view ends.

Do not assume the client has every entity.

Client code should handle missing entities, nullspace, and stale entity references.
Avoid client decisions that require hidden server-only or out-of-PVS entities unless a deliberate message/state path provides the data.

Coordinate with prediction and feedback.

Predicted local feedback may happen before server PVS feedback.
Avoid duplicate popups or sounds when both local prediction and PVS broadcasts exist.

Validate visibility behavior.

Test with another client or call out when multi-client verification was not possible.
For admin/debug visibility, check cleanup paths as carefully as setup paths.

Reference Map

../ss14-netcode/SKILL.md
../ss14-prediction/SKILL.md
../ss14-audio/SKILL.md
../ss14-debugging-workflow/SKILL.md

Good File Anchors

Content.Server/**/Pvs*.cs
Content.Server/**/PvsOverride*.cs
Content.Client/**/ContentEye*.cs
Content.Server/**/Filter*.cs
Content.Client/**/Overlay*.cs

Common Pitfalls

Broadcasting feedback globally when PVS or station/PVS filters are enough.
Assuming a client can resolve an entity that may have left PVS.
Leaving PVS overrides active after an admin camera, ghost, or debug view closes.
Treating PVS as security for data that should never be sent.