fix: NetworkObject component should always precede NetworkBehaviour components [MTT-7216] #2685
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 fixes the issue where it was possible for a
NetworkObject
component to be positioned afterNetworkBehaviour
components which could result in theNetworkBehaviour
components that preceded theNetworkObject
component to not have theirOnNetworkDespawn
method invoked on an in-scene placedNetworkObject
when the scene was unloaded during a scene transition.MTT-7216
Changelog
NetworkBehaviour
component'sOnNetworkDespawn
was not being invoked on the host-server side for an in-scene placedNetworkObject
when a scene was unloaded (during a scene transition) and theNetworkBehaviour
component was positioned/ordered before theNetworkObject
component.Testing and Documentation
NetworkObjectTests.NetworkObjectComponentOrder