Enemy Territory

Introduction
Enemy Territory is a first person shooter that uses the Quake 3 engine. This article covers installation, configuration and troubleshooting.

Installation
First accept licence:

Edit/add into "make.conf" this keyword -> ACCEPT_LICENSE="RTCW-ETEULA".

To install Enemy Territory run:

The game installs to.

Enemy Territory is a Quake III based game and will need it's pak-.pk3 file, see Quake III.

PunkBuster
To play online on most servers you will need to update the PunkBuster anti-cheat software. See the Quake 3 article for instructions.

The path where Enemy Territory is installed is.

Sound
See the Quake 3 article for information on getting sound working. Some additional notes and an alternative ALSA patch are detailed below.

ALSA Patch
There is an alpha hack that makes Enemy Territory use ALSA for sound by replacing standard sound system functions in runtime, as aoss won't work for ET. This may fix issues when using other applications at the same time, such as TeamSpeak 2.

It's located at SDL Support for Enemy Territory...

wget -q -O - http://nullkey.kapsi.fi/et-sdl-sound/et-sdl-sound.gz | gzip -d > et-sdl-sound && chmod a+x et-sdl-sound

Now start Enemy Territory with:

Note if you want to hook this up to XQF you need to tell XQF that the "Command Line" is "" and the "Working Directory" is ""

OSS Parameters
Set the OSS parameters for Enemy Territory with:

Further details on this method are in the Quake 3 article.

Also:

Settings
A lot of times setting will appear lost or change seemingly randomly. This is because each profile and mod can have it's own settings. To help keep a consistent environment:


 * Only use one profile. Even if you set a default profile, it never seems to stick and you'll find yourself playing a player you didn't intend with lower XP and different settings.
 * Change the options in the main menu and not during the game. Settings can be lost if already playing a game and then exited from the game. After the settings are as you like quit and restart.
 * When saving settings use the back button and not the escape button to leave a menu.

Mods use their own settings too, so enter all of your settings once again for each mod.

Persistent Settings
There is a rather easy way to make your settings persistent (even when using different mods). You can use the file which may initially be located in the  directory (if it isn't, create it). will be executed at every start of the game.

What is supposed to be in autoexec.cfg? It makes sense to keep in it all settings you want to make persistent. Initially settings found in the file can be used (which is created when ending the game). If unfamiliar with the settings you find in that file, check out: ET 4 newbies and scripting for newbies.

Now with a basic idea what should be in, edit it. Keep in all the important settings and get rid of the rest.

When beginning the game the will be loaded/executed. In a already running game the can be loaded from console(~): )

If there are other mods (like etpro, jaymod, etpub) installed, create a symbolic link to them. This has a distinct advantage: only one will be used, which makes it easy to keep tyhe settings up to date for all installed mods. For example if etpro is installed:

64-bit (amd64)
If you are on the amd64 platform and you have a chipset with OSS problems, install the package. You'll then need to start et like this:

See Gentoo Bug 77031 Comment 10 for more background.

Failed Compile
Note: If it fails to compile with GCC 4.3 with the following error, add to the :

hooks.cpp: In function ‘unsigned int calculateProcCRC32’: hooks.cpp:377: error: ‘PATH_MAX’ was not declared in this scope hooks.cpp:380: error: ‘filename’ was not declared in this scope hooks.cpp:384: error: ‘filename’ was not declared in this scope