| Commit message (Collapse) | Author | Age | Lines |
| ... | |
| |\ \
| | |
| | | |
Quiz command fix
|
| | |\ \
| |/ /
|/| | |
|
| |\ \ \
| | | |
| | | | |
Use error_embed for errors, tidy code, show cmd signature for user errors.
|
| | | | | |
|
| | | | | |
|
| |/ / / |
|
| | | |
| | |
| | | |
Co-Authored-By: Mark <[email protected]>
|
| | | |
| | |
| | | |
Co-Authored-By: Mark <[email protected]>
|
| | | | |
|
| | |\ \ |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
- I cleaned up some residue code
- The quiz now selects a random category if None provided
- Updated doc strings
- Displaying the category when the quiz is starting
|
| | | | |
|
| | |\ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
adding space around special chars
Co-Authored-By: Mark <[email protected]>
|
| | |/ / |
|
| | | |
| | |
| | |
| | | |
command
|
| | |\ \ |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | | |
functions for the start and end quiz. Added another check to check if the game is still running before sending the answer.
|
| | | | |
| | | |
| | | |
| | | | |
longer run again if stopped n stuff.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Corrected all typos.
- the quiz command is now a command group to allocate the leaderboard command(a command which shows the leaderboard for the current bot session).
- Few other refinements with language and stuff.
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
for the quiz game:
New scoreboard for every game.
Store overall score board which refreshs when bot restarts.
|
| | | | | |
|
| | | | |
| | | |
| | | | |
Co-Authored-By: Leon Sandøy <[email protected]>
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | |_|/
|/| | |
|
| |\ \ \
| | | |
| | | | |
[Feature] `.bm` `.pin` bookmarks/personal-pins
|
| | |\ \ \ |
|
| | | |\ \ \
| |_|/ / /
|/| | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Make the daily Advent of Code subscription service actually ping subscribers
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The Advent of Code cog has a subscription system that allows members
to subscribe to a daily notification indicating the puzzle for that
day has become available. However, we introduces a more stringent
role mentionability policy that meant that the mentions did not
actually ping the members subscribed.
To solve this, I've made sure that the bot unlocks the role before
making the announcement using the `unlock_role` context manager. This
also means the role is automatically unlocked after the message is
sent.
In addition, I noticed that Seasonalbot was consistently announcing
the puzzle about 0.5 seconds early. I've correct this by adding a
second to the sleep delay. In addition, the bot now verifies that the
puzzle is available using a small HEAD request. While this does send
a request to the AoC server, it prevents multiple users from sending
unnecessary requests by following our link before the puzzle is
actually available.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
I have made the `#advent-of-code` channel id configurable using the
same environment variable technique used for other settings. This
makes it easier to test features that rely on this channel in a test
environment.
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Currently, our regualar roles are not mentionable by default. This
means that features that rely on roles to keep track of users that
want to receive announcements, like the AoC Day Countdown, don't
actually ping the users subscribed to it. The solution is obviously
that the bot should unlock prior to making the announcement.
However, this is complicated by the fact that there needs to be a
sufficient delay. both between unlocking and sending the message
and between sending the message and locking the role again. If not,
Discord's not done synchronizing across all servers and some users
won't receive a ping.
To make this easier, I have implemented a context manager that takes
an instance of `discord.Role` and an optional `delay` (default: 5s)
that yields a context in which the role is unlocked. This context
manager also makes sure that the role is locked even if an exception
occured within the unlocked context.
|