rb.bx README:

COPYING:

Again, Copyright (c) 1999 Jeff Frasca <ph43drus@home.com>, this software is covered by the GPL, it is also under no warranty what so ever, if you some how manage to destroy your machine with this script, don't expect me to do anything about it.  Feel free to email me with what happened though.  I like getting shocked and amazed every now and then.


This script is designed to be used as a bot.  The commands don't work from the client running the script.  The way I use it is to have the script in the ~/.ircrc or ~/.bitchxrc file and then use cron to start the client in the unix background (I use it on a weekly basis), or you can start the bot in the background.  This is primarily an example of the use of roll.

Here are the basic features:

!roll <dice>  # this runs roll, and then displays it in the channel
!nroll -<number> <dice> # this runs roll <number> number of times and rolls 
		the <dice> specified each time.
!log <logfile> # Starts logging.  Logfile can use tilde expansion.
		NOTE: this will NOT pick up anything that you say.
!nlog         # Stops logging
!quit         # tells the script to kill your client.  This is disabled 
		by default.  If you want to use it, just edit rb.bx and 
		uncomment it.  
There is another disabled feature in the script.  It is the ability to simply invite the bot into a channel and have it join.  This is also marked, all that is needed is for it to be uncommented.

Oh yeah, there is one other undocumented feature.  Find it and figure out what it does on your own.  If you are wondering why it is undocumented, just email me.  (if you are a member of my gaming troop, you know what I'm talking about, and why I put it in there... besides you can ask me at game).

BUGS

There is only one major bug in this script that I have a problem with.  This script runs as a frontend for roll, that is why it was created, all the other stuff is just extra.  Basically, when I was figuring out BX scripting to write this thing, I couldn't find anything that would pick up the return value of an application.  So instead of implementing quiet mode as I orginally had intended, I had that do the grunt work for the output.  So, if you want to change what gets messaged to the channel, you have to go find it in roll, and change it there.  This script does not control the output (I consider this a bug, because I would rather do it in here).

If the bot gets invited to more than one channel, it only pays attention to its current channel.  I've been procrastinating on fixing this.
