Find a file
2006-01-15 18:02:01 +00:00
doc C_EXECUTE security. 2005-10-30 15:03:02 +00:00
include (EF_COUNTRY, cou_ca): New. 2006-01-14 16:28:33 +00:00
info The code to fail when new subject's file exists failed always. Fix. 2006-01-15 08:05:13 +00:00
m4 Replace the build process. The new one requires GNU Make, Autoconf 2005-12-20 20:25:35 +00:00
man Client UTF-8 support. 2005-05-27 17:00:25 +00:00
scripts Spelling fix. 2005-10-11 19:23:11 +00:00
src Remove useless width from printf conversion %c. 2006-01-14 20:06:29 +00:00
.cvsignore (info, html): Implement. 2005-12-22 10:09:17 +00:00
bootstrap Provide and document means to set up a fresh source tree from CVS. 2005-12-21 09:19:33 +00:00
compile Replace the build process. The new one requires GNU Make, Autoconf 2005-12-20 20:25:35 +00:00
config.guess Replace the build process. The new one requires GNU Make, Autoconf 2005-12-20 20:25:35 +00:00
config.sub Replace the build process. The new one requires GNU Make, Autoconf 2005-12-20 20:25:35 +00:00
configure.ac Update copyright notice. 2006-01-05 13:36:57 +00:00
COPYING Import of Empire 4.2.12 2003-08-23 12:23:04 +00:00
CREDITS Import of Empire 4.2.12 2003-08-23 12:23:04 +00:00
depcomp Replace the build process. The new one requires GNU Make, Autoconf 2005-12-20 20:25:35 +00:00
GNUmakefile.in Update copyright notice. 2006-01-05 13:36:57 +00:00
INSTALL Replace the build process. The new one requires GNU Make, Autoconf 2005-12-20 20:25:35 +00:00
install-sh Replace the build process. The new one requires GNU Make, Autoconf 2005-12-20 20:25:35 +00:00
LEGAL Update copyright notice. 2006-01-05 13:36:57 +00:00
LICENSE Import of Empire 4.2.12 2003-08-23 12:23:04 +00:00
Make.mk (distclean): Clean up another rev. 1.11 leftover. 2006-01-15 18:02:01 +00:00
README Provide and document means to set up a fresh source tree from CVS. 2005-12-21 09:19:33 +00:00

Welcome to Empire 4, codenamed Wolfpack.  Congratulations on your choice!

See the "LEGAL", "LICENSE", "CREDITS" and "README" files for all the
related information and legal notices. It is expected that any future
projects/authors will amend these files as needed.

For questions and comments, please contact "wolfpack@wolfpackempire.com".

If you want to build the server, follow the few simple steps below.  If
you are looking for more information on the files here, options for
the server, etc. take a look in the "doc" directory, then follow the steps
below to build and start the server.

(1) Unpacking the server
  If you're building from a tarball, unpack it.
  If you're building from CVS, check out and run bootstrap.  This
  requires Autoconf and Automake to be installed.

(2) Building a server
  Note that you may not have to build a server.  If you received the
  server in binary format, go to the next step, "Creating the world."

  To build the server, you need to do the following steps:
FIXME needs work

  1) Get a copy of the source.  Since you're reading this, we assume
     you have done that. 
  2) Gunzip the source.  Again, since you're reading this . . . ;-)
  3) Run configure.
  4) Run make.  You need GNU make.

(3) Creating the world
  (NOTE: If you received a binary, you must edit the included data/econfig
   file to represent the paths where your data and info directories are.)
  1) First, pick the world size you want to use.  Once you have chosen
     a world size, edit the "data/econfig" file (it was either created
     at build time, or shipped with the binary) and change the WORLD_X
     and WORLD_Y to be the sizes you want. The default world size is 64x32.
     IMPORTANT: WORLD_X *MUST* be divisible by 2.  In addition, if you
     change the world size later, you *MUST* re-create the world by
     running "bin/files" again.
  2) Go into the "bin" directory, and run "./files".
  3) If you want to create a new world, run "./fairland 10 30" to create
     a sample world (read the documentation for fairland for more info on
     it's arguments.)
  Note that "files" and "fairland" use the world size in the econfig file
  if it exists in the data directory.  If this file doesn't exist, and you
  don't specify one, it will use the default world size the server was
  compiled with (Wolfpack binaries ship with a 64x32 world size)  You can
  create an econfig file with default values using the "bin/pconfig"
  executable.

(4) Running the server
  1) Run the bin/emp_server executable to start the server.

That's it.  Once running, you can log on to the server using the emp_client
program found in the "bin" directory.  The initial deity country name/password
is POGO/peter.

If you get a "You're not a deity!" message and logged off, check the
"data/server.log" file and look at the end for a "NON-AUTH" entry.
There should be a "user@host" message in there that failed to log in.
Enter this user and host in the auth file, and you should be able to
log into the server as a deity now.

For more information on options, programs, files and other general hints
look in the "doc" directory.  The README there describes the files there and
what they talk about.

For more information or help, send e-mail to "wolfpack@wolfpackempire.com" and
we'll try to answer if we can.  Also check out our web site at
"http://www.wolfpackempire.com"

Have fun!

 -- The Wolfpack development team...