Repository navigation
docs(entity): define configurable subscription policies - #293
Merged
Merged
Conversation
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
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.
Record the agreed configuration-driven Entity subscription design: games choose candidate scopes, visibility conditions, scalar/table/child selections and scene visibility. The framework evaluates those rules without hardcoded game data groups. Include matching bilingual JSON examples and transitions for out-of-vision party tracking, grant removal and connection-local baseline replacement.
Keep equipment inspection separate, and describe authoritative final values with planned revision jumps while preserving structural base/lifetime validation. Clearly distinguish these plans from the currently implemented fixed-projection, consecutive-revision contract; no runtime, protocol or exporter support is claimed by this PR.
Validation: full Nimbus check passed, including generated HTML, Markdown and AI exports; bilingual JSON examples match and all selected classes, fields, table columns and child references resolve against the room schema. The existing CI policy classifies these four paths as documentation-only. No code or raw test artifacts are included.