Issue#739 Always parents created child lifetime scope game object #760
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
…the parent game object that creates it
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
ok, thank you very much. Sorry for the late response. |
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.
PR to addres this issue: #739
If the parent lifetime scope is the root, parenting the child lifetime scope game object to it would automatically make it "not be destroyed on load" (DontDestroyOnLoad).
This change results in all
CreateChildapi behave the same with regards to their game object parent/child relationship (previous discrepancy was outlined in the issue linked above).