| Commit message (Collapse) | Author | Age | Lines |
| |
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I left as many available as possible. Some of the commands also handle
being outside of their original season, e.g. by showing the amount of
time until Hacktoberfest begins, if not currently active. These were
left available as well.
If a group is to be locked, the `invoke_without_command` param must
be False (default), otherwise the group's callback will be circumvented
if a valid subcommand is invoked.
I adjusted these where necessary, except for the `HacktoberStats` cog,
whose cmd group takes an arg, which would require a more involved
adjustment - I decided to leave it as is, and instead manually lock
both subcommands.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Defining seasons in seasonal packages' __init__.py files made more
sense when extensions were strictly tied to seasons. It introduces an
annoying circular dependency where a seasonal package must be imported
in order for the __init__.py file to run and register the season, but
it also imports SeasonBase from the parent directory so that it can
inherit from it.
I have made the decision to scrap the seasonal __init__.py files, and
instead define all seasons directly under SeasonBase. The classes are
no longer scattered around, we remove the above mentioned import
problem, and everything is more transparent and easier to digest.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We no longer use the class docstrings for announcements, and they
mostly contain outdated information. Sentences still relevant are
used to populate the `description` attr (which shows in the branding
embed), the rest is scrapped.
The descriptions themselves can still be improved in the future, once
we figure out exactly in which direction we want to go with them.
The idea of providing a description for each season's branding was
originally brought up by neonsea, co-authored below.
Co-authored-by: Rasmus Moorats <[email protected]>
|
| |
|
|
|
|
| |
We'll use this to colour the branding embed, as it currently looks very
plain. Seasons can either provide their own, or just use the default
green.
|
| |
|
|
|
| |
Ensure that all inheriting seasons are now providing the right attrs
as defined in `SeasonBase`.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The pipfile will need to be re-locked to add a dependency so may as well
re-pin some dependencies to reflect the more recent versions that will
be used. discord.py was pinned to a patch version instead of a minor
version to be on the safe side.
Notable updates:
* discord.py -> 1.3.2
* flake8-annotation -> 2.0
* pre-commit -> 2.1
|
| |
|
|
| |
Redirect any output to seasonalbot commands, where relevant
|
| | |
|
| |
|
| |
hacktoberstats cog handled in separate PR
|
| |
|
|
| |
summary
|
| |\
| |
| | |
Cycle Evergreen Animated Server Icons
|
| | | |
|
| |/ |
|
| |
|
|
| |
Fix last message scoping issue with show your project reactions
|
| |\ |
|
| | |\ |
|
| | | | |
|
| | |/
| |
| |
| |
| |
| | |
Utilize new ctx.send_help coro
Bump d.py minor version & relock
|
| |/ |
|
| | |
|
| |\
| |
| |
| | |
Resolve merge conflicts
|
| | |\
| | |
| | | |
Add new Cog class inheritance & event listener decoration
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |\ |
|
| | | | |
| | | |
| | | | |
flake8 shame...
|
| | | | | |
|
| | | | |
| | | |
| | | | |
Per the contributor doc
|
| | | |\ \ |
|
| | | | | |
| | | | |
| | | | | |
Mitigates recent breaking d.py changes
|
| | | | | | |
|
| |\| | | | |
|
| | | | | |
| | | | |
| | | | | |
a requested change
|
| | | |_|/
| |/| | |
|
| |/ / / |
|
| | | | |
|
| | |/
|/|
| | |
Includes the File for the cog containing the command in addition to the JSON file containing the list of pickup lines
|
| |\ \
| |/
|/| |
Add .myvalenstate
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
A bug appeared, that, if a user were to have only one or two Valenstates,
would throw an IndexError, thus blocking the command to run at its fullest.
This commit aims at fixing this bug by refining how the leftovers are handled:
Before there was only one line determining the leftover string, that was
than put into the embed's add_field method with some extra stuff around
it and a fixed title.
This has now been changed to having a variable title changing with the
length of the matches list. For example if you have 3 original matches,
the matches list would be of length 2, thus the original title is displayed.
If you have only 2 or just 1 match however, the matches list would be of
length 1 or 0, each of which feature their own title and text now.
Some style changes have been made as well: the add_field and set_image
methods are now one liners.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
A few things have been changed:
- The comment under STATES = json.load(file) was useless and has been
removed
- A logging statement has been put under the setup function:
log.debug("MyValenstate cog loaded")
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Closes #108
This pull request adds a beta version of the command myvalenstate.
This command sends an embed containing a users valenstate to the channel
it has been called in. The process used here is to first put the username
into a spaceless, lower case form and than compare it to the countries
listed under valenstates.json, put into the same form, using an implementation
of the Levenshtein algorithm.
This beta version already implements everything needed for the command to
work properly. The follwing things are missing, not meant for the future
full implementation or are subject to change if needed:
- Short comments (25 missing)
- name parameter in myvalenstate (not meant for staying/Debug)
- Object names in valenstates.json (subject to change) (1)
- Docstring for levenshtein (subject to change)
- Docstring for myvalenstate (subject to change)
(1) - The object names can be put into the right case to omit the operation
operation on line 54 (lower_state = state.lower().replace(' ', ''))
|
| |\ \
| | |
| | | |
Added command .bemyvalentine
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
lists insted of dictionary.
|
| | | |
| | |
| | |
| | | |
that has to be checked needs to be a poe/compliment/custom message.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
1.Fixed indentation
2.Removed unneccessory comments
3.Re-named the varible Role to lovefest_role
4.Edited te random user function
5.Removed unneccessory f strings(just removing the f letter,lol)
|