cynic
/
modular-discord-bot-fw
mirror of https://github.com/kurisufriend/modular-discord-bot-fw
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
11 Commits
1 Branch
0 Tags
82 KiB
 
Tag: Branch: Tree: 77464883b1
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '77464883b1'
${ noResults }
BuildTools 77464883b1
allow for plugins ot clean up after themselves 		3 years ago
default_plugins split config-defined plugins and builtin plugins 4 years ago
plugins split config-defined plugins and builtin plugins 4 years ago
.gitignore every single time. 4 years ago
LICENSE Initial commit 4 years ago
README.md this was uncommitted 3 years ago
client.py allow for plugins ot clean up after themselves 3 years ago
config.json hot reloading and authentication 4 years ago
disc_api.py api stuff werks, client will idle and get events. 4 years ago
grim_logger.py api stuff werks, client will idle and get events. 4 years ago
main.py split config-defined plugins and builtin plugins 4 years ago
plugin_manager.py allow for plugins ot clean up after themselves 3 years ago

README.md

modular-discord-bot-fw

framework for discord bots that uses contained files for individual feature plugins that can be modified and reloaded on the fly

basic structure:

  • client class has implementations for handling opcodes
    • event response is up to the client (!!)
    • this lets us expose events for plugins to hook into, but keeps core API interaction defined in-class
    • any and all bot features should be useable via independent feature plugins
      • these are dynamically found and run, so they can be hotloaded, modified, etc. without disconnecting or restarting the whole bot session

todo board

core:

  • basic rate limiting
  • make sure broken sockets are properly addressed with a resume or reconnect
  • initial presence in config
  • full REST api implementation
  • plugins need to be asynchronously run (or something)

plugins:

  • save session config to file
    • re: runtime modufication of authenticated users and such

done:

  • plugin manager & hook integration
  • default plugins so the bot does something out of the box
    • plugin reloading, user (command) authentication, etc. will also probably be written in plugin form
  • take config as cli param