Bug reports, suggestions, questions welcome! Send to:   datafox@gewi.kfunigraz.ac.at

  Installation
--------------

Notes: This is a "background" bot! (In IRC you'll see another "person" with the same address
as you.) This is not a pop-up bot/script, although there is a little script included!
You need at least mIRC version 4.6! The bot is NOT compatible with lower versions of mIRC!

1. Unzip all files to your mIRC directory (the directory where mirc.exe or mirc32.exe is).
2. Be sure to unzip the sub-directory "databot"!
3. You need to run "multple instances" of mIRC to use the bot. For this, I'm using a part of
   the mIRC FAQ by Tjerk Vonck. If you already know how to do that, skip this part; if you
   don't, READ IT CAREFULLY!!! Oh, it's a bit old, so the mirc.ini can not be found in
   c:\windows. Use mirc.ini and databot.ini in your mIRC dir. And there's a DataBot icon
   included

> 6-19 Running multiple copies of mIRC.
> 
> mirc.exe 16-bit :
> 
> You can't just start the 16-bit mirc.exe a second time.  If you want to run a second copy of
> mIRC16 (don't ask me why), it's best to
> rename your mirc.exe to mirc1.exe and also copy your mirc.exe to another instance, like
> mirc2.exe.  ( In the windows File
> Manager select mirc.exe and with File/Copy copy it to mirc2.exe, and with File/Rename
> rename it to mirc1.exe.  Both copies
> can be kept in the same directory (the mIRC home dir.)) Do the same for the mirc.ini file that
> can be found in the c:\windows
> directory or in mIRC's home dir.  (Unless specified otherwise mIRC uses the mirc.ini file
> found in c:\windows. )  Copy mirc.ini to a
> mirc1.ini and to a mirc2.ini.  Now in the Program Manager, rename the mIRC icon to an icon
> called mIRC1, and use that to start
> the first copy.  'Under' the icon, on the startup line, state "c:\path\mirc1.exe -i
> c:\path\mirc1.ini" to make sure mirc1.exe will use
> the mirc1.ini!  Also, make an icon called mIRC2, and use that to start the second copy.  On
> the startup line 'under the icon' state
> "c:\path\mirc2.exe -i c:\path\mirc2.ini" to make sure mirc2.exe will use the mirc2.ini!  The -i
> startup line parameter tells mIRC to
> use the file after it as ini file.  If you want to place the mirc.ini files in another directory than
> your windows or home dir, make sure
> to specify the full and correct path!  You can now startup both exe's and configure them
> independently..... Nice huh?
> 
> 
> mirc32.exe 32-bit :
> 
> If you use the 32-bit version of mIRC you CAN run a second instance without problems
> without having to provide a second,
> renamed .exe file.  You don't have to rename and or copy the mirc32.exe.  BUT you still
> have to create 2 icons with unique
> mirc.ini names on the startup-line to get your 2 mIRC's working independently and not
> interfering ....  Don't forget that :-)
> 

4. The inis you'll use for your two mIRCs are 1) your normal mirc.ini (or whatever you use),
   and 2) the file databot.ini. I have to stress again that databot.ini and the mirc.exe must
   be in the same directory! Additionally, there must be a sub-directory called "databot" in
   your mIRC directory!
5. You do not need to change anything in any files. Just start the bot's mIRC. The title bar
   should say "mIRC - DataBot, ..." or something. If it doesn't, you didn't load databot.ini
   correctly. Read this part again. Go to File/Setup and change everything so it matches
   your settings. At least choose a nickname for your bot (don't use "DataBot". That's shitty)
   and enter your email address. Enter the same email address as in your other mIRC.
6. Now check if the commands are loaded: Go to Tools/Aliases... A list of commands starting
   with a comment line saying "Bot commands!!" should be there. Then look into Tools/Remote.../
   Events. Over 400 lines should be there. If one of these was empty or contained your
   alias definitions, you need to edit databot.ini. The section you're looking for is [Files]
7. If everything is correct till now, connect your bot's mIRC and your chat mIRC. After
   connecting you should see some status messages scrolling up, then over 70 command
   variabled being set. This may take some time. At the end you can read some status infos
   and "Connect & init finished". You can minimize mIRC's window now.
8. Switch to your chatting mIRC. Send the text "@login" to the bot. Do this by typing
   "/msg yourbotsnick @login" (w/o quotes). The bot should respond by saying hello and a
   CTCP command. This is for the chat-mIRC-side bot support.
9. If it worked till here, your bot is ready for use! Try commands like "@join", "@help" etc.

Read also the file HINTS.TXT






                /------\
                [  **  ]                               (C)
                [   ---/
                [   ---\
                [  *    ]   [   ]    /----\    ---/
                [  *    ]   [   ]    [ *  ]      /
                \------/     [-]     \----/    /____
                                          ]
                                      ____]


                              proudly
                             presents:


                        D A T A B O T    I I
                          (DataBot v2.05)




  TABLE OF CONTENTS
===================

0. Installation
1. Introduction
2. Description of the user levels
3. Commands
4. Contact info / Credits

Please read the file HINTS.TXT too.

Note: This documentation may be a bit outdated. So if you find something weird, don't just
believe it!


  Introduction
--------------

DataBot is meant to be a "background application", which means that you can use your
normal chat program to chat, but let a mIRC run in the background, and this mIRC is the
bot. Don't worry if you don't understand this, you'll get it after installing the bot.

DataBot has pretty good security. There's a good flood pretection against CTCP flooding,
command flooding, channel text flooding, nick flooding and (whatever it is) invite flooding.
It uses the genuine IRC flood detect method (which is cool). Additionally, nickname changes
while flooding are recognized. Besides this protection there's a ingenious (sorry for
the exaggeration) handling of the user levels, especially at opping and kicking. For
example, the boss is allowed to op anybody, except shitlisted and blocked users. A level
4 user is allowed to op directly a level-3-user, but a level-3-user is not allowed to op
anybody, except other level-4-users. Additionally, a level-4-user can op anybody (except
shitlisted and blocked users) using the @op command. This restriction is because DataBot
reports every usage of every command to the boss (you). And, of course, server ops are
not allowed, except for level-4-users and the boss. But don't forget: there are always
holes in a security wall. If you really get to find one, _please_ mail me with a
description of the circumstances, and I'll promise you an update as soon as possible
(as long it's not a mIRC bug :)  ).

DataBot is powerful. Although I'm not very experienced in writing war routines, I've
added commands for massop and -deop, a takeover routine and some simple flood commands.
But new suggestions are always welcome! ;)

DataBot is customizable. There's a special ini-file (datacfg.ini) where all important
standard values are saved. Changing this values on-line with commands is also possible,
and the bot will save the changes in most cases (where it's logical) automatically.

DataBot is advanced. Most of the commands are "multi-commands" which means that you
can specify more than one channel/nickname. The best example is probable @kick. You
can only say "@kick lameguy" (simplest type) or you could use "@kick #mirc #friendly
lameguy lame2 kickme" (most complex structure). For further information read the
General Notes of the Commands section.



  Description of the user levels
--------------------------------

Mainly, there are 4 levels. For a description of who is allowed to do what, see
the sections Commands.

* Level 1: The general user. Everybody _not_ registered has level 1. By @ADDing
somebody at level 1 you reset him/her to a general user.
* Level 2: A friend. Add somebody at this level if you know him/her and want to
give him/her little control over your channels.
* Level 3: A Pseudo-Op. This means that the person is _not_ allowed to get channel
ops (@), but can do most things using the bot. Use this level for somebody you don't
_completely_ trust. Also useful to prevent channel takeovers.
* Level 4: Your partner. Give somebody you completely trust level 4. He/She is
allowed to get channel ops, therefore has control over the channel, but _not_ over
the bot and its level list. So a level-4-person can kick etc, but cannot de-op or
kick somebody else with level 4. Of course he/she can't make the bot join, part or
add users.

There are also some special levels (You don't need to care about temporary levels
and the internal level handling):

* The boss. This is usually you and has complete control over the bot. You shouldn't
give this level to somebody else (and you normally can't). Consider this as level
100 :)
* Blocked. A blocked user is allowed to talk in your channels, but has no (really no)
access to the bot's commands. Of course he/she is not allowed to get ops.
* Shitlisted/Banned. If someone gets shitlisted, he/she will get kicked out of
all channels by the bot. A temporary ban will also be created. He/She won't be able
to join the channel.

There's also a "fake" user level:
* Ignored. This uses the internal mIRC ignore command. The bot won't even receive
messages sent to it. Use this for somebody flooding you and your bot (btw: the bot
should automatically ignore flooding people. Mail me if it doesn't ;) )


  Commands
----------

General notes:
The commands are sorted by levels.

msg=send as /msg (or /query); chan=type in channel

Examples are only given if there are parameters.

Note that for most commands you have to be op in the channel.

Most commands allow you to specify more than one channel/nickname. This is indicated by
eg. "@join <chan> [<chan> [<chan> ...]]". This means you have to specify at least one
channel, but you may specify as many channels as you like (nearly). Something like
"@part [<chan> [<chan> [<chan> ...]]]" means that you may specify one or more channels,
but you don't have to. If you don't specify a channel, the bot will part the current
channel. This means that the command "@part" without parameters is _only_ valid if typed
in a channel. Just sending "@part" in a private message (/msg...) won't have an effect.
But sending eg "@part #mirc #datafox" in the channel #friendly does not include leaving
of #friendly! The word "dependend" in the command specification indicates that there's
a difference between using the command in a channel or a private message (/msg).
Another type of such multi-commands is @op and @dop. The simplest syntax is eg "@op
coolguy", which will op CoolGuy in the current channel, so this is only available
in a channel. In both channel and /msg the syntax "@op #mirc datafox" is available
(ops datafox in #mirc). But the cool thing is: you can specify multiple channels AND
multiple nicknames! Eg "@op #chan1 #chan2 #chan3 nick1 nick2" will op nick1 and nick2
in the channels #chan1 #chan2 #chan3. Cool huh? You should get the idea of the multi-
commands by now. (Note: Level and flood commands (@add, @shit, @bother etc) don't have
this feature, you can only add one person at the same time (but of course you can use
these commands "in a row"))
Be careful with multi-commands with parameters of this kind (like @kick and @ban):
"[<chan> [<chan> [<chan> ...]]] <nick> [<nick> [<nick> ...]]". If you specify, say, 5
channels and 4 nicknames the bot will do 5*4=20 kicks! You could risk a flood excess!
But, well, try it!  ;)

Sorry for always taking #mirc and #friendly as example channels. :)

PLEASE NOTE: Since you can customize the command character (by default a "@") and the
login command too (by default "login") the commands listed here do not necessarily match
the actual commands. If you didn't change anything in datacfg.ini, the commands will match
the actual commands. But I hardly recommend that you change at least the login command to
any password. Of course you can modify the command character too :) Oh, you can change the
command character online using the @commchar command.


@whoami
(msg or chan; all standard levels)
Sends the nickname, the address and the current level of the user

@time
(msg or chan; all standard levels)
Sends the local time of the bot (ie the current date and time settings of the system)

@files
(msg or chan; all standard levels)
Opens a file server. The home directory is specified in datacfg.ini and can be changed
there. You can change this value in run-time with the @offerdir command too, but this
will not change the default in the datacfg.ini file. The Welcome file is fserve.txt in
the DataBot directory. Change this if you want to.

@login
(msg; all levels, but only once, usually directly after connecting; customizable)
Initializes the bot and marks you as its owner. Without doing this the bot does work,
but nobody has control over it. Since the bot enables this command again if its boss
(you) quits IRC, you can customize this command, ie you can make it like a password.
Modify the file DATACFG.INI for this. For example, if you change it to "mypassword",
you need to type "@mypassword" to log in correctly. If you've changed the command
character to eg a tilde ( ~ ), the command would become "~mypassword". So you needn't
be afraid that someone takes over your bot while you are not connected to IRC (excess
flood, ping timeout etc). Nice feature, huh? :) But be careful not to choose an existing bot
command. It should work though, but better choose something else. You can change the
password value using the @password command. This will be saved into the ini-file too.

@inviteme <chan> [<chan> [<chan> ...]]
(msg or chan; levels 2-boss)
Allows a user to invite himself/herself to a channel. This is only useful if your bot
is on an invite-only channel
Eg: @inviteme #mirc
    @inviteme #mirc #datafox #friendly

@topic [<chan> [<chan> [<chan> ...]]] <newtopic>
(msg or chan (dependent); levels 2-boss)
Changes the topic of one or more channels. (Future: Topic protector)
Eg: @topic A new topic
    @topic #mirc #datafox #friendly The new topic of #mIRC, #DataFox and #Friendly!

@count
(chan; level 2-boss)
Sends you the number of persons in the current channel.

@level <nick/address>
(msg or chan; levels 3-boss)
Returns a level definition of the user list of the bot. You can specify a nickname or a
full user address (form: "nick!handle@dialin.host.domain", usually just
"*!*handle@*.host.domain"). Something like "*!*@*.at" won't return anything, since the
specified address has to match exactly an user definition.
Eg: @level DataFox
    @level *!*datafox@*.kfunigraz.ac.at

@kick [<chan> [<chan> [<chan> ...]]] <nick> [<nick> [<nick> ...]]
(msg or chan (dependent); levels 3-boss)
Kicks a user from a channel. Here's again the security: nobody can kick you or the bot
using this command. Kicking of level-3 and level-4-users is not allowed too. But the boss
(you) can kick everybody using this command.
Eg: @kick LameGuy
    @kick #mirc #datafox #friendly lameguy lame2 lamer

@ban [<chan> [<chan> [<chan> ...]]] <nick> [<nick> [<nick> ...]]
(msg or chan (dependent); levels 3-boss)
Bans the address of an user from a channel. This works _only_ with nicknames, the bot will
look the right address up. (This restriction is for security reasons. For the boss, there's
a @banad command.) The bot will only do a temporary ban for 2 minutes.
Eg: @ban BanMe
    @ban #mirc #friendly ban_me and_me me_too

@bkick [<chan> [<chan> [<chan> ...]]] <nick> [<nick> [<nick> ...]]
(msg or chan (dependent); levels 3-boss)
Bans and kicks a user from a channel. Here's again the security: nobody can bkick you or
the bot using this command. BKicking of level-3 and level-4-users is not allowed too. But
the boss (you) can bkick everybody using this command.
Eg: @bkick LameGuy
    @bkick #mirc #datafox #friendly lameguy lame2 lamer

@invite [<chan> [<chan> [<chan> ...]]] <nick> [<nick> [<nick> ...]]
(msg or chan (dependent); levels 3-boss)
Allows a user to invite one or more persons to one or more invite-only channel. Inviting of
shitlisted/blocked users is not allowed (except by the boss).
Eg: @invite myfriend
    @invite #mirc #datafox #friendly friend1 friend2 friend3

@say [<chan> [<chan> [<chan> ...]]] <text>
(msg or chan (dependent); levels 3-boss)
Makes the bot say a text in a channel.
Eg: @say Hi!
    @say #datafox #mirc #friendly Multi-hi!

@me [<chan> [<chan> [<chan> ...]]] <text>
(msg or chan (dependent); levels 3-boss)
Makes the bot "do" some text, ie if the bot would type "/me <text>"
Eg: @me is a bot
    @me #friendly #mirc invites you to #datafox

@sayall <text>
(msg or chan; levels 3-boss)
The bot will say <text> in all channels it's currently on.
Eg: @sayall Hiya everybody!!

@meall <text>
(msg or chan; levels 3-boss)
The bot will "do" <text> (like /me ...) in all channels it's currently on.
Eg: @meall invites everybody to #datafox

@free
(chan; levels 3-boss)
Sets the modes +n-timsplk in the current channel.

@std
(chan; levels 3-boss)
Sets the standard modes +nt-imsplk in the current channel.

@lock
(chan; levels 3-boss)
Sets the modes +ntis-mplk in the current channel.

@opme [<chan> [<chan> [<chan> ...]]]
(msg or chan (dependent); levels 4&boss)
Lets the user get opped in a channel.

@op [<chan> [<chan> [<chan> ...]]] <nick> [<nick> [<nick> ...]]
(msg or chan (dependent); levels 4&boss)
With this command you can op a user in the current channel or a user in an other channel.
If you type this in a channel, you can leave <chan> out, it will apply to the current
channel then. But you can specify <chan> too. If you send this as a private /msg to the
bot, you have to speicify <chan>. Level 4 users are allowed to op any person, but only
via the bot command (only a direct op of a level-3 user is allowed).

@dop [<chan> [<chan> [<chan> ...]]] <nick> [<nick> [<nick> ...]]
(msg or chan (dependent); levels 4&boss)
Deops a user. See @op. Restrictions similar to @op.

@bother <nick>
(msg or chan; levels 4&boss)
Bothers any user with some long messages.
Eg: @bother LameGuy

@join <chan> [<chan> [<chan> ...]]
(msg or chan; boss level)
Makes the bot join one or more channels (at the same time)
Eg: @join #mirc
    @join #mirc #datafox #friendly

@part [<chan> [<chan> [<chan> ...]]]
(msg or chan (dependent); boss level)
Makes the bot part a channel. In a channel you can use "@part" which makes the bot
leave the current channel, or you could specify <chan> (works as both channel message
or private message). You can also specify more than one channels.
Eg: @part
    @part #mirc #datafox #friendly

@partall
(msg or chan; boss level)
The bot will part all channels without any checking of any kind. I guess that's the
simplest command of the whole bot.

@add <nick> <level/alias>
(msg or chan; boss level)
Adds the user <nick> at <level>. Valid levels are 1-4. Or you can use instead of the
level numbers the aliases (names) of the levels which are general, friend, pseudo-op
and partner. However, only the first two characters are significant, which are for
level 1 "ge", level 2 "fr", level 3 "ps" or "op" and level 4 "pa" (not case sensitive)
Eg: @add DataFox 4
    @add DataFox pa
    @add Anybody Pseudo-Op

@block <nick>
(msg or chan; boss level)
A blocked user is allowed to be on your channels, but he/she doesn't have any access to
the bot's commands. This is pretty similar to the @ignore command, but since the @ignore
command totally ignores the user, he/she can get ops in your channels!
Eg: @block OtherLame

@shit <nick>
(msg or chan; boss level)
Adds the user <nick> to the shitlist/banlist. A shitlisted user is not allowed to be on
one of your channels, so if he/she joins a channel, he/she will automatically kicked and
temporarily banned (for 2 minutes). Additionally, after typing the @shit command, the bot
will do an initial check of all channels the bot is on and will kick/ban the just shit-
listed user.
Eg: @shit LameGuy

@remove <nick>
(msg or chan; boss level)
This removes a user from the user list. This means he/she gets resetted to level 1. This
will also remove existing blocks/shits on this user.
Eg: @remove ResetNick

@ignore <nick>
(msg or chan; boss level)
This will add a user's address to the internal mIRC ignore list. This will result in a
complete ignore of this user. Since this is a very powerful command I decided to remove
a ignore automatically after 2 minutes. Use this command ONLY if someone keeps flooding
you and the flood control does not trigger. Since mIRC 4.52 does not reply to unknown
CTCP messages any more, and I've added a CTCP flood control, you won't need this very
often. Please mail me with a description of the flood method if my control doesn't trigger.
Eg: @ignore FloodGuy

@nick <nick>
(msg or chan; boss level)
Lets you choose a new nickname for the bot. It will immediately change its nickname to
the specified value.
Eg: @nick NewBot

@rn
(msg or chan; boss level)
"rn" is the short form of "randomnick", so the bot will choose a completely random nick.
It's 4-9 characters long, consisting of upper case letter (A-Z), lower case letters (a-z)
and numbers (0-9). You can return to the previous nickname with the @oldnick command.
Have fun! ;)

@oldnick
(msg or chan; boss level)
After choosing a random nick, you can re-choose the previous nickname. Works even after
multiple @rn commands, but will not work after disconnecting and reconnecting.

@welcome on/off
(msg or chan; boss level)
Enables or disables the Welcome message for channels your bot is op in (what a sentence!).
Any changes will be saved into the datacfg.ini file. Note: This applies only to level-1
users!

@welcomeall on/off
(msg or chan; boss level)
Enables or disables the Welcome message for all channels your bot on. If it's on, the
setting of welcome is irrelevant. Any changes will be saved into the datacfg.ini file.
Note: This applies only to level-1-users!

@talk [<chan> [<chan> [<chan> ...]]]
(msg or chan (dependent); boss level)
Sends the text "<nick> is a DataBot II. Type @help to get a list of your commands" to
one or more channels. Nothing special.
Eg: @talk
    @talk #datafox #mirc

@offerdir <dir>
(msg or chan; boss level)
Changes the home directory of the file server. It must be a complete and "absolute" path,
like "c:\offer" (This is for security reasons). This value will not automatically saved
to datacfg.ini.
Eg: @offerdir c:\internet\mirc\offer

@commchar <char/text>
(msg or chan; boss level)
Changes the command character. It can also be more than one character, but it may not
conatain any spaces! After using this command, the bot will set the command variables again;
this may take some time. The change of the command character will be reported to all channels
the bot's currently in. The new value will also be saved into datacfg.ini. The whole thing is
of course not case sensitive.
Instead of the normal "Eg:" thingie, here's an example of consecutive use of this command,
prsuming the command character is now "@":
@commchar !
!commchar CMD~
cmd~commchar comm
commcommchar @
(Now it's the same as before)

@newnick
(msg or chan; boss level)
This is required if the bot doesn't recognize your nickname change. This will only happen
if you change your nickname while not being on one of your bot's channels. The reason for
this command is that the bot has to know your nickname, because it logs everything to you.
So, type @newnick if you don't get any messages from your bot.

@status
(msg or chan; boss level)
Sends you the current status of the switches and variables. Note that with proper usage
you won't ever get the message "Login is enabled". If you do, please mail me about the
problem :)

@die [<msg>]
(msg or chan; boss level)
The bot will quit IRC, optionally with the specified quit message.
Eg: @die
    @die See ya!

@exit [<msg>]
(msg or chan; boss level)
The bot will quit IRC and mIRC, optionally with the specified quit message.
Eg: @exit
    @exit See ya!

@password <newpass>
(msg; boss level)
Changes immediately the value of the bot's password. It also saves it to the datacfg.ini
file. For a description of the password function read the description of the @login command
and/or the introduction in datacfg.ini.
Eg: @password login

@massop [<chan> [<chan> [<chan> ...]]]
(msg or chan (dependent); boss level)
Performs a massop on a channel, which means that the bot will op all current non-ops.
Please note that this will op everybody, including level-1 users and maybe shitlisted (but
I think the bot will trigger on opping shitlisted people... try it ;)  )
Eg: @massop
    @massop #mirc #friendly

@massdop [<chan> [<chan> [<chan> ...]]]
(msg or chan (dependent); boss level)
Performs a mass-de-op on a channel. Read the description of @massop.

@takeover [<chan> [<chan> [<chan> ...]]]
(msg or chan (dependent); boss level)
This performs a typical channel takeover. This means that the bot first does a mass-deop,
which deops everybody except its boss (you) and itself, then sets the topic to the one
specified in datacfg.ini, sets the modes of the channel as in datacfg.ini and finally
leaves the channel, leaving you as the only op. This requires the bot to be op on the
channel. The bot does not check at all if you are (op) in the channel. This command
is not well tested, but it should work. Mail me with a descriptions of the circumstances
if any problems occour. Be careful with the multi-channel option, you could risk a flood
excess!
Eg: @takeover
    @takeover #mirc #lamechannel

@banad [<chan> [<chan> [<chan> ...]]] <address> [<address> [<address> ...]]
(msg or chan (dependent); boss level)
Bans an address from a channel. This is similar to doing /mode <chan> +b <address>. This
won't do a temporary ban. When using the multi-ban feature, the bot will always ban 4
addresses at one time (ie the command would be "/mode #chan +bbbb *!*@add1 *!*@address2 ..."
Eg: @banad *!*@*.lame.host.com
    @banad #mirc #friendly #datafox *!*adolf*@* *!*hitler*@* *!*nazi*@*

@flood <nick>
(msg or chan; boss level)
Does a CTCP VERSION flood on somebody. You may want to combine this with a chat-mIRC-side
CTCP flood as described in HINTS.TXT. For further information read the text in DATACFG.INI.
Eg: @flood LameGuy

@remote <chan>/off
(chan; boss level)
This enables or disables the so-called remote control of a channel. This requires an "owned"
channel, ie a channel the bot is op in. In this channel, you can use the @remote command.
The bot must already be in the specified channel. After using the command the bot will
change the topic and modes of the receiving channel (the channel you used the command in).
Now, the bot will send all messages from the specified channel to the receiving channel.
By giving the bot a "human" nickname, you can allow multiple people to listen to a
conversation in an other channel without being in that channel. The people in the
observed channel won't notice anything. Everyone in the receiving channel can send messages
to the observed channel by prefixing a line with "!". The same can be done for actions,
the prefix is "<". If you set your command character to one of these, you won't be able to
use any commands in the receiving channel, except for "@remote off"
Eg: @remote #friendly
Eg for sending a message: !Hi folks!            Will result in eg:    <DataBot> Hi folks!
Eg for sending an action: <is laughing          Will result in eg:    * DataBot is laughing

@chans
(msg or chan; boss level)
Counts and lists the channels the bot is currently in.

@reread
(msg or chan; boss level)
Re-reads all values from datacfg.ini. You don't need to login again after using it.

@stop
(msg or chan; boss level)
Stops any running flooding/bothering. Also resets the nickname.



  Contact info / Credits
------------------------

If you find bugs, have suggestions for new commands or just have a question, mail me at:
  datafox@gewi.kfunigraz.ac.at


Programmer: DataFox       (datafox@gewi.kfunigraz.ac.at)
Administrator: SpellBin

Bug finders: DataFox
             SpellBin

Suggestions: Edgester
