TODO: Version 1
1) Setup basic config: Version 0.0.1 - Done
Config file directives:
BotKillerDB - DB file for the bot killer to track channels and users who enter the channels (by hostname).
BotKillerName - Name (IRC nickname) of the pseudo client.
BotKillerIdent - Ident of the pseudo client.
BotKillerHost - Hostname of the pseudo client (real, vhost, or fake, doesnt matter ;P ).
BotKillerRealName - Real name of the pseudo client.
BotKillerModes - Either a quoted list of modes the bot should use such as "+BqS" or "default" to use standard service bot modes.
BotKillerAkillLimit - The number of times a given client (hostname) can join a tagged channel before its perm akilled.
BotKillerAkill1st - The length of time for the first akill of a hostname.
BotKillerAkill2nd - The length of time for the second thru the (BotKillerAkillLimit - 1) akills of a host name.
2) Read basic config and store for processing: Version 0.0.5 - Done
3) Create pseduo client from config values: Version 0.0.7 - Done
4) Create example config section: Version 0.0.8 - Done
5) Create instructions on how to edit the services.conf and autoload the module: Version 0.0.9
6) Setup header section of source code: Version 0.1.0
*) Create proper references to Anope: 0.1.2
*) Create proper Credits section: 0.1.3
*) Create release history: 0.1.4
*) Create author contact info: 0.1.5
*) Create GNU licencing section: 0.1.6
*)
7) Implement db interactivity: Version 0.2.0
*) open/close DB: Version: 0.2.1
*) read/write DB: Version 0.2.2
8) Setup new chanserv command: Version 0.3.0
*) /cs TAG <chan> ON|OFF|WARN: Version 0.3.1
*) WARN: Implemented via WALLOPS.
9) Add config directive to make pseudo client join a single chan: Version 0.4.0
Config file directives:
BOTKILLERJOINCHAN - The chan that the pseudo client should join.
BOTKILLERLOG - Have the pseudo client give reports to the chan about what its doing.
10) Make /cs TAG <chan> WARN log to assigned chan, if used, or wallops if not used: Version 0.5.0
*) Allow WARN to use both methods if desigred: Version 0.5.1