Single player games do not require a server (although you can still connect to one if you like) as a "virtual server" is run by the dopewars client.
The dopewars server can be heavily customised by means of the configuration files. For example, you can change the names of all the game locations so that the game is set in your home city rather than New York. Any players that then connect to your customised server will play this customised game.
Non-interactive servers
Usually, however, you will not need to use server commands (most can be
specified in the configuration files anyway)
and so will want a non-interactive server. This will sit in the background
and quietly deal with dopewars games without disturbing you, the user. To
"persuade" the server to be non-interactive, you must redirect standard
input and output, and use your shell's job control to put it in the background,
with a command similar to the following:-
dopewars -s < /dev/null >> /var/log/dopewars.log &
(this writes server output to the logfile /var/log/dopewars.log.
Alternatively you can redirect this output to /dev/null.)
Private and public: the dopewars metaserver
By default, whenever a server is started or stopped, whether interactive or
non-interactive, it reports its status to the dopewars
metaserver. The metaserver is actually just
a collection of CGI scripts which update a list of currently active servers
on the dopewars
webpage. This lets
people running clients see which servers are available for multiplayer games.
Whether your server connects to the metaserver can be configured with the
MetaServer.Active configuration
file setting, or the -s and -S
command line options.
N.B. Your machine may have trouble connecting with the metaserver in some circumstances, most notably if you are using an enforced proxy server or your DNS does not correctly resolve your IP address to your domain name. In such cases, you may be unable to connect to the metaserver, or it may register your server with an incorrect name. For information on getting round these difficulties, see the metaserver page.