		Galactic Bloodshed 2.0

   Galactic Bloodshed 1.3.1 was the first version of the game where
the networking is taken advantage of. I would like to thank the
people at CMU (see TinyMUD_copyright.h) for providing such an efficient
interface. I tried to exploit this to the fullest for this version.

   The code is divided into two parts, GB_server
and GB_client. Most of the user playing the game will
just need the client, since the server is run at the game site and
managed by the host there. Game documentation is in the subdirectory
Docs.

   If you wish to host a GB game, you must have GB_server, GB_docs
and GB_client. After unsharing all the files, you can compile and
link them by doing 'make' from the top level directory.
The Makefile is set up for 4.3 BSD Unix, if you are running
on a different operating system, you may need to change the Makefile
to suit your system. You should also check and perhaps edit the
files server/config.h and server/files.h.

   Assuming all goes well, you should have several programs in the
server's directory, and one program in the client's directory (GB_client).
In the server's directory:
	GB_daemon
	GB_enroll
	GB_server
	makeuniv

'GB_daemon' is the program which wakes up every few hours and send the
update password (specified by DAEMON_PASSWORD) to the client which
then tells the server to do an update. The default update time is 4 hours, 
but you can change that with 'GB_daemon <hours between updates>'. It is a 
good idea to make your update times a factor of 24 hours. If you want to
force an update just do 'GB_doturn' by itself.

Players cannot enroll by themselves in this version. The game's host
must do that by running 'GB_enroll' and following the instructions. It
is a good idea to bring the game down for this (log in as a God status
player and do '@@shutdown'). Always make player #1 (the first one
enrolled God status, as many game functions default to player 1).

Before starting a game you must create a universe for your users to play in.
Do 'makeuniv' and follow the instructions.

Once you are set up you can start the program with 'GB_server <port>'. You
must specify the port that you are going allow communications. Choose the 
number '2010' since the client looks it up by default.

Also, be careful about setting up your default paths correctly. Edit the
files "files.h" and Makefile.

Good luck,

Garrett Warren van Cleef
vancleef@pooh.caltech.edu
4/11/90


I made some changes to the server code so that it would compile and
execute on a 4.2bsd Unix (Sun OS 3.5). I also added #ifdef's where
necessary for non-ANSI C compilers and cleaned up the Makefiles,
including adding defines for host and port via the Makefile and
the creation of a top level Makefile to compile the client and
server.

Because of these changes this posting no longer matches the source
available via ftp (scam.Berkeley.EDU), I am setting the PATCHLEVEL
at 1.

Bill Randle
billr@saab.CNA.TEK.COM
6/1/90
