- Assigned to you:
- No blueprints or bugs assigned to you.
- No users assigned to blueprints and bugs.
- No blueprints are targeted to this milestone.
- No bugs are targeted to this milestone.
Download files for this release
The Widelands Development Team is proud to announce the immediate availability of build 17 of Widelands. Widelands is a free, cross-platform strategy game in which players control the fate of a small tribe that can grow into a big empire, in a style of play that is unique in the open source world. Please visit our homepage http://
Some of the highlights of this build are:
* Basic sea-faring functionality.
* Improvements to the Editor.
* Multiplayer scenarios (Fun maps).
* Support for dismantling buildings.
* Support to adjust the number of wares in a building.
* a new in-game help for many buildings. Work is ongoing.
* Improved in-game statistics.
* Improved rendering engine.
* new maps, sounds, music, graphics & animations.
As usual, there have been many more improvements to the usability and performance, as well as numerous game-play improvements and bug-fixes.
Widelands is currently translated to 100% into the following languages: German, Italian. It is > 80% translated into the following languages: Polish, French, Slovak, Czech, Spanish, Dutch, Brazilian, Swedish, Russian, Portuguese. You can help out translating directly in your web browser: http://
Widelands uses SDL as graphics and input library and is currently available for Windows (32-bit) and Mac OS X (Intel) and in source code. We no longer ship binary Linux packages because of the poor compatibility between Linux distributions. Instead, we try to make compiling for Linux users as easy as possible. Also, most distributions will pick up build 17 into their repositories very quickly. Both binary and source packages are available from http://
Simply download the binary package for your operating system and run the widelands executable! If your operating system is not supported, download a source package and try to compile it for yourself. See the homepage for the libraries you need to have installed.
If you like what you see, please visit our homepage, http://
We especially welcome every helping hand, even if you just want to contribute by helping us find bugs. Also translators for all languages are always needed. If you want to get even more involved in the further development of Widelands, you can subscribe to widelands-
Widelands Build 17 takes us a good step forward towards a stable 1.0 version. However, as Widelands is still under heavy development, there are some unfinished features and minor known bugs that haven't been fixed until the release of Build 17. The following list is not meant to be complete, but is supposed to help you avoiding known problems and handling them if they appear.
1st) Compile time issues
* Widelands does not compile, if using gcc 4.7. Fix: add "#include <unistd.h>" to the file "src/main.cc"
2nd) Unfinished feature "seafaring" issues
Build 17 ships with the very basics of the new "seafaring" feature. Many sub-features are not yet implemented, so don't waste your time searching for them ;).
The limitations are as follows:
* It is not possible to colonize other islands, just transport between existing ports.
* There are no "rowboat roads" yet.
* Computer players do not use seafaring.
* The only official map supporting seafaring is the multiplayer scenario "Together we're strong" (Start it in scenario mode!)
* On maps without port buildspaces, the shipyard is buildable, but will not produce ships.
* On maps with port buildspaces, it might happen that ships are build in small lakes, so best place shipyards near the coast but away from smaller lakes.
3rd) OpenGL rendering issues
* The "smooth" rendering of the terrain does not work on all graphics chips.
4th) Other known bugs
* Editor: Unable to reload a self created map in the editor. A workaround can be found at: https:/
* Campaign: Games from the atlantean campaign saved in Build16 are playable in Build17, but can't be won.
0 blueprints and 0 bugs targeted
There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.