OpenXcom gives the original X-COM games a new engine while keeping their old data
The project makes the game files, user saves and mods separate parts of a modern installation.

The aliens can come back without bringing the original game engine. OpenXcom supplies an open-source replacement for UFO: Enemy Unknown, known as X-COM: UFO Defense in the US, and X-COM: Terror From the Deep. The old resources remain the raw material. Apparently even an alien invasion benefits from replacing the infrastructure.
The OpenXcom README describes a C++ and SDL project under the GPL. It also puts an important condition near the installation instructions: the engine requires “a vanilla copy of the X-COM resources.” Downloading a new engine doesn’t include permission or data files for the original commercial games.
For Windows users who own the games on Steam, the installer can detect the files and copy the resources. Manual setup is also documented, with separate UFO and TFTD subfolders. The project supports resources from either or both games, so the installation can match the copies somebody actually owns.
Vanilla means something practical here. The README warns against starting with modified resources, such as files already changed by XcomUtil, because they may cause bugs or crashes. A replacement engine needs a known starting point before optional changes are layered on top. Old folders often contain more archaeological surprises than their owner remembers.
OpenXcom has its own mod system and includes standard mods based on familiar community functionality. Additional mods go into individual subfolders and are enabled in the game’s Options menu. An archive with an extra enclosing directory may need its contents moved so the expected rules and terrain folders are at the right level.
That last detail explains a common kind of apparently broken mod. The files can be present on disk and still be invisible to the program because the folder layout is wrong. An extraction utility’s convenient extra directory has become the latest defense against the extraterrestrial threat (very effective against menus, too).
The project distinguishes user, configuration and data locations. Saves, screenshots and mods belong to the user area; configuration has its own home; original resources live in data locations. Command-line options can override those paths. This makes portable or deliberately separated installations possible, provided the owner knows which part is being moved.
A copy of X-COM: UFO Defense is therefore a source of game resources, while OpenXcom is the software that uses them. The project’s own installation instructions remain the authority for the required directory layout. A store listing alone doesn’t explain that arrangement.
The preservation benefit is that old creative work can remain usable while a maintainable engine and community modifications grow around it. The remaining setup work is specific and unglamorous: clean original data, correct folders and the right game selected for the intended mods.
The invasion has a new launcher.