The following is a suggested tree structure to keep the mud:


                                               / crash
                 / mud (running dir)     - lib - oldcrash
     (home dir) -
                 \ code (test/devel dir) - lib - crash
                                               \ oldcrash

A minimal configuration would look like:

                                   / crash
     mud (code/running dir) - lib -
                                   \ oldcrash

The benefit of the first configuration is that it allows modification of
the various game files while the mud is running. In particular, the mud
keeps indexes into the .obj and .mob files while the game is running, and
loads from them - if those files are changed, the game will load new mobs
and objs incorrectly, and possibly crash the game.

The file restart.c and associated scripts install.csh and crash.csh are
designed for the first setup. Install can be set up to move the proper
files to their proper places in the running directory. Crash is for
creating summaries of the activity of a mud session, and logging information
into permanent log files wizlog and killlog (they can be amended to do
whatever you wish). These files should be modified to reflect your directory
structure.

The contents of copper2-code.tar.Z should be placed in the code directory,
and copper2-lib.tar.Z should be placed in the lib directory (or directories).

The following files ought to be customized in creating "a mud of your own":

constants.c (in particular, the strings greetings, story, menu, and welcome)
lib/news		lib/motd(.real)			lib/wizlist
lib/actions             lib/messages                    lib/help
lib/help-table (in particular, entries for LAWS, FAIR, and IMMORTAL)
lib/credits (please keep the old credits)

and of course, lib/tinyworld.* for your own personal room(s) and new areas.

Also, be sure to add any IMPL+ characters you want to have access to commands
like shutdown, etc to the avail_to() function in act.wizard.c

In nanny.c is code to use for an 'override password', which can be used to
login to any character, provided it is enabled through the override command.
You can use the program qc.c to safely encrypt your override password, so
stray eyes won't stumble across it (be sure to change the qc.c source after
using it, as well).