fix: prevent exception when showing despawned NetworkObject - up port of #3029 #3030
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.
Up-port of #3029
This resolves an issue where a
NetworkObject
component could be despawned or itsGameObject
destroyed in the same frame prior to attempting to show it.MTTB-377
fix: #3023
Changelog
NetworkSpawnManager.HandleNetworkObjectShow
could throw an exception if one of theNetworkObject
components to show was destroyed during the same frame.Testing and Documentation
NetworkVisibilityTests.HideShowAndDeleteTest
.