Advertisement
Rapptz

new bot changes

Jul 12th, 2015
629
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.90 KB | None | 0 0
  1. I have reworked the bot significantly. A lot of things have changed. Some things you won't care about, the others you might.
  2.  
  3. Nevertheless I list all the changes here for prosperity.
  4.  
  5. 1. All commands now have a "!command help" command, even if they're not useful.
  6. 2. !botcommands now lists help text for every command.
  7. 3. Bot commands now take in a bot parameter rather than a message parameter.
  8. 4. The owner-only message has been standardised and consistent throughout every command.
  9. 5. The bot now has new commands: !season, !debug, and !refresh
  10. 6. !season handles the seasonal ranking stuff. It requires a subcommand which I will list below.
  11. 7. !season check <username> will check the user's ranking in the current ranking period.
  12. 8. !season rank <url> will add a URL to the seasonal database.
  13. 9. !season top <number> [condensed?] returns the current top <number> players in the ranking. Pass in "yes" to the last parameter
  14. if you want it in a single line rather than multiple lines. e.g. "!season top 16 yes" will give you the top 16 in a single line.
  15. 10. !season reset will remove all data from the season. Use !season top <number> before doing this because otherwise it'll be gone forever.
  16. 11. !debug command is meant for personal use -- it helps me debug the bot if issues arise obviously.
  17. 12. !refresh reloads the entire command set and the configuration. This means that when I work on the bot there will be less
  18. chances of it going down because I can just refresh it instead. Again, personal use mainly.
  19.  
  20. Due to how many changes there are, chances are something /might/ have broken. I went out of my way to make sure nothing did
  21. but sometimes these things pop up.
  22.  
  23. With these changes in place I suspect that it will be easier to add more complicated commands in the future such as the long
  24. awaited "!timer" command. However that'll happen when I have feel like working on the bot which is not often.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement