aboutsummaryrefslogtreecommitdiffstats
path: root/bot/bot.py (unfollow)
Commit message (Collapse)AuthorLines
2019-02-23loaded json file in the init methodGravatar Rohan-22/+26
2019-02-21Made the try catch block narrow and only catching KeyErrorsGravatar Rohan-21/+21
2019-02-20Wrote the command as described in the issue #107Gravatar Rohan-0/+317
2019-02-20Update whoisvalentine.py to address requested changesGravatar Darth Delay-3/+5
A few things have been changed to address the changes listed under PR #122: - Changed the color tag of the embed from both commands from discord.Color.dark_magenta() to bots.constants.Colours.pink - Renamed valentine_facts to valentine_fact These changes are needed to fit the projects standards.
2019-02-19Add .who_is_valentine and .valentine_factsGravatar Darth Delay-0/+75
Closes #102 This pull request adds the commands who_is_valentine and valentine_facts. The who_is_valentine command sends information about Saint Valentine of Terni to the channel the command has been called in. This is done by making use of the valentine_facts.json file's 'whois' attribute, which has all the information stored in it. The valentine_facts command sends a random fact with a random title to the channel the command has been called in. This is done by making use of the of the valentine_facts.json file's 'titles' and 'text' attribute, in which both, the information for the titles and the facts are stored in. Both commands do have docstrings, which explain what the command does in an easy manner. At the moment, there's a really sparse amount of facts available. I seek to add a lot more in the near future.
2019-02-17Add direct reference to terning emoji to constants, fun cogGravatar sco1-1/+11
2019-02-17changed variable name from message to time_remainingGravatar Rohan-2/+2
2019-02-17Changed the variable name error_message to messageGravatar Rohan-2/+2
2019-02-17I did the following changes:Gravatar Rohan-1/+7
1)Added a help text to .savethedate 2)Edited the error message for cooldowns so that it shows not only seconds remaining but also minutes(if cooldowntime>60 seconds)
2019-02-16Escape markdown in usernamesGravatar Ava-9/+13
2019-02-16Somewhat normalize argumentsGravatar Ava-5/+12
2019-02-163rd code review. Added docstring.Gravatar astieman-0/+3
2019-02-16Fixed grammar, quotation style and dictionary styleGravatar abdullah oday-11/+12
2019-02-16Unindented commentGravatar abdullah oday-1/+1
2019-02-16Fixed an issue with the requestGravatar abdullah oday-20/+19
2019-02-16Fixed log.warningGravatar abdullah oday-1/+1
2019-02-16Made warning message more explicitGravatar abdullah oday-3/+4
2019-02-16Fix import orderingGravatar Ava-1/+1
One of the dependencies seems to install `typing` from PyPi for some reason, which confused PyCharm's import optimizer.
2019-02-16Improve command help docstringGravatar Ava-8/+17
2019-02-16Added logging for KeyErrorGravatar abdullah oday-0/+2
2019-02-152nd code review complete. Default roll once and warning to roll at least ↵Gravatar astieman-2/+2
once implemented.
2019-02-16Used bot.http_session instead of creating a new session, and now checking ↵Gravatar abdullah oday-16/+19
for KeyError
2019-02-15Removed "Generator" fom log.debugGravatar abdullah oday-1/+1
2019-02-15Fixed quotation style, removed unnecessary newlineGravatar abdullah oday-14/+13
2019-02-15Refine love calculator commandGravatar Ava-61/+84
2019-02-15Fixed grammar issues, Moved constants to the top, Changed function nameGravatar abdullah oday-14/+13
2019-02-15Fix LoveCalculator 0% bugGravatar Darth Delay-3/+3
Recently a test of the .love command revealed an unintentional reaction when 100% are reached. In previous versions this command had used a gigantic conditional block, checking for the current percentage given by the love_meter formula. When reaching 0 (meaning that the UserID's evenly divided with 100) it would automatically convert that 0 to 100. A big mistake from my side back then. This has been fixed with these changes. By quickly modifying the formula to use a mod 101 instead of a mod 100, we get an accurate percentage, ranging from 0-100% instead of 0-99%. love_matches.json has also been fixed to address these changes, meaning that the lowest entry now actually is 0 and the highest 100. TL;DR: -> Edited love_meter formula to calculate mod 101 instead of mod 100 -> Edited lowest and highest entry in love_matches.json to be 0 and 100
2019-02-14Code review changes implemented. Reverted so error handling is done by base bot.Gravatar astieman-15/+7
2019-02-14changed import orderGravatar abdullah oday-1/+1
2019-02-14removed print functionGravatar abdullah oday-1/+0
2019-02-14Replaced urlib with aiohttp , added docstrings and fixed issuesGravatar abdullah oday-22/+24
2019-02-14createdGravatar abdullah oday-1/+3