Levels #560
Merged
Levels #560
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
It's not useful but I hope its a good start :3
I started making a level command :3
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
…del to better reflect its purpose and improve code readability
This new class listens for messages and processes XP gain and level up. It also checks if the message is from a bot, if the message is from a blacklisted channel, or if the message starts with a prefix. If any of these conditions are met, the function returns without processing XP.
…clarity in member-related operations
refactor(levelset.py): replace user with member for consistency and clarity refactor(xpblacklist.py): replace user with member for consistency and clarity refactor(xpreset.py): replace user with member for consistency and clarity refactor(xpset.py): replace user with member for consistency and clarity
…show XP progress in level embeds
ghost
marked this pull request as ready for review
This comment was marked as duplicate.
This comment was marked as duplicate.
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
…fault behavior when no member is provided feat(levels.py): consolidate level management commands into a single cog for better organization and maintainability refactor(levels.py): remove redundant files and integrate functionality into levels cog fix(levels.py): correct string formatting in logger debug statement style(help.py): remove unnecessary punctuation in help command aliases field for consistency
kzndotsh
approved these changes
Oct 4, 2024
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.
Description
Implements levelling system, allows configuration of blacklisted channels and mutlipliers & level role rewards in settings.yml.
New commands: xpset levelset xpblacklist xp xpreset
xplacklist is toggleable bool to make user unable to gain xp
xpreset sets level and xp to 0
xpset and levelset update the relevant value and change the other to the appropiate amount
New db model "levels" to store all the new data into the db
New service levels.py to increment xp on message send
Checks to ensure that inputs are valid
Guidelines
My code follows the style guidelines of this project (formatted with Ruff)
I have performed a self-review of my own code
I have commented my code, particularly in hard-to-understand areas
I have made corresponding changes to the documentation if needed
My changes generate no new warnings
I have tested this change
Any dependent changes have been merged and published in downstream modules
I have added all appropriate labels to this PR
I have followed all of these guidelines.
How Has This Been Tested? (if applicable)
Tested extensivly in ATL Dev sandbox
Screenshots (if applicable)
n/a
Additional Information
thanks to @AmilieCoding for some coding contributions and @wlinator and @kzndotsh for improvements for a PR and all the contributors for input on how to implement and help on testing this!