| Commit message (Collapse) | Author | Age | Lines |
| |
|
|
|
| |
Moves the valentine's day features to the holidays folders.
Corrected the paths to reflect the folder moves.
|
| |
|
|
|
|
| |
This skips the role check if the author is running the love calc command on themselves. We still want to check the the user running against has the role, along with if the author is running it against 2 other people.
i have also included info on how to get the lovefest role in the error embed.
|
| | |
|
| |
|
| |
Co-authored-by: Matteo Bertucci <[email protected]>
|
| |
|
|
| |
Now that we don't allow arbitrary strings, we can simplify the input validation/modification we do.
|
| |
|
|
| |
Since we update how the command behaves, by not allow arbitrary stings, and being symmetrical, we should reflect this in the docstring.
|
| |
|
|
| |
This ensures the same result for same input, regardless of order
|
| |
|
|
| |
This ensure that only uses that have opted into the love fest event can actually be used as part of this command.
|
| |
|
|
| |
This ensure the valentines themed command can only be ran during the valentines season.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
- Change commands.Bot type hints to bot.Bot
- Remove the setting of Cog.bot if it isn't being used
- Change ctx.author -> ctx.message.author
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The previous system required each extension's `setup` func to log
that the cog was loaded. This leads to inconsistent messages all
trying to convey the same thing, variable logger names in the output
file are difficult to read, and several extensions were not logging
at all.
By logging directly in the `add_cog` method, we reduce code repetition,
ensure consistent format, and remove the responsibility to remember
that a log should be made.
|
|
|
It is believed that this is now a more logical name for the package,
as extensions no longer bind to seasons.
Internally, packages are still grouped into seasonal sub-packages.
There are quite a few, and it makes sense to group them by a common
theme that inspired their functionality.
|