Readme for chefbot, $Id: README.chefbot 2 2004-11-29 00:47:38Z alan $

It's easiest if the files are arranged (whatever you like for yourbots)

/.../yourbots/
    chefbot.pl
    items.pl
    recipes.pl
    KoLBot.pm
    KoLBot/
        All the stuff in KoLBot
    state/
	Empty

Under GNU/Linux, edit chefbot.pl, items.pl, recipes.pl: line 1 to
point to your perl interpreter.  In Windows, you will have to use 
'perl xxxx.pl' for all the commands below instead.

The files "items.txt" and "recipes.txt" are needed, but not included
because I consider any content that would be in them to be
Jick's/Asymmetric's IP and not mine to distribute.

items.txt: 
Go to the mall in the kingdom, and look for a store title "Items in
the Kingdom".  Save the source of that frame as 'items.html.'

Run (linux)

items.pl items.html > items.txt

In windows/dos, I think this will work

perl items.pl items1.html > items.txt

recipes.txt: 
go to http://www.agesoftime.com/kol/kol_list_mix.php and save the page
as 'recipes.html'.  Then run

recipes.pl recipes.html > recipes.txt

This should now ignore any recipes that call for items that aren't in
the items database, making the rest of this paragraph obsolete.  This
will die from time to time, as item.txt won't be complete (no store
has pickles right now) and you'll have to patch you list by hand. I
use description numbers of 1,2,3... and item numbers of 9901, 9902,
..., for items that I don't know the real numbers of.  If the bots
ever come across them, they'll throw exceptions, but I haven't had
time for an exhastive search, and I don't think this info
(particularly the description numbers) are available on the web.  If
you find better stores/web sites for this, please let me know.  Also
be aware that ice-cold-beer causes a problem.  You'll have to add
"(Willer)" to you items.txt file or delete it from
"kol_list_mix.php.html" and then patch the recipes.  I don't remember
exactly how to do this.

Edit chefbot.pl: 
Some distance down there is configuration.  Only worry about $config
for the time being.  Enter the name of the character you will be
testing with for "chefbot" and their password.  WARNING: at this point
you should read all the source to be sure your password isn't mailed
to me, or whatever.  If you're paranoid, it might be easier to strip
the character first, and figure you can get Jick to change the
password if I do steal the character.  Don't worry about the other
config section for the time being, it is for a second sauceror character.

run chefbot.pl.  I got the logging fixed! Now, you can specify a log
file in the configuration, and both standard output and error will go
there in addition to the terminal, if defined.

chefbot.pl

If all that worked, test it out with another character sending things
and messages to your bot, then mess with the code.  If not, you know
where to reach me.

