fix: exception thrown when rpc received for depsawned object (back-port) #3055
Conversation
This file contains 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
NoelStephensUnity
changed the title
fluong6
approved these changes
Sep 9, 2024
NoelStephensUnity
deleted the
fix/exception-thrown-when-rpc-received-depsawned-object
branch
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.
Backported from #3052
This resolves the issue where an exception is thrown if universal RPC is received after a
NetworkObjecthas been despawned. Now it logs a warning if developer logging is enabled otherwise it just silently ignores the RPC.MTTB-361
fix: #3007
Changelog
NetworkObjectthat has been despawned.Testing and Documentation