Warzone 2100 - a free and open source real time strategy game. Check out our forums at forums.wz2100.net
C++ C JavaScript PHP CMake M4 Other
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
3rdparty [CMake] Use GNUInstallDirs, and `WZ_DATADIR` Aug 12, 2018
build_tools [Travis CI] Deploy source tarball Jun 25, 2018
cmake [CMake] Mark additional variables as advanced Aug 12, 2018
data A few more tweaks to semperfi-js. Aug 13, 2018
doc [CMake] Use GNUInstallDirs, and `WZ_DATADIR` Aug 12, 2018
docker Add Ubuntu 18.04 Clang Dockerfile Jul 8, 2018
icons [CMake] Use GNUInstallDirs, and `WZ_DATADIR` Aug 12, 2018
lib [macOS] Fix macOS 10.12+ deprecation warning Aug 12, 2018
m4 fixes #4701: fix autogen.sh warnings (patch 1/2) Jan 10, 2018
macosx [Travis CI] Add macOS CMake build Aug 12, 2018
pkg [CMake] Initial CPack DEB & RPM support Aug 12, 2018
po [CMake] Mark additional variables as advanced Aug 12, 2018
src Let syncRequest() handle objects without an assert. Aug 15, 2018
tests fixes #4693: replace deprecated function PHYSFS_addToSearchPath() wit… Mar 7, 2018
tools fixes #4693: replace deprecated function PHYSFS_read() Mar 7, 2018
win32 [Windows] Automatically update executable copyright date (autorevision) Jun 20, 2018
.gitattributes Exclude external stuff from Github's language statistics. Mar 16, 2017
.gitignore [Git] Ignore vcpkg directory Aug 12, 2018
.gitmodules Update miniupnpc to 2.1+ (latest) Jun 27, 2018
.travis.yml [Travis CI] Enable additional set of warnings for CMake builds Aug 12, 2018
AUTHORS Fix up Authors ordering. Mar 11, 2018
CMakeLists.txt [CMake] Disable additional set of warnings by default Aug 12, 2018
COMPILE Replace the outdated content of COMPILE with a pointer at the wiki. May 14, 2011
COPYING Create final repository structure. Jun 28, 2007
COPYING.NONGPL Update miniupnpc to 2.1+ (latest) Jun 27, 2018
COPYING.README Warzone 2100, I have the honour to release you from any license uncla… Jun 11, 2008
ChangeLog fixes #4777: warn about setting antialiasing to a value > 16, which c… May 17, 2018
Doxyfile Small update of the Doxygen files. Sep 16, 2011
Makefile.am Update miniupnpc to 2.1+ (latest) Jun 27, 2018
README.md README: Fix AppVeyor build status May 26, 2018
appveyor.yml [AppVeyor] Install Asciidoctor for documentation generation Jun 25, 2018
autogen.sh Simplify build process by getting rid of bison/flex dependencies. Sep 20, 2013
config.rpath Port r3878 and r3879 from trunk/ Mar 1, 2008
configure.ac Update miniupnpc to 2.1+ (latest) Jun 27, 2018
fixbrokendependencies Move broken dependency hack out of most Makefile.am's, except the for… Dec 16, 2010
get-dependencies.ps1 [Windows] Update vcpkg commit in get-dependencies.ps1 Aug 12, 2018
get-dependencies_mac.sh [Travis CI] Add macOS CMake build Aug 12, 2018
releaseBranch Simplify usage of version_getVersionString(). Jan 12, 2012


Warzone 2100

Homepage of the Warzone 2100 Project


Warzone 2100, released in 1999 and developed by Pumpkin Studios, was a ground-breaking and innovative 3D real-time strategy game.

In 2004 Eidos, in collaboration with Pumpkin Studios, decided to release the source for the game under the terms of the GNU GPL, including everything but the music and in-game video sequences, which were released later.

State of the game

After the liberation of the Warzone 2100 source-code on December 6th, 2004, all proprietary technologies have been replaced with open-source counterparts.

Right now supported platforms are Linux, Windows, and macOS. There are reports that Warzone 2100 is working on BSD, too.

Latest development builds

Build Status Windows Build Status

Development builds are a snapshot of the current state of development, from the latest (successfully-built) commit. Help testing these builds is always welcomed, but they should be considered a work-in-progress.

Reporting bugs

This game still has bugs and if you run into one, please use the bugtracker (http://developer.wz2100.net/) to report this bug. In order to faster fix those bugs we require that you follow these rules:

  1. If the game crashes you may save a memory dump. Please do so and upload it when reporting the bug. (Linux locates that file at /tmp/warzone2100.gdmp, Windows at /Program Files/Warzone 2100/warzone2100.RPT, macOS by clicking "Details" in the crash error message) A self created backtrace is just as useful.
  2. Give as much information about what you were doing before the crash/bug occurred.
  3. Try to reproduce the bug and add a description of the process to your bug- report.
  4. You may even upload save-games. These consist of one or two file(s) and one folder. All two/three are named after your save-game (e.g. MySaveGame.es, MySaveGame.gam and the folder MySaveGame).
  5. Bug-reports are not submit-and-forget. It may be that you forgot some information or forgot to upload a file. So it is, too, in your interest to watch the bug-report after it has been submitted. Additionally you receive e-mails of comments to your bug-report.


Warzone 2100 uses an own sub-directory in a user's home directory to save configuration data, save-games and certain other things. Additionally you can use this directory to place custom maps and mods so the game can find them. The location of this directory depends on the operating system.

Warzone directory under GNU/Linux

Under GNU/Linux, Warzone conforms to the XDG base directory spec.

By default, the directory warzone2100-<version> can be found in your home-directory under the path ~/.local/share/. (If the XDG_DATA_HOME environment variable is defined, the Warzone folder will be located within $XDG_DATA_HOME.)

The leading dot in the .local part of the path indicates that it is a hidden directory, so depending on your configuration you may not be able to see it. However, you can still access it by typing the path into your address-bar.

Warzone directory under Windows

The directory Warzone 2100 Project\Warzone 2100 <version> is located under the %APPDATA% folder.

Typical %APPDATA% paths:

  • Windows XP: \Documents and Settings\$USER$\Application Data
  • Windows Vista+: \Users\$USER$\AppData\Roaming

Hence, the default path for the Warzone configuration data on Windows Vista+ would be: C:\Users\$USER$\AppData\Roaming\Warzone 2100 Project\Warzone 2100 <version>\

By default, the %APPDATA% folder is hidden. Entering: %APPDATA%\Warzone 2100 Project\ into the address bar of Windows Explorer will browse to your Warzone directory.

Warzone directory under macOS

The directory Warzone 2100 <version> can be found in your home-directory at: ~/Library/Application Support/

By default, recent version of macOS hide your account's Library folder. To view it in Finder, hold down the Option (⌥) key while clicking the Go menu, and your Library folder will appear as a menu choice.

Configuration file

The configuration file is just called 'config' and contains several configuration options, some of them can be changed by using command-line options or using the in-game menus, others can only be changed by editing the file by hand.

If at any point you did something wrong, you can delete the old configuration file and just restart Warzone 2100. Then the game will regenerate a new configuration file with default values.

Command-line options

Warzone 2100 can be started with different options and arguments. For a list of these options, run the game with the --help option.

Notes: These options all have two dashes (--), not one dash only (-). Also, if the option has an argument, you need to separate the option and its argument with a '=' sign - spaces do not work.

Note: Some options have corresponding entries in the configuration-file and will persist from one start of Warzone 2100 to the next.

Multiplaying via internet

There are two methods to start a multiplayer-game via internet: using the host's IP or using the lobby-server. Make sure to be able to communicate on TCP-ports 2100 and 9999. Note that for port forwarding, you only need to configure your router to forward port 2100.

You can choose whether to connect via Lobby or IP:

  • If you choose IP, Warzone 2100 asks you for the ip-address of the host and will try to connect to that IP.
  • If you choose Lobby, Warzone 2100 will connect to the lobby server, as long as the lobby-server-address in your config-file has not been changed.

You will see a list of games from which you can select one.

You can kick unwanted players out of not-yet-started game by clicking left on them while holding the right mouse button.

When you are hosting a game it will automatically be listed on the lobby-server. If you do not want your games to be listed on the lobby-server, you have to change the entry "masterserver_name=lobby.wz2100.net" in your config to some- thing invalid as "nomasterserverplease".

If you then want to see the games that are listed on the lobby-server you may enter "lobby.wz2100.net" when prompted to enter the host's IP or change the entry in the config-file back. You will have to restart Warzone 2100 in order for config-changes to take effect.


Like many other games Warzone 2100 features a certain set of cheats that can be used to have an advantage in the singleplayer-campaign and skirmish-games, or to just help mod- and map-makers with testing. Cheats do not work in multiplayer, unless all players agree to it.

Cheats are likely to contain or trigger bugs, so use with care, especially during campaign.

Entering cheat mode

To be able cheats while in-game, press shift and backspace simultaneously. An on-screen message should appear telling you that cheat-mode has been enabled. You can disable it using the same key combination again.

Pressing ctrl+o opens up the debug menu, which is useful for inspecting the game state, or just messing around.

Cheat commands

After activating cheat-mode cheats can be entered using the normal chat- function. Cheats are ordered by their use and where they can be used.

There are many cheat commands. Some examples:

  • "biffer baker" - Your units do more damage and are stronger
  • "double up" - Your units are twice as strong
  • "give all" - Allows you to build and research everything
  • "work harder" - All currently active research topics are instantly researched
  • "research all" - Everything is researched instantly
  • "let me win" - You win the current campaign mission
  • "superpower" - Gives you maximum power

Modding information

Warzone AI, maps and campaign can be scripted using javascript.

Links to further information

How to build

Getting the Source

To properly build the game, either:

  • Download a release tar.xz, which contains all the source code and revision information.


  • Clone the Git repo:

    git clone https://github.com/Warzone2100/warzone2100.git
    cd warzone2100
    git submodule update --init --recursive

    Note: Initializing submodules is required.

Do not use GitHub's "Download Zip" option, as it does not contain submodules or the Git-based autorevision information.


See http://developer.wz2100.net/wiki/CompileGuideLinux

Windows Cross compile

See http://developer.wz2100.net/wiki/CompileGuideWindows/Cross

Windows using MSVC

  • Prerequisites
  • Preparing to build: Build dependencies are provided via vcpkg from Microsoft.
    • Run the get-dependencies.ps1 script from powershell in order to download and build the dependencies.
  • Building from the command-line:
    • Change directory to the warzone2100 repo directory
    • Configure
      • Visual Studio 2017: cmake -H. -DCMAKE_TOOLCHAIN_FILE=vcpkg\scripts\buildsystem\vcpkg.cmake -Bbuild -G "Visual Studio 15 2017"
      • Visual Studio 2015: cmake -H. -DCMAKE_TOOLCHAIN_FILE=vcpkg\scripts\buildsystem\vcpkg.cmake -Bbuild -G "Visual Studio 14 2015"
    • Build
      • Release: cmake --build build --config Release
      • Debug: cmake --build build --config Debug
  • Building using Visual Studio 2017:
    1. Open Visual Studio 2017
    2. Open the warzone2100 folder using File > Open > Folder...
      • Allow Visual Studio some time to load the project and retrieve information from CMake.
    3. Create a VS CMake settings JSON file using CMake > Change CMake settings.
      • This creates CMakeSettings.json
    4. Add the following variables to cmakeCommandArgs in CMakeSettings.json:
      • -DCMAKE_PREFIX_PATH=C:\Qt\Qt5.9.4\5.9.4\msvc2015 (change to use the appropriate path to your Qt installation)
      • -DCMAKE_TOOLCHAIN_FILE=vcpkg\scripts\buildsystems\vcpkg.cmake
      • Note: Visual Studio should automatically escape and turn each \ into \\
    5. After letting Visual Studio re-run CMake configure with the new settings, you can build using the CMake menu.


See macosx/README.md