In order to simplify how things are done with this project, we have a
new streamlined approach on how to handle things.
If you want to contribute to the project, you really should make an
account on github, and clone our repository located at
Once you have cloned the project, you are now free to do whatever you wish.
Now that you have your very own repository, fix what you have to fix,
or create what you want to create, and then submit a ticket on trac
http://developer.wz2100.net/newticket, with either a link to your
cleaned patch, or a patch that can be applied with the ticket, and a
good description of what you are showing us.
Please don't just do merge requests from github, since the way github
handles it is subpar.
See https://github.com/isaacs/github/issues/2 &
https://github.com/isaacs/github/issues/5 for some more reasons why.
We also encourage you to use the forum to state your intentions on
what your plans are, that way, you will get feedback, and establish
Also note, that some patches won't be accepted if they alter the core
game in a manner that is deemed unfit. This is also why it is a good
idea to get some feedback before you start working on a patch.
We don't want someone making Warzone 2100 into a FPS. While you could,
and that very well may be a fun project, this project is about making
the best RTS game possible, with the motto "Strategy by Design". It
would be better to just fork Warzone, and proceed accordingly.
You should also squash all your *related* commits (changes) into one
patch *before* you submit your final patch to us.
For more information about this, please see
http://developer.wz2100.net/wiki/CommitGuidelines step 6.
For translations, we will apply your patch before we do the next
release, usually in the RELEASE CANDIDATE PHASE.
For patches to the code, we will first do a code review to see if the
fix really does fix the issue at hand, and if so, we will usually
apply after the review was done, if no issues were found.
Please note, when writing code, please follow the style guideline
located here http://developer.wz2100.net/wiki/CodingStyle
For patches for anything else, the rule of thumb is, if it fixes
something that is broken, then there is a high chance that it will be
applied as soon as can be verified.
If it is simply updating libraries or other trivial issues, then we
will wait until the RELEASE CANDIDATE PHASE to apply said patch.
Get latest updates about Open Source Projects, Conferences and News.