Ignore Discord Username Updates from New Username System Rollout + 2 Misc Changes #430
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
metadata correction for Ornaran 10K Run badge, add barnisfrankscompliation.mp4 file and drops.json entry
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.
Discord is rolling out their new username system which means we're seeing a lot of messages in #captains-log as a result due to the on_user_update() event being fired when this happens.
Digging into it a bit it appears we can check if the discriminator during this update changed and if so ignore the update (during the username change the user's discriminator is changed to "0")
Two other misc changes included: