| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
| |
This is just a QoL of life thing, avoiding having us to check if the bot is here or not before issuing a command
Co-authored-by: ChrisJL <[email protected]>
|
|
|
|
| |
Since it is the only way to add bots to threads, it would make sense to be able to execute that command.
|
|
|
|
|
|
| |
Since the Discord.py repository has been archived, we can switch to the latest commit of 2.0a0, knowing no breaking change will occur (still pinned to the commit just in case).
This commit also solves two small problems due to that fix, the avatar interface changing and Embed.name disappearing. Quite a painless migration.
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| | |
channel check if debug is true
|
| | |
|
| |\ |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Closes #393
|
| |/
|/| |
|
| |
| |
| |
| | |
We no longer have this channel, so this cog serves no purpose.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Since we disable both privileged intents, we can just construct an
instance with them already off. As Senjan notes, this will also
future-proof us against any privileged intents added in the future.
Co-authored-by: Senjan21 <[email protected]>
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
With 'd.py' 1.5.1, the Member converter will now lazily fetch the
member object.
It is believed that this removes our need for the intent.
|
| | |
|
|/
|
|
|
|
|
| |
For now, we require the privileged 'Guild Members' intent, to maintain
all current functionality (e.g. Member convertors working with IDs).
In the future, we may look into disabling this intent.
|
|
|
|
|
| |
This was open to abuse when the bot relayed user input. The fix relies
on a discord.py alpha feature.
|
|
|
|
| |
This emulates the main bot's message for consistency.
|
|
|
|
|
|
| |
All calls to `wait_until_ready` are replaced with the new event.
To help with static analysis, we annotate `bot` attrs as instances
of our custom SeasonalBot class where necessary.
|
|
|
|
|
|
|
|
|
|
|
| |
See docstring for explanation & comparison to the `on_ready` event.
This is taken from the Python bot repository. Originally implemented
by Mark. The `on_guild_available` callback was adapted and simplified
from the original implementation, as with Sentry in place, it is
believed that dispatching an error webhook is unnecessary.
Co-authored-by: MarkKoz <[email protected]>
|
| |
|
| |
|
|
|
|
|
| |
Previously, this was done by the SeasonManager cog, which was removed
during our deseasonification efforts.
|
| |
|
|
|
|
| |
Co-authored-by: MarkKoz <[email protected]>
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
The diff should demonstrate how much code repetition we prevent.
We do not make use of `_apply_asset` for nickname changes - due to
the comparative simplicity and conceptual difference, this method
provides its own error handling.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Current `set_avatar`, `set_icon` and `set_banner` methods are almost
identical - they only differ in the type of asset they upload. This
leads to a lot of code repetition, especially w.r.t. error handling.
We instead add a generic method that is parametrized by an AssetType
param, and by the target entity (i.e. bot, or guild) that the asset
should be applied to. All error handling can then be done in one place.
Error handling methodology is adjusted - instead of suppressing errors,
we catch and log them. Since we no longer determine whether the upload
succeeded based on 'before' != 'after', this solves a bug where
re-applying the same asset resulted in a warning-level log, triggering
Sentry.
|
| |
|
|
|
|
|
|
|
| |
The method is a left-over from the old seasonal system. We no longer
use it, the bot's username never changes, only the nickname.
The amount of internal branching logic makes it difficult to maintain.
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
The methods will pretend that the selected asset was uploaded
successfully. This allows extensive testing of the branding manager
without API abuse.
|
|
|
|
|
| |
This is unused and no longer necessary, as all extensions load only
once: on start-up, in `__main__.py`.
|
|\
| |
| |
| |
| |
| |
| | |
This merges the newly added help cog.
Resolve slight conflict in the __main__ module caused by the the master
branch still assuming the presence of the legacy season manager cog.
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
Bot root, seasons cog, easter cogs, evergreen cogs, halloween cogs
|
| |
|
| |
|
|\
| |
| |
| | |
Resolve merge conflicts
|
| | |
|