fix: distributable or sessionowner flag always defaults for in-scene placed NetworkObjects #3407
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
EmandM
approved these changes
Apr 15, 2025
NoelStephensUnity
deleted the
fix/distributable-flag-always-set-in-scene-objects
branch
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.
This PR removes the opinionated restrictions to permissions with in-scene placed NetworkObjects and matches the DAHost redistribution logic to mirror the rust server's when a client disconnects.
MTT-11973
Changelog
NetworkObjects would only allow the ownership permission to be no less than distributable or sessionowner.Testing and Documentation
Backport
No backport is needed since this is a distributed authority specific fix.