- General questions
- Setting up
What is ET: Legacy?
What about compatibility?
ET: Legacy is aiming to remain backwards compatible with ET 2.60b servers and as many of its mods as possible.
There are, however, some limitations:
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, bugged and insecure! Like Splash Damage and id Software, we do not recommend their use!
PunkBuster is not supported
Before the GPL release, the PunkBuster code parts of Wolfenstein: Enemy Territory were stripped from the source code. Therefore, 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, potentially lag inducing service installed.
Note that PunkBuster support for Wolfenstein: Enemy Territory has been discontinued since 2011.
ETPro is only compatible on the server, not the client side
The built-in Anti-Cheat of ETPro prohibits all client game version binaries except ET 2.60(b) clients from connecting. As a server admin you can, however, run ETPro mod on an ET: Legacy server. Unfortunately, it is unlikely that either the ETPro source code or that a new ETPro version will be released, whitelisting ET: Legacy binaries. Therefore, it is doubtful that ET: Legacy and ETPro will ever be compatible.
Note the Legacy mod provided with ET: Legacy aims to be a viable and up-to-date alternative. Give it a try!
Mac OS X is barely compatible
Mac OS X is only compatible with mods that provide mac binaries, like our default Legacy mod. However, at least for Legacy, the binaries are only compatible with Mac OS X 10.9 Mavericks or better, and some newer version of Mac OS X are troublesome.
Mac OS X 10.15 Catalina dropped support for 32 bit compatibility, breaking most mods compatibility. At this time, the official ET: Legacy binaries are not compatible either.
Apple deprecated OpenGL in 2018, which will inevitably end Mac OS X support in the near future. While we could implement their Metal API, we don't have the resources to upgrade our renderer. Please consider using Bootcamp instead.
Omni-bot is not compatible with Mac OS X and you will therefore not be able to spawn bots on a local server.
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, like our default Legacy mod.
Note that if you want to be able to play 32 bit only mods, you should install the Linux 32 bit version. Don't forget to install the required 32 bit libraries on your 64 bit machine!
What about security?
There are good reasons to run ET: Legacy on dedicated ET servers! The genuine ET engine code for 2.60b hasn't been touched by any developer since 2006. ET: Legacy fixed all known security issues and exploits which have been detected since creation of ET 2.60b:
- DDoS protection
- wwwDL exploit
- Secunia Advisory SA19984
You can find all changes in our Changelog. If you are aware of a security related bug, don't hesitate to let us know about the issue!
How does Legacy compare to ETPro?
The default Legacy mod provided with ET: Legacy aims to be a viable and up-to-date alternative to ETPro. It isn't a carbon copy, but does integrate all useful features for competitive games, along side other modern features for a more user-friendly experience.
In comparison with ETPro, Legacy currently lacks the following:
ETTV is unfortunately 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 however implemented the Anti-Wallhack feature by Laszlo Menczel for the Q3 engine. We are also shipping a Lua based server administration module by default to help manual administrative work.
Why not putting this project on Steam? This would surely revive this game!
While the engine and game source code have been released under a free and open source license, the original assets (3D models, textures, sounds, etc.) were not. ET: Legacy still relies on the original, proprietary assets covered by the original EULA. We are thus legally unable to put it on Steam without prior legal agreement, or without replacing all the assets with our own work to make ET: Legacy entirely stand-alone first. The required workload to make this happens is huge (see #218), but feel free to contribute if you want to see this happening one day.
We have tried to contact the IP owners asking for the release of the original game assets under a license permitting use, modification and redistribution, but without much success.
When will the next version be released?
There is no ETA and it will be released when it is ready. You can however help make it happen sooner by becoming involved in the project. Check the current milestone to get an overview of what needs to be done before the next release.
It is essential that you read our INSTALL.txt file that is shipped with the latest binaries.
There are a few technicalities that you should consider before installing ET: Legacy.
Original game assets
As mentioned above, ET: Legacy is not entirely stand-alone as it still relies on the original game assets. These can't be packaged with our official release because of restriction imposed by the original EULA.
In order to run ET: Legacy, you'll need to copy assets from an original Wolfenstein: Enemy Territory installation.
Our installer do it for you, but you can also manually download them legally and for free from the official Splash Damage website.
Make sure the following genuine Wolf: ET files are copied to the
etmain folder of your ET: Legacy installation directory (fs_basepath):
Only add the files to your
fs_basepath! Having them in both the
fs_homepathwill lead to an error.
Can I overwrite my previous Wolfenstein: Enemy Territory installation?
No. Don't try to overwrite an existing Wolfenstein: Enemy Territory installation. Choose a different folder! Also, do not try to overwrite a previous ET: Legacy version. Uninstall it first!
Can I install ET: Legacy alongside the original Wolfenstein: Enemy Territory installation?
Yes. You can install both as if they were separate games.
Can I have multiple installations in parallel?
Yes. It is possible to have multiple installations of both Wolfenstein: Enemy Territory and ET: Legacy at the same time, or multiple installations of ET: Legacy at the same time.
Note however that all ET: Legacy installations will share the same
fs_homepath by default.
Can I use my ET config files for ET: Legacy?
No. This is likely to produce unwanted side effects, as many cvars have been deleted, changed or added. See List of Cvars. We have constantly removed unused cvars from the code and because any cvar from your config file is processed at runtime the game does not benefit if you use config files containing more cvars definitions than required. Literally hundreds of cvars have been removed from the original code while we have added a few.
My FPS are poor compared to Wolfenstein: Enemy Territory. What do I do?
By default ET: Legacy sets the game resolution to the used OS desktop resolution. This wasn't the default behaviour of vanilla ET and the resolution set by ET: Legacy might be higher compared to vanilla ET especially when widescreen devices are plugged in. But higher resolutions require more calculations and as result FPS may not be satisfactory anymore.
- If you want to compare FPS (ET vs. ET: Legacy), choose the same resolution as used in vanilla ET.
- If you want to increase FPS in general, lower the game resolution but keep your aspect ratio.
ERROR: Connection aborted - corrupt/duplicate official pak file server installation
This is a server side issue and clients can't fix it. In most cases there are duplicate .pk3 files in
fs_basepath on the server. Admins should remove the files from
fs_homepath. See Path and File Structure.
Unknown Event: 129
When you have a dll of a mod in
fs_homepath and you connect to a server the very first time, this dll in
fs_homepath is used instead of the server dll, causing different events from that server. Remove the file in
Axis players hear allied sound announcements and vice versa
Same reason as for the Unknown Event issue.
ERROR: BG_IndexForString: unknown token 'Tripmine’
This means you do not have
pak3.pk3 in your path or the legacy client mod file (cgame) is not loaded.
ERROR: VM_Create on UI failed
Make sure you installed your game correctly and that the proper path and file structure is preserved.
Mouse movement is too slow/fast! I cannot aim!
Go to the
Options menu and adjust your
Mouse sensitivity. It is different from ET 2.60b.
Visual C++ Redistributable
Make sure to have the Microsoft Visual C++ 2013 Redistributable Package (x86) installed.
The Windows installer will propose you to install it if it is not detected on your machine.
I can't connect with the Linux 64-bit client
As mentioned above, Linux 64 bit clients are only compatible with mods providing a 64 bit version. Opt for the 32 bit version if you want to play other mods.
I have extremely low FPS on my AMD Radeon graphics card
r_primitives 2. Don't forget to restart the renderer with
No sound - audio driver not found
If you get the following, ensure you have PulseAudio installed.
SDL audio driver is "(UNKNOWN)" SDL_OpenAudio() failed: No available audio device
Don't forget that you might need to have 32 bit sound libraries installed as well (f.e. libasound).
Tilde key (~) does not open my console!
SHIFT + Esc key combination. This should work on any keyboard layout!
Client crashes directly on startup
SDL might not detect a valid graphical mode automatically. Start ET: Legacy with:
./etl +set r_fullscreen 1 +set r_mode <MODE_NUMBER>
<MODE_NUMBER> with the right resolution integer from
r_mode but don't use
r_mode -2. See List of Cvars.
I can't connect to True Combat: Elite servers on linux
You are probably missing
Mac OS X issues
See Compatibility section above.
Newer 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.
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 the following, you might have to create a dummy cvar, f.e.
seta r_nv_fogdist_mode "GL_EYE_RADIAL_NV".
NxAC: CVAR_VIOLATION Cvar: r_nv_fogdist_mode INCLUDE NV ()
Although we do keep several dummy cvars in the source code to remain compatible with W: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 anticheat is badly configured.