-
-
Notifications
You must be signed in to change notification settings - Fork 516
Home
Useful links: Compile Guide • Wiki timeline • Ticket timeline • Commit timeline
Version 3.1 game mechanics, including all researchable technologies, are listed in the Beta Guide.
For older versions, select an appropriate version of the older guide from web.archive.org.
You might also want to learn about
- CommandLine Options
- Cheats (for versions 2.2 and lower, try this page
- File Locations
- Configuration Options
- Keyboard Shortcuts
Also read the FAQ, visit Warzone 2100 Atlassian and use the forums.
If you are missing the campaign videos, get them here.
Our Addons page offers lots of maps and mods, and much more can be found via the forums.
Even before a new version is released, you can download it as version "master" from our latest development builds to try it.
Installation instructions are found in our Compile Guide. Be sure to provide feedback!
Recommended links to learn what developers are currently planning:
- Development section of the forums
- [Outstanding tickets]
- Commit timeline
Want to see Warzone improved in some way? Discuss it in the Suggestions forum section.
Bug reports are appreciated. If you are unfamiliar with Trac, read our article on Bug Reporting. To ensure the developers can succeed in finding a solution, it is very important that your problem description is as detailed, precise and specific (smart!) as possible. Attached log files, screenshots and perhaps even a video can be essential to understanding a problem.
Please do not add feature requests to the bug tracker unless you have a working patch you want us to consider. Always keep in mind that that our developers work out of their own choice in their spare time and your wish list might differ from theirs. In Open Source there is the expectation that you will attempt something yourself before expecting others to help you. Rather than making demands, think about what you personally could contribute to the project.
The wiki needs more editors. Feel free to contribute / suggest changes!
Apart from the forums, there are a few other online communities dedicated to this game. Russian speakers might like the Warzone 2100 VK page.
Most developer communication happens on IRC and in the issue tracker. There is also a low-volume email list that is used for important communications. All new tickets in the issue tracker are also sent to the email list.
We use the Freenode IRC network. The IRC channel for gamers is #warzone2100-games, developer talk happens on #warzone2100-dev (you need a registered nickname to join this channel), and #warzone2100 is for general discussions, tech support and small talk.
Warzone can be translated into other languages. We don't speak all of those, so we need your help.
For editing maps, there are currently three options:
- EditWorld by Pumpkin Studios
- FlaME (forums thread), the most popular tool, written in Visual Basic. Can run on Linux via Mono.
- SharpFlame (forums thread), a portable and modern fork of FlaMe written in C#
Read Mods and Maps on how to edit mods and maps. Also make use of these links:
You should visit the Artwork page as well as the Artwork forums section and view these artwork galleries.
The leading effort to improve game graphics is made by Art Revolution (forums thread). Please contribute if you can.
If you want to improve the AI, start with the AI Tutorial. For the SemperFi AI, also visit its wiki page.
Many AIs have been created, and some have been all but forgotten. For an overview of currently relevant ones, look at the results of EuPhobos' AI tournament.
Especially important are NullBot (description, forums thread) and BoneCrusher.
New AIs are usually written in JavaScript and presented here.
We use C++ and git. To start, read the Coding page and learn about the Repository Structure.