dswp.de • projects:dswpbot:todo

projects/dswpbot/todo.txt · Last modified: 2010/08/05 21:58 by Unclefragger

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

Things we should implement, change or adjust in the bot:
  * create a new function //reply(<event_object> event,<string> Message)// ((maybe not the event but an other object)) to replace in plugin decision to reply in a channel or privmsg
    * check if the user is allowed to use a command (and allowed to use @ for public reply) within the core-bot, don't even waste resources executing the plugins if the user isn't allowed to. Needs a place for for configuration, maybe main bot config? Subsections for all desired commands then those override default settings, so you don't have to set anything for default levels, only to override.
    * merge EV_PUBMSG and EV_PRIVMSG into EV_PRIVMSG (closer to IRC protocol), if it's a whisper replace in origin $BotName with PRIVMSG -- to be more detailed and maybe just implemented
  * less dswp and db dependent, maybe fall back mode where all users are admin lvl (just for testing purposes)
  * use python logging err, warn, debug and so on
  * on join pm people if there are new messages in their inbox (forum's)
  * introduce idle state after one hour of no chat
    * on return pm if there are new messages
  * !seen command, self explanatory

Wishlist (add your wishes here):
  * have a !news command that handles topic altering and/or maybe get news from the forums