This repository was archived by the owner on Jun 10, 2022. It is now read-only.
Newly created actor without ownership will properly receive default ownership once authoritative user is assigned #744
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
If an actor - without the owner property being defined - is created directly after the
onStarted()event, it will receive a default owner ofundefinedsince the authoritative user hasn't been assigned yet. This update will add the actor to_rigidBodyOrphanSetso that once the authoritative user is assigned, the actor will properly receive the default owner.Related issues #732 #742
Requires PR #743