This document explains how to set up an Outgun server.
This document applies to Outgun 1.0. There are some minor differences to older versions.
An Outgun server uses about 1.5 kB/s of bandwidth for each player. The exact amount depends on what the players do, and is slightly increased by larger numbers of players. For a LAN server, the network connection is not a problem. For an internet server, you should have at least an ADSL connection. A dial-up is out of the question because the lag becomes significally big. A heavy use of the connection affects the server and increases lag.
For a temporary use, you can start a server in the Outgun client, in the Local server menu. When you close the client, the server stops too. The client uses some extra processor time and memory compared to just the server, so that is not very useful for a long time server.
If you are planning to keep the server on many hours a day or even all the time, you should make it a dedicated server. The simplest ways to start the server in command line are, depending the operating system:
|in Linux with X||./outgun -ded|
|in Linux without X||./outgun-ded|
|in Windows||outgun -ded|
Find more about the command line server options in a separate document.
The Windows version of Outgun has
Dedicated server.bat file that starts a dedicated server.
The default server settings in the gamemod file usually need some customising. You should at least set a new name of the server because ‘Anonymous host’ is not too informative. A good practice is to include the name of the country where the server is located. That helps the players to understand why the ping is what it is (some people seem to think their ping should be good in every server in the world though).
The server port is 25000 by default. Change that if you can’t use it, by the command line option
-port or in gamemod file.
Maximum number of players depends partly on your connection. If you have 512 kbits/s for upload, you can probably have a server of 16 players, and with 2 Mbits/s, 32 players.
You will need to open the chosen server port for all incoming UDP traffic in your firewall. Having NAT (network address translation, done by many ADSL routers too) makes things more complicated, and especially in that case you will want to see the Firewall setup guide for more detailed instructions.
There is a simple program to monitor the server, called srvmonit. It helps you to see what is happening on your server when you are not there.