| Commit message (Collapse) | Author | Age | Lines |
| | |
|
| |\
| |
| | |
Update or-gotcha.md
|
| | |\
| |/
|/| |
|
| |\ \
| | |
| | | |
Invoke fuzzywuzzy's processor before matching
|
| | |\ \
| |/ /
|/| | |
|
| | | |
| | |
| | |
| | |
| | | |
Fixes a regression where the string to be matched was not processed
beforehand.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Trying to match a string with only non-alphanumeric characters
results in a warning by fuzzywuzzy.
Processing the string before matching lets us avoid the warning, which
which uses the root logger and thus isn't supressible.
|
| | | |\
| |_|/
|/| | |
|
| |\ \ \
| | | |
| | | | |
DM relay - minor fixes
|
| | |\ \ \
| |/ / /
|/| | | |
|
| |\ \ \ \
| | | | |
| | | | | |
Relay all DMs sent to the bot to #dm_log
|
| | |\ \ \ \
| |/ / / /
|/| | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Allow ordering talentpool/bigbrother watched users by oldest added
|
| | |\ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
python-discord/bug/info/1050/remove-help-reactions-404
Suppress NotFound when removing help command reactions
|
| | |\ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Users can no longer see available channels if they're on cooldown. They
will instead see a special "cooldown" channel which will explain
what's going on.
|
| |/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The message may be deleted somehow before the wait_for times out.
Fixes #1050
Fixes BOT-6X
|
| | | | | | | |
|
| | |\ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | |_|/ /
| |/| | | |
|
| | | |\ \ \
| |_|/ / /
|/| | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Sanitize bot output
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | | |
Co-authored-by: Leon Sandøy <[email protected]>
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
https://github.com/python-discord/bot/issues/1041
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Weird.
https://github.com/python-discord/bot/issues/1041
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When we're using the !reply command, using a regular UserConverter is
somewhat problematic. For example, if I wanted to send the message
"lemon loves you", then I'd try to write `!reply lemon loves you` -
however, the optional User converter would then try to convert `lemon`
into a User, which it would successfully do since there's like 60 lemons
on our server.
As a result, the message "loves you" would be sent to a user called
lemon.. god knows which one.
To solve this bit of ambiguity, I introduce a new converter which only
converts user mentions or user IDs into User, not strings that may be
intended as part of the message you are sending.
https://github.com/python-discord/bot/issues/1041
|
| | | | | | |
| | | | | |
| | | | | | |
Co-authored-by: Sebastiaan Zeeff <[email protected]>
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
https://github.com/python-discord/bot/issues/1041
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Without this, it is difficult to know precisely who the user that is
DMing us is, which might be useful to us.
https://github.com/python-discord/bot/issues/1041
|
| | | | |/ /
| | | | |
| | | | |
| | | | | |
This reverts commit 042f472a
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
If you're typing up a reply and the bot gets another DM while you're
typing, you might accidentally send your reply to the wrong person.
This could happen even if you're very attentive, because it might be a
matter of milliseconds. The complexity to prevent this isn't worth the
convenience of the feature, and it's nice to get rid of the caching as
well, so I've decided to just make .reply require a user for every
reply.
https://github.com/python-discord/bot/issues/1041
|
| | | | |\ \ |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Also now catches the exception if a user has disabled DMs, and adds a
red cross reaction.
https://github.com/python-discord/bot/issues/667
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
https://github.com/python-discord/bot/issues/667
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
https://github.com/python-discord/bot/issues/667
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
https://github.com/python-discord/bot/issues/667
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
https://github.com/python-discord/bot/issues/667
|