Run any Skill in Manus with one click

ss14-pvs-networking

Stars0

Forks0

UpdatedMay 20, 2026 at 14:00

PVS and visibility guidance for SS14 Shine 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/shine

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 Shine 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

shine-project

ss14-art/shine

Master workflow for working in the Shine Project 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-05-200

ss14-ai-workflow

ss14-art/shine

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

2026-05-200

ss14-atmos

ss14-art/shine

Atmospherics guidance for SS14 Shine work, including gas simulation, pipes, vents, scrubbers, air alarms, mapping atmos, flow/reaction design, performance, and why most atmos logic is authoritative/server-side rather than predicted.

2026-05-200

ss14-audio

ss14-art/shine

Audio guidance for SS14 Shine work, including SoundSpecifier, sound collections, predicted audio, MIDI/soundfonts, resource placement, localization-adjacent feedback, and avoiding duplicated or hardcoded sound playback.

2026-05-200

ss14-chemistry

ss14-art/shine

Chemistry guidance for SS14 Shine work, including reagents, reactions, metabolism, solution containers, reagent effects/conditions, entity solutions, and chemistry prototype localization.

2026-05-200

ss14-client-server-shared

ss14-art/shine

Placement and dependency rules for SS14 Content.Shared, Content.Server, Content.Client, Resources, and tests. Use when deciding where Shine code belongs or when splitting predicted/shared logic from server authority and client presentation.

2026-05-200

name	ss14-pvs-networking
description	PVS and visibility guidance for SS14 Shine 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.