fix: networkvariablebase not being reinitialized if networkobject persists between sessions #3181
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 PR resolves the issue where a
NetworkObject
instance with aNetworkBehaviour
that includes one or moreNetworkVariableBase
derived class properties persists between network sessions is not having itsNetworkVariableBase.Initialize
method invoked again when spawned again. This resulted in clients not being updated to changes in theNetworkVariableBase
derived class properties for a period of time equal to the duration of the last spawned time frame from its previous network session.MTTB-881
Changelog
NetworkVariableBase
derived classes were not being re-initialized if the associatedNetworkObject
instance was not destroyed and respawned.Testing and Documentation