Advanced Server Setup Guide

These directions are modifications to the directions that are posted at GameAdmins.com. This is a set of configuration files for the Castle Wolfenstein release that you can use to get your win32/linux server up with in no time.

Remember that this game is based on the Quake3 engine and so most of the standard Quake3 commands and variables work fine on it. For a description of the Quake3 variable meanings see Command from S4nDMod Variables list.

To create a batch file to get your server up and running quickly, go through these steps:

Step 1: Create a WolfMP.bat file

Go to your Return to Castle Wolfenstein Directory (default is C:\Program Files\Return to Castle Wolfenstein). Right Click in a blank space, then select New --> Text Document. Name it "WolfMP.bat".

Open the file up in your favorite text editor and past one of the following two command lines:

Command line for Windows servers:
wolfMP.exe +set dedicated 2 +set net_IP XXX.XXX.X.X +set net_port 27960 +set com_hunkMegs 64 +set com_zoneMegs 24 +set vm_game 0 +exec server.cfg

Command line for Linux servers:
./wolfded +set dedicated 2 +set net_IP XXX.XXX.X.X +set net_port 27960 +set fs_basepath ./ +set com_hunkMegs 64 +set com_zoneMegs 24 +set vm_game 0 +set ttycon 0 +exec server.cfg

Make sure to insert your server's I.P. address where the X's are. The standard port is 27960, but if you already have a q3 server on that port just use 27961.



Step 2: Create a default.cfg file

Create another text file in the /main directory inside the ReturnToCastleWolfenstein directory and name it "default.cfg". This document should actually remain empty. It's just there to prevent bogus fail messages.



Step 3: Create a server.cfg file

Create a document in your /main directory and call it "server.cfg". The server.cfg is the main startup config and calls all the other configuration files (except default.cfg - Wolfenstein calls those automatically).

Paste the following into the server.cfg file:

// Public Info
exec public.cfg

// Server Config
seta sv_pure 1
seta com_hunkMegs "96"
seta com_zoneMegs "32"

// General Settings
seta sv_maxclients "26"
seta sv_privateClients "2"
seta sv_fps "20"
seta g_friendlyFire "1"
seta g_warmup "20"
seta sv_zombietime "1"
seta g_inactivity "120"

// Voting
seta g_allowVote "0"
seta g_complaintlimit "3"
seta g_teamForceBalance "1"

// Extras
seta sv_maxPing "500"
seta sv_minPing "0"
seta sv_floodProtect "1"
seta sv_maxRate "7000"

// Server Passwords
seta rconpassword ":]"
seta sv_privatePassword ":["

// Game Type Settings
// Set the type of game: 5=Custom
seta g_gametype 5
seta timelimit "20"

// Start the Game Map
exec MapRotate.cfg

You can, of course, alter these settings.

Variable
maxclients
privateclients
fps
friendlyfire
warmup
zombietime

allowVote
complaintlimit
teamForceBalance

maxPing
minPing
floodProtect
maxrate

rconpassword
privatePassword
timelimit
Description
Maximum number of players that can connect
Number of private reserved slots
Set max frames/second the server sends the client
Friendly fire (0 = off; 1 = on)
Warmup time in seconds
# of minutes before inactive players are booted

Allow voting (0 = off; 1 = on)
Max # of playerkilling complaints before booting
Automatic evening of teamss

Maximum allowable ping
Minimum allowable ping
Toggles server flood protection
Sets the upper limit on rate for all players

Sets password for remote console control of the server
Sets password for private clients to login with
Time limit for each round

See S4nDMoD Variables list for a more complete list of variables that you can include in this .cfg file.

Step 4: Create a MapRotate.cfg file

Create a document in your /main directory and call it "MapRotate.cfg". Paste the following into it:

// Start the Game Map

set d1 "set g_gametype 5 ; map mp_depot; set nextmap vstr d1a"
set d1a "map_restart; set nextmap vstr d1b"
set d1b "map_restart; set nextmap vstr d1c"
set d1c "map_restart; set nextmap vstr d2"
set d2 "set g_gametype 5 ; map mp_assault ; set nextmap vstr d2a"
set d2a "map_restart; set nextmap vstr d2b"
set d2b "map_restart; set nextmap vstr d2c"
set d2c "map_restart; set nextmap vstr d3"
set d3 "set g_gametype 5 ; map mp_sub ; set nextmap vstr d3a"
set d3a "map_restart; set nextmap vstr d3b"
set d3b "map_restart; set nextmap vstr d3c"
set d3c "map_restart; set nextmap vstr d4"
set d4 "set g_gametype 5 ; map mp_village ; set nextmap vstr d4a"
set d4a "map_restart; set nextmap vstr d4b"
set d4b "map_restart; set nextmap vstr d4c"
set d4c "map_restart; set nextmap vstr d5"
set d5 "set g_gametype 5 ; map mp_base ; set nextmap vstr d5a"
set d5a "map_restart; set nextmap vstr d5b"
set d5b "map_restart; set nextmap vstr d5c"
set d5c "map_restart; set nextmap vstr d6"
set d6 "set g_gametype 5 ; map mp_assault ; set nextmap vstr d6a"
set d6a "map_restart; set nextmap vstr d6b"
set d6b "map_restart; set nextmap vstr d6c"
set d6c "map_restart; set nextmap vstr d7"
set d7 "set g_gametype 5 ; map mp_castle ; set nextmap vstr d7a"
set d7a "map_restart; set nextmap vstr d7b"
set d7b "map_restart; set nextmap vstr d7c"
set d7c "map_restart; set nextmap vstr d1"

vstr d1

You can change the maps in rotation by editing this file and taking out the sections for the maps you don't want, or moving them around to rotate in a different order.

Step 5: Create a Public.cfg file

The public.cfg file contains information about your server that the public can find out, as well as the designating what master server lists the server reports to. Create a document in your /main directory and call it "Public.cfg". Paste the following into it:

// Server Config
seta sv_hostname "SERVERNAME"
seta g_motd "MESSAGE_OF_THE_DAY"

// public info
seta "Administrator" "ADMIN_NAME"
seta "Email" "EMAIL_ADDRESS"
seta "url" "URL"
seta "Location" "LOCATION"
seta "CPU" "CPU_DESCRIPTION"
seta "icq" "ICQ_NUMBER"
seta "Clan" "CLAN_NAME"
seta "Connection" "CONNECTION_SPEED"

// add up to 4 additional master servers to report to
seta sv_master1 "wolfmaster.idsoftware.com"

Edit the fields in all caps above, filling in the correct information for your server.

Okay, you should be all set! Make sure all those .cfg files are in your /main Wolfenstein directory, then start your server with the .bat file!