Installing Quake3 &
WFA Files on the Linux Server
Download the latest 1.31 Linux Dedicated binaries http://www.quake3world.com/files (10 MB).
Installation:
Create a directory for Quake 3 usually /usr/local/games/quake3 and copy or upload the pak0.pk3 pack file from your Windows CD to the baseq3 directory.
Create a directory called wfa under the quake3 and copy the WFA files into the wfa directory
Then make the 1.31 update executable and then run it like so:
chmod +x linuxq3apoint-1.31.x86.run
./linuxq3apoint-1.31.x86.run
Follow the instructions in the installer and your server will be all ready to configure.
This is straight from the Installation Instructions off of zerowing:
Quake III Arena
Quake III: Weapons Factory Arena
Installation instructions
------
What you need:
- retail CD-ROM of Quake III Arena for Windows or linux
- Weapons Factory Arena files
- a computer running linux (kernel >= 2.2 glibc >= 2.1)
- running the client requires X11 and 3D hardware acceleration with OpenGL
Installation:
If you have the retail CD-ROM of Quake III Arena for linux:
- install Quake III Arena from the CD-ROM
- run the Point Release installer
(to buy Quake III Arena for linux online, try http://www.tuxgames.com/)
If you have the retail CD-ROM of Quake III Arena for Windows:
- run the Point Release installer first
- now you need to copy the main pak files from the CD-ROM or from your win32 partition. Namely, you need to copy baseq3/pak0.pk3 and for Team Arena, missionpack/pak0.pk3 see below for more instructions on how to copy the files:
WARNING: Those instructions are provided as a reference, depending on your distribution the CD-ROM might not have the same mount point. Please refer to your linux documentation for additional information.
- open a root shell and cd to the default installation path:
cd /usr/local/games/quake3
- mount the Quake III Arena CD-ROM and install the game content
cp /mnt/cdrom/Quake3/baseq3/pak0.pk3 /usr/local/games/quake3/baseq3
- optionally, mount the Quake III: Team Arena CD-ROM
cp /mnt/cdrom/Setup/missionpack/pak0.pk3 /usr/local/games/quake3/missionpack
NOTES:
- If you are running Quake III Arena and Quake III: Team Arena on a Windows partition, you can save some space by symlinking the game assets to their windows installation:
ln -s /win/quake3/baseq3/pak0.pk3 /usr/local/games/quake3/baseq3/pak0.pk3
ln -s /win/quake3/missionpack/pak0.pk3 /usr/local/games/quake3/missionpack/pak0.pk3
(Windows partition is mounted as /win and Quake III Arena installation is C:\quake3)
Getting Help:
- consult the FAQ in Help directory
- head over to the Weapons Factory forums http://www.forumplanet.com/weaponsfactory
- visit us in irc.enterthegame.com #wfa
Starting the Linux Server
For Linux users it is best to use screen to launch your quake
3 server so you can log out of the shell. If you use screen to start the server
you can hit ctrl a then ctrl D and it will allow you to log out of the telnet
session. You can later re-claim the screen process by typing screen
-r at the command prompt. This example uses screen.
cd /usr/local/games/quake3
screen ./linuxq3ded +set fs_game wfa +set dedicated
2 +set
sv_pure 0 +set gametype 4 +exec wfa-server.cfg
This should start your server running and execute the wfa-server.cfg and start the 2castles-wfa map or whatever map you call at the end of the wfa-server.cfg.
Several people have pointed out that you can also use the command line:
./linuxq3ded +set fs_game wfa +set dedicated 2 +set sv_pure 0 +set gametype 4 +exec wfa-server.cfg > /dev/null 2>&1 &
This will make the server fork off and run as a daemon.
This will allow you to cron the command and make the server start automatically
every time the server reboots.
IT IS STRONGLY ADVISABLE, FOR SECURITY REASONS, THAT
YOU DO NOT RUN QUAKE3 AS ROOT
Configuring the Linux Server
For all server types the basic wfa-server.cfg and wfa-server.ini files are alike. To create one for your own specific server, visit http://www.shadowspawn.net/content/game/quake/server-config.asp for assistance on the default configuration.
Some final notes on running specific configurations
It is strongly
advisable to keep the sv_allowdownload option to "0" since this
still crashes servers when more than 7 downloads are happening at the same
time. The whole purpose of sv_allowdownload is to allow clients who do not
have the files to download them so they can participate; however Id software
has acknowledged this problem and will address it in a future release.
Running two pure
servers at the same time in the same directory will force all clients to
download all the files no matter which files are unique between the two.
If a server is running
on the pure setting (sv_pure 1) and a client does not have the corresponding
files, ie. modified .pk3 file or different version of the WFA mod or even a
different map with the same name, they will not be able to connect to the
server.
If a server is running
on the pure setting and a client does not have the corresponding
map (ie. new-radicalmap-wfa) they will still be able to play on the server
until that map is up.
The hunkmegs are for
the engine to conserve memory for items it must load and store. The server
is NOT the client, all it needs to hold is really the map and entities, and
whatever other information that makes the game or rather mod specific. Here
is a snippet from ID software:
com_hunkmegs - allocates a certain amount of memory for map and item
loading. The default of 56 is required for the client but is overkill for a
dedicated server, and thus wasting precious server memory. For general use
free for all, tournament maps, and team deathmatch, a com_hunkmegs setting
of 16 is sufficient. Using the included tournament maps only, a com_hunkmegs
setting of 12 may be used to conserve more memory. Capture The Flag requires
a minimum com_hunkmegs setting of 26 with the included maps.
NOTE: user made or future map releases may require a higher setting. If you
receive an ERROR: Hunk_Alloc failed then try increasing the com_hunkmegs
setting in increments of 2 until the map successfully loads.
So a safe number really is around 75-80, however play around with what you
have.
As always, be sure to visit the forum at http://www.forumplanet.com/weaponsfactory/ and subscribe to the wfa-admin mailing list at http://www.shadowspawn.net/wfadmin and the public one at http://www.shadowspawn.net/wfa to make sure you have the latest updates, announcements, and other technical news.