| Commit message (Collapse) | Author | Age | Lines |
| ... | |
| |\ \
| | |
| | |
| | |
| | | |
python-discord/bug/filters/1027/ignore-webhook-names
Ignore webhooks for nickname filter
|
| | |\ \
| |/ /
|/| | |
|
| |\ \ \
| | | |
| | | | |
Utils: show error message for long poll titles
|
| | |\ \ \
| |/ / /
|/| | | |
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | | |
Help channel message pin fixes
|
| | |\ \ \ \
| |/ / / /
|/| | | | |
|
| |\ \ \ \ \ |
|
| | |\ \ \ \ \
| |/ / / / /
|/| | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The claimed channel check in `on_message` relies on the cache being
cleared when a channel goes dormant. If it's not cleared, it will think
the channel is still in use.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The bot's pin message was being picked up as the last message, so the
system was not considering the channel empty.
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This can be used for both pinning and unpinning messages. The error
handling code was largely similar between them.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Fixes #1082
Fixes BOT-7G
|
| | | | | | | |
|
| | | | | | | |
|
| | | |/ / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Embeds have a maximum length of 256 for titles.
Fixes #1079
Fixes BOT-7Q
|
| | | |/ /
| | | |
| | | |
| | | | |
Fixes #1027
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
Prevent the tasks from starting again if the bot restarts.
|
| | | | |
| | | |
| | | |
| | | | |
Consistency with the new `_stop_tasks` method.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I really didn't like the constants, but the construction of allowed
mentions instances is syntactically noisy, so I prefer to keep it
out of the important logic.
Abstracting it behind a function seems to be the best approach yet.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
A Discord error code 50_0007 signifies that the DM dispatch failed
because the target user does not accept DMs from the bot.
Such errors are ignored as before.
Any other 403s will however cause the bot to stop making requests.
This is in case the bot gets caught by an anti-spam filter and
should immediately stop.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Prevent a ghost ping from occurring upon reaction.
Co-authored-by: Senjan21 <[email protected]>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If the kwarg isn't passed, it uses the value that was given to the
bot on init (False), despite the kwarg defaulting to True.
Thanks to Mark and Senjan for helping me understand this.
Co-authored-by: MarkKoz <[email protected]>
Co-authored-by: Senjan21 <[email protected]>
|
| | | | |
| | | |
| | | |
| | | | |
Co-authored-by: Joe Banks <[email protected]>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Makes it easy for users to re-join.
Co-authored-by: Joe Banks <[email protected]>
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The Limit values are mostly assumptions, as this feature is very
difficult to test at scale. Please see docstring amendmends for
further information.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Generic request dispatch method to avoid code duplication with error
handling & bad status logging.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Suppress errors coming from Discord when changing the confirmation
message in case it gets deleted, or something else goes wrong.
This commit also adds either the ok hand or the warning emoji to
the edited message content, as with the guild syncer confirmation.
Co-authored-by: MarkKoz <[email protected]>
|
| | | | |
| | | |
| | | |
| | | | |
Co-authored-by: MarkKoz <[email protected]>
|
| | | | |
| | | |
| | | |
| | | | |
Co-authored-by: MarkKoz <[email protected]>
|
| | | | |
| | | |
| | | |
| | | | |
Co-authored-by: MarkKoz <[email protected]>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This just reads better.
Co-authored-by: MarkKoz <[email protected]>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In an edge case, the `_kick_members` and `_give_role` could act on
a member who has verified *after* being marked by `_check_members`
as unverified.
To address this, we perform one additional check just before sending
the request. Testing seems to indicate that the `discord.Member`
instance get updates as appropriate, so this should at least reduce
the chances of such a race happening to very close to nil.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If tasks are stopped manually, they will not automatically restart
on cog reload or bot restart.
Using `maybe_start_tasks` is necessary because we cannot interface
with Redis from a sync context.
We're using 1 and 0 because RedisCache does not currently permit
bool values due to a typestring conversion bug.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Allow checking whether tasks are running, starting them, and stopping
them.
Currently, the tasks cannot be started or stopped separately. It is not
believed that we would need such a level of granularity.
Calling `cancel` on a task that isn't running is a no-op.
|
| | | | |\
| |_|_|/
|/| | | |
|
| |\ \ \ \
| | | | |
| | | | | |
Deps: update discord.py to 1.4.0
|
| |/ / / /
| | | |
| | | |
| | | | |
It was released on PyPI. No longer need to clone via git.
|