*** General info and waffle ***

The mud consists of the following parts:

defs.h     - macros
globals.h  - global var declaration
externs.h  - global var extern declrations
main.c     - main server code
main2.c    - additions to main server
objects.c  - main creation calling code for objects
rooms.c    - contains room structure set up
regions.c  - contains region structure setup and region functions
skills.c   - contains skill functions
motd1      - 1st message of the day (pre login)
motd2      - 2nd message of the day (post login)
items/     - directory containing item object code
npcs/      - directory containing npc object code
world/     - directory containing startup mudlib room code
userdata/  - directory containing user data files
helpfiles/ - directory containing the help files
DOCS/      - directory containing this documentation

All object , room and region control code is written in C and is compiled in
with the rest of the source to produce a single binary executable. There is no
database (apart from the saved user stats) with this mud system , it is all
hard coded. This has advantages and disadvatages....

Advantages:
  - Very fast execution.
  - No thrashing of hard drive while mud continually reads database.
  - Can program mud in standard C , don't have to learn some esoteric mud
    programming language.
  - Main server simple compared to other systems, hence less bug prone.
  - No worries about database corruption.

Disadvantages:
  - As is common with C, one small bug can crash the whole program.
  - Need to recompile for each code change made.
  - Can't alter any code on the fly and test it while the mud is still
    running.

I'm sure there are a few others for both categories but those are the main
ones. Its a case of which suits your needs best.
