Run any Skill in Manus with one click

ss14-pvs-networking

Stars3

Forks7

UpdatedMay 23, 2026 at 21:36

PVS and visibility guidance for SS14 SS14-ART-CORE work, including Potentially Visible Set, session-specific networking, owner-only data, PVS overrides, nullspace entities, hidden information, and anti-cheat-sensitive prediction.

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/ss14-core

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

4 files

SKILL.md

readonly

name	ss14-pvs-networking
description	PVS and visibility guidance for SS14 SS14-ART-CORE work, including Potentially Visible Set, session-specific networking, owner-only data, PVS overrides, nullspace entities, hidden information, and anti-cheat-sensitive prediction.

SS14 PVS Networking

Rules

Clients only receive entities in PVS unless overrides/subscriptions apply.
Do not network hidden information globally for convenience.
Use owner-only/session-specific state for private data.
Use PVS overrides sparingly and remove them when no longer needed.
Consider nullspace entities for abstract data, but remember they are not normally visible to clients.

Review Questions

Which clients actually need this data?
Can a cheater infer hidden roles, inventory, objectives, or contraband from it?
Does leaving PVS pause or detach the entity and break predicted logic?
Is an override temporary, scoped, and documented?

Bundled References

references/session-specific-data.md: owner-only/session-specific component state and hidden-information review.
references/pvs-overrides.md: session/global overrides, view subscribers, nullspace, cleanup, and scope.

Sources

Read prediction guide PVS sections and basic-networking-and-you.md through ss14-wizden-docs.

More from this repository

same repository

ss14-ai-workflow

ss14-art/ss14-core

Preflight, implementation, and self-review workflow for AI agents working on SS14-ART-CORE SS14 code. Use when planning or making any repository change, reviewing PRs, hardening instructions, or deciding which .agents skills/rules apply.

2026-06-183

ss14-art-core

ss14-art/ss14-core

Master workflow for working in the SS14-ART-CORE SS14 fork. Use for any code, content, resource, test, review, or agent-instruction change in this repository, especially Content.Shared, Content.Server, Content.Client, Resources, .agents, CodeRabbit, and fork/upstream merge-sensitive work.

2026-06-183

ss14-porting-and-licensing

ss14-art/ss14-core

Porting, attribution, fork isolation, upstream merge, and license guidance for SS14-ART-CORE. Use before importing code/assets from WizDen, Delta-V, Starlight,

2026-06-183

ss14-prototype-basics

ss14-art/ss14-core

SS14 YAML prototype, data field, localization, guidebook, entity table, reagent, and resource placement guidance. Use when editing Resources, prototypes, FTL, YAML, entity definitions, components serialized to YAML, or guidebook entries.

2026-06-183

ss14-upstream-maintenance

ss14-art/ss14-core

Upstream/fork maintenance guidance for SS14-ART-CORE. Use when touching non-_Art files, reviewing upstream diffs, preserving path similarity, porting fork code, marking ss14-art-edit blocks, or deciding whether an engine/content change is allowed.

2026-06-183

ss14-wizden-docs

ss14-art/ss14-core

Route and summarize the local WizDen documentation snapshot for SS14-ART-CORE SS14 work. Use when an agent needs SS14/RobustToolbox docs context for ECS, prediction, networking, UI, prototypes, mapping, departments, design docs, rendering, toolshed, setup, debugging, porting, or licensing.

2026-06-183

name	ss14-pvs-networking
description	PVS and visibility guidance for SS14 SS14-ART-CORE work, including Potentially Visible Set, session-specific networking, owner-only data, PVS overrides, nullspace entities, hidden information, and anti-cheat-sensitive prediction.

SS14 PVS Networking

Rules

Clients only receive entities in PVS unless overrides/subscriptions apply.
Do not network hidden information globally for convenience.
Use owner-only/session-specific state for private data.
Use PVS overrides sparingly and remove them when no longer needed.
Consider nullspace entities for abstract data, but remember they are not normally visible to clients.

Review Questions

Which clients actually need this data?
Can a cheater infer hidden roles, inventory, objectives, or contraband from it?
Does leaving PVS pause or detach the entity and break predicted logic?
Is an override temporary, scoped, and documented?

Bundled References

references/session-specific-data.md: owner-only/session-specific component state and hidden-information review.
references/pvs-overrides.md: session/global overrides, view subscribers, nullspace, cleanup, and scope.

Sources

Read prediction guide PVS sections and basic-networking-and-you.md through ss14-wizden-docs.