Add Thread Safety to AllegianceManager PassXP #3728
Merged
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
This follows the same thread-safety pattern used in other parts of AllegianceManager, like HandlePlayerDelete. The intent here is that AllegianceManager should mange its own thread safety. Callers shouldn't have to worry about if an AllegianceManager action should be thread safe or not.
|
This needs testing. |
gmriggs
approved these changes
Nov 1, 2021
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.
This follows the same thread-safety pattern used in other parts of AllegianceManager, like HandlePlayerDelete.
The intent here is that AllegianceManager should mange its own thread safety. Callers shouldn't have to worry about if an AllegianceManager action should be thread safe or not.