{"id":13441965,"url":"https://github.com/Warzone2100/warzone2100","last_synced_at":"2025-03-20T13:31:31.003Z","repository":{"id":1183709,"uuid":"1084181","full_name":"Warzone2100/warzone2100","owner":"Warzone2100","description":"Command the forces of The Project in a battle to rebuild the world after mankind has been nearly destroyed by nuclear missiles. A 100% free and open source real-time strategy game for Windows, macOS, Linux, BSD+","archived":false,"fork":false,"pushed_at":"2024-04-13T00:31:39.000Z","size":693462,"stargazers_count":3027,"open_issues_count":448,"forks_count":508,"subscribers_count":117,"default_branch":"master","last_synced_at":"2024-04-14T00:37:48.921Z","etag":null,"topics":["c-plus-plus","campaign","cheats","cmake","freebsd","game","games","internet","javascript","linux","mac","macos","multiplayer","open-source","real-time-strategy","rts","strategy-game","windows"],"latest_commit_sha":null,"homepage":"https://wz2100.net","language":"C++","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"gpl-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/Warzone2100.png","metadata":{"files":{"readme":"README.md","changelog":"ChangeLog","contributing":null,"funding":".github/FUNDING.yml","license":"COPYING","code_of_conduct":".github/CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":"AUTHORS","dei":null},"funding":{"github":"Warzone2100","open_collective":"warzone2100"}},"created_at":"2010-11-16T04:36:26.000Z","updated_at":"2024-04-15T22:02:08.799Z","dependencies_parsed_at":"2024-04-13T20:03:33.012Z","dependency_job_id":null,"html_url":"https://github.com/Warzone2100/warzone2100","commit_stats":{"total_commits":19372,"total_committers":173,"mean_commits":"111.97687861271676","dds":0.8051827379723312,"last_synced_commit":"a2e1212f9a6420774935a29e7e0d7b55a7aa3c1f"},"previous_names":[],"tags_count":144,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Warzone2100%2Fwarzone2100","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Warzone2100%2Fwarzone2100/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Warzone2100%2Fwarzone2100/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Warzone2100%2Fwarzone2100/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/Warzone2100","download_url":"https://codeload.github.com/Warzone2100/warzone2100/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":219842910,"owners_count":16556577,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["c-plus-plus","campaign","cheats","cmake","freebsd","game","games","internet","javascript","linux","mac","macos","multiplayer","open-source","real-time-strategy","rts","strategy-game","windows"],"created_at":"2024-07-31T03:01:40.137Z","updated_at":"2024-10-28T02:30:33.909Z","avatar_url":"https://github.com/Warzone2100.png","language":"C++","funding_links":["https://github.com/sponsors/Warzone2100","https://opencollective.com/warzone2100"],"categories":["C++","Applications","Strategy","Native"],"sub_categories":["Games","Strategy"],"readme":"Warzone 2100\n============\n\n[Homepage of the Warzone 2100 Project](https://wz2100.net/)\n\nOrigins\n-------\n\nWarzone 2100, released in 1999 and developed by Pumpkin Studios, is a\nground-breaking and innovative 3D real-time strategy game.\n\nIn 2004 Eidos, in collaboration with Pumpkin Studios, decided to release\nthe source for the game under the terms of the GNU GPL, including everything\nbut the music and in-game video sequences, which were released later.\n\nState of the game\n-----------------\n\nAfter the liberation of the Warzone 2100 source-code on December 6th, 2004, all\nproprietary technologies have been replaced with open-source counterparts.\n\nCurrently, the supported platforms are Linux, Windows, and macOS. There are reports\nthat Warzone 2100 is also working on BSD.\n\nInstallation\n------------\n\nVisit https://wz2100.net for the latest stable release for Windows, macOS and Ubuntu.\n\nNote for videos in Ubuntu: For important information during the game, download the videos manually. Assuming the game is installed in the standard `~/.local/share/` folder, use these commands:\n```shell\nmkdir ~/.local/share/warzone2100\nwget https://github.com/Warzone2100/wz-sequences/releases/download/v3/standard-quality-en-sequences.wz -O ~/.local/share/warzone2100/sequences.wz\n```\n\nLatest development builds\n-------------------------\n\n\n[![Windows Build Status](https://img.shields.io/github/actions/workflow/status/Warzone2100/warzone2100/CI_windows.yml?branch=master\u0026label=Windows\u0026logo=windows)](https://github.com/Warzone2100/warzone2100/actions?query=workflow%3AWindows+branch%3Amaster+event%3Apush)\n [![macOS Build Status](https://img.shields.io/github/actions/workflow/status/Warzone2100/warzone2100/CI_macos.yml?branch=master\u0026label=macOS\u0026logo=apple)](https://github.com/Warzone2100/warzone2100/actions?query=workflow%3AmacOS+branch%3Amaster+event%3Apush)\n [![Ubuntu Build Status](https://img.shields.io/github/actions/workflow/status/Warzone2100/warzone2100/CI_ubuntu.yml?branch=master\u0026label=Ubuntu\u0026logo=ubuntu\u0026logoColor=FFFFFF)](https://github.com/Warzone2100/warzone2100/actions?query=workflow%3AUbuntu+branch%3Amaster+event%3Apush)\n [![Fedora Build Status](https://img.shields.io/github/actions/workflow/status/Warzone2100/warzone2100/CI_fedora.yml?branch=master\u0026label=Fedora\u0026logo=fedora\u0026logoColor=FFFFFF)](https://github.com/Warzone2100/warzone2100/actions?query=workflow%3AFedora+branch%3Amaster+event%3Apush)\n [![FreeBSD Build Status](https://img.shields.io/cirrus/github/Warzone2100/warzone2100/master?label=FreeBSD\u0026logo=FreeBSD)](https://cirrus-ci.com/github/Warzone2100/warzone2100/master)\n [![Drone Cloud CI ARM64 Build Status](https://img.shields.io/drone/build/Warzone2100/warzone2100/master?label=ARM64%20Linux)](https://cloud.drone.io/Warzone2100/warzone2100)\n [![Packaging status](https://repology.org/badge/tiny-repos/warzone2100.svg)](https://repology.org/project/warzone2100/versions)\n\n### Windows\n\nHow to get the latest Windows development builds:\n1. View the **[latest successful Windows builds](https://github.com/Warzone2100/warzone2100/actions?query=workflow%3AWindows+branch%3Amaster+event%3Apush+is%3Asuccess)**.\n2. Select the latest workflow run in the table / list.\n   This should display a list of **Artifacts** from the run.\n3. Download the `warzone2100_win_x86_portable` or `warzone2100_win_x86_installer` artifact (depending on whether you want the portable build or the full / regular installer).\n\u003e Note: A free GitHub account is currently required to download the artifacts.\n\n### macOS\n\nHow to get the latest macOS development builds:\n1. View the **[latest successful macOS builds](https://github.com/Warzone2100/warzone2100/actions?query=workflow%3AmacOS+branch%3Amaster+event%3Apush+is%3Asuccess)**.\n2. Select the latest workflow run in the table / list.\n   This should display a list of **Artifacts** from the run.\n3. Download the `warzone2100_macOS_universal` or `warzone2100_macOS_universal_novideos` artifact (depending on whether you want the full app bundle or not).\n\u003e Note: A free GitHub account is currently required to download the artifacts.\n\n### Ubuntu\n\nHow to get the latest Ubuntu development builds:\n1. View the **[latest successful Ubuntu builds](https://github.com/Warzone2100/warzone2100/actions?query=workflow%3AUbuntu+branch%3Amaster+event%3Apush+is%3Asuccess)**.\n2. Select the latest workflow run in the table / list.\n   This should display a list of **Artifacts** from the run.\n3. Download the appropriate `warzone2100_ubuntu\u003cversion\u003e_amd64_deb` artifact.\n   - If you are running Ubuntu 20.04: `warzone2100_ubuntu20.04_amd64_deb`\n   - If you are running Ubuntu 22.04: `warzone2100_ubuntu22.04_amd64_deb`\n\u003e Note: A free GitHub account is currently required to download the artifacts.\n4. Extract the contents of the downloaded .zip (`warzone2100_ubuntu\u003cversion\u003e_amd64.deb`) to your Desktop.\n5. Execute the following commands in Terminal:\n```shell\ncd ~/Desktop\nsudo apt install ./warzone2100_ubuntu\u003cversion\u003e_amd64.deb\n```\n6. Download the video for crucial information during the game, for more see \"Videos\" section. Assuming the game is installed in the standard `~/.local/share/` folder, use this command (update `warzone2100-\u003cversion\u003e`):\n```shell\nwget https://github.com/Warzone2100/wz-sequences/releases/download/v3/standard-quality-en-sequences.wz -O ~/.local/share/warzone2100-\u003cversion\u003e/sequences.wz\n```\n\n### Linux (from source)\n\nClone this Git repo and build, following the instructions under:\n[How to Build](#how-to-build)\n\n\u003e Development builds are a snapshot of the current state of development, from the\n\u003e latest (successfully-built) commit. Help testing these builds is always welcomed,\n\u003e but they should be considered a work-in-progress.\n\n### Videos\nYou can download videos from [here](https://github.com/Warzone2100/wz-sequences/releases/tag/v3), or [here](https://sourceforge.net/projects/warzone2100/files/warzone2100/Videos/). You will need to rename the downloaded file to `sequences.wz`, and place it into your Warzone 2100 directory, as described above.\nNote that `.wz` files are just `.zip` in disguise, you can rename it and extract the content if wish to inspect them.\n\nReporting bugs\n--------------\n\nThis game still has bugs and if you run into one, please use the GitHub bugtracker\n(https://github.com/Warzone2100/warzone2100/issues) to report the bug. In order to fix\nthose bugs more quickly, we require that you follow these rules:\n\n   1. If the game crashes you may save a memory dump. Please do so and upload it\n      when reporting the bug. (Linux locates that file at /tmp/warzone2100.gdmp,\n      Windows at /Program Files/Warzone 2100/warzone2100.RPT, macOS by\n      clicking \"Details\" in the crash error message)\n      A self created backtrace is just as useful.\n   2. Give as much information about what you were doing before the crash/bug\n      occurred.\n   3. Try to reproduce the bug and add a description of the process to your bug\n      report.\n   4. You may even upload save files. These consist of one or two file(s) and\n      one folder. All two/three are named after your savegame (e.g.\n      MySaveGame.es, MySaveGame.gam and the folder MySaveGame).\n   5. Bug reports are not submit-and-forget. It may be that you forgot some\n      information or forgot to upload a file. So it is also in your interest to\n      watch the bug-report after it has been submitted. Additionally, you can enable\n      e-mails of comments to your bug report.\n\nConfiguration\n-------------\n\nWarzone 2100 uses its own subdirectory in a user's home directory to save\nconfiguration data, save files and certain other things. Additionally you can\nuse this directory to place custom maps and mods so the game can find them. The\nlocation of this directory depends on the operating system.\n\n### Warzone 2100 directory under GNU/Linux\n\nUnder GNU/Linux, Warzone 2100 conforms to the [XDG base directory spec](https://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html).\n\nBy default, the directory `warzone2100-\u003cversion\u003e` can be found in your home directory\nunder the path `~/.local/share/`.\n(If the `XDG_DATA_HOME` environment variable is defined, the Warzone 2100 folder will\nbe located within `$XDG_DATA_HOME`.)\n\nThe leading dot in the `.local` part of the path indicates that it is a hidden\ndirectory, so depending on your configuration you may not be able to see it.\nHowever, you can still access it by typing the path into your address bar.\n\n### Warzone 2100 directory under Windows\n\nThe directory `Warzone 2100 Project\\Warzone 2100 \u003cversion\u003e` is located under the\n`%APPDATA%` folder.\n\nTypical `%APPDATA%` paths:\n- Windows XP: `\\Documents and Settings\\$USER$\\Application Data`\n- Windows Vista+: `\\Users\\$USER$\\AppData\\Roaming`\n\nHence, the default path for the Warzone 2100 configuration data on Windows Vista+ would be:\n`C:\\Users\\$USER$\\AppData\\Roaming\\Warzone 2100 Project\\Warzone 2100 \u003cversion\u003e\\`\n\nBy default, the `%APPDATA%` folder is hidden. Entering:\n`%APPDATA%\\Warzone 2100 Project\\` into the address bar of Windows Explorer\nwill browse to your Warzone 2100 directory.\n\n### Warzone 2100 directory under macOS\n\nThe directory `Warzone 2100 \u003cversion\u003e` can be found in your home directory at:\n`~/Library/Application Support/`\n\nBy default, recent version of macOS hide your account's Library folder. To view it in\n**Finder**, hold down the **Option (⌥)** key while clicking the **Go** menu, and your Library folder\nwill appear as a menu choice.\n\n### Configuration file\n\nThe configuration file is just called 'config' and contains several configuration\noptions, some of them can be changed by using command-line options or using\nthe in-game menus, others can only be changed by editing the file manually.\n\nIf at any point you did something wrong, you can delete the old configuration\nfile and just restart Warzone 2100. Then the game will regenerate a new\nconfiguration file with default values.\n\nCommand-line options\n--------------------\n\nWarzone 2100 can be started with different options and arguments. For a list\nof these options, run the game with the --help option.\n\nNotes: These options all have two dashes (--), not one dash only (-). Also,\nif the option has an argument, you need to separate the option and its argument\nwith a '=' sign - spaces do not work.\n\nNote: Some options have corresponding entries in the configuration file and will\npersist from one start of Warzone 2100 to the next.\n\nMultiplaying via internet\n-------------------------\n\nThere are two methods to start a multiplayer game via the internet: using the host's\nIP or using the lobby server. Make sure you are able to communicate on TCP ports\n2100 and 9999. Note that for port forwarding, you only need to configure your\nrouter to forward port 2100.\n\nYou can choose whether to connect via Lobby or IP:\n\n* If you choose IP, Warzone 2100 asks you for the IP address of the host and\n  will try to connect to that IP.\n* If you choose Lobby, Warzone 2100 will connect to the lobby server, as long as\n  the lobby-server-address in your config file has not been changed.\n\nYou will see a list of games from which you can select.\n\nYou can kick unwanted players out of a game before it begins by clicking left on\nthem while holding the right mouse button.\n\nWhen you are hosting a game it will automatically be listed on the lobby server.\nIf you do not want your games to be listed on the lobby-server, you should\nchange the entry \"masterserver_name=lobby.wz2100.net\" in your config to some-\nthing invalid, for example: \"nomasterserverplease\".\n\nIf you then want to see the games that are listed on the lobby server you may\nenter \"lobby.wz2100.net\" when prompted to enter the host's IP or change the\nentry in the config file back. You will have to restart Warzone 2100 in order\nfor config changes to take effect.\n\nCheats\n------\n\nLike many other games, Warzone 2100 features a certain set of cheats that can be\nused to have an advantage in the singleplayer-campaign and skirmish-games, or to\njust help mod-makers and map-makers with testing. Cheats do not work in multiplayer,\nunless all players agree to it.\n\nCheats are likely to contain or trigger bugs, so use with care, especially\nduring campaign.\n\n### Entering cheat mode\n\nTo be able cheats while in-game, press shift and backspace simultaneously.\nAn on-screen message should appear telling you that cheat mode has been enabled.\nYou can disable it using the same key combination again.\n\nPressing ctrl+o opens up the debug menu, which is useful for inspecting the\ngame state, or just messing around.\n\n### Cheat commands\n\nAfter activating cheat mode, cheats can be entered using the normal chat-\nfunction. Cheats are ordered by their use and where they can be used.\n\nThere are many cheat commands. Some examples:\n\n* `biffer baker` - Your units do more damage and are stronger\n* `double up` - Your units are twice as strong\n* `give all` - Allows you to build and research everything\n* `work harder` - All currently active research topics are instantly researched\n* `research all` - Everything is researched instantly\n* `let me win` - You win the current campaign mission\n* `superpower` - Gives you maximum power\n* `teach us` - Gives experience to selected units\n* `makemehero` - Makes selected units Heroes\n* `clone wars` - Clones selected units (x10)\n* `clone wars!` - Clones selected units (x40)\n* `clone wars!!` - Clones selected units (x135)\n* `kill` - Kills selected object\n* `john kettley` - Toggles weather conditions\n* `get off my land` - Kills all enemy units and structures\n* `showfps` - Shows average FPS\n* `reload me` - Reloads selected weapon instantly\n* `damage me` - Selected object takes 20% damage\n* `showunits` - Displays unit count information\n* `showorders` - Displays unit order/action state\n* `droidinfo` - Shows unit stats\n\nAll available commands can be found in this file: https://github.com/Warzone2100/warzone2100/blob/master/src/cheat.cpp\n\nModding information\n-------------------\n\nWarzone 2100 AI, maps and campaign can be scripted using JavaScript.\n\nLinks to further information\n* [Scripting](doc/Scripting.md)\n* [Model format](doc/PIE.md)\n* [Animation](doc/Animation.md)\n\nHow to build\n-------------------\n\n### Getting the Source\n\nTo properly build the game, either:\n- Download a release `tar.xz`, which contains all the source code and revision information.\n\n  _OR_\n\n- Clone the Git repo:\n  ```shell\n  git clone https://github.com/Warzone2100/warzone2100.git\n  cd warzone2100\n  git fetch --tags\n  git submodule update --init --recursive\n  ```\n  \u003e Note: Initializing submodules is required.\n\nDo **not** use GitHub's \"Download Zip\" option, as it **does not contain submodules** or the Git-based autorevision information.\n\n### Linux\n\n* Prerequisites\n   * Compiling tools (ex. CMake, GCC/G++/Clang, ninja-build)\n   * Archiving tools (ex. zip, p7zip)\n   * Various libraries:\n      * [SDL](https://www.libsdl.org) ≥ 2.0.5 _(strongly recommended: ≥ 2.0.20)_\n      * [PhysicsFS](https://icculus.org/physfs/) ≥ 2.0.3-3 _(strongly recommended: ≥ 3.0.2)_\n      * [libpng](https://www.libpng.org/pub/png/libpng.html) ≥ 1.2\n      * [libtheora](https://theora.org)\n      * [libvorbis](https://xiph.org/vorbis)\n      * [libogg](https://xiph.org/ogg/)\n      * [opus](https://github.com/xiph/opus)\n      * [Freetype](https://www.freetype.org/) _(strongly recommended: ≥ 2.10.4)_\n      * [Harfbuzz](https://github.com/harfbuzz/harfbuzz) ≥ 1.0 _(strongly recommended: ≥ 3.3.0)_\n      * [fribidi](https://github.com/fribidi/fribidi)\n      * [OpenAL-Soft](https://openal-soft.org)\n      * [libcurl](https://curl.haxx.se/libcurl/) _(strongly recommended: ≥ 7.58.0)_\n      * [libsodium](https://github.com/jedisct1/libsodium) ≥ 1.0.14\n      * [SQLite](https://www.sqlite.org/index.html) ≥ 3.14\n   * For language support: [Gettext](https://www.gnu.org/software/gettext/)\n   * To generate documentation: [Asciidoctor](https://asciidoctor.org) ≥ 1.5.3\n   * To build with Vulkan support: the full [Vulkan SDK](https://vulkan.lunarg.com/sdk/home) _(strongly recommended: ≥ 1.2.148.1)_\n* **Installing prerequisites:**\n   * Using `get-dependencies_linux.sh`:\n      1. Specify one of the linux distros supported by the script: (`ubuntu`, `fedora`, `alpine`, `archlinux`, `opensuse-tumbleweed`) _REQUIRED_\n      2. Specify a mode: (`build-all` (default), `build-dependencies`) _OPTIONAL_\n\n      Example:\n      ```shell\n      sudo ./get-dependencies_linux.sh ubuntu build-dependencies\n      ```\n* **Building from the command-line:**\n   1. Starting from the _parent_ directory of the warzone2100 source code (which is assumed to be in a folder named `warzone2100`), create a **sibling** build directory:\n      ```shell\n      mkdir build\n      ```\n   2. Change directory into the sibling `build` directory:\n      ```shell\n      cd build\n      ```\n   3. Run CMake configure to generate the build files:\n      ```shell\n      cmake -DCMAKE_BUILD_TYPE=RelWithDebInfo -DCMAKE_INSTALL_PREFIX:PATH=~/wz/install -GNinja ../warzone2100\n      ```\n      \u003e - [Modify the `CMAKE_INSTALL_PREFIX` parameter value as desired](https://cmake.org/cmake/help/latest/variable/CMAKE_INSTALL_PREFIX.html) to configure the base installation path.\n      \u003e - The `../warzone2100` path at the end should point to the warzone2100 source directory.\n   4. Run CMake build:\n      ```shell\n      cmake --build . --target install\n      ```\n\n### Windows using MSVC\n\n* Prerequisites\n   * **Visual Studio 2022** (Visual Studio 2017-2019 may work, but 2022+ is strongly encouraged)\n      - If you do not already have Visual Studio installed, you can download the free **Visual Studio Community** from: https://developer.microsoft.com/en-us/windows/downloads\n      - IMPORTANT: You need the fully-featured Visual Studio IDE. “Visual Studio Code” does not include the necessary support for building C++ Windows apps.\n   * **CMake 3.20+** (https://cmake.org/)\n   * **Git** (if not building from a release source archive)\n   * **7-Zip** (https://www.7-zip.org)\n   * **Vulkan SDK 1.2.148.1+** (https://vulkan.lunarg.com/sdk/home)\n      - Required only if you want to build with Vulkan support.\n* **Preparing to build:**\n   Build dependencies are provided via [vcpkg](https://github.com/Microsoft/vcpkg) from Microsoft.\n   * Run the `get-dependencies_win.ps1` script from powershell in order to download and build the dependencies.\n* **Building from the command-line:**\n   * Change directory to the warzone2100 repo directory\n   * Configure\n      * Visual Studio 2022: `cmake -H. -DCMAKE_TOOLCHAIN_FILE=vcpkg\\scripts\\buildsystems\\vcpkg.cmake -Bbuild -G \"Visual Studio 17 2022\"`\n      * Visual Studio 2019: `cmake -H. -DCMAKE_TOOLCHAIN_FILE=vcpkg\\scripts\\buildsystems\\vcpkg.cmake -Bbuild -G \"Visual Studio 16 2019\"`\n      * Visual Studio 2017: `cmake -H. -DCMAKE_TOOLCHAIN_FILE=vcpkg\\scripts\\buildsystems\\vcpkg.cmake -Bbuild -G \"Visual Studio 15 2017\"`\n   * Build\n      * Release: `cmake --build build --config Release`\n      * Debug: `cmake --build build --config Debug`\n* **Building using Visual Studio:**\n   1. Open Visual Studio\n   2. Open the warzone2100 folder using **File** \u003e **Open** \u003e **Folder...**\n      - Allow Visual Studio some time to load the project and retrieve information from CMake.\n   3. Create a VS CMake settings JSON file using **CMake** \u003e **Change CMake settings**. You can also reach this dialog by clicking \"Manage Configurations\" in the configuration dropdown in the toolbar. Make sure the CMake components in Visual Studio are installed (by running the Visual Studio Installer).\n      - This creates `CMakeSettings.json`\n   4. Add the following variables to `CMakeSettings.json`:\n      - To `cmakeCommandArgs`, add: `-DCMAKE_TOOLCHAIN_FILE=vcpkg\\scripts\\buildsystems\\vcpkg.cmake`\n      - Note: Visual Studio automatically escapes and turns each `\\` into `\\\\`\n   5. After letting Visual Studio re-run CMake configure with the new settings, you can build using the **CMake** menu.\n\n### macOS\nSee [platforms/macos/README.md](platforms/macos/README.md)\n\nLicensing\n-------------------\n\nWarzone 2100 is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.\n\n[![SPDX-License-Identifier: GPL-2.0-or-later](https://img.shields.io/static/v1?label=SPDX-License-Identifier\u0026message=GPL-2.0-or-later\u0026color=blue\u0026logo=open-source-initiative\u0026logoColor=white\u0026logoWidth=10\u0026style=flat-square)](COPYING)\n\nMore information: [COPYING.README](COPYING.README), [COPYING.NONGPL](COPYING.NONGPL)\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2FWarzone2100%2Fwarzone2100","html_url":"https://awesome.ecosyste.ms/projects/github.com%2FWarzone2100%2Fwarzone2100","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2FWarzone2100%2Fwarzone2100/lists"}