[who]
### who
This lists all the users connected to the bot your on and
the bots connected to this one.  Soon typing .who <bot> 
will display users on that bot.
[quit]
### quit
 This is the proper way to exit the dcc chat party line.
[motd]
### motd
 This re-displays the MOTD file to you, this is the text
 file written by the owner of the bot.  It might have info
 about things in the channel, or whatever, it is upto the
 owners jurisdiction.
[chattr]
### chattr <nick> <+ or - <flag>>
 This can be typed with just a nick to get the current flags,
 or with a flag to add or remove one.  In this version, only
 one flag can be added or removed at a time.

 ex.
 .chattr Killar
 This displays Killar's current flags.

 .chattr Killar +o
 This adds Killar to the op list, giving him many op commands.
 This also displays the flags after the change has been made.

Help on flags:
 d - auto deop
 f - flooding access
 p - protect
 o - op
 m - master
 n - owner *note - only one person should really have
for security reasons.
[set]
### set <variable> [value]
 This is used to set all the variables so that the bot reacts
 to situations how you want him to.
KillNetAdminDieAutoOp
FserveFserveMsgFservedirDccLimit
FserveLimit XdccDir HomeChan
use '.help set <variable>' for more info on each variable.
[adduser]
###adduser <nick>
This command adds a user to the userlist, the nick specified
 must be someone in the home channel for your bot.  Just
 a user like this gives them party line access, and that's
 it.  You miust use the .chattr command to give them more
 or less flags.  Use .-user to remove a user.
[-user]
### -user <nick>
 This removes the specified nick from the userlist, this
 person does not need to be present in channel to remove him
 or her from the list.  This removes all flags and anything
 related to the user.
[op]
### op <nick>
 This ops the specified nick if both the person issuing the
 command and the nick specified have +o flag.
[deop]
### deop <nick>
 This de-ops the specfied nick. The person issuing the command
 has to have +o and the nick specified has to NOT have +o.  If
 the nick specified is on the op list, it won't deop him.
[topic]
###topic <new topic>
 This changes the topic in the bots homechannel to the one
 specified, you hvae to have +o to use this.
[lusers]
###lusers
 This lists all the users in the bots data base.  It shows the
 handle, hostmask, and flags.  You must have +m to access
 this command.
[msg]
### msg <nick> <message>
 This sends a message to the specifed nick, you have to have
 +o to use this command.
[link]
###link <bot-nick>
 This sends a request to the specified bot for a link, it is
 only sent if the nick specifed is a bot.  Once the other bot
 recieves the message and verifies that he is a bot they attempt
 to link through a dcc chat.  A message "*** Link to <bot-nick>"
 will be displayed when they are linked.
[unlink]
###unlink <bot-nick>
 This unlinks the specifed bot if it is connected.
[say]
###say <text>
 This makes the bot talk in the home channel, you must have
 +o to use this command.
[jump]
###jump <server> [port]
 This jumps the bot to a new server, you may also specify a
 port.  (Not specifing a port makes it go back to default,
 which is 6667)  You must have +m to use this command.
[die]
###die
 This kills the bot complety, it logs off the server and even
 closes off Mirc.  This command may only be used by the owner
 unless you .set Die 1  That gives access for masters to use
 the die command. (for more info type .help set die)
[setKillNet]
###set KillNet <1 or 0>
 This sets the flooding portion of KillBot on or off.  Setting
 it to one turns it on, meaing your bot participates in the
 floods going on with the linked bots and you can join in too.
 If this is set to 0 then your bot just doesn't reacte to them,
 it just passes them along the network to ther bots.  Also when
 set to 0 you cannot send commands either.
[setdie]
###set Die <1 or 0>
 This tells wether you want to give access to masters to use the
 .die command to shut down your bot.  Setting it to 1 allows
 masters to use the .die command, setting it to 0 only allows
 owners to use this command.
[sethomechan]
###set HomeChan <#channel>
 This is the channel that the bot is supposed to join on connect
 to and to manage.  You can change the homechan on the fly while
 while connected.  The bot can only process all channel related
 functions while in the Home Channel.  This would be a channel
 you have ops in and need a bot to help manage it.
[setfserve]
###set Fserve <1 or 0>
 This turns the File Server on or off, setting it to 0 turns all
 ways of accessing the File Server.  You can access the File
 threw the dcc party line, or via a command in the channel. (see
 more on .help set fservemsg for info on that) But if you set this
 to 0 is turns all those things off, if it is set to 1, then you
 can access it from those methods.
[setfservemsg]
###set FserveMsg <0 or [text]>
 Setting this to 0 turns off this method of activating a File 
 Server, which is from a channel message.  Setting this to a one
 word command allows people to type that command in the bots Home
 Channel and access, provided the File Server is turned on. (see
 .help set Fserve for more info on that)
[setdcclimit]
### set DccLimit <#>
 This sets the max amount of Dcc Sends that can be open at one
time.  I recommend this be set to 2 or 3 so the other person can
 get some actual speed, cause it may seem like YOUR transfering a
 lot but on the other end the speed probably sucks :) so don't be
 lame and set this to like 6 or 7.
[setfservelimit]
### set FserveLimit <#>
 This sets the max amount of File Servers that can be open at one
 time. I recommend this be set to 1 or 2, if you set this high for
 for some reason that can actually lag your preformance A LOT, so
 don't do it, set it to 1 or 2. 
[setfservedir]
### set FserveDir <dir>
 This is the directory that your file server starts up on when 
 someone uses it.  ex. d:\temp\files\
[autoget]
###autoget <1 or 0>
 This sets if your auto dcc get is on, you will be noticed in
 dcc chat of file intiation whether this is turned on or not.
 1 = on, and 0 = off.
[fserve]
### fserve
 If the bots File Server is turned on then it starts up another
 Dcc Chat to File Serve with for you.
[join]
###join <#channel>
 This joins the specified channel and then updates the internal
 address list (IAL).  This is useful for making the bot join so
 you can add users to your bot.  When your bot is in this channel
 it will not react to anything, only operations are allowed in the
 bot's home channel.
[part]
###part <#channel>
 This parts the specified channel, if you say the home channel it
 WILL NOT part this channel unless you are the owner or have owner
 access.
[knjoin]
###kn join <#channel>
 This makes all bots participating in the flooding network to join
 the specified channel.
[knslowjoin]
###kn slowjoin <#channel> [period of time to join over in seconds]
 This makes all the bots join the channel using a random timer with
 with the amount of time you put in. If you specify 45 seconds then
 the bots will join the channel over a 45 second period.
[knpart]
###kn part <#channel>
 This makes all the bots participating in the flooding network to
 part the specified channel.
[knmsg]
###kn msg <nick or #channel> <message>
 This makes all the bots on the flooding network to message the 
 specified nick or channel with the message given.
[knvf]
### kn vf <nick1 or #channel1> [nick2 or #channel2] [etc]
 This uses a version flood to flood the nick(s) or channel(s)
 specified.  You can type in upto 7 nicks or channels to flood at
 one time.
[knef]
### kn ef <nick1 or #channel1> [nick2 or #channel2] [etc]
 This uses a echo flood to flood the nick(s) or channel(s)
 specified.  You can type upto 3 nicks or channels to flood at the
 same time.

 * note - I love this flood :)
[xdcclist]
### xdcc list
This is used to obtain the xdcc file offering list, if any are
offered or if xdcc is turned on.
[xdccsend]
### xdcc send #
This sends a request to recieve the file offered at the slot you
slot you have specified.  You only will recieve a file if there
are any slots open at the time.
[xdccon]
### xdcc on
This turns the xdcc offer bot on.
[xdccoff]
### xdcc off
 This turns the xdcc offer bot off.
[killneton]
### killnet on
 This turns the flooding portion of KillBot on.  In this system
all the bots that are linked to you can flood with enourmous power,
 this is of course the bots that have KillNet turned on also.  If you
 use ircii clones, then they follow every command of the bot it is
 connected to, so if KillNet is off, it is off on them also.  Type
[killnetoff]
### killnet off
 This turns the flooding portion of KillBot off.
[whoami]
### whoami
 I put this in to lesson some confusion with the bot's user system,
 I use this to find out what nickname the bot has me under and such
 so when i use .chattr i can get the right nick.  It also shows your
 flags if you want to know that, your hostmask and pretty much 
 everything the bot knows about you.
[xdccoffer]
### xdcc offer <file> [description]
 This is used to offer a file using the xdcc protocol.  Make sure
 you set your xdcc direcory and place all offered files there, or
 else the script won't find them and won't add them.
[setxdccdir]
### set xdccdir <path>
 This set's the directory in which the xdcc part of the script will
 look for and resource files from.  This can be any directory and
 does not have to be on the KillBot directory.  If the directory you
 you set does not exist then everything will mess up, you have been
 warned.
[setadmin]
### set admin <nick>
 This is just a variable that you can set to the Administractor of
 the bot, in other words, the person running it.
[xdccremove]
### xdcc remove #
 Use this to remove the packet number you specify.  Type '.xdcc list'
 to get a list of the files.
[knmf]
### kn mf <nick1 or #channel1> [nick2 or #channel2] [etc]
 This flood is called Multi-Flood, it sends a bunch of different
 ctcp's, i don't think it's very effective but it's in there if
 your looking for something different :)
[knpf]
###kn pf <nick1 or #channel1> [nick2 or #channel2] [etc]
 This is a ping flood, it can be very effective in some cases
 because some scripts weaken their ctcp protection again't the
 ping ctcp so they can let other users check lag with them.  That
 usually isn't the case but if you run out of other floods to do
 then here's another one to use :)
[whois]
### whois <nick>
 Use this to lookup information about a certain user, if gives you
 their hostname, and that's about it at this point.
[+channel]
### +channel <#channel>
  This is part of the multi-channel feature of KillBot, type '.+channel
  #mircscripts' for the bot to join that channel and to protect it and
  such as it does all Home Channels. Type .channels to list the channels
  the bot is in already.
[-channel]
### -channel <#channel>
  This removes a channel from the Home Channels list, type '.channels'
  to get a list of channels your bot is in.
[channels]
### channels
  This displays all the channels your bot currently has set to being
  a Home Channel.
[dccstats]
### dcc stats
  This shows all incoming and outgoing dcc transfers. You can use this
  to view who is leeching off you or giving you stuff.
[ping]
###  ping <bot>
  This allows you to ping a bot on the dcc network, use this to figure
  out if there is a lagged link and you need to reorganize your network
  and such.
[xdccreset]
### xdcc reset
  This resets the Leeched: parameter to 0