| Commit message (Collapse) | Author | Age | Lines |
| | |
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| | |\ |
|
| | |/
| |
| | |
Solves https://github.com/python-discord/bot/issues/1896
|
| | |\
| | |
| | | |
Mod-log thread: use soft colors
|
| | |/
| |
| | |
Seems like we have been using the wrong colors in mod-log.
|
| | |\
| | |
| | | |
Handle edge case of `message.author` being a `discord.User` when claiming a help channel.
|
| | | |\
| | |/
| |/| |
|
| | |\ \
| | | |
| | | | |
Migrate to on_socket_event_type event
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Discord.py 2.0 (Namely this commit https://github.com/Rapptz/discord.py/commit/e2250d402e8ad035b2653eb411c8e744cc9eb3bf) removed the socket_response event, and replaced it with the socket_event_type event, which just sends the type of event triggered on the websocket.
Since this event was removed, no socket stats were being incremented, as the event never triggered.
I have looked through the rest of the bot, and we do not use the socket_response event type anywhere else.
|
| | | | |
|
| | |\ \
| | | |
| | | | |
Fix attr error since asset attrs have changed in 2.0
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes #1886
Fixes BOT-1NZ
This was updated with Discord.py 2.0.
|
| | |\ \
| | | |
| | | | |
Use MISSING sentinal rather than None for no files
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes #1884
Fixes BOT-1NY
Discord.py 2.0 changed how this works, webhooks now look for the MISSING sentinal, rather than None to determine whether files are being passed.
This was updated in this commit: https://github.com/Rapptz/discord.py/commit/a6f7213c89e9d592c69ea3c631b0cb2bdab19577
|
| | |\ \
| | | |
| | | | |
Direct users to the appeals server when banned
|
| | | |\ \
| | |/ /
| |/| | |
|
| | |\ \ \ |
|
| | |/ / /
| | | |
| | | |
| | | |
| | | | |
Fixes #1881
Fixes BOT-1NX
|
| | |\ \ \
| | | | |
| | | | | |
Prevent repetitive stale inventory warnings from erroneously generated inventories
|
| | | |\ \ \
| | |/ / /
| |/| | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* Run debug log before help command invocation to avoid delayed logs
* Refactored other areas of code slightly, ensuring logging is done as soon as possible. Removed outdated comment
* Ensured debug logs were sent for disabled commands
Co-authored-by: Xithrius <[email protected]>
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* Regex: add a word boundary before .gg and use named groups
Before this commit, `an-arbitrary-domain.gg/notaninvite` would trigger the filter.
This solve the issue by adding a word boundary before this branch of the pattern.
* Regex: replace the word boundary by a word char
Co-authored-by: ChrisJL <[email protected]>
Co-authored-by: ChrisJL <[email protected]>
Co-authored-by: Xithrius <[email protected]>
|
| | |\ \ \ \
| | | | | |
| | | | | | |
Formats Help Command Output
|
| | | |\ \ \ \
| | |/ / / /
| |/| | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Closes #1232
Modifies the docstring sent for per-command help to remove weird formatting issues mentioned in #1232. Removes newlines that are not used for paragraph breaks, after retrieving the docstring, and lets the embed handle it on the discord side.
Allow overriding this behaviour via \u2003 to denote a non-escapable break.
Co-authored-by: Hassan Abouelela <[email protected]>
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Some doc symbols are improperly generated and never exist on the doc page
the inventory file defines them in, causing the stale warning to get raised
every time the page is parsed (at a maximum every week because of the redis
expire).
This can be prevented by keeping a counter in redis for the items which were
stale, every time the item is warned for the counter is incremented and set to
expire in 3 weeks.
Then a warning is only raised when the counter is below 3, resulting in the
unpreventable warning only being raised twice until it is fixed by the
maintainers after it expires in 3 weeks after the last increment.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is a new appeals process we are trialing. Users who get banned join this server and DM a modmail bot, who relays the message to the main server for mods to discuss.
I have updated the shortening logic to allow for extra information to be included at the end of the embed, while still staying under the limit.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | |/
| | | | |
| | | | |
| | | | | |
NB: Will give a sentry warning when this happens.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| |\| | | | |
|
| | |\ \ \ \
| | |/ / /
| |/| | |
| | | | |
| | | | | |
python-discord/modlog-ingore-channels-mods-can't-view
Modlog ignore channels mods can't view
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Since channels that mods can't read are now implicitly ignored, there is no need to explicitly ignore them.
|
| | | | | | |
|