fix: owner authoritative parenting backport #3453
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
Fixing API documentation issues.
NoelStephensUnity
changed the title
EmandM
approved these changes
May 26, 2025
NoelStephensUnity
deleted the
fix/owner-authoritative-parenting-fixes-backport
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 backports the the
NetworkObject.SyncOwnerTransformWhenParentedandNetworkObject.AllowOwnerToParentfunctionality.MTTB-1284
fix: #2842
Changelog
NetworkObject.SyncOwnerTransformWhenParentedwhich will not synchronize transform values sent by the server when parented (primarily for owner authoritative motion models).NetworkObject.AllowOwnerToParentwhich allows a client owner to parent locally and have the changes synchronize with the server and other clients (primarily for owner authoritative motion models).Testing and Documentation
Backport
No back port needed as this is a targeted backport of certain v2.x features that could be useful to projects still using v1.x.