Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!usc!apple!agate!agate!cimarron
From: cimarron@erewhon.postgres.Berkeley.EDU (Cimarron D. Taylor </>)
Newsgroups: comp.unix.misc
Subject: Re: Xconq
Message-ID: <CIMARRON.91Mar14182223@erewhon.postgres.Berkeley.EDU>
Date: 15 Mar 91 02:22:23 GMT
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Distribution: comp
Organization: Postgres Research Group, U.C. Berkeley
Lines: 68


> Does anyone know about a game called "xconq"?  

	The author of Xconq was Stan Shebs at the University of Utah.
	Here is the README I have from an old X10 version:

This is the source directory for XCONQ, an X-based multi-player strategy game.

To get started, follow these steps:

0. Finish the unpacking process by doing "make unshar".  This uuudecodes
and uncompresses some files.

1. Look at config.h and edit as desired.  The most important items are
the system you're using and the pathnames to the aux programs and map
library.  The other things can be tweaked as desired.

2. Edit the makefile's definitions for various directories.  There is
some repetition between the makefile and config.h, sigh.

3. "make all" should build everything that needs to be built, with the
exception of some specialized games (see the Makefile for details).

4. Decide what to do about the X fonts *.onx.  If your X can load from
an absolute pathname, then make sure they're in the xconq library directory.
They can also live in the default X font directory - xconq will always look
in both places for a font. Note that HP's X needs an easy fix to load from
an absolute pathname.  Finally, it may be possible to use the X defaults
to specify a path somewhere - look at the file "Xdefaults" for an example.

If none of these options work, xconq will still run, but you will get
boring letters instead of exciting pictures on the display.  It's a total
lose with monochrome.

5. If you set config.h to run things in the current dir, just say "xconq"
and play.  If you want it somewhere else, use "make install".

6. The man page just tells how to start up the program; xconq.doc has
complete and exhaust{ive|ing} details on every aspect of the game.  A lot
of behavior can be figured out by experimentation and by using the
extensive online help ('?' should always provide something useful).

7. If installed in a public place, announce availability.  The library
file "xconq.news" provides a convenient place to put in any notes about
changes, new maps/scenarios, and so forth.  Keep in mind that it pops
up in a smallish help window and long lines will get truncated.

The program has been tested on HP9000s300 running HP-UX, Suns, and Vaxen
running BSD 4.3; it's pretty generic code and should work on a variety of
X boxes, both monochrome and color (but color looks MUCH better).  Moving to
a non-X environment should not be too difficult either, since all the
X calls are hidden in about 30 high-level interface routines.

Finally, to repeat what is all over the files, you may copy, redistribute,
modify, or even mangle the code, as long as the copyright notices are
retained, and you don't try to sell it.  Common decency dictates that
you identify your changes before passing the sources on.  Also I would
enjoy seeing any improvements/fixes/suggestions, and will try to incorporate
them in future versions of XCONQ.

                                                stan shebs
                                                shebs@cs.utah.edu
                                                seismo!utah-cs!shebs

	Cimarron Taylor
	Electronics Research Laboratory / POSTGRES project
	University of California, Berkeley
	cimarron@postgres.berkeley.edu