Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is ET: Legacy?
ET: Legacy is an open-source project that builds a client and server for Wolfenstein: Enemy Territory, designed to stay fully compatible with the original 2.60b release. Its stated goal is to keep a well-regarded online FPS playable and current without splitting the existing community, so players can join familiar servers while benefiting from ongoing maintenance and modernization.
Who it is for
- Returning players who still have Enemy Territory habits and want a maintained way to install and play.
- Server operators who need a compatible server that works with the established 2.60b ecosystem.
- Contributors — the project describes itself as an international community of developers and users working openly and transparently, and invites anyone to join.
What the project covers
The site presents ET: Legacy as both a client and a server, not just a patch or launcher. It also points to community spaces, a test server, development activity from its main repository, and blog notes. That mix suggests two practical uses: getting a working game installation, and following or testing changes before they reach wider use.
Why compatibility matters here
Enemy Territory's longevity comes from its maps, mods and servers built over many years. A client that breaks compatibility would fragment that pool; ET: Legacy's emphasis on 2.60b compatibility is the trade-off it chooses — preserving the existing game rather than reinventing it. The cost is that it inherits the original's older interface and conventions, which is precisely what long-time players tend to want.
A practical first step
If you want to play, start by checking the project's download and setup guidance, then verify you can connect to a populated server before tweaking settings. If you run a server, test ET: Legacy against your existing configuration and mods on a staging instance first. For background on the game itself, see Splash Damage.
How do I download and install ET: Legacy to play Wolfenstein: Enemy Territory?
ET: Legacy is a community-built, open-source client and server for Wolfenstein: Enemy Territory that stays compatible with the original 2.60b version, so it is meant for players who want the classic game with modern fixes rather than a remake. Downloading and installing it is a two-part job: get the ET: Legacy client, then point it at the original Enemy Territory game data, which the project does not redistribute.
What you need before you start
- A legitimate copy of Wolfenstein: Enemy Territory (the original free release) so the client has the game assets it expects.
- A desktop OS the project supports — ET: Legacy targets Windows, Linux and macOS.
- Roughly a few hundred megabytes free, plus a stable connection for multiplayer.
Install steps
- Go to ET: Legacy and open its download section.
- Pick the build for your operating system and download the installer or archive.
- Install or extract it to a normal folder — avoid system directories so the game can write configs and mods.
- On first launch, point the client at your existing Enemy Territory installation if it does not detect it automatically.
- Set your resolution, controls and audio, then test in a local match before joining online servers.
- To play multiplayer, use the in-game server browser or connect directly to a server address.
Practical notes
The main trade-off is that ET: Legacy is a compatibility layer, not a standalone game: without the original assets it will not run, and some servers still run older clients, so a few communities may expect vanilla 2.60b. For most players the payoff is better support for modern screens, input handling and security fixes while keeping the same maps and gameplay. If you only want to test the water, the project's own test server is the quickest way to confirm everything works before you commit to a full setup.
If you hit trouble, check the community section on the site first — installation and asset-path questions are common, and the project's community is the fastest place to get a specific answer for your OS.
Is ET: Legacy compatible with the original Wolfenstein: Enemy Territory 2.60b servers and mods?
Yes. ET: Legacy is built as a fully compatible client and server for Wolfenstein: Enemy Territory 2.60b, so the intent is that you can join existing 2.60b servers and play with people using the original game, rather than being confined to a separate ecosystem. The project describes itself as an open source client and server replacement that keeps the game "alive and up to date" while preserving the gameplay many players still consider unmatched.
What compatibility covers
- Client side: You can use ET: Legacy as your game client and connect to 2.60b servers.
- Server side: You can also run ET: Legacy as the server, which matters if you host matches or a community server.
- Mods: Compatibility with existing Enemy Territory mods is the point of the project, since mods are what most public servers actually run.
Where to check before you commit
Compatibility is a project goal, not a guarantee for every mod or server configuration. Some mods and server-side extensions make assumptions about the original engine, and edge cases can appear in things like anticheat, custom client commands or heavily modified server binaries. If you play on one specific server or use one specific mod, test that setup first rather than assuming every variant behaves identically.
A practical next step: install ET: Legacy, try your usual server list, and compare the experience with the original 2.60b client on the same servers. Forums and the project's community channels are the fastest way to confirm whether a particular mod is known to work. If you are comparing options, the original game and its community patches are documented at Splash Damage and id Software, while ET: Legacy itself is at ET: Legacy.
How can I contribute to the ET: Legacy open source project?
Contribute by picking the kind of work you can sustain: code, testing, documentation, translations, community support, or infrastructure. ET: Legacy describes itself as an international community of developers and users keeping Wolfenstein: Enemy Territory alive, with development done collaboratively and openly, and it explicitly says anyone is welcome to join.
Ways to contribute
- Code and engine work. The project maintains a client and server for Wolfenstein: Enemy Territory, so there is ongoing work in C/C++ and related tooling. Start small: fix a bug, improve a build script, or clean up a warning, then let maintainers guide you toward larger systems.
- Testing. Play on the project's test server and report what breaks, including steps to reproduce, your OS, and logs. Compatibility with existing Enemy Territory 2.60b clients and servers is central to the project's goal, so regression reports are especially valuable.
- Documentation and translations. Clear install, server-setup, and troubleshooting guides reduce repeat questions. If you speak a language other than English, translation help reaches players who would otherwise bounce off English docs.
- Community support. Answer questions in the project's community channels, help new players get connected, and moderate constructively. This is often the easiest entry point if you are not a programmer.
- Infrastructure and moderation. Servers, mirrors, CI, and anti-abuse work are less visible but keep the project running.
A practical first step
Look at the project's repository activity and issue tracker, then choose one small, clearly scoped task rather than announcing a large feature. Introduce yourself in the community channel, say what you can do and how much time you have, and ask where help is most needed right now. Maintainers usually prefer a contributor who completes a small fix over one who promises a rewrite.
Decision criteria
- If you can code but are new to the codebase, start with a bug fix or a build improvement.
- If you cannot code, testing and documentation are the highest-leverage options.
- If you have server hardware or bandwidth, offering a test or mirror server is directly useful.
- If your time is limited, regular triage — confirming bugs, closing duplicates, answering newcomers — still counts.
For official downloads, source, and community links, use ET: Legacy. You can also compare notes with the wider Wolfenstein: Enemy Territory community at Splash Damage, the original developer, though that site is not the project's coordination hub.
What are the main differences between ET: Legacy and the original Enemy Territory client?
ET: Legacy is a community-built, open-source client and server that aims to stay fully compatible with the original Wolfenstein: Enemy Territory 2.60b. In practice, that means you can keep playing the same game, on the same kinds of servers, while getting a codebase that is actively maintained rather than frozen.
Where the differences show up
- Maintenance and modern systems. The original 2.60b client is long unmaintained and can be awkward on current operating systems and hardware. ET: Legacy exists to keep the game running and up to date, which matters most if you have had trouble launching or playing the original.
- Client and server together. ET: Legacy is not just a client; the project also provides a server. Server operators get a maintained server to run, while players use the matching client.
- Compatibility as the goal. The stated aim is full compatibility with 2.60b, so the intent is not to replace Enemy Territory with a different game. Gameplay is meant to feel like the original, which is why the project describes the original's gameplay as still unmatched by many.
- Community-driven development. Development is described as collaborative, open and transparent, with an international community of developers and users. Changes come from that community rather than a single commercial publisher.
- Project infrastructure. The site points to a community area, a test server and repository activity, which is how you can see what is currently being worked on before you commit to switching.
A practical way to decide
If the original client already runs well for you and your usual servers, there is little reason to change. If you are on a newer machine, run into compatibility problems, or operate a server and want something maintained, ET: Legacy is the more sensible starting point. Because compatibility is the design goal, you are not choosing a different style of play, just a maintained way to run the same one.
A useful next step is to check the project's test server and recent repository activity before downloading, so you can confirm the current state of development matches what you need. For background on the game itself, see ET: Legacy.
How do I set up and run my own ET: Legacy server?
To run your own ET: Legacy server, start with the official project at ET: Legacy. It describes itself as an open source, fully compatible client and server for Wolfenstein: Enemy Territory 2.60b, so your server will work with players using the original 2.60b client as well as the ET: Legacy client. The practical path is: get the server files, configure a config file, open the right ports, and test locally before inviting anyone.
What you need
- A machine to host it: a spare PC, a VPS, or a home server. A small VPS is the usual choice if you want it online 24/7.
- The ET: Legacy server package for your operating system, plus the game data files (the original Enemy Territory assets, since the project is built around compatibility with the 2.60b game).
- A text editor for the server config, and basic comfort with a command line.
Basic setup flow
- Install the server binary and place the game data in the expected directory structure.
- Create a server config file. Typical settings cover the server name, a welcome message, the port, max players, the map rotation, and admin passwords. Keep the remote/admin password strong and separate from the join password.
- Set the map rotation and any game-type or campaign options you want. Start with a small rotation while testing.
- Launch the server from the command line, pointing it at your config, and watch the console for errors.
- Connect from your own client using
localhostor the LAN address to confirm it loads a map and accepts players. - Open the server port on your firewall and, if hosting at home, forward it on your router. Then test from outside your network.
Decisions that matter more than the install
| Choice | Why it matters |
|---|---|
| Public vs private | A public server needs anti-cheat habits, admin coverage, and a clear ruleset. A private one mainly needs a password and a small map list. |
| Home vs VPS | Home hosting is cheap but depends on your upload speed and router setup; a VPS gives a stable address and uptime. |
| Vanilla vs mods | Staying close to stock keeps compatibility broad; mods add features but narrow who can join. |
Getting help and staying current
The site lists a Community section and an ET: Legacy Test Server, which is useful for checking how your setup behaves against a known-good server. If you get stuck, the project's community channels are the right place to ask, since the developers and long-time server admins there deal with exactly these configuration questions.
A sensible first milestone: get one map running locally, connect with a friend over the internet, then add maps and admin tools. That order surfaces firewall and config problems early, when they are easiest to fix.
User reviews (0)