/*********************************************************************
  Title: emp_mux
  Author: Alan M. Levi (levi@cs.psu.edu)
  Last date of modification: March 10, 1993
*********************************************************************/
   
List of files:
	README (this file)
	main.c client.c (source files)
	main.h client.h (header files)
	GNUmakefile (makefile)

	emp_mux is a tool for use with Empire which multiplexes
client connections through a single player.  This allows multiple
clients to give commands to the empire server.

	Before using this client, make sure that the deity running
the empire server knows that you're using it.

	emp_mux has been tested on SUN sparcstations.  It is compatible
with xemp version 4.11.

Disclaimer/copyright:
	This program comes with no warranty.  Use at your own risk.
This program is for personal use only.  It's not for sale or resale.
It may be modified and distributed as long as this file remains intact.

Installation:
	1. You will need gmake (gnumake) and gcc.
	2. Edit main.c and change the default port number to something
	   else.  This is for your protection.
	3. type "gmake depend"
	4. type "gmake emp_mux".
	5. An executable called "emp_mux" is created.

Usage:
	1. Run emp_mux.  This connects to the empire server.  You will need
	   to keep emp_mux connected to your tty.  i.e. don't put a "&"
	   after the command.
	2. Make sure that your client is compatible with emp_mux.  You need
	   to tell the client that it is connecting to emp_mux and not directly
	   to the server.  xemp 4.11 uses the -9 option for this.
	3. Connect to emp_mux with your client.  You will need to know
	   its listen port.
	4. Enjoy your game!

Features:
	1. emp_mux will automatically reconnect to the server if you
	   go below 0 BTUs.  However, it will do so no more than once
	   every 30 commands given.
	2. You can manually reconnect by typing an "r" followed by
	   <return>.
	3. Clients may connect and disconnect at will.
	4. To quit, type "q" followed by <return>.

Bugs:
	1. To restart a multiplexer, a change of the listen port
	   may be required.

	2. The multiplexer is not secure.  Country name and password are
	   not checked by the multiplexer.  Be careful who you give
	   the port number to.

	3. Players have prioritized access to the empire server based
	   on the order in which they have connected.  This probably
	   will not be a problem for human player connections.  However,
	   robot connections experience/cause problems because of this.

To do:

emp_client has been modified to be compatible, but still needs work.  Scripts
	give it trouble.  Single-line commands are usually ok.

