File: README  (for rand_mon)
Version: 1.0
Author: John Lame (lame@clark.net, john.lame@gsc.gte.com)

rand_mon is a perl program designed to randomize
the properties of the monsters of Angband and
it's variants.  There are numerous configuration
parameters to enable you to control the degree
and type of randomization you desire.  These are
located in rand_mon.cfg and fairly well documented.

DISCLAIMER---------------------------------DISCLAIMER
I have made every effort to ensure that r_info
files created by this program will not cause Angband
to crash but I have not (for obvious reasons) tested
every possible type of monster that could be created
and therefore cannot make any guarantees regarding
the stability of the game or of your savefiles if you
choose to use this software.
------------------END OF DISCLAIMER------------------

rand_mon.tar contains 4 files.
rand_mon.pl (subroutines)
rand_mon.cfg (configuration parameters)
rand_mon (the main program)
README (this file)

To install rand_mon, simply extract the files to
<your angband or angband variant directory>/lib/edit.
On unix (and perhaps other) systems you may need
to edit the first line of rand_mon.pl, rand_mon.cfg,
and rand_mon to reflect the location of perl on
your system. 

rand_mon is a perl program and, as such, requires that 
perl be installed on your system.  I use perl5 but
I don't do anything fancy so I imagine that earlier
versions of perl will suffice.  If you don't have
perl, I would strongly encourage you to go directly
to www.perl.com and get the latest version because
Perl is really cool!

rand_mon takes no command line parameters.  It reads
the "r_info.txt" file in the current directory and
creates an "r_info.new" file with which you may then
overwrite the existing r_info.txt file.  If your
operating system is case-sensitive and if "r_info.txt"
is not the name of your monster file, you will need
to modify the value of $r_old in rand_mon.cfg.  In
any case, PLEASE MAKE A BACKUP COPY OF YOUR r_info.txt
FILE BEFORE USING THIS SOFTWARE.

Regarding use of this code.  Feel free to use and/or
modify any or all of it.  If you have comments or
criticisms on the coding style, the design, the
logic, the preset values of the configuration parameters,
or anything else at all, I'm happy to listen and discuss.

John Lame (lame@clark.net, john.lame@gsc.gte.com)
