jurassicplayer
commented
8 years ago Things left to do:
- Decide how to deal with passing the MODE parameters to plugins (Rizon puts the mode in the trailing, IRCHighway puts it in the params, and I don't have a good way to standardize it)
- Pass quit messages to plugins
- Make sure the template plugin follows those.
- Put some server management into the IRCClient class (at the very least, iterate through a config to get the information for each server and connect).
- Possibly update all of the plugins as needed.
So it's kind of that time of the year where I feel like restarting on my IRC bot...again.
I've moved the plugin managing stuff out of the actual irc bot and made the main script more or less just something that instantiates the objects and then sits there doing nothing. The irc client will have to magically deal with starting/closing server connections...or just not deal with it at all. Currently it should be able to correctly spawn a thread per server for receiving data which just leaves iterating through the "list of servers" and connecting to all of them to be handled by the client. The plugin manager also has access to the IRC message object (which will sort out the data into nicer variables) and the actual server object, allowing it to use the server methods to send replies back. I might need to expand the template plugin to be able to catch certain replies (or maybe even all) so that things like authenticating might work (an idea only in my head, not entirely fleshed out). Something along the lines of open an "auth ticket" with the user nick, request info from the server, match server auth reply with the user nick, and then check authentication status. It's probably better to have the whole auth thing as a separate plugin.