Persist new public keys in the player database when using Easy Connect - #4780
Merged
Azhrei merged 1 commit intoMay 17, 2024
Merged
Conversation
Do it whether the player was previously known or not.
kwvanderlinde
force-pushed
the
bugfix/4779-easy-connect-commit
branch
from
May 15, 2024 06:35
a4863ba to
098ad82
Compare
thelsing
approved these changes
May 17, 2024
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Identify the Bug or Feature request
Fixes #4779
Description of the Change
Commits the player database whenever new keys are added as part of Easy Connect. Previously we only committed if the player was already known, but now we do it regardless.
Possible Drawbacks
Should be none.
Documentation Notes
N/A
Release Notes
This change is