Fix object data initialization and event priority conflict with pawn #731
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
Because now there are issues with Objects components sending CreateObject RPCs on connect sooner than Pawn calling RemoveBuildingForPlayer This way, created objects are again removed with game mechanis after receiving RemoveBuildingForPlayer
|
Fixes #726 |
Cheaterman
approved these changes
Oct 7, 2023
ksenonadv
approved these changes
Oct 7, 2023
Hual
approved these changes
Oct 7, 2023
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.
Remove pawn comp player connect event priority
Because now there are issues with Objects components sending
CreateObject RPCs on connect sooner than Pawn calling RemoveBuildingForPlayer
This way, created objects are again removed with game mechanis after
receiving RemoveBuildingForPlayer
Initialize player object data on player pool entry create