Frequently Asked Questions


What is ET: Legacy?

ET: Legacy is an open source project based on the code of Wolfenstein: Enemy Territory which was released in 2010 under the terms of General Public License v3.

Set during World War II and heavily focused on team work, the game was initially released in 2003 by Splash Damage and id Software. More than a decade after its release, after spending countless hours of escorting tanks and trucks, stealing gold and radar parts and transmitting confidential documents, it was time to dust off the game which consistently refused to go down.

There are two aspects to this project, an updated game version "Enemy Territory: Legacy" and a new mod "legacy".

  • The main goal of ET: Legacy is to fix bugs and security exploits, remove old dependencies, add useful features and modernize its graphics while still remaining compatible with ET 2.60b and as many of its mods as possible.
  • The main goal of legacy is to stay close to the original gameplay experience and provide a viable alternative to ETPro for competitive play while staying lightweight but extensible through additional Lua scripts.

>>> Read more.

What about Compatibility?

ET: Legacy is aiming to remain compatible with ET 2.60b and as many of its mods as possible.

There are, however, some limitations:

PunkBuster™ is not supported:

Before the GPL release the PunkBuster™ code parts of Wolfenstein: Enemy Territory were stripped from the source. Due to that, ET: Legacy does not and will never be able to work on servers where PunkBuster™ is enabled. On the plus side however, there is no system-wide, permanently running and therefore potentially lag inducing service installed.

ETPro is only compatible on the server, not the client side:

The ETPro built-in Anti-Cheat prohibits all client gameversion binaries except ET 2.60(b) clients from connecting. (Console Output) As a server admin you can, however, run ETPro mod on an ET: Legacy server. Unfortunately, it is rather unlikely that either the ETPro source code or that a new ETPro version will be released, whitelisting ET: Legacy binaries. Therefore, it is unlikely that ET: Legacy and ETPro will ever be compatible.

Mac OS X is only compatible with mods providing mac binaries:

As of early 2019, compatible mods are: silent 0.9, noquarter 1.2.9, jaymod 2.2.0, etpub 1.0.0 and our default mod legacy. However, at least for legacy, the binaries are only compatible with Mountain Lion or better. Please also note that Omni-bot is not compatible with Mac OS X and you will therefore not be able to spawn bots.

Linux 64-bit is only compatible with 64-bit mods:

Linux 64-bit ET: Legacy clients can only connect to servers running mods providing a 64-bit version. Our default mod legacy is, along with ETRun, the only mod providing a 64-bit version (as of early 2019). If you want to be able to play other mods, you need to install the Linux 32-bit version. Don’t forget to install the required 32-bit libraries on your 64-bit machine.

ET 2.55 is not supported:

As Wolfenstein: Enemy Territory 2.55 is not open source, we can’t support this game version with all necessary fixes of security exploits. There are good reasons as to why the official game download and the official source are only available as 2.60b. 2.55 clients are outdated and insecure! Like Splash Damage and id software, we do not recommend their use!

>>> Complete compatibility overview.

How does legacy compare to ETPro?

As we are aware of the necessity of having a competitive mod, we decided to create legacy, the default mod shipped with ET: Legacy.
The main goal of legacy is to stay close to the original gameplay experience and provide a viable alternative to ETPro for competitive play while staying lightweight but extensible through additional Lua scripts.

Contrary to ETPro, legacy is under active development and is being continuously shaped according to reliable feedback from the competitive scene.
With this mod we are not aiming for a 1:1 replication, but rather an own, updated and eventually more user-friendly competitive experience.

In comparison with ETPro legacy currently lacks the following:

Unfortunately, ETTV is not open source. Therefore, we would have to rebuild its functionality from scratch. There are plans for a similar ETLTV feature, however, due to other priorities and most of all Twitch, it hasn’t been fully implemented yet.

The open source nature of ET: Legacy makes it practicably impossible to implement a traditional Anti-Cheat (which can be bypassed anyway). We implemented the Anti-Wallhack feature by Laszlo Menczel for the Q3 engine. Furthermore, there are plans for an authentication system as well as a real-time player analysis approach. In the meantime, we are shipping WolfAdmin, a Lua based server administration module by default to help administrative work.

>>> Please join our Discord and start chatting with our @league moderators for questions, suggestions and reports.

Is there a reliable Anti-Cheat?


Is there a shoutcaster mode?


How can I customize my game?

Document how to adjust cvars, navigate the console, use configs, apply startup parameters, etc.

What about Steam?

While the engine and game source code have been released under the terms of General Public License v3, the original game assets (3D models, textures, sounds, etc.) are still protected by the original EULA. ET: Legacy still relies on the original, proprietary assets and is therefore not entirely stand-alone. Due to the license restrictions, we are legally unable to push the game on Steam without replacing all the assets with own or appropriately licensed work first. The required workload to make this happens is huge (see #218), that’s why we need as many helping hands on deck as we can get.

After receiving a response from Bethesda support saying that all decision power lies within Activision, we have put up an open letter to Activision asking for the release of the original game assets under a license permitting use, modification and redistribution.
While we wait, please feel free to join us on Discord and start participating in the project.

>>> Open letter to ZeniMax
>>> Open letter to Activision.


NOTE: It is essential that you read our INSTALL.txt file that is shipped with the latest ET: Legacy binaries!

Anything to keep in mind before installing?

There are a few technicalities that you should consider before installing ET: Legacy.

Original game assets:

As mentioned in the "What about Steam?" section, ET: Legacy is not entirely stand-alone as we still rely on the original game assets due to their use and redistribution still being restricted by the original EULA.
Therefore, you will need to retrieve the genuine ET files yourself from an original Wolfenstein: Enemy Territory installation, which you can download from the official website of Splash Damage, the developer studio of Enemy Territory.
In the etmain folder of this installation you need to locate the files listed below and copy them to the etmain folder of your ET: Legacy installation directory (fs_basepath).

CAREFUL: Only add the files to your fs_basepath! Having them in both the fs_basepath and fs_homepath will lead to this error.

64-bit clients:

As mentioned in the "What about Compatibility?" section, Linux 64-bit clients are only compatible with mods providing 64-bit versions.
Opt for the 32-bit version if you want to play other mods.

Overwriting existing installations:

Do not attempt to overwrite an existing Wolfenstein: Enemy Territory installation. Choose a different location!
On that matter, also do not overwrite a previous ET: Legacy installation. Uninstall it first!

Multiple installations in parallel:

It is possible to have multiple installations of both Wolfenstein: Enemy Territory and ET: Legacy at the same time.
Note, however, that all ET: Legacy installations will share the same fs_homepath by default! Refer to this section for how to apply startup parameters like fs_homepath.

Visual C++ Redistributable:

On Windows, you need to ensure you have the latest Microsoft Visual C++ Redistributable installed.
The Windows installer will prompt you to install it if it is not detected on your machine.

>>> Installation guides for further help.


NOTE: Check our list of cvars for a comprehensive overview of all available configurations.

Can ET config files be used for ET: Legacy?

We do not recommend using configs created for original Wolfenstein: Enemy Territory in ET: Legacy! Keep in mind that many cvars have been deleted, changed or added - see List of cvars. We have removed multiple deprecated cvars from genuine GPL code and because all cvars from your config file are processed at runtime, the performance does not benefit from using more cvar definitions than required. Provide sample configs.

How to try the new openGL 3.2 renderer?

On our YouTube channel you can find some sneak peeks into our new renderer.
For testing it yourself, launch the ET: Legacy client with the +set cl_renderer opengl2 parameter. Note, however, that the renderer remains in an experimental state as of early 2019.
Use +set cl_renderer opengl1 to revert back to the old renderer. Refer to this section for how to apply startup parameters like cl_renderer.

How to change default fonts?

If you wish to use your own custom fonts in ET: Legacy, you can very well do so. To achieve this, put your custom fonts in the etmain/fonts (or legacy/fonts) folder. Be sure to rename them ariblk.ttf and courbd.ttf.

How to set up a custom game resolution?

If you wish so, you can adjust your game to use custom resolutions.

NOTE: We do, however, recommend to use the native desktop resolution /r_mode -2.
/r_mode -1 For that, first enable custom screen resolution.
/r_customheight 1600 Then specify your custom resolution in pixels.
/r_customwidth 900
/vid_restart Then restart the renderer so the new resolution can take effect.

How do FPS from ET: Legacy compare with those of ET?

By default ETL sets the game resolution to the native OS desktop resolution. This wasn’t the default behaviour of vanilla ET and the resolution set by ET: Legacy might be higher compared to ET 2.60b, especially when widescreen devices are plugged in. Higher resolutions require more calculations and as result FPS may not be satisfactory anymore. To properly compare FPS between ET and ETL you first should use the same resolution (/r_mode setting). Should FPS in ETL still be lower, please try using one of the sample configs for maximum performance. Provide sample configs.

NOTE: If you are using an AMD Radeon graphics card, set /r_primitives 2 and subsequently restart the renderer with /vid_restart. This is most probably related to an issue introduced in Catalyst drivers.


ERROR: Connection aborted - corrupt/duplicate official pak file server installation.

In most cases, there are duplicate pk3 files (e.g. pak0.pk3) in fs_homepath and fs_basepath on the server.
It is recommended to keep the files in fs_basepath and remove them from fs_homepath. See Path_and_File_Structure of ET: Legacy.

ERROR: Fail 00: Can’t open PK3...

In this case, ETL has detected an unwanted file in the game’s filesytem. In most cases, these are corrupt pk3 files downloaded by shady servers.
If you have contact to the respective server admin, you might try contacting them about its contents. If not, simply join a different server.

ERROR: BG_IndexForString: unknown token 'Tripmine’

If you encounter this error, it means you do not have pak3.pk3 in your game directory or legacy client mod (cgame) is not loaded.
Make sure you copy the genuine pk3.pk3 from an original ET installation or another trusted source.

Unknown Event: 129

If you have a .dll of a mod in fs_homepath and you connect to a server running the respective mod for the very first time, this .dll in fs_homepath is prioritised over the mod .dll running on the server, resulting in your game having different events than the server. Remove the .dll from your fs_homepath and reconnect to the server.

SDL audio driver is "(UNKNOWN)"

Try changing the SDL audio driver to "alsa" or something else:

export SDL_AUDIODRIVER="alsa"

If you still can not hear any sound and you have PulseAudio installed, try disabling it completely. Don’t forget that you need to have 32-bit sound libraries installed as well, this includes the libasound library.

SDL_OpenAudio() failed: No available audio device

Try changing the SDL audio driver to "alsa" or something else:

export SDL_AUDIODRIVER="alsa"

If you still can not hear any sound and you have PulseAudio installed, try disabling it completely. Don’t forget that you need to have 32-bit sound libraries installed as well, this includes the libasound library.

VM_Create on UI failed

Make sure your game was correctly installed. To do so, please compare your path and file structure to the one provided in this wiki article. Keep an emphasis on the mod folder of the mod that is running on the server you were trying to connect to.

Axis players hear allied sound announcements and vice versa

Same reason as for the Unknown Event: 129.

Game crashes directly on startup

On some systems (e.g. Linux Mint) SDL does not detect a valid graphical mode. Start ET: Legacy with the following startup parameters:

./etl +set r_fullscreen 1 +set r_mode <MODE_NUMBER>
Replace <MODE_NUMBER> with the right resolution integer from /r_mode see List of Cvars but don’t use /r_mode -2.

Unable to connect to True Combat: Elite servers on Linux

You are probably missing libstdc 5, run sudo apt-get install libstdc++5:i386.

silEnT mod Anti-Cheat

New silEnT mod whitelists official ET: Legacy releases. If you connect to a silEnT mod server with a client compiled from source, then the admins may tell you that they get a lot of warnings about your client.

Nitmod (NxAC)

NxAC Client Cvars Scanner searches for some cvars which were unused or obsolete and therefore removed from ET: Legacy. If you get errors such as:

Cvar: r_nv_fogdist_mode INCLUDE NV ()

You have to create a dummy cvar, in the above case seta r_nv_fogdist_mode "GL_EYE_RADIAL_NV" (source:
Although we do keep several dummy cvars in the source code to remain compatible with ET 2.60b, in this particular case a better solution would be to contact the server admins or N!tmod authors and tell them their Anti-Cheat configuration might need some adjustment.