Wolfpack Empire - mirror of https://git.pond.sub.org/empserver
http://wolfpackempire.com/
Markus Armbruster
68f7c0ceda
Change struct range from exclusive to inclusive upper bounds, for consistency with struct realmstr and the area syntax. Also fix many bugs. real()'s conversion from struct range's exclusive upper bounds to struct realmstr's inclusive upper bounds could underflow and store -1 in the realms file. Harmless, because its users didn't mind: list_realm() and nstr_exec_val() convert back to relative coordinates, and sarg_getrange() is only used by sarg_area(), which happened to undo the damage. The change to inclusive upper bounds gets rid of the broken conversion. xyinrange() incorrectly treated the upper bound as inclusive, unless the bounds were equal. Impact: * nxtitem() and nxtitemp() cases NS_AREA and NS_DIST attempted to hack around xyinrange()'s lossage(!), but screwed up: sectors on the lower bound of of a range spanning the the whole world were skipped. This affected all command arguments that support area or distance syntax for items. In sufficiently small worlds, it could also make radar miss satellites and ships, sonar miss ships, satellite miss ships and land units, nuclear detonations miss ships, planes, land units and nukes, automatic supply miss ship and land unit supply sources, ships and land units fail to return fire, ships fail to fire support. * draw_map() could draw units sitting just right or just below of the mapped area. No effect, as these parts of the map weren't actually shown. xydist_range() produced an inclusive upper bound when it decided that the range covers everything in that dimension (which it didn't get quite right either). This could make snxtsct_dist() and snxtitem_dist() initialize the iterator with an incorrect upper bound. Similar impact as the xyinrange() / nxtitem() lossage. border() could print the hundreds line unnecessarily. snxtsct() and snxtsct_all() screwed up for odd WORLD_Y: they failed to include (WORLD_Y - 1) / 2 in the y-range. This affected all command arguments that support "*" syntax for sectors, plus add ... c, power n, and break. snxtsct_all() failed to normalize the bounds (presumed harmless). There were a few correct, but somewhat unclean uses of struct range with inclusive upper bounds: * nat_reset() used one internally. * pathrange() worked with inclusive upper bounds internally, but corrected to exclusive upper bounds before passing the range out. * sarg_getrange() worked with inclusive upper bounds. Its only caller sarg_area() corrected that to exclusive upper bounds. The change to inclusive upper bounds cleans this up. unit_map() and xysize_range() had no issues (isn't that amazing?), but need to be updated for the changed struct range semantics. |
||
|---|---|---|
| doc | ||
| include | ||
| info | ||
| m4 | ||
| man | ||
| scripts | ||
| src | ||
| .gitignore | ||
| bootstrap | ||
| compile | ||
| config.guess | ||
| config.sub | ||
| configure.ac | ||
| COPYING | ||
| CREDITS | ||
| depcomp | ||
| GNUmakefile.in | ||
| INSTALL | ||
| install-sh | ||
| Make.mk | ||
| README | ||
Welcome to Empire 4, code-named Wolfpack.
Empire is a multi-player, client/server Internet based war game.
Copyright (C) 1986-2008, Dave Pare, Jeff Bailey, Thomas Ruschak, Ken
Stevens, Steve McClure
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License (in file
`COPYING'), or (at your option) any later version.
See file `CREDITS' for a list of contributors.
Directory `doc' has additional information. File `doc/README'
describes the files there and what they talk about.
To build the server and set up a game, follow the steps below.
(1) Unpacking the source tree
If you downloaded a tarball, unpack it.
If you cloned a git repository, run bootstrap. This requires
recent versions of Autoconf and Automake to be installed.
(2) Building a server
Prerequisites: IEEE Std 1003.1-2001 (POSIX.1-2001), GNU make, a
curses library, Perl, and either nroff or GNU troff (`groff').
See file `INSTALL' for detailed compilation and installation
instructions. Quick guide for the impatient: run configure; make;
make install. The last step is optional; everything runs fine
right from the build tree.
If make fails without doing anything, you're probably not using
GNU make. Some systems have it installed as `gmake'.
Solaris supports POSIX.1-2001, but you need to set up your
environment for that. Try passing
SHELL=/usr/xpg4/bin/sh PATH=/usr/xpg6/bin:/usr/xpg4/bin:$PATH
to make. See standards(5) for details.
(3) Creating a game
* Create a configuration for your game. make install installs one
in $prefix/etc/empire/econfig ($prefix is /usr/local unless you
chose something else with configure). You can use pconfig to
create another one.
* Edit your configuration file. See doc/econfig for more
information.
Unless you put your configuration file in the default location
(where make install installs it), you have to use -e with all
programs to make them use your configuration.
* Run files to set up your data directory.
* Run fairland to create a world. For a sample world, try
`fairland 10 30'. This creates file ./newcap_script, which will
be used below. You can edit it to change country names and
passwords.
Check out fairland's manual page for more information.
* Start the server. For development, you want to run it with -d
in a debugger, see doc/debugging. Do not use -d for a real
game!
* Log in as deity POGO with password peter. This guide assumes
you use the included client `empire', but other clients should
work as well.
For help, try `info'.
To change the deity password, use `change re <password>'.
* Create countries with `exec newcap_script'.
Your game is now up!
Naturally, there's more to running a real game than that, but that's
beyond the scope of this file.
Please report bugs to <wolfpack@wolfpackempire.com> or via SourceForge
http://sourceforge.net/projects/empserver (registration required).
For more information or help, try rec.games.empire on Usenet, or 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!
Wolfpack!