This repository was archived by the owner on Nov 10, 2021. It is now read-only.
Queue level updates on bot startup #79
Merged
Conversation
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
Instead of running through all members on boot (because it doesn't work), level updates are queued so a user's level is updated on that their next message
Muirrum
approved these changes
Mar 6, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
To help with transitioning to the new level algorithm (#77), when the bot starts, we should figure out whose levels need to be updated. At the moment, for reasons I can't quite figure out (and is also holding up #23 and by extension #26), we can't update member roles without retrieving the
GuildMemberfrom a message they've sent. Therefore the bot now just notes whose level roles need to be updated and updates them on their next message.