Difference between revisions of "Ackis2.0"
From Makers Local 256
m (→Client Features: added moar) |
m (added overview) |
||
| Line 1: | Line 1: | ||
| + | =Overview= | ||
| + | The bot is comprised of one Engine and at least one Client. Each Client and the Engine being separate processes there will need to be an API for them to communicate either via trusted local socket or ACLed tcp socket. The Engine has different modules, separate files probably that can be loaded and unloaded at start and runtime. Each of these modules has an init section which tells the engine which events they want to hook. Each of the clients send every event they can to the engine. | ||
| + | |||
=Status= | =Status= | ||
<onlyinclude>{{{status|Early Planning}}}</onlyinclude> | <onlyinclude>{{{status|Early Planning}}}</onlyinclude> | ||
Revision as of 12:17, 16 August 2007
Overview
The bot is comprised of one Engine and at least one Client. Each Client and the Engine being separate processes there will need to be an API for them to communicate either via trusted local socket or ACLed tcp socket. The Engine has different modules, separate files probably that can be loaded and unloaded at start and runtime. Each of these modules has an init section which tells the engine which events they want to hook. Each of the clients send every event they can to the engine.
Status
Early Planning
Features
- Single Engine with multiple connect routes
- s2s connection with the IRC server for god like abilities
- regular client connection
Engine Features
- RSS
- "brain" to learn
- Markov chains?
- Weather
- IMDB
- tie in with http://www.pogdesign.co.uk/cat/ ?
- tie in with utorrent webstats?
Client Features
- nickserv aware
- ACLs
- tracks nick changes
- ability to not die or trash the connection when the engine kicks it
- ability to restart or notify the Admin(via ACL) when the engine dies
