-
Notifications
You must be signed in to change notification settings - Fork 447
fix: Never distribute an object to a client who is not an observer #3323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
EmandM
merged 8 commits into
develop-2.0.0
from
fix/MTTB-1041-never-distribute-to-non-observer
Mar 6, 2025
Merged
fix: Never distribute an object to a client who is not an observer #3323
EmandM
merged 8 commits into
develop-2.0.0
from
fix/MTTB-1041-never-distribute-to-non-observer
Mar 6, 2025
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
…/com.unity.netcode.gameobjects into fix/MTTB-1041-never-distribute-to-non-observer
…/com.unity.netcode.gameobjects into fix/MTTB-1041-never-distribute-to-non-observer
…/com.unity.netcode.gameobjects into fix/MTTB-1041-never-distribute-to-non-observer
NoelStephensUnity
approved these changes
Mar 6, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💯
NoelStephensUnity
added a commit
that referenced
this pull request
Mar 11, 2025
<!-- Replace this block with what this PR does and why. Describe what you'd like reviewers to know, how you applied the engineering principles, and any interesting tradeoffs made. Delete bullet points below that don't apply, and update the changelog section as appropriate. --> - Ensure objects with no observers (or only current owner as observer) are treated as if `DontDestroyWithOwner = true` on client disconnect - Explicitly check if childObject has new client as observer on client connect <!-- Add short version of the JIRA ticket to the PR title (e.g. "feat: new shiny feature [MTT-123]") --> [MTTB-1041](https://jira.unity3d.com/browse/MTTB-1041) Changelog for this is in #3323. <!-- Add RFC link here if applicable. --> ## Changelog - Fixed: Ensure objects with no observers are treated as if `DontDestroyWithOwner = true` on client disconnect ## Testing and Documentation - No tests have been added. <!-- Uncomment and mark items off with a * if this PR deprecates any API: ### Deprecated API - [ ] An `[Obsolete]` attribute was added along with a `(RemovedAfter yyyy-mm-dd)` entry. - [ ] An [api updater] was added. - [ ] Deprecation of the API is explained in the CHANGELOG. - [ ] The users can understand why this API was removed and what they should use instead. --> Co-authored-by: Noel Stephens <[email protected]>
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.
MTTB-1041
Changelog
Testing and Documentation
Closes #3299