Document replication definition files and the unified player/prop upd…#34
Merged
Conversation
…ate path Add a 'Replication definition files' section explaining the per-type <type>_def.json whitelist, the replication zones (distance/frequency), and two common pitfalls (silently-dropped unlisted properties, and keeping scenename/ position/parent_id in the same zone so a prop is not spawned at the world origin). Note that the player is now just an object of type 'player' (no player-specific update path) and add a 'Spawning a prop from the game server' section for spawn_prop_authoritative. Fix a copy-paste error in the player example.
ddurieux
approved these changes
Jun 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Update networkGame/props_player to match the unified player/prop replication now in develop.
<type>_def.jsonwhitelist, the replication zones (
distance/frequency), and two pitfalls that bit us:silently-dropped unlisted properties, and keeping
scenename/position/parent_idin thesame zone (else a prop spawns at the world origin).
player(no more player-specific update path).spawn_prop_authoritative).client_send_action_to_server→server_send_properties_to_client).