Repository navigation
Restore pool interaction and balls with registration permission - #151
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.
The deployed client returned
permission_denied:props.registerwhile initializing the full-rack pool renderer. Model registration stopped before the target sphere, state subscription and ball rendering were installed, removing both the ALT interaction and all balls.Declare the dedicated
props.registermanifest permission alongsideworld.props. Correct the native-contract documentation: creating props and registering their cooked model definitions require separate permissions. Make the enabled-client native double read the real manifest permission block and refuse registration when that capability is missing. This reproduces the current failure before the manifest change and passes with the permission declared, including real-menu selection and camera entry.Validation: enabled-client lifecycle test, Lua syntax/sandbox and diff checks; full suite: 6,722 checks, zero failures; all 68 Lua audits pass. GitHub CI required before merge. No asset, physics, camera, menu, target-layout or server-configuration changes. The existing 0.3.0 preload remains in use. In-game reconnect validation is still required after deployment.
Follow-up #149. MANUAL and POOL_MODELS.md updated; documentation tracking: opx77-framework/opx77_doc#19.