| Commit message (Collapse) | Author | Age | Lines |
| |
|
|
|
| |
This is a solution for the #862 issue, which says the Hanukka holiday can also be in November and not only in December.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* (trivia-quiz): Add Wikipedia Guess Game
This commit also moves all the 'dynamic' question generator to a separate class.
Closes: #446
* (trivia quiz): Use tuples for command aliases
* (trivia quiz): Edit congratulations message
* (trivia quiz): Use default dict for storing player scores
* (trivia quiz): 'done_question' to 'done_questions'
* Add space after 'Congratulations' word
* Use classmethods for dynamically generating questions
* Don't add wiki category if max error fetches hit
If the task hit max error fetches, which is 3 currently, it would remove wikipedia from listed categories and not add it to loaded questions.
If it doesn't hit max fetches, then it adds them.
* Don't hardcode the number of questions in RULES
* Add information field only if it exists
* Add "cs" and "python" categories to the `.quiz` command
* add 30 questions each under the categories "cs" and "python"
add the two categories into the code and modify the starting phase
Co-authored-by: Xithrius <[email protected]>
Co-authored-by: ToxicKidz <[email protected]>
* refactor: Use yesterday's most read to make trivia questions
Since random wikipedia article guess questions weren't really "knowledgeable", no one could really guess it or gain any "good" knowledge from them, so after asking wookie (this commits mentions his review comments above also), I decided to use these.
* refactor: Logic to remove pronounciations from question
Co-authored-by: wookie184 <[email protected]>
* fix: Set to correct question limit
If the number of questions are less then the default limit which can
happen in the case of wikipedia guess game as it is dependent on the
most read articiles on wikipedia, it would create a infinite loop
sending us into infinite amount of errors, so let's prevent that, thanks
wookie
* chore: Add comment for d5f8205 change
* refactor: Remove double mention of dataclass in quizentry
* chore: Use r"" over noqa
We can use r"", a raw string, here to make it clear that \* and \s
aren't supposed to be handled as escape sequences and just use the "raw
string".
* fix: Correct off by one bug
Originally, before this commit, we checked the number of questions left
by comparing `len(done_questions) > self.question_limit`, so question
limit had to be 1 since if it wasn't we would compare 7 > 7, which would
be false and then it would send another question.
To correct this bug, we now use == comparision on the two, so if the
number of done questions is same as the question limit it means that the
round is over. I have changed the relevant parts of the code to reflect
this change i.e. where-ever we did +-1 due to the off by one bug.
* refactor: Noramlize the title to remove all punctuations
Since the title can sometimes contain punctuations making it very
difficult to get the matching answer to the question, we originally
removed all such questions. This took the question count down :( and
wasn't an effective way. Therefore now we keep them but as normalized,
yay!
I have also updated the code documentation to make the process much
clearer to anyone reading the "normalizing" code section of the wiki
questions generator.
* refactor: Keep answers as a list & not ",".join()
Wasn't fitting in character limit so shorterned it ^^ lol. Okay, getting
to the point, this mentions fix error's comment of making quiz entry
except the answers as a list and not as a string which could a comma
joined list. The same structure was in the json resource, where multiple
answers where joined with commas. This didn't allow you to use commas in
answers.
So I went ahead and did a bit more than requested to change the json
structure and make `answers` a list. Also now all questions are in the
form of the quiz entry to keep it same through out the code and var
tolerance has become a valid param in QuizEntry, this is done because it
was differing between questions, if not needed this would make the
process to add `var_tol` as a argument to the json easier. And that's
it!
Co-authored-by: Objectivitix <[email protected]>
Co-authored-by: Xithrius <[email protected]>
Co-authored-by: ToxicKidz <[email protected]>
Co-authored-by: wookie184 <[email protected]>
|
|\ |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This moves all the fun commands and games into the fun folder.
This commit also makes changes to the duck_game.
It was setting a footer during an embed init, which is no longer
possible with the version of d.py we use. Additionally, an issue with
editing an embed that had a local image loaded.
The workaround for the time being is to update the message,
not the embed.
|
| | |
|
| |
| |
| |
| |
| |
| | |
Separates out the useful/practical seasonal bot features from the
evergreen folder into a "utilities" folder.
Adjusts the paths to resources to reflect the folder move.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Part of this restructure involves splitting out the massive evergreen
folder into a `fun` folder and then a `utilities` folder. To help with
that we've rename the `util` folder to `core`.
The core functions to run the bot have been moved into this folder.
`.source`, `.ping`, and `.int e` have been moved into this folder.
|
| |
| |
| |
| |
| |
| | |
Additionally, this commit fixes an error with the pridepfp command.
The avatar image now uses discord.py's v.20 avatar.url instead
of avatar_url
|
| |
| |
| |
| |
| | |
Hannukah was previously in the Christmas folder, which was weird.
This now moves it to its own folder under Holidays.
|
| |
| |
| |
| |
| | |
Moves the Pride features to the Holidays folder.
Corrected the paths to reflect this change.
|
| |
| |
| |
| |
| | |
Moves the valentine's day features to the holidays folders.
Corrected the paths to reflect the folder moves.
|
| |
| |
| |
| |
| | |
Moves all the hallowen features to the holidays folder.
Also updates the paths to reflect the folder moves.
|
| |
| |
| |
| |
| |
| | |
This moves the easter seasonal features into a more cohesive
holidays/easter folder. Additionally, this splits out earth day into
its own holiday folder.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Moves Advent of Code and Hacktoberfest into an events
folder. Although these are roughly associated with holidays,
they are standalone events that we have participated in
in the past.
Therefore they're being moved to an events folder
separate from the "fun" or "holidays" folders.
|
|/
|
|
| |
Logs below warnings aren't relevant when working on the bot
|
|\ |
|
| |\ |
|
| | |\ |
|
| | | |
| | | |
| | | |
| | | | |
`discord.Member.permissions_in()` was removed in d.py 2.0 in favour of using `discord.Channel.permissions_for()` everywhere.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |/ |
|
| | | |
|
| |/ |
|
| | |
|
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| | |
Hard-coded in the appropriate 404 jpgs for wehn a status code does
not exist from the dog or cat urls.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
The unknown error embed was not using the text correctly,
using the suggestion from wookie to fix.
The "404" response from the dog URL returns 302 instead,
changed the elif to check if 302 response is returned.
|
| |
| |
| |
| |
| | |
Changed the range check for the status code.
Previously was 599, now 600.
|
| |
| |
| |
| |
| |
| |
| | |
Corrected the URL for the Dog embed (was mistakenly using CAT URL.
Created a standalone ERROR_LENGTH_EMBED to send if the code used
by the user is not in the range 100, 599.
Changed the response status check to include 299 (to be proper).
|
| |
| |
| |
| |
| | |
This will avoid sending the error embed even when the status codes
are ok.
|
| | |
|
| |
| |
| |
| | |
Also updated the line breaks, black was formatting on save locally.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Now that the branch is correctly tracking only the changes to the
file `status_codes.py` the other requests can be addressed. Currently
the only change not addressed is to handle the range of responses
allowed. My focus will be on lines 45 to 64 for these changes.
Issues #428 #500 #608
PR #610
|
|\| |
|