| Commit message (Collapse) | Author | Age | Lines |
| |
|
|
|
| |
Co-authored-by: wookie184 <[email protected]>
Co-authored-by: Amrou Bellalouna <[email protected]>
|
| |
|
| |
Co-authored-by: wookie184 <[email protected]>
|
| |
|
|
|
|
| |
This makes sure that all cogs that need keys won't load.
Which helps in avoiding exceptions at runtime, and give a clearer warning at startup time.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This also renames the Client class to Bot, to align better with Python.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
- Fixes misspelling of hanukkah regex
- Move `_check_message` docstring to imperative mood
- Remove redundant `_short_circuit_check` from `_check_message`
- Remove redundant comma from `EarthDay`'s reaction list
- Sort triggers for Halloween and Christmas
|
| |
|
|
|
|
|
|
|
|
| |
Triggers for reactions are moved from a dict to to a 2-deep NamedTuple.
This is cleaner for multiple reactions, and allows for additional parameters,
such as months.
Message case checking is altered from `.lower` to `re.IGNORECASE`.
Not only does the regex flag short circuit, it doesn't modify
the string in question
|
| |
|
|
|
| |
Additional pending reactions mean putting the reaction Cog in the
halloween directory no longer makes sense. Approriate renamings follow.
|
| |
|
| |
This change adjusts the regex pattern used in detecting `spooky` to include fun variants such as `spoopy` and `spookier`. The `k` is replaceable with a `p`, the `y` can be interchanged with `i` allowing `ier` and `iest` endings. (`yer` and `yest` are also valid). The number of `o`s remains at two (2) or more.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
| |
Co-authored-by: ChrisJL <[email protected]>
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |\| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
rewrote hanukkah to use datetime.strptime
left a helper method and some variables in order to allow extending
to use a cache in the future, rather than requesting the api every invoke
that is out of scope of this commit and pull, since the command is
currently broken.
I've only kept the same functionality, without trying to rewrite the
entire command.
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Check whether a reaction is for a bot message when adding candies
upon reactions. Previously you could use bot's reaction buttons which
would trigger `on_reaction_add` and have a high chance of getting candies
(or skulls). It can easily be abused to spam reactions, which apparently
doesn't trigger an auto-mute like spamming messages do, AFAIK.
In any case, I don't really feel good about reactions triggering candies.
Despite this fix, the game *can* still be abused (but I won't tell you how).
Though this occuring by accident is less likely than before. Either figure
it out yourself or don't try to cheat :P
This patch can be tested using the `.snake antidote` game when you react
to the recipe buttons. Using `.help` works too but it produces a lot of
noise in the logs. Tic tac toe may be helpful as well. Anyway, you could
just react to bot messages yourself.
|
| | |
|
| | |
|
| | |
|
| |
|
| |
This caused a `TypeError` to be raised, as the `id` argument could only be used as a positional argument and not by keyword.
|
| |\ |
|
| | |
| |
| |
| |
| | |
Previously only ignored its own messages, but now ignores messages from
all bots.
|