These instructions assume a Unix system.  Modify them accordingly for the
type of system you're stuck with, if it isn't Unix.

0) Install the source code for Angband version 2.8.1.  This code has only
   been tested with that release; if you choose to try to use an older
   version of Angband, you're on your own.

1) Unpack the distribution archive.  You've probably already done this, but
   just in case, you should probably do something like this:

	cd /some/path/angband-281
	gzip -dc randart-0.1.tar.gz | tar xvf -

2) Note that the previous step overwrites src/Makefile, and places a file
   called randart.diff in the src directory.  Apply the randart.diff patch
   using something like this:

	cd /some/path/angband-281
	patch -p1 <src/randart.diff

   This makes modifications to init1.c and init2.c.

3) Edit src/Makefile and src/config.h as you normally would.  You should
   probably make sure you enable debugging (-g), and enable wizard mode
   (ALLOW_WIZARD).  That way, you'll be able to dig in and track down any
   strange behavior you may observe.  Pay attention to the setting of
   DEFAULT_PATH in config.h.

4) Build the randart program, and optionally the game itself.  You'll
   probably want to do something like this:

	cd /some/path/angband-281/src
	make randart
	make angband
	mv randart angband ..

5) Create a names file in lib/file/names.txt.  I've supplied a sample file
   in this distribution, which you may want to edit.  It's just a text file,
   with one name per line.  These are the names which will be randomly
   assigned to the random artifacts.

6) Run the randart program to generate a file called a_info.rnd.  This is the
   new, randomized artifact list in the format of a_info.txt.  Read through
   it to see whether you like the results.  Something like:

   	cd /some/path/angband-281
	./randart
	more a_info.rnd

   When invoked, randart will attempt to read the old a_info information from
   the files in the lib/data and/or lib/edit directories.  This uses the same
   routines that the regular Angband does.  Note that this will create
   lib/data/a_info.raw if it did not already exist.  However, the a_info.raw
   file generated by this process is NOT RANDOMIZED.  It's the same one that
   would have been produced if you'd run angband first, instead of randart.

7) If you want to use the random artifact file that was produced, copy it to
   lib/edit using something like this:

   	cd /some/path/angband-281
	cp lib/edit/a_info.txt lib/edit/a_info.bak
	cp a_info.rnd lib/edit/a_info.txt
	rm lib/data/a_info.raw

   If you want to use a different randomized file, either because you didn't
   like the first one or because you want one that you haven't already looked
   at, then just run randart again before you do the copy.

Note that overwriting the a_info.txt file will NOT cause problems for
the future use of randart!  The only fields of a_info.txt which are
important to the random artifact generation routines (level, rarity,
ACTIVATE, tval & sval on the "special" cases) are left intact by the
randomization algorithm.  When you run randart, it doesn't matter whether
it's reading the original a_info.txt or an a_info.txt that was produced
by the randomization routine.  You could even use an a_info.txt file
that was produced by John May's "artefact" program, since that program
also preserves all the essential information.