The Battle for Wesnoth Wiki - User contributions [en]

BuildingMaps

2016-10-26T03:34:01Z

Tr0ll: typo

{{Create}}

<div class="thumb tright"><div>
[http://www.wesnoth.org/images/sshots/wesnoth-1.11.8-4.jpg http://www.wesnoth.org/images/sshots/wesnoth-1.11.8-4-175.jpg]
<div class="thumbcaption">Map editor</div></div>
</div>

A map is the most basic of user made content you can create. Complex scenarios can be developed on them, or they can be played on their own as simple battlefields with no extra work required.

Wesnoth features a fully featured map editor, accessible from the Map Editor option at the main menu. Inside you will find all the tools you need to create your own arenas to stage your adventures.

Inside the individual map files themselves are simply terrain codes that the games translates into graphics when you play. Usually you will never have to edit these files manually, but it can come in handy to understand the format. For more on terrain codes and the map data format, see the [[TerrainCodesWML]] page.

For further instructions on what to do once you have completed your map, see below.

== Creating a map ==

=== Note before you start ===

As of Wesnoth 1.12, the Map Editor has become more fully featured, and includes options to define scenario-related items on your map, such as name, unit placement, graphical items, time of day schedules, etc. In order to create a plain map file with no scenario data, use the File → Save Map option. Scenario-specific content will not be saved unless you select the File → Save Scenario option. 

More on scenario-specific content is discussed in [[BuildingScenarios]].

=== General guide to map making ===

When you first open the map editor, you are presented with a large blank canvas covered in Grass. Below is a general guide to turning this empty meadow into an interesting and challenging battlefield.

#Decide on the intended use Maps intended to use in a campaign usually portray a location relative to the story being told, while maps intended for use in multiplayer usually have a more "arena-like" quality to them - they're usually symmetrical, feature many types of terrains to benefit all units, and are often in not-rectangle shapes. 
#Choose your map size You can resize your map with the resize function. Choose one proportional to the gameplay you would like to see on it. A close-knit battle arena? Smaller is better. A large epic, battle with many sides? Go larger. Remember, though, to not make it too big, or you will bore your players. 
#Decide on a theme Wesnoth includes many different terrains for many different situations. Caves, dungeons, meadows, icy wastes, beautiful fall scenery, etc. Decide on a general theme for your map and be sure to work with the terrains that best fit your chosen theme. 
# Place large geographic features first If you were designing an outdoors map, now would be the time to draw large features such as mountain ranges, rivers, etc. On an indoors map, place the walls, design the passages and rooms, etc. It doesn't have to be perfect, just a general outline to work with. 
# Add castles, villages, and roads Every map needs castles and keeps to recruit on, and roads or flat terrain for units to move on (most units move best on Flat terrain such as roads, grass, or dirt). Add these now, making sure not to make your castles too big or close to one another. The placement of these determines the general flow of your scenario, so choose carefully. Also add villages. These will provide your team income and healing, so don't place them too close to each other (a general rule is about 6 hex radius (at minimum) around each village). Too many close together will result in imbalance from too much gold and health regeneration. 
# Finer details and revision Begin filling in the more open spaces of your map. Add forests, trees, hills, dirt, floors, the lot, while at the same time tweaking the general layout to fit your intended design. This is where the map really begins to reach completion. Also note to be sure to draw terrain features in a way that work with your plans for the scenario; for example, be sure to place bridges where you want your units to be able to cross a river. 
# Embellishments Your map is almost complete, but in order to look polished, throw in a few embellishments. Make the grass different colors. Put rocks and mud in the rivers. Strew trash around your buildings. Scatter flowers in the meadows. It's up to you, just don't overdo it.

It can take a lot of practice. Making good, balanced, interesting maps is an art unto itself. ESR has more handy tips in his [http://catb.org/~esr/wesnoth/campaign-design-howto.html#_map_composition Campaign Design How-To] article. You can also ask for assistance on the [http://www.wesnoth.org/forum/viewforum.php?f=15 Multiplayer Development forum].

== Now what? ==

You've created an awesome map with the map editor, but now what? It's actually quite simple.

=== Play your map ===

If you just want to play the map, maybe against the computer or with a friend, all you have to do is save it into the map editor's folder (the default location). Then, when you launch the game and host a multiplayer game, the map should appear at the top of the map choices screen.

When creating a game on the multiplayer server, your map will be described to other players as a "User Map" and any replays stored on the server will refer to the game as "User Map."

For the curious: Saving a map file like this creates a stand-alone file that holds the map data. That file is by default saved in userdata/editor/maps/, and maps in that location are added to the top of the multiplayer map selection list.

=== Use your map in a scenario ===

If you're interested in more complex gameplay, you can use your map in a scenario. More information on how to proceed is on the [[BuildingScenarios]] page.

=== Share your map ===

When you're ready to share your map with the world, post it to the [http://www.wesnoth.org/forum/viewforum.php?f=15 Multiplayer Development forum] or package it to be distributed on the in-game add-ons server. For instructions on how to distribute maps, see [[Distributing_content]]

== See Also ==

* [[TerrainCodesWML]]
* [[ScenarioWML]]
* [[ReferenceWML]]

SavefileWML

2016-10-26T03:18:13Z

Tr0ll:

{{WML Tags}}
== The format for Wesnoth savegames ==

A Wesnoth savegame is a file stored in '''~saves/''' (See "user data directory", [[PreprocessorRef]]).
n order to view or modify these files, the option Compressed Saves (Advanced Preferences) must be set to "No". Also, since they are not config(.cfg) files the normal coloring will not be generated. To generate coloring, simply save the file as .cfg, then open it again.

There are 3 types of savegames: Start-of-scenario, replay and in-game (including autosave and out-of-sync save). The information included in a save depends on its type.

{|
|-
| || Start-of-scenario || Replay || In-game
|-
| General info and statistics || Yes || Yes || Yes
|-
| [snapshot] || No || No || Yes
|-
| [replay] || No || Yes || Yes
|-
| [replay_start] || No || Yes || Yes
|-
| [carryover_sides] || No || Yes || Yes
|-
| [carryover_sides_start] || Yes || Yes || Yes
|}

{{DevFeature1.13|0}} There are 4 types of savegames: Start-of-scenario, replay and in-game (including autosave and out-of-sync save). The information included in a save depends on its type.

{|
|-
| || Start-of-scenario || Expanded Start-of-scenario || Replay || In-game
|-
| General info and statistics || Yes || Yes || Yes || Yes
|-
| [snapshot] || No || No || No || Yes
|-
| [replay] || No || No || Yes || Yes
|-
| [replay_start] || No || No || Yes || Yes
|-
| [carryover_sides] || No || No || Yes || Yes
|-
| [carryover_sides_start] || Yes || Yes || No || No
|-
| [scenario] || No || Yes || No || No
|}

{{DevFeature1.13|0}} There are also 2 types of Server generated replays
{|
|-
| || Fresh game || Start-of-scenario || Reloaded game
|-
| General info and statistics || Yes || Yes || Yes
|-
| [snapshot] || No || No || Yes
|-
| [replay] || Yes || Yes || Yes
|-
| [replay_start] || No || No || Yes
|-
| [carryover_sides] || No || No || Yes
|-
| [carryover_sides_start] || Yes || Yes || No
|-
| [scenario] || Yes || Yes || No
|}

'''General info and statistics'''

Contains general information about the scenario, campaign and version of Battle for Wesnoth the savegame is from. This information is included in all savegames.
Not all tags of this section are explained here.

* '''version''': The version of Wesnoth this game was saved by. If the savegame is from a different version of Wesnoth than the one currently running, the message "This save is from a different version of the game. Do you want to try to load it?" is displayed
* '''campaign_type''': Whether the scenario is a scenario or multiplayer.
* '''campaign_define''': When this replay is loaded, the symbol campaign_define will be stored. See also "#ifdef", [[PreprocessorRef]]
* '''difficulty''': The difficulty level of the savegame. Normal values are "EASY", "NORMAL", and "HARD".
* '''label''': heading of the save
* '''next_scenario''': Name of the next scenario in a campaign
* '''scenario''': Name of the current scenario
* '''[multiplayer]''': If the game is a multiplayer game, multiplayer information is inculded here
* '''[statistics]''': Describes previous scenarios
** '''mid_scenario''': If "false", the scenario will be reloaded and any modifications will be played with.
** '''[scenario]''': Describes basic statistics of a previous scenario. See [[StatisticalScenarioWML]] for a description of [scenario]

'''[snapshot]'''

The [snapshot] describes the current state of the game in an in-game save. It has the same format as the rest of the savefile and holds the map of the scenario. The snapshot is loaded when “Show replay” is not selected.

* '''playing_team''': the number of the team whose turn it is, starting with 0
* '''turn_at''': The number of the current turn
* '''map_data''': The data for the map. The mini-map generated by this data is displayed to the right

'''[replay_start]'''

[replay_start] is a full snapshot of the start of the first turn of a scenario. It describes the position the player was in when the game started and is used as starting point for replays.

'''[replay]'''

The [replay] contains everything that happened in the scenario since it started.

* '''[command]''': Describes one action. Syntax for [command] is described in [[ReplayWML]]

'''[carryover_sides_start]'''

[carryover_sides_start] contains the carryover data from the previous scenario, like retained gold and units. It is also used to store in-game data required in the next level, such as variables, the random seed and menu items. [carryover_sides_start] retains the data throughout the scenario.

* '''random_calls''' and '''random_seed''': Used to determine and synchronize random events in the game
* '''[side]''': Player information, retained gold, recruits and recalls for all sides in the game
* '''[end_level_data]''': Contains the information how the carryover data should be used.*
* '''[variables]''': a list of the current values of all variables. The attribute variable//=//value// means that the variable variable has the value value. The tag [array//]describes a unit stored in the array array (see [[SingleUnitWML]]). See also [[VariablesWML]]
* '''[menu_item]''': Custom WML menu items

'''[carryover_sides]'''

[carryover_sides] is a copy of the data in [carryover_sides_start]. Anything to be used in the new scenario is removed from [carryover_sides]. At the end of the scenario the carryover for the next scenario is added to what is left in [carryover_sides].

'''[scenario]'''

{{DevFeature1.13|0}} Expanded Start-of-scenario saves are almost the same as normal start-of-scenario saves, except that they also contain the start [scenario] so it doesnt need to be read from the game config
This type of savegame is mostly used internally, especialy this type of save is used at the beginning of a fresh networked mp game, where this host sends this type of savefile to the other clients, which is then loaded by them.

But in theory the game can also read an expanded start-of-scenario save from disk.

== See Also ==
* [[ReferenceWML]]

[[Category: WML Reference]]

SavefileWML

2016-10-26T03:17:07Z

Tr0ll:

{{WML Tags}}
== The format for Wesnoth savegames ==

A Wesnoth savegame is a file stored in '''~saves/''' (See "user data directory", [[PreprocessorRef]]).
n order to view or modify these files, the option Compressed Saves (Advanced Preferences) must be set to "No". Also, since they are not config(.cfg) files the normal coloring will not be generated. To generate coloring, simply save the file as .cfg, then open it again.

There are 3 types of savegames: Start-of-scenario, replay and in-game (including autosave and out-of-sync save). The information included in a save depends on its type.

{|
|-
| || Start-of-scenario || Replay || In-game
|-
| General info and statistics || Yes || Yes || Yes
|-
| [snapshot] || No || No || Yes
|-
| [replay] || No || Yes || Yes
|-
| [replay_start] || No || Yes || Yes
|-
| [carryover_sides] || No || Yes || Yes
|-
| [carryover_sides_start] || Yes || Yes || Yes
|}

{{DevFeature1.13|0}} There are 4 types of savegames: Start-of-scenario, replay and in-game (including autosave and out-of-sync save). The information included in a save depends on its type.

{|
|-
| || Start-of-scenario || Expanded Start-of-scenario || Replay || In-game
|-
| General info and statistics || Yes || Yes || Yes || Yes
|-
| [snapshot] || No || No || No || Yes
|-
| [replay] || No || No || Yes || Yes
|-
| [replay_start] || No || No || Yes || Yes
|-
| [carryover_sides] || No || No || Yes || Yes
|-
| [carryover_sides_start] || Yes || Yes || No || No
|-
| [scenario] || No || Yes || No || No
|}

{{DevFeature1.13|0}} There are also 2 types of Server generated replays
{|
|-
| || Fresh game || Start-of-scenario || Reloaded game
|-
| General info and statistics || Yes || Yes || Yes
|-
| [snapshot] || No || No || Yes
|-
| [replay] || Yes || Yes || Yes
|-
| [replay_start] || No || No || Yes
|-
| [carryover_sides] || No || No || Yes
|-
| [carryover_sides_start] || Yes || Yes || No
|-
| [scenario] || Yes || Yes || No
|}

'''General info and statistics'''

Contains general information about the scenario, campaign and version of Battle for Wesnoth the savegame is from. This information is included in all savegames.
Not all tags of this section are explained here.

* '''version''': The version of Wesnoth this game was saved by. If the savegame is from a different version of Wesnoth than the one currently running, the message "This save is from a different version of the game. Do you want to try to load it?" is displayed
* '''campaign_type''': Whether the scenario is a scenario or multiplayer.
* '''campaign_define''': When this replay is loaded, the symbol campaign_define will be stored. See also "#ifdef", [[PreprocessorRef]]
* '''difficulty''': The difficulty level of the savegame. Normal values are "EASY", "NORMAL", and "HARD".
* '''label''': heading of the save
* '''next_scenario''': Name of the next scenario in a campaign
* '''scenario''': Name of the current scenario
* '''[multiplayer]''': If the game is a multiplayer game, multiplayer information is inculded here
* '''[statistics]''': Describes previous scenarios
** '''mid_scenario''': If "false", the scenario will be reloaded and any modifications will be played with.
** '''[scenario]''': Describes basic statistics of a previous scenario. See [[StatisticalScenarioWML]] for a description of [scenario]

'''[snapshot]'''

The [snapshot] describes the current state of the game in an in-game save. It has the same format as the rest of the savefile and holds the map of the scenario. The snapshot is loaded when “Show replay” is not selected.

* '''playing_team''': the number of the team whose turn it is, starting with 0
* '''turn_at''': The number of the current turn
* '''map_data''': The data for the map. The mini-map generated by this data is displayed to the right

'''[replay_start]'''

[replay_start] is a full snapshot of the start of the first turn of a scenario. It describes the position the player was in when the game started and is used as starting point for replays.

'''[replay]'''

The [replay] contains everything that happened in the scenario since it started.

* '''[command]''': Describes one action. Syntax for [command] is described in [[ReplayWML]]

'''[carryover_sides_start]'''

[carryover_sides_start] contains the carryover data from the previous scenario, like retained gold and units. It is also used to store in-game data required in the next level, such as variables, the random seed and menu items. [carryover_sides_start] retains the data throughout the scenario.

* '''random_calls''' and '''random_seed''': Used to determine and synchronize random events in the game
* '''[side]''': Player information, retained gold, recruits and recalls for all sides in the game
* '''[end_level_data]''': Contains the information how the carryover data should be used.*
* '''[variables]''': a list of the current values of all variables. The attribute variable//=//value// means that the variable variable has the value value. The tag [array//]describes a unit stored in the array array (see [[SingleUnitWML]]). See also [[VariablesWML]]
* '''[menu_item]''': Custom WML menu items

'''[carryover_sides]'''

[carryover_sides] is a copy of the data in [carryover_sides_start]. Anything to be used in the new scenario is removed from [carryover_sides]. At the end of the scenario the carryover for the next scenario is added to what is left in [carryover_sides].

'''[scenario]'''

{{DevFeature1.13|0}} Expanded Start-of-scenario saved are almost the same as normal start-of-scenario saves, except that they also contain the start [scenario] so it doesnt need to be read from the game config
This type of savegame is mostly used internaly, especialy this type of save is used at the beginning of a fresh networked mp game, where this host sends this type of savefile to the other clients. which is then loaded by them

But in theory the game can also read an expanded start-of-scenario save from disk.

== See Also ==
* [[ReferenceWML]]

[[Category: WML Reference]]

SpellingMistakes

2016-01-01T22:46:25Z

Tr0ll: /* Tutorial */

SpellingMistakes

2015-06-29T01:55:53Z

Tr0ll: /* Tutorial */

SpellingMistakes

2015-06-29T01:55:02Z

Tr0ll: /* Tutorial */

Talk:Download

2013-03-10T00:35:07Z

Tr0ll: link to discussion on forum

[http://forums.wesnoth.org/viewtopic.php?f=17&t=38476 A forum topic for this page]

Download

2013-03-10T00:20:02Z

Tr0ll: Undo revision 48678 by Marsianen (Talk)

{{Download/Translations}}
Welcome to the Battle for Wesnoth downloads page. The BFW project team only officially releases the source code. Binary packages are only provided by community volunteers and hosted here. Torrents are also unofficial.

If the latest binaries are not currently available for your OS, please check back in a few days to see if they have been placed here. Packagers have been informed of the release, please be patient. In the meantime, read the [[FAQ#A_new_version_is_out.2C_but_where_is_the_download_for_.5BWindows.2C_Mac_OS.2C_etc..5D.3F|FAQ]].

__NOTOC__
Jump to: [[Download#Stable_.281.10_branch.29|Stable Branch]] | [[Download#Stable_.28older_versions.29|Stable Branch (older versions)]] | [[Download#Development_.281.11_branch.29|Development Branch]]

== Stable (1.10 branch) ==
The stable files are meant to be used as a stable and rather balanced version of the game. Each version of the 1.10 branch is compatible to each other.

Version 1.10.5 is the latest stable version. This version is recommended for most players since the 1.10 online multiplayer community is very large and user-made campaign server has a robust content selection.

==== Source code ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.5/wesnoth-1.10.5.tar.bz2/download Current Version] (1.10.5, 327.7 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.4/wesnoth-1.10.4.tar.bz2/download Previous Version] (1.10.4, 326.8 MB)

* [[CompilingWesnoth|Compiling Guide]] - how to compile the source code

==== MS Windows ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.5/wesnoth-1.10.5-win32.exe/download Current Version] (1.10.5, 301.2 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.4/wesnoth-1.10.4-win32.exe/download Previous Version] (1.10.4, 300.6 MB)

==== Mac OS X (10.5+) ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.5/Wesnoth_1.10.5.dmg/download Current Version] (1.10.5 328.8 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.4/Wesnoth_1.10.4.dmg/download Previous Version] (1.10.4 328.1 MB)

==== GNU/Linux ====
* There are binaries for many different GNU/Linux Distributions. Not all are always up to date with the current release. Please have a look at the [[WesnothBinariesLinux|Linux binary page]] for more information about the binaries for your Distribution.

==== OpenPandora ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.5/wesnoth-1.10.5-1.pnd/download Current Version] (1.10.5-1, 320.5 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.4/wesnoth-1.10.4-1.pnd/download Previous Version] (1.10.4-1, 319.7 MB)

==== Miscellaneous ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.5/wesnoth-1.10.5.tar.bz2.md5/download md5sum for current source code]
* [http://www.wesnoth.org/wiki/Download_Xdeltas#Stable_Version_1.10.x Xdelta for the source code]
* [http://sourceforge.net/projects/wesnoth/files/ SourceForge page for current and all previous versions]

== Stable (older versions) ==
Several operating systems do not offer a binary of the latest stable release. Here is a list of the latest known (stable version) binaries for various systems. For those older versions there often is no (official) multiplayer or addon server available anymore.

==== AmigaOS4 ====
* [http://www.amigasoft.net/pages/games/download/Wesnoth186.lha.lzh Older Version] (1.8.6, 300MB)

==== (Open)Solaris ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.4/wesnoth-1.4.5/wesnoth-solaris-i386-1.4.5.pkg.bz2/download Older Version] (1.4.5, 145.6 MB), not compatible with 1.6.x

==== OS/2 & eComStation ====
* [http://download.smedley.info/wesnoth-1.4.5-os2-20080828.zip Older Version] (1.4.5, 160 MB), not compatible with 1.6.x

==== RISC OS ====
*[http://www.riscos.info/packages/arm/Games/wesnoth_1.4.5-1.zip Older version] (1.4.5-1, 140MB), not compatible with 1.6.x

==== Syllable ====
* [http://downloads.syllable.org/Syllable/i586/applications/contributed/Battle-for-Wesnoth/Battle-for-Wesnoth-1.2.6.application Older Version] (1.2.6, 60.8 MB), not compatible with 1.6.x

== Development (1.11 branch) ==
Version 1.11.x is the latest development version, boasting updated graphics and new exciting features. However, there may be occasional bugs or performance problems in the development versions since heavy changes are taking place all the time. For balanced and stable gaming, it is recommended you use the latest version of the 1.10.x branch. This version is recommended for coders and campaign developers, as well as those who want to preview the future of Wesnoth. People familiar with SVN and compiling can follow the latest development by checking [[WesnothSVN]].

==== Source code ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.1/wesnoth-1.11.1.tar.bz2/download Current Version] (1.11.1, 338.8 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.0/wesnoth-1.11.0.tar.bz2/download Previous Version] (1.11.0, 334.1 MB)

* [[CompilingWesnoth|Compiling Guide]] - how to compile the source code

==== MS Windows ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.1/wesnoth-1.11.1-win32.exe/download Current Version] (1.11.1, 312.0 MB))
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.0/wesnoth-1.11.0-win32.exe/download Previous Version] (1.11.0, 307.8 MB))

==== Mac OS X (10.5+) ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.1/Wesnoth_1.11.1a.dmg/download Current Version] (1.11.1 338.9 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.0/Wesnoth_1.11.0.dmg/download Previous Version] (1.11.0 334.4 MB)

==== GNU/Linux ====
* There are binaries for many different GNU/Linux Distributions. Not all are always up to date with the current release. Please have a look at the [[WesnothBinariesLinux|Linux binary page]] for more information about the binaries for your Distribution.

==== OpenPandora ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.1/wesnoth-1.11.1-1.pnd/download Current Version] (1.11.1-1, 330.3 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.0/wesnoth-1.11.0-1.pnd/download Previous Version] (1.11.0-1, 326.2 MB)

==== Miscellaneous ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.1/wesnoth-1.11.1.tar.bz2.md5/download md5sum for current source code]
* [http://wiki.wesnoth.org/Download_Xdeltas#Development_Version_1.11.x Xdelta for the source code]
* [http://sourceforge.net/projects/wesnoth/files/ SourceForge page for current and all previous versions]
* [http://sourceforge.net/projects/wesnoth/files/unofficial/Mac%20Compile%20Stuff/wesnoth_compile_mac_1.9.zip/download MacCompileStuff for 1.9]

== License ==
''Main article: [[Wesnoth:Copyrights]]

This program is free software; you can redistribute it and/or modify it under the terms of the [http://www.fsf.org/copyleft/gpl.html GNU General Public License version 2], as published by the [http://www.fsf.org Free Software Foundation].
This program is distributed in the hope that it will be useful, but without any warranty; without even the implied warranty of merchantability or fitness for a particular purpose. See the GNU General Public License for more details.

== UMC Editor ==
This is available with Wesnoth 1.9.x and greater (including Wesnoth 1.10.x).
Details and installation steps can be found at: http://eclipse.wesnoth.org

== See also ==
* [http://changelog.wesnoth.org Changelog]
* [[WesnothBinaries| More binaries]]
* [[WesnothSVN]] - bleeding edge version from SVN

[[Category:Building and Installing]]

Download

2013-03-10T00:18:34Z

Tr0ll: Undo revision 48679 by Marsianen (Talk)

{{Download/Translations}}
Welcome to the Battle for Wesnoth downloads page. The BFW project team only officially releases the source code. Binary packages are only provided by community volunteers and hosted here. Torrents are also unofficial.

If the latest binaries are not currently available for your OS, please check back in a few days to see if they have been placed here. Packagers have been informed of the release, please be patient. In the meantime, read the [[FAQ#A_new_version_is_out.2C_but_where_is_the_download_for_.5BWindows.2C_Mac_OS.2C_etc..5D.3F|FAQ]].

__NOTOC__
Jump to: [[Download#Stable_.281.10_branch.29|Stable Branch]] | [[Download#Stable_.28older_versions.29|Stable Branch (older versions)]] | [[Download#Development_.281.11_branch.29|Development Branch]]

== Stable (1.10 branch) ==
The stable files are meant to be used as a stable and rather balanced version of the game. Each version of the 1.10 branch is compatible to each other.

Version 1.10.5 is the latest stable version. This version is recommended for most players since the 1.10 online multiplayer community is very large and user-made campaign server has a robust content selection.

==== исходный код ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.5/wesnoth-1.10.5.tar.bz2/download Current Version] (1.10.5, 327.7 МБ)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.4/wesnoth-1.10.4.tar.bz2/download Previous Version] (1.10.4, 326.8 МБ)

* [[CompilingWesnoth|Compiling Guide]] - how to compile the source code

==== MS Windows ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.5/wesnoth-1.10.5-win32.exe/download Current Version] (1.10.5, 301.2 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.4/wesnoth-1.10.4-win32.exe/download Previous Version] (1.10.4, 300.6 MB)

==== Mac OS X (10.5+) ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.5/Wesnoth_1.10.5.dmg/download Current Version] (1.10.5 328.8 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.4/Wesnoth_1.10.4.dmg/download Previous Version] (1.10.4 328.1 MB)

==== GNU/Linux ====
* There are binaries for many different GNU/Linux Distributions. Not all are always up to date with the current release. Please have a look at the [[WesnothBinariesLinux|Linux binary page]] for more information about the binaries for your Distribution.

==== OpenPandora ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.5/wesnoth-1.10.5-1.pnd/download Current Version] (1.10.5-1, 320.5 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.4/wesnoth-1.10.4-1.pnd/download Previous Version] (1.10.4-1, 319.7 MB)

==== Miscellaneous ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.5/wesnoth-1.10.5.tar.bz2.md5/download md5sum for current source code]
* [http://www.wesnoth.org/wiki/Download_Xdeltas#Stable_Version_1.10.x Xdelta for the source code]
* [http://sourceforge.net/projects/wesnoth/files/ SourceForge page for current and all previous versions]

== Stable (older versions) ==
Several operating systems do not offer a binary of the latest stable release. Here is a list of the latest known (stable version) binaries for various systems. For those older versions there often is no (official) multiplayer or addon server available anymore.

==== AmigaOS4 ====
* [http://www.amigasoft.net/pages/games/download/Wesnoth186.lha.lzh Older Version] (1.8.6, 300MB)

==== (Open)Solaris ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.4/wesnoth-1.4.5/wesnoth-solaris-i386-1.4.5.pkg.bz2/download Older Version] (1.4.5, 145.6 MB), not compatible with 1.6.x

==== OS/2 & eComStation ====
* [http://download.smedley.info/wesnoth-1.4.5-os2-20080828.zip Older Version] (1.4.5, 160 MB), not compatible with 1.6.x

==== RISC OS ====
*[http://www.riscos.info/packages/arm/Games/wesnoth_1.4.5-1.zip Older version] (1.4.5-1, 140MB), not compatible with 1.6.x

==== Syllable ====
* [http://downloads.syllable.org/Syllable/i586/applications/contributed/Battle-for-Wesnoth/Battle-for-Wesnoth-1.2.6.application Older Version] (1.2.6, 60.8 MB), not compatible with 1.6.x

== Development (1.11 branch) ==
Version 1.11.x is the latest development version, boasting updated graphics and new exciting features. However, there may be occasional bugs or performance problems in the development versions since heavy changes are taking place all the time. For balanced and stable gaming, it is recommended you use the latest version of the 1.10.x branch. This version is recommended for coders and campaign developers, as well as those who want to preview the future of Wesnoth. People familiar with SVN and compiling can follow the latest development by checking [[WesnothSVN]].

==== Source code ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.1/wesnoth-1.11.1.tar.bz2/download Current Version] (1.11.1, 338.8 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.0/wesnoth-1.11.0.tar.bz2/download Previous Version] (1.11.0, 334.1 MB)

* [[CompilingWesnoth|Compiling Guide]] - how to compile the source code

==== MS Windows ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.1/wesnoth-1.11.1-win32.exe/download Current Version] (1.11.1, 312.0 MB))
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.0/wesnoth-1.11.0-win32.exe/download Previous Version] (1.11.0, 307.8 MB))

==== Mac OS X (10.5+) ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.1/Wesnoth_1.11.1a.dmg/download Current Version] (1.11.1 338.9 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.0/Wesnoth_1.11.0.dmg/download Previous Version] (1.11.0 334.4 MB)

==== GNU/Linux ====
* There are binaries for many different GNU/Linux Distributions. Not all are always up to date with the current release. Please have a look at the [[WesnothBinariesLinux|Linux binary page]] for more information about the binaries for your Distribution.

==== OpenPandora ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.1/wesnoth-1.11.1-1.pnd/download Current Version] (1.11.1-1, 330.3 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.0/wesnoth-1.11.0-1.pnd/download Previous Version] (1.11.0-1, 326.2 MB)

==== Miscellaneous ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.1/wesnoth-1.11.1.tar.bz2.md5/download md5sum for current source code]
* [http://wiki.wesnoth.org/Download_Xdeltas#Development_Version_1.11.x Xdelta for the source code]
* [http://sourceforge.net/projects/wesnoth/files/ SourceForge page for current and all previous versions]
* [http://sourceforge.net/projects/wesnoth/files/unofficial/Mac%20Compile%20Stuff/wesnoth_compile_mac_1.9.zip/download MacCompileStuff for 1.9]

== License ==
''Main article: [[Wesnoth:Copyrights]]

This program is free software; you can redistribute it and/or modify it under the terms of the [http://www.fsf.org/copyleft/gpl.html GNU General Public License version 2], as published by the [http://www.fsf.org Free Software Foundation].
This program is distributed in the hope that it will be useful, but without any warranty; without even the implied warranty of merchantability or fitness for a particular purpose. See the GNU General Public License for more details.

== UMC Editor ==
This is available with Wesnoth 1.9.x and greater (including Wesnoth 1.10.x).
Details and installation steps can be found at: http://eclipse.wesnoth.org

== See also ==
* [http://changelog.wesnoth.org Changelog]
* [[WesnothBinaries| More binaries]]
* [[WesnothSVN]] - bleeding edge version from SVN

[[Category:Building and Installing]]

Download

2013-03-10T00:17:43Z

Tr0ll: Undo revision 48677 by Marsianen (Talk)

{{Download/Translations}}
Welcome to the Battle for Wesnoth downloads page. The BFW project team only officially releases the source code. Binary packages are only provided by community volunteers and hosted here. Torrents are also unofficial.

If the latest binaries are not currently available for your OS, please check back in a few days to see if they have been placed here. Packagers have been informed of the release, please be patient. In the meantime, read the [[FAQ#A_new_version_is_out.2C_but_where_is_the_download_for_.5BWindows.2C_Mac_OS.2C_etc..5D.3F|FAQ]].

__NOTOC__
Jump to: [[Download#Stable_.281.10_branch.29|Stable Branch]] | [[Download#Stable_.28older_versions.29|Stable Branch (older versions)]] | [[Download#Development_.281.11_branch.29|Development Branch]]

== Stable (1.10 branch) ==
The stable files are meant to be used as a stable and rather balanced version of the game. Each version of the 1.10 branch is compatible to each other.

Version 1.10.5 is the latest stable version. This version is recommended for most players since the 1.10 online multiplayer community is very large and user-made campaign server has a robust content selection.

==== Исходный код ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.5/wesnoth-1.10.5.tar.bz2/download Current Version] (1.10.5, 327.7 МБ)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.4/wesnoth-1.10.4.tar.bz2/download Previous Version] (1.10.4, 326.8 МБ)

* [[CompilingWesnoth|Compiling Guide]] - how to compile the source code

==== MS Windows ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.5/wesnoth-1.10.5-win32.exe/download Current Version] (1.10.5, 301.2 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.4/wesnoth-1.10.4-win32.exe/download Previous Version] (1.10.4, 300.6 MB)

==== Mac OS X (10.5+) ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.5/Wesnoth_1.10.5.dmg/download Current Version] (1.10.5 328.8 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.4/Wesnoth_1.10.4.dmg/download Previous Version] (1.10.4 328.1 MB)

==== GNU/Linux ====
* There are binaries for many different GNU/Linux Distributions. Not all are always up to date with the current release. Please have a look at the [[WesnothBinariesLinux|Linux binary page]] for more information about the binaries for your Distribution.

==== OpenPandora ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.5/wesnoth-1.10.5-1.pnd/download Current Version] (1.10.5-1, 320.5 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.4/wesnoth-1.10.4-1.pnd/download Previous Version] (1.10.4-1, 319.7 MB)

==== Miscellaneous ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.5/wesnoth-1.10.5.tar.bz2.md5/download md5sum for current source code]
* [http://www.wesnoth.org/wiki/Download_Xdeltas#Stable_Version_1.10.x Xdelta for the source code]
* [http://sourceforge.net/projects/wesnoth/files/ SourceForge page for current and all previous versions]

== Stable (older versions) ==
Several operating systems do not offer a binary of the latest stable release. Here is a list of the latest known (stable version) binaries for various systems. For those older versions there often is no (official) multiplayer or addon server available anymore.

==== AmigaOS4 ====
* [http://www.amigasoft.net/pages/games/download/Wesnoth186.lha.lzh Older Version] (1.8.6, 300MB)

==== (Open)Solaris ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.4/wesnoth-1.4.5/wesnoth-solaris-i386-1.4.5.pkg.bz2/download Older Version] (1.4.5, 145.6 MB), not compatible with 1.6.x

==== OS/2 & eComStation ====
* [http://download.smedley.info/wesnoth-1.4.5-os2-20080828.zip Older Version] (1.4.5, 160 MB), not compatible with 1.6.x

==== RISC OS ====
*[http://www.riscos.info/packages/arm/Games/wesnoth_1.4.5-1.zip Older version] (1.4.5-1, 140MB), not compatible with 1.6.x

==== Syllable ====
* [http://downloads.syllable.org/Syllable/i586/applications/contributed/Battle-for-Wesnoth/Battle-for-Wesnoth-1.2.6.application Older Version] (1.2.6, 60.8 MB), not compatible with 1.6.x

== Development (1.11 branch) ==
Version 1.11.x is the latest development version, boasting updated graphics and new exciting features. However, there may be occasional bugs or performance problems in the development versions since heavy changes are taking place all the time. For balanced and stable gaming, it is recommended you use the latest version of the 1.10.x branch. This version is recommended for coders and campaign developers, as well as those who want to preview the future of Wesnoth. People familiar with SVN and compiling can follow the latest development by checking [[WesnothSVN]].

==== Source code ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.1/wesnoth-1.11.1.tar.bz2/download Current Version] (1.11.1, 338.8 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.0/wesnoth-1.11.0.tar.bz2/download Previous Version] (1.11.0, 334.1 MB)

* [[CompilingWesnoth|Compiling Guide]] - how to compile the source code

==== MS Windows ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.1/wesnoth-1.11.1-win32.exe/download Current Version] (1.11.1, 312.0 MB))
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.0/wesnoth-1.11.0-win32.exe/download Previous Version] (1.11.0, 307.8 MB))

==== Mac OS X (10.5+) ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.1/Wesnoth_1.11.1a.dmg/download Current Version] (1.11.1 338.9 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.0/Wesnoth_1.11.0.dmg/download Previous Version] (1.11.0 334.4 MB)

==== GNU/Linux ====
* There are binaries for many different GNU/Linux Distributions. Not all are always up to date with the current release. Please have a look at the [[WesnothBinariesLinux|Linux binary page]] for more information about the binaries for your Distribution.

==== OpenPandora ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.1/wesnoth-1.11.1-1.pnd/download Current Version] (1.11.1-1, 330.3 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.0/wesnoth-1.11.0-1.pnd/download Previous Version] (1.11.0-1, 326.2 MB)

==== Miscellaneous ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.1/wesnoth-1.11.1.tar.bz2.md5/download md5sum for current source code]
* [http://wiki.wesnoth.org/Download_Xdeltas#Development_Version_1.11.x Xdelta for the source code]
* [http://sourceforge.net/projects/wesnoth/files/ SourceForge page for current and all previous versions]
* [http://sourceforge.net/projects/wesnoth/files/unofficial/Mac%20Compile%20Stuff/wesnoth_compile_mac_1.9.zip/download MacCompileStuff for 1.9]

== License ==
''Main article: [[Wesnoth:Copyrights]]

This program is free software; you can redistribute it and/or modify it under the terms of the [http://www.fsf.org/copyleft/gpl.html GNU General Public License version 2], as published by the [http://www.fsf.org Free Software Foundation].
This program is distributed in the hope that it will be useful, but without any warranty; without even the implied warranty of merchantability or fitness for a particular purpose. See the GNU General Public License for more details.

== UMC Editor ==
This is available with Wesnoth 1.9.x and greater (including Wesnoth 1.10.x).
Details and installation steps can be found at: http://eclipse.wesnoth.org

== See also ==
* [http://changelog.wesnoth.org Changelog]
* [[WesnothBinaries| More binaries]]
* [[WesnothSVN]] - bleeding edge version from SVN

[[Category:Building and Installing]]

Download

2013-03-10T00:16:40Z

Tr0ll: Undo revision 48680 by Marsianen (Talk)

{{Download/Translations}}
Welcome to the Battle for Wesnoth downloads page. The BFW project team only officially releases the source code. Binary packages are only provided by community volunteers and hosted here. Torrents are also unofficial.

If the latest binaries are not currently available for your OS, please check back in a few days to see if they have been placed here. Packagers have been informed of the release, please be patient. In the meantime, read the [[FAQ#A_new_version_is_out.2C_but_where_is_the_download_for_.5BWindows.2C_Mac_OS.2C_etc..5D.3F|FAQ]].

__NOTOC__
Jump to: [[Download#Stable_.281.10_branch.29|Stable Branch]] | [[Download#Stable_.28older_versions.29|Stable Branch (older versions)]] | [[Download#Development_.281.11_branch.29|Development Branch]]

== Stable (1.10 branch) ==
Стабильный файлы, предназначенные для использования в качестве стабильного и достаточно сбалансированной игры. Все версии 1.10 филиала совместимы друг с другом.

Version 1.10.5 is the latest stable version. This version is recommended for most players since the 1.10 online multiplayer community is very large and user-made campaign server has a robust content selection.

==== Исходный код ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.5/wesnoth-1.10.5.tar.bz2/download Current Version] (1.10.5, 327.7 МБ)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.4/wesnoth-1.10.4.tar.bz2/download Previous Version] (1.10.4, 326.8 МБ)

* [[CompilingWesnoth|Compiling Guide]] - how to compile the source code

==== MS Windows ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.5/wesnoth-1.10.5-win32.exe/download Current Version] (1.10.5, 301.2 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.4/wesnoth-1.10.4-win32.exe/download Previous Version] (1.10.4, 300.6 MB)

==== Mac OS X (10.5+) ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.5/Wesnoth_1.10.5.dmg/download Current Version] (1.10.5 328.8 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.4/Wesnoth_1.10.4.dmg/download Previous Version] (1.10.4 328.1 MB)

==== GNU/Linux ====
* There are binaries for many different GNU/Linux Distributions. Not all are always up to date with the current release. Please have a look at the [[WesnothBinariesLinux|Linux binary page]] for more information about the binaries for your Distribution.

==== OpenPandora ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.5/wesnoth-1.10.5-1.pnd/download Current Version] (1.10.5-1, 320.5 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.4/wesnoth-1.10.4-1.pnd/download Previous Version] (1.10.4-1, 319.7 MB)

==== Miscellaneous ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.5/wesnoth-1.10.5.tar.bz2.md5/download md5sum for current source code]
* [http://www.wesnoth.org/wiki/Download_Xdeltas#Stable_Version_1.10.x Xdelta for the source code]
* [http://sourceforge.net/projects/wesnoth/files/ SourceForge page for current and all previous versions]

== Stable (older versions) ==
Several operating systems do not offer a binary of the latest stable release. Here is a list of the latest known (stable version) binaries for various systems. For those older versions there often is no (official) multiplayer or addon server available anymore.

==== AmigaOS4 ====
* [http://www.amigasoft.net/pages/games/download/Wesnoth186.lha.lzh Older Version] (1.8.6, 300MB)

==== (Open)Solaris ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.4/wesnoth-1.4.5/wesnoth-solaris-i386-1.4.5.pkg.bz2/download Older Version] (1.4.5, 145.6 MB), not compatible with 1.6.x

==== OS/2 & eComStation ====
* [http://download.smedley.info/wesnoth-1.4.5-os2-20080828.zip Older Version] (1.4.5, 160 MB), not compatible with 1.6.x

==== RISC OS ====
*[http://www.riscos.info/packages/arm/Games/wesnoth_1.4.5-1.zip Older version] (1.4.5-1, 140MB), not compatible with 1.6.x

==== Syllable ====
* [http://downloads.syllable.org/Syllable/i586/applications/contributed/Battle-for-Wesnoth/Battle-for-Wesnoth-1.2.6.application Older Version] (1.2.6, 60.8 MB), not compatible with 1.6.x

== Development (1.11 branch) ==
Version 1.11.x is the latest development version, boasting updated graphics and new exciting features. However, there may be occasional bugs or performance problems in the development versions since heavy changes are taking place all the time. For balanced and stable gaming, it is recommended you use the latest version of the 1.10.x branch. This version is recommended for coders and campaign developers, as well as those who want to preview the future of Wesnoth. People familiar with SVN and compiling can follow the latest development by checking [[WesnothSVN]].

==== Source code ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.1/wesnoth-1.11.1.tar.bz2/download Current Version] (1.11.1, 338.8 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.0/wesnoth-1.11.0.tar.bz2/download Previous Version] (1.11.0, 334.1 MB)

* [[CompilingWesnoth|Compiling Guide]] - how to compile the source code

==== MS Windows ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.1/wesnoth-1.11.1-win32.exe/download Current Version] (1.11.1, 312.0 MB))
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.0/wesnoth-1.11.0-win32.exe/download Previous Version] (1.11.0, 307.8 MB))

==== Mac OS X (10.5+) ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.1/Wesnoth_1.11.1a.dmg/download Current Version] (1.11.1 338.9 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.0/Wesnoth_1.11.0.dmg/download Previous Version] (1.11.0 334.4 MB)

==== GNU/Linux ====
* There are binaries for many different GNU/Linux Distributions. Not all are always up to date with the current release. Please have a look at the [[WesnothBinariesLinux|Linux binary page]] for more information about the binaries for your Distribution.

==== OpenPandora ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.1/wesnoth-1.11.1-1.pnd/download Current Version] (1.11.1-1, 330.3 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.0/wesnoth-1.11.0-1.pnd/download Previous Version] (1.11.0-1, 326.2 MB)

==== Miscellaneous ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.1/wesnoth-1.11.1.tar.bz2.md5/download md5sum for current source code]
* [http://wiki.wesnoth.org/Download_Xdeltas#Development_Version_1.11.x Xdelta for the source code]
* [http://sourceforge.net/projects/wesnoth/files/ SourceForge page for current and all previous versions]
* [http://sourceforge.net/projects/wesnoth/files/unofficial/Mac%20Compile%20Stuff/wesnoth_compile_mac_1.9.zip/download MacCompileStuff for 1.9]

== License ==
''Main article: [[Wesnoth:Copyrights]]

This program is free software; you can redistribute it and/or modify it under the terms of the [http://www.fsf.org/copyleft/gpl.html GNU General Public License version 2], as published by the [http://www.fsf.org Free Software Foundation].
This program is distributed in the hope that it will be useful, but without any warranty; without even the implied warranty of merchantability or fitness for a particular purpose. See the GNU General Public License for more details.

== UMC Editor ==
This is available with Wesnoth 1.9.x and greater (including Wesnoth 1.10.x).
Details and installation steps can be found at: http://eclipse.wesnoth.org

== See also ==
* [http://changelog.wesnoth.org Changelog]
* [[WesnothBinaries| More binaries]]
* [[WesnothSVN]] - bleeding edge version from SVN

[[Category:Building and Installing]]

Download/ru

2013-03-10T00:14:56Z

Tr0ll: Marsianen's partly translated Russian version

{{Download/Translations}}
Welcome to the Battle for Wesnoth downloads page. The BFW project team only officially releases the source code. Binary packages are only provided by community volunteers and hosted here. Torrents are also unofficial.

If the latest binaries are not currently available for your OS, please check back in a few days to see if they have been placed here. Packagers have been informed of the release, please be patient. In the meantime, read the [[FAQ#A_new_version_is_out.2C_but_where_is_the_download_for_.5BWindows.2C_Mac_OS.2C_etc..5D.3F|FAQ]].

__NOTOC__
Jump to: [[Download#Stable_.281.10_branch.29|Stable Branch]] | [[Download#Stable_.28older_versions.29|Stable Branch (older versions)]] | [[Download#Development_.281.11_branch.29|Development Branch]]

== Stable (1.10 branch) ==
Стабильные файлы, предназначенные для использования в стабильной и достаточно сбалансированной игре. Все версии 1.10 филиала совместимы друг с другом.

Версия 1.10.5 является самой последней стабильной версией. This version is recommended for most players since the 1.10 online multiplayer community is very large and user-made campaign server has a robust content selection.

==== Исходный код ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.5/wesnoth-1.10.5.tar.bz2/download Current Version] (1.10.5, 327.7 МБ)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.4/wesnoth-1.10.4.tar.bz2/download Previous Version] (1.10.4, 326.8 МБ)

* [[CompilingWesnoth|Compiling Guide]] - how to compile the source code

==== MS Windows ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.5/wesnoth-1.10.5-win32.exe/download Current Version] (1.10.5, 301.2 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.4/wesnoth-1.10.4-win32.exe/download Previous Version] (1.10.4, 300.6 MB)

==== Mac OS X (10.5+) ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.5/Wesnoth_1.10.5.dmg/download Current Version] (1.10.5 328.8 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.4/Wesnoth_1.10.4.dmg/download Previous Version] (1.10.4 328.1 MB)

==== GNU/Linux ====
* There are binaries for many different GNU/Linux Distributions. Not all are always up to date with the current release. Please have a look at the [[WesnothBinariesLinux|Linux binary page]] for more information about the binaries for your Distribution.

==== OpenPandora ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.5/wesnoth-1.10.5-1.pnd/download Current Version] (1.10.5-1, 320.5 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.4/wesnoth-1.10.4-1.pnd/download Previous Version] (1.10.4-1, 319.7 MB)

==== Miscellaneous ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.10/wesnoth-1.10.5/wesnoth-1.10.5.tar.bz2.md5/download md5sum for current source code]
* [http://www.wesnoth.org/wiki/Download_Xdeltas#Stable_Version_1.10.x Xdelta for the source code]
* [http://sourceforge.net/projects/wesnoth/files/ SourceForge page for current and all previous versions]

== Stable (older versions) ==
Several operating systems do not offer a binary of the latest stable release. Here is a list of the latest known (stable version) binaries for various systems. For those older versions there often is no (official) multiplayer or addon server available anymore.

==== AmigaOS4 ====
* [http://www.amigasoft.net/pages/games/download/Wesnoth186.lha.lzh Older Version] (1.8.6, 300MB)

==== (Open)Solaris ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.4/wesnoth-1.4.5/wesnoth-solaris-i386-1.4.5.pkg.bz2/download Older Version] (1.4.5, 145.6 MB), not compatible with 1.6.x

==== OS/2 & eComStation ====
* [http://download.smedley.info/wesnoth-1.4.5-os2-20080828.zip Older Version] (1.4.5, 160 MB), not compatible with 1.6.x

==== RISC OS ====
*[http://www.riscos.info/packages/arm/Games/wesnoth_1.4.5-1.zip Older version] (1.4.5-1, 140MB), not compatible with 1.6.x

==== Syllable ====
* [http://downloads.syllable.org/Syllable/i586/applications/contributed/Battle-for-Wesnoth/Battle-for-Wesnoth-1.2.6.application Older Version] (1.2.6, 60.8 MB), not compatible with 1.6.x

== Development (1.11 branch) ==
Version 1.11.x is the latest development version, boasting updated graphics and new exciting features. However, there may be occasional bugs or performance problems in the development versions since heavy changes are taking place all the time. For balanced and stable gaming, it is recommended you use the latest version of the 1.10.x branch. This version is recommended for coders and campaign developers, as well as those who want to preview the future of Wesnoth. People familiar with SVN and compiling can follow the latest development by checking [[WesnothSVN]].

==== Source code ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.1/wesnoth-1.11.1.tar.bz2/download Current Version] (1.11.1, 338.8 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.0/wesnoth-1.11.0.tar.bz2/download Previous Version] (1.11.0, 334.1 MB)

* [[CompilingWesnoth|Compiling Guide]] - how to compile the source code

==== MS Windows ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.1/wesnoth-1.11.1-win32.exe/download Current Version] (1.11.1, 312.0 MB))
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.0/wesnoth-1.11.0-win32.exe/download Previous Version] (1.11.0, 307.8 MB))

==== Mac OS X (10.5+) ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.1/Wesnoth_1.11.1a.dmg/download Current Version] (1.11.1 338.9 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.0/Wesnoth_1.11.0.dmg/download Previous Version] (1.11.0 334.4 MB)

==== GNU/Linux ====
* There are binaries for many different GNU/Linux Distributions. Not all are always up to date with the current release. Please have a look at the [[WesnothBinariesLinux|Linux binary page]] for more information about the binaries for your Distribution.

==== OpenPandora ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.1/wesnoth-1.11.1-1.pnd/download Current Version] (1.11.1-1, 330.3 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.0/wesnoth-1.11.0-1.pnd/download Previous Version] (1.11.0-1, 326.2 MB)

==== Miscellaneous ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.11.1/wesnoth-1.11.1.tar.bz2.md5/download md5sum for current source code]
* [http://wiki.wesnoth.org/Download_Xdeltas#Development_Version_1.11.x Xdelta for the source code]
* [http://sourceforge.net/projects/wesnoth/files/ SourceForge page for current and all previous versions]
* [http://sourceforge.net/projects/wesnoth/files/unofficial/Mac%20Compile%20Stuff/wesnoth_compile_mac_1.9.zip/download MacCompileStuff for 1.9]

== License ==
''Main article: [[Wesnoth:Copyrights]]

This program is free software; you can redistribute it and/or modify it under the terms of the [http://www.fsf.org/copyleft/gpl.html GNU General Public License version 2], as published by the [http://www.fsf.org Free Software Foundation].
This program is distributed in the hope that it will be useful, but without any warranty; without even the implied warranty of merchantability or fitness for a particular purpose. See the GNU General Public License for more details.

== UMC Editor ==
This is available with Wesnoth 1.9.x and greater (including Wesnoth 1.10.x).
Details and installation steps can be found at: http://eclipse.wesnoth.org

== See also ==
* [http://changelog.wesnoth.org Changelog]
* [[WesnothBinaries| More binaries]]
* [[WesnothSVN]] - bleeding edge version from SVN

[[Category:Building and Installing]]

Talk:Voting

2013-02-12T22:55:58Z

Tr0ll: Created page with 'How do we change the maintainer on the Freshmeat listing? I'm not surprised if Sirp doesnt have time to keep the entry up to date.'

How do we change the maintainer on the Freshmeat listing? I'm not surprised if Sirp doesnt have time to keep the entry up to date.

SpellingMistakes

2013-01-30T03:25:21Z

Tr0ll: /* Under the Burning Suns */

SpellingMistakes

2013-01-30T03:14:48Z

Tr0ll: add section for UtBS

Creating Unit Art

2013-01-18T04:20:17Z

Tr0ll: /* Basic unit image specifications */ add Alaranta's diagram showing overlap recommendations for oversized images

Here's the information needed to start doing units art for Wesnoth. Please update the wiki with links to examples and other tips and tricks realted to unit art. This page started from [http://www.wesnoth.org/forum/viewtopic.php?p=104809#104809 this forum thread].

== The Medium ==

The medium used to create unit art is known as 'pixel art'. If you do not understand what pixel art is, or if you have only a general understanding of what it is, I suggest reading [http://www.pixeljoint.com/forum/forum_posts.asp?TID=11299 The Pixel Art Tutorial] by Cure. It is a tutorial comprised of a series of sequential forum posts on the www.pixeljoint.com forum and gives an in-depth overview of pixel art, explaining in detail what pixel art is and what it is not. Using other mediums (such as brush art) to create unit art is fine if you are creating unit art for [[Glossary|UMC]] add-ons (although it is still strongly recommended that you use pixel art for the sake of consistency with mainline units), but only units drawn in pure pixel art will be accepted into mainline.

== Basic unit image specifications ==

Wesnoth can only use two kinds of graphic files: PNGs, or JPEGs. JPEGs aren't suitable for unit images, because they can't store transparency data (and are lossy). Because of this, we always use PNGs for unit images.
*Final format: transparent PNG
** Color depth should be 24-bit (8 bits per RGB channel). This may be listed as "PNG-24" or "8-bit RGBA".
** Be aware that "Indexed color", "color map", or "PNG-8" is a different format. Although it might work in a buggy way, we strongly recommend you not use these.
* Canvas size is 72 x 72 pixels (it can actually be slightly wider, and can fit in the area of a hex and its immediately surrounding tiles, but try not to do this if at all possible, because it has performance and graphical glitch issues).
*All but exceptionally large units should be contained in the hex if possible - the white in the template shown at right: http://forums.wesnoth.org/download/file.php?id=4334&type=.png
*Compare the size of your unit to the size of similar existing core units.
*<div style="float:right; padding:1ex; margin:1ex; border: thin dotted; font-size:80%;">http://forums.wesnoth.org/download/file.php?id=60404&type=.png</div>For oversize units, there are limitations with respect to the terrain system and asthetics. Sprites that are much bigger than the hex tend to end up getting partially obscured by terrain in inconvenient places and look bad. If you want everything to be always visible or believably covered then the black area in the picture is safe. You can usually exceed this to the left and right without much trouble, but going down is problematic with the great tree and stands out. The gold hex represents the hex the unit is actually in. Also, making units too large will hide those behind it, so even though the appearance will be correct in the entire black area, you will want to leave more than half of each of the hexes outside the gold one visible so as not to make other units vanish. [http://forums.wesnoth.org/viewtopic.php?f=23&t=38203&p=546367#p546331]
*Light comes from the artist's (''not'' the unit's!) upper right (for shading and highlights)
*Unit must look in the lower right (again, the artist's lower right, not the unit's) direction
*Units are centered horizontally
*Unit's feet are positioned around 55 pixel down from the top edge of the canvas, lower for taller units if necessary
*Shadows at 60 opacity, using a specific dark blue color (see [[Creating_Shadows_Under_Units|Creating Shadows Under Units]]).
*Outlines should be used, made with a darker, but similar color to what they're surrounding, this makes the unit feel bigger then the amount of pixels you'd use for the same with a black outline. Note that pure black (RGB #000000) should ''never'' be used to outline a sprite.
*Use consistent names for your files, beginning with the unit name, so that they are kept together when browsing the files. Try to imitate the naming scheme used for mainline units.

== Unit animation specifications ==

You can have as many frames for animations as you like, and in fact, for any given cue, you can have more than one animation, which will be randomly chosen by the game. Images and animations must be done for:
*base frame (1 frame)
*attack for each type (at least 4 frames, about 6 frames is optimal depending on the type of attack and the weapon(s) involved)
*directional attacks (generally are desired for any attack that's a straight motion, rather than a slash. I.e. spears and thundersticks)
*defense (usually 2 frames long not including the base frame, separate animations may be drawn for ranged and melee defense animations)

== Additional Notes ==

*Test early with different backgrounds. Go to your game terrain files, pick, say, 3 terrains, preferably with different colors, and have a look what they look like against the background, because that way if you have used alpha channels, it may look better in game than as the average standard sprite.

*Test your unit early in the game. Replacing an existing unit graphic with yours is the fastest way (be sure to make a copy of the originals so you don't lose them.)

*Test your unit next to mainline units in-game. This will help you ensure that your unit matches the style and proportions of the mainline units as closely as possible.

== See Also ==
* [[BuildingUnits]]
* [[Create]]
* [[Create Art and Music]]
* [[Art Tutorials]]

[[Category: Art Tutorials]]

Creating Unit Art

2013-01-18T03:50:32Z

Tr0ll: /* Basic unit image specifications */ insert referenced image inline

Here's the information needed to start doing units art for Wesnoth. Please update the wiki with links to examples and other tips and tricks realted to unit art. This page started from [http://www.wesnoth.org/forum/viewtopic.php?p=104809#104809 this forum thread].

== The Medium ==

The medium used to create unit art is known as 'pixel art'. If you do not understand what pixel art is, or if you have only a general understanding of what it is, I suggest reading [http://www.pixeljoint.com/forum/forum_posts.asp?TID=11299 The Pixel Art Tutorial] by Cure. It is a tutorial comprised of a series of sequential forum posts on the www.pixeljoint.com forum and gives an in-depth overview of pixel art, explaining in detail what pixel art is and what it is not. Using other mediums (such as brush art) to create unit art is fine if you are creating unit art for [[Glossary|UMC]] add-ons (although it is still strongly recommended that you use pixel art for the sake of consistency with mainline units), but only units drawn in pure pixel art will be accepted into mainline.

== Basic unit image specifications ==

Wesnoth can only use two kinds of graphic files: PNGs, or JPEGs. JPEGs aren't suitable for unit images, because they can't store transparency data (and are lossy). Because of this, we always use PNGs for unit images.
*Final format: transparent PNG
** Color depth should be 24-bit (8 bits per RGB channel). This may be listed as "PNG-24" or "8-bit RGBA".
** Be aware that "Indexed color", "color map", or "PNG-8" is a different format. Although it might work in a buggy way, we strongly recommend you not use these.
* Canvas size is 72 x 72 pixels (it can actually be slightly wider, and can fit in the area of a hex and its immediately surrounding tiles, but try not to do this if at all possible, because it has performance and graphical glitch issues).
*All but exceptionally large units should be contained in the hex if possible - the white in the template shown here: http://forums.wesnoth.org/download/file.php?id=4334&type=.png
*Compare the size of your unit to the size of similar existing core units
*Light comes from the artist's (''not'' the unit's!) upper right (for shading and highlights)
*Unit must look in the lower right (again, the artist's lower right, not the unit's) direction
*Units are centered horizontally
*Unit's feet are positioned around 55 pixel down from the top edge of the canvas, lower for taller units if necessary
*Shadows at 60 opacity, using a specific dark blue color (see [[Creating_Shadows_Under_Units|Creating Shadows Under Units]]).
*Outlines should be used, made with a darker, but similar color to what they're surrounding, this makes the unit feel bigger then the amount of pixels you'd use for the same with a black outline. Note that pure black (RGB #000000) should ''never'' be used to outline a sprite.
*Use consistent names for your files, beginning with the unit name, so that they are kept together when browsing the files. Try to imitate the naming scheme used for mainline units.

== Unit animation specifications ==

You can have as many frames for animations as you like, and in fact, for any given cue, you can have more than one animation, which will be randomly chosen by the game. Images and animations must be done for:
*base frame (1 frame)
*attack for each type (at least 4 frames, about 6 frames is optimal depending on the type of attack and the weapon(s) involved)
*directional attacks (generally are desired for any attack that's a straight motion, rather than a slash. I.e. spears and thundersticks)
*defense (usually 2 frames long not including the base frame, separate animations may be drawn for ranged and melee defense animations)

== Additional Notes ==

*Test early with different backgrounds. Go to your game terrain files, pick, say, 3 terrains, preferably with different colors, and have a look what they look like against the background, because that way if you have used alpha channels, it may look better in game than as the average standard sprite.

*Test your unit early in the game. Replacing an existing unit graphic with yours is the fastest way (be sure to make a copy of the originals so you don't lose them.)

*Test your unit next to mainline units in-game. This will help you ensure that your unit matches the style and proportions of the mainline units as closely as possible.

== See Also ==
* [[BuildingUnits]]
* [[Create]]
* [[Create Art and Music]]
* [[Art Tutorials]]

[[Category: Art Tutorials]]

Creating Unit Art

2013-01-18T03:34:16Z

Tr0ll: switch bolding to level1 section headers in order to modularize future editing and auto-insert table of contents

Here's the information needed to start doing units art for Wesnoth. Please update the wiki with links to examples and other tips and tricks realted to unit art. This page started from [http://www.wesnoth.org/forum/viewtopic.php?p=104809#104809 this forum thread].

== The Medium ==

The medium used to create unit art is known as 'pixel art'. If you do not understand what pixel art is, or if you have only a general understanding of what it is, I suggest reading [http://www.pixeljoint.com/forum/forum_posts.asp?TID=11299 The Pixel Art Tutorial] by Cure. It is a tutorial comprised of a series of sequential forum posts on the www.pixeljoint.com forum and gives an in-depth overview of pixel art, explaining in detail what pixel art is and what it is not. Using other mediums (such as brush art) to create unit art is fine if you are creating unit art for [[Glossary|UMC]] add-ons (although it is still strongly recommended that you use pixel art for the sake of consistency with mainline units), but only units drawn in pure pixel art will be accepted into mainline.

== Basic unit image specifications ==

Wesnoth can only use two kinds of graphic files: PNGs, or JPEGs. JPEGs aren't suitable for unit images, because they can't store transparency data (and are lossy). Because of this, we always use PNGs for unit images.
*Final format: transparent PNG
** Color depth should be 24-bit (8 bits per RGB channel). This may be listed as "PNG-24" or "8-bit RGBA".
** Be aware that "Indexed color", "color map", or "PNG-8" is a different format. Although it might work in a buggy way, we strongly recommend you not use these.
* Canvas size is 72 x 72 pixels (it can actually be slightly wider, and can fit in the area of a hex and its immediately surrounding tiles, but try not to do this if at all possible, because it has performance and graphical glitch issues).
*All but exceptionally large units should be contained in the hex if possible (the white in the attached template)
*Compare the size of your unit to the size of similar existing core units
*Light comes from the artist's (''not'' the unit's!) upper right (for shading and highlights)
*Unit must look in the lower right (again, the artist's lower right, not the unit's) direction
*Units are centered horizontally
*Unit's feet are positioned around 55 pixel down from the top edge of the canvas, lower for taller units if necessary
*Shadows at 60 opacity, using a specific dark blue color (see [[Creating_Shadows_Under_Units|Creating Shadows Under Units]]).
*Outlines should be used, made with a darker, but similar color to what they're surrounding, this makes the unit feel bigger then the amount of pixels you'd use for the same with a black outline. Note that pure black (RGB #000000) should ''never'' be used to outline a sprite.
*Use consistent names for your files, beginning with the unit name, so that they are kept together when browsing the files. Try to imitate the naming scheme used for mainline units.

== Unit animation specifications ==

You can have as many frames for animations as you like, and in fact, for any given cue, you can have more than one animation, which will be randomly chosen by the game. Images and animations must be done for:
*base frame (1 frame)
*attack for each type (at least 4 frames, about 6 frames is optimal depending on the type of attack and the weapon(s) involved)
*directional attacks (generally are desired for any attack that's a straight motion, rather than a slash. I.e. spears and thundersticks)
*defense (usually 2 frames long not including the base frame, separate animations may be drawn for ranged and melee defense animations)

== Additional Notes ==

*Test early with different backgrounds. Go to your game terrain files, pick, say, 3 terrains, preferably with different colors, and have a look what they look like against the background, because that way if you have used alpha channels, it may look better in game than as the average standard sprite.

*Test your unit early in the game. Replacing an existing unit graphic with yours is the fastest way (be sure to make a copy of the originals so you don't lose them.)

*Test your unit next to mainline units in-game. This will help you ensure that your unit matches the style and proportions of the mainline units as closely as possible.

== See Also ==
* [[BuildingUnits]]
* [[Create]]
* [[Create Art and Music]]
* [[Art Tutorials]]

[[Category: Art Tutorials]]

SpellingMistakes

2013-01-03T18:24:22Z

Tr0ll: /* The South Guard */

AnimationWML

2012-10-07T21:03:30Z

Tr0ll: typo

{{WML Tags}}

== Introduction ==

This page covers unit animations. At any point in game, units are playing an animation. Even when the unit is standing, it is actually playing a single frame animation.

This page will deal with the two problems of animations
* How are animations chosen
* What exactly is drawn

== How animations are drawn ==
=== Animations ===
Any unit has a huge set of animations to choose from. Animations are WML blocks in the unit type, enclosed in either the generic type '''[animation]''' or some more specific tags such as '''[attack_anim]''' '''[idle_anim]''' and the like. An animation is what a unit displays when a given event is triggered, and a certain set of conditions are met such as
* unit is attacking
* unit is idling
* unit is attacking (event) and uses a melee weapon (condition)
* unit is attacking (event) and uses a melee weapon (condition) and opponent can't retaliate (condition)

events and conditions are described entirely in the [animation] block, and will be discussed in the animation choice section.

=== Frames ===

An animation is cut in frames. Frames are WML blocks that are contained either in '''[frame]''' WML blocks or in generic '''[xxx_frame]''' block. (the xxx part can be any string not starting with an underscore) the xxx part in the frame name is called the frame prefix. frames of the type '''[frame]''' are said to have an empty prefix

A frame typically describes an image, where an how to render it. It can contain such things as
* the image to display
* how transparent should that image be
* where to draw that image.

At any given time, an animation will display one frame for each frame prefix it can find. I.e if your animation has both '''[frame]''' and '''[missile_frame]''' blocks, both will be displayed at the same time

The frame with the empty prefix is special in many way. It is assumed to contain the image representing the unit itself, and as such the engine will heavily temper with it in multiple ways, such as providing a default image if none is available, or forcing the image to be green when the unit is poisoned

=== Timing, Clock, Multiple animations ===
When an animation is played it has an internal clock that is run. The step of this clock is the milisecond, and each frame is played for a given duration. Each animation also has a starting time which tells the animation engine at what value the animation clock should start

This starting time is very important when multiple animations from different units are played synchronously Typically a fight involves a unit playing its defense animation while the opponent plays its attack animation (and a third might play its leading animation, too). In that case all animations have a common clock, and are played concurrently.

The convention is that the "important time" (usually the time of the hit) is at time 0. everything before should be at negative time, everything after at positive time. This is a WML convention that is not enforced by the engine

In that case, it is very important that these animations (which can have different lengths) be synchronized. Fight animations are synchronized around the point of impact, so they all reach time 0 when the attack lands (or misses). This is accomplished through the use of the '''start_time''' key of the '''[animation]''' tag.

Just like the '''[frame]''' tag can have a prefix, so can the '''start_time''' key. A '''start_time''' key without prefix will affect a '''[frame]''' tag without prefix, while a '''start_time''' key with a prefix will affect a '''[frame]''' tag with the same prefix.

==== Example Syntax ====
[attack_anim]
[filter_attack]
name=bow
[/filter_attack]
'''start_time'''=-350
'''missile_start_time'''=-150
[missile_frame]
duration=150
image="projectiles/missile-n.png"
image_diagonal="projectiles/missile-ne.png"
[/missile_frame]
[if]
hits=yes
[frame]
duration=350
sound=bow.ogg
[/frame]
[/if]
[else]
hits=no
[frame]
duration=350
sound=bow-miss.ogg
[/frame]
[/else]
[/attack_anim]

=== The content of a frame ===
==== Syntax summary ====
[frame]
duration=<integer>
begin=<deprecated,integer>
end=<deprecated,integer>
image=<string>
image_diagonal=<string>
image_mod=<string>
sound=<string>
halo=<progressive string>
halo_x=<progressive int>
halo_y=<progressive int>
halo_mod=<string>
alpha=<progressive float>
offset=<progressive float>
blend_color=<red, green, blue>
blend_ratio=<progressive float>
text=<string>
text_color=< red, green, blue >
submerge=<progressive float>
x=<progressive int>
y=<progressive int>
directional_x=<dev feature 1.9,progressive int>
directional_y=<dev feature 1.9,progressive int>
layer=<progressive int>
auto_hflip=<dev feature 1.9, boolean>
auto_vflip=<dev feature 1.9, boolean>
primary=<dev feature 1.9, boolean>
[/frame]

==== Progressive parameters ====

Some parameters above are marked as ''progressive'' This means that you can specify that during the time the frame is displayed, the parameter should smoothly slide from one value to an other.

A typical example would be a unit progressively fading out, becoming transparent

To do that, you could use:

alpha=1~0

To make a frame, which is 900ms long, slide to transparent for 300ms, stay transparent for another 300ms and finally fade back to normal for 300ms, use:

alpha=1~0:300,0:300,0~1:300

you could also specify it like that

alpha=1~0,0,0~1

when a timing is missing, the engine will do its best to fill in in a fair way.

a progressive string has a similar syntax

halo=halo1.png:300,halo2.png:300,halo2.png:300

==== Field Description ====

** '''begin''': (deprecated) will be replaced by '''duration= <end - begin >'''
** '''end''': (deprecated) see '''begin''' and also [[AnimationWML#Timing.2C_Clock.2C_Multiple_animations|Timing, Clock, Multiple animations]] section for coverage of '''start_time''' which combines with '''duration''' to replace '''begin=''' '''end='''.
** '''duration''': how long the frame should be displayed. Use instead of '''begin=''' and '''end='''.
** '''image''': the image to display during the frame.
** '''image_diagonal''': the image to display when the attack occurs diagonally (directions ne,se,sw,nw).
** '''image_mod''': a string modifications (see [[ImagePathFunctionWML]] ) that will be applied to all images
** '''sound''': the sound to play when the frame begins. Can be a comma-separated list of sounds, in which case one of them is chosen randomly every time.
** '''halo''': the halo to display at the time.
** '''halo_x''': the position the halo is displayed in pixel relative to the unit's center.
** '''halo_y''': the position the halo is displayed in pixel relative to the unit's center.
** '''halo_mod''': a string modifications (see [[ImagePathFunctionWML]] ) that will be applied to all haloes
** '''alpha''': transparency level to apply to the frame. This is a floating point progressive parameter ranging from 0.0 to 1.0.
** '''offset''': the position of the image relative to the hex the unit is facing, 0.0 will display the unit in the center of the hex, 1.0 in the center of the faced hex, -1.0 at the center of the hex behind you. This is a progressive parameter.
** '''blend_color''': a comma separated list of numbers representing a color in RGB (0-255); this color will be mixed to the frame to give it a tint.
** '''blend_ratio''': this is a progressive parameter ranging from 0 to 1: 0 means no tint, 1 means target color only.
** '''text''': if specified, floats a label with the given text above the unit (identical to the floating damage and healing numbers).
** '''text_color''': the color of the above floating label.
** '''submerge''': the part of the unit that should drawn with 50% opacity (for units in water)
** '''x''': x offset applied to the frame
** '''y''': y offset applied to the frame
** '''directional_x''': the x offset, in pixels, applied to the frame in the direction the unit is facing
** '''directional_y''': the y offset, in pixels, applied to the frame in the direction the unit is facing
** '''layer''': layer used to draw the frame, see discussion bellow
** '''auto_hflip''': should the image flip horizontally depending on sprite orientation
** '''auto_vflip''': should the image flip vertically depending on sprite orientation
** '''primary''': should the engine consider that frame as a primary frame (affected by visual effects like stone and poison)

=== Drawing related animation content ===
==== Syntax summary ====
[animation]
<animation choice related content>
[frame]
<frame content>
[/frame]
[frame]
<frame content>
[/frame]
start_time=<integer>
offset=<progressive float>
image_mod=<string>
blend_color=<r,g,b>
blend_ratio=<progressive float>
halo=<progressive_string>
halo_x=<progressive int>
halo_y=<progressive int>
halo_mod=<string>
submerge=<progressive float>
x=<progressive int>
y=<progressive int>
directional_x=<dev1.9,progressive int>
directional_y=<dev1.9,progressive int>
layer=<progressive int>

[xxx_frame]
<frame content>
[/xxx_frame]
xxx_start_time=<integer>
xxx_image_mod=<string>
xxx_offset=<progressive float>
xxx_blend_color=<r,g,b>
xxx_blend_ratio=<progressive float>
xxx_halo=<progressive_string>
xxx_halo_x=<progressive int>
xxx_halo_y=<progressive int>
xxx_halo_mod=<string>
xxx_submerge=<progressive float>
xxx_x=<progressive int>
xxx_y=<progressive int>
xxx_directional_x=<dev1.9,progressive int>
xxx_directional_y=<dev1.9,progressive int>
xxx_layer=<progressive int>

[/animation]

==== Parameter handling ====
All drawing related parameters in '''[animation]''' can be matched with a corresponding parameter in a '''[frame]''' block (or a '''[xxx_frame]''' block) The value provided in the animation will be used if no value is provided in the frame.

The point of these two level of parameters is to easily be able to specify a parameter at the animation level and override it for a special case of frame.

== How animations are chosen ==
Within a unit description block there are multiple animations. Each animation is meant to be played in a very special set of circumstances. We will discuss here how to tell the animation engine when a given animation should be played.

Let's take an example. Suppose we have a unit which has the skirmisher ability. We have the following movement animations :
* a normal walking animation
* a swimming animation when the unit is in water
* a tiptoeing animation when moving next to an enemy unit

Ok. most of the time it's easy to guess what animation should be. However if you are both in water and next to an enemy unit, the animation to play is not obvious.

To solve that question, each animation has a number of filtering criteria. The engine follow the following rules to select an animation
* Start with all animations
* Drop all animations with a criteria that fails on the current situation
* Take the animations that have the most matching criteria
* If there are more than one animation remaining, take an animation randomly
* If all animations have been dropped, the engine will provide a smart default.

here is a pseudo-code explanation of this algorithm:

foreach animation
animation_score = 0
foreach filter-criteria
if <criteria-fails>
animation_score = -1;
break;
elsif <criteria-matches>
animation_score++
endfor
if animation_score > max_score
<empty animation list>
max_score = animation_score;
push(animation,animation_list);
elsif animation_score = max_score
push(animation,animation_list);
endfor
<choose an animation randomly from animation_list>

Note that all animations don't have all the filters...

so, if we have a unit with
# an animation for water terrain
# an animation for SE on grassland
# an animation with no criteria
# an animation for N,NE,NW,S,SW,SE
# an animation for NW

* 3. will never be taken, because 4. will always trump it
* on water going NW, it can be 1. 4. 5.
* on water, any direction but NW, it will be 1. or 4.
* on SE grassland it will be 2.
* on other grasslands, it will be 4. (4. or 5. if NW)

=== Generic animation filters available for all animations ===
* '''apply_to''': a list of comma separated keywords describing what event should trigger the animation (movement, attack...) the complete list is given below
* '''value''': a list of comma separated integer, the meaning depends on the triggering event. the meaning is given with the list of event
* '''value_second''': a list of comma separated integer, the meaning depends on the triggering event. the meaning is given with the list of event
* '''terrain''': a list of comma separated terrain letters, the animation will only be used on these terrains. See [[FilterWML#Filtering Terrains|Filtering Terrains]]. this has been replaced by '''terrain_type'''
* '''terrain_type''': a list of comma separated terrain codes, the animation will only be used on matching terrains. See [[FilterWML#Filtering Terrains|Filtering Terrains]].
* '''[filter]''': this will filter using a [[StandardUnitFilter|standard unit filter]] on the animated unit. Note that matching all criterias in the filter will only earn you one point for animation selection, but that you can have multiple '''[filter]''' blocks in an animation.
* '''[filter_second]''': this will filter using a [[StandardUnitFilter|standard unit filter]] on the unit in the hex faced. Note that matching all criteria in the filter will only earn you one point for animation selection, but that you can have multiple '''[filter_second]''' blocks in an animation. Also note that if the faced hex is empty, the whole filter will fail.
* '''direction''': a list of directions (n,ne,se,s,sw,nw), the animation will only be used when acting or moving in this direction (the attack direction for attack animations, moving direction for movement animations, direction of lead unit for leading animations, and so on).
* '''frequency''': this integer value allows to easily tweak the matching frequency of animations. The filter will fail n-1 times out of n, randomly. Note that unlike every other filter, matching this filter won't give an extra point.
* '''[filter_attack]''': a standard attack filter to match on the attacker's attack. See [[FilterWML#Filtering Weapons|Filtering Weapons]].
* '''[filter_second_attack]''': a standard attack filter to match on the defender's attack. See [[FilterWML#Filtering Weapons|Filtering Weapons]]. Also note that if the defender doesn't have any weapon to retaliate with, this filter will always fail.
* '''hits''': filters attack animations based on whether the attack hits, misses or kills. Accepts a list of the following:
** '''hit''': the attack hits, defender survives.
** '''no''' or '''miss''': the attack misses.
** '''kill''': the attack hits, defender dies.
** '''yes''': is an alias of '''hit,kill'''.
* '''swing''': a list of numbers representing the swing numbers this animation should match (numbered from 1). this has been replaced by value_second
* '''base_score''': a number that will always be added to the score. Use with caution

=== Events triggering animations and default animations ===
==== standing ====
This animation is triggered whenever any other animation is finished, and is played in loop until another animation is triggered

this is the default "standing image" for the unit

''value='' is not used, and always contains 0

''value_second='' is not used, and always contains 0

if no standing animation is set a single frame animation based on the enclosing unit's '''image=''' field is used
==== selected ====
This animation is triggered whenever the unit is selected

''value='' is not used, and always contains 0

''value_second='' is not used, and always contains 0

if no animation is available, the default uses the standing animation(s) with ''blend_ratio="0.0~0.3:100,0.3~0.0:200" blend_color=255,255,255''
==== recruited ====
This animation is triggered whenever the unit is recruited or recalled

''value='' is not used, and always contains 0

''value_second='' is not used, and always contains 0

if no animation is available, the default uses the standing animation(s) with ''alpha=0~1:600''

==== recruiting ====

This animation is triggered for the leader when a unit is recruited or recalled

''value='' is not used, and always contains 0

''value_second='' is not used, and always contains 0

no default animation is needed

note that is not triggered for WML triggered animations

==== levelout ====
This animation is triggered whenever the unit levels, before the unit is replaced by the new unit.

''value='' is not used, and always contains 0

''value_second='' is not used, and always contains 0

if no animation is available, the default uses the standing animation(s) with ''blend_ratio="0~1:600" blend_color=255,255,255''

==== levelin ====
This animation is triggered whenever the unit levels, after the unit is replaced by the new unit.

''value='' is not used, and always contains 0

''value_second='' is not used, and always contains 0

if no animation is available, the default uses the standing animation(s) with ''blend_ratio="1~0:600" blend_color=255,255,255''

==== movement ====
This animation is used whenever a unit moves. There are multiple things to consider when dealing with movement animation
* unit stay ''exactly'' 150ms in each hex. so you typically want to have an offset of ''0~1:150,0~1:150,0~1:150,0~1:150,0~1:150'' or something similar
* when a unit enters a hex, the current anim is tested again.
** if the current animation is still valid (i.e it passes all its filter) it is kept, whatever the final score is
** if it fails, a new movement anim is searched

''value='' contains the number of steps already taken

''value_second='' contains the number of steps left

if no animation is available, the default uses the standing animation(s) with ''offset="0~1:150,0~1:150,0~1:150,0~1:150,0~1:150,0~1:150,0~1:150,0~1:150,0~1:150,0~1:150"''

==== pre_movement ====
This animation is used before any unit movement

''value='' is not used, and always contains 0

''value_second='' is not used, and always contains 0

==== post_movement ====
This animation is used after any unit movement

''value='' is not used, and always contains 0

''value_second='' is not used, and always contains 0

==== pre_teleport ====
This animation is triggered whenever the unit teleports, but before it has moved to the target hex

''value='' is not used, and always contains 0

''value_second='' is not used, and always contains 0

if no animation is available, the default uses the standing animation(s) with ''blend_ratio="1~0:150" blend_color=255,255,255''
==== post_teleport ====
This animation is triggered whenever the unit teleports, but after it has moved to the target hex

''value='' is not used, and always contains 0

''value_second='' is not used, and always contains 0

if no animation is available, the default uses the standing animation(s) with ''blend_ratio="0~1:150" blend_color=255,255,255''
==== healing ====
This animation is triggered when the unit has healing powers and uses them

''value='' is the number of points healed

''value_second='' is not used, and always contains 0

No default is provided by the engine
==== healed ====
This animation is triggered whenever the unit is healed for any reason

''value='' is the number of points healed

''value_second='' is not used, and always contains 0

if no animation is available, the default uses the standing animation(s) with ''blend_ratio="0:30,0.5:30,0:30,0.5:30,0:30,0.5:30,0:30,0.5:30,0:30" blend_color=255,255,255''
and plays the sound ''heal.wav''
==== poisoned ====
This animation is triggered whenever the unit suffers poison damage

''value='' is the number of points lost

''value_second='' is not used, and always contains 0

if no animation is available, the default uses the standing animation(s) with ''blend_ratio="0:30,0.5:30,0:30,0.5:30,0:30,0.5:30,0:30,0.5:30,0:30" blend_color=0,255,0''
and plays the sound 'poison.ogg''

==== defend ====
This animation is triggered during a strike, of the unit receiving the blow

''value='' is the number of point lost, if any

''value_second='' is the number of the swing, starting from 1

No default is provided by the engine
==== attack ====
This animation is triggered during a strike, of the unit giving the blow

''value='' is the number of damage dealt, if any

''value_second='' is the number of the swing, starting from 1

if no animation is available, the default uses the standing animation(s) with ''offset="0~0.6:150,0.6~0:150"'' for melee attacks
No default is provided for range attacks
==== leading ====
This animation is triggered for units with the leading special ability, when the unit they are leading is attacking

''value='' is not used, and always contains 0

''value_second='' is the number of the swing, starting from 1

No default is provided by the engine

==== resistance ====
This animation is triggered for units with the resistance special ability affecting neighbouring fights, when the unit they are helping is defending

''value='' is not used, and always contains 0

''value_second='' is the number of the swing, starting from 1

No default is provided by the engine

==== death ====
This animation is triggered when a unit die.

''value='' is not used, and always contains 0

''value_second='' is not used, and always contains 0

if no animation is available, the default uses the standing animation(s) with ''alpha=1~0:600'' and plays the sound in ''die_sound='' of the enclosing unit
==== victory ====
This animation is triggered when a unit finishes a fight by killing the other unit

''value='' is not used, and always contains 0

''value_second='' is not used, and always contains 0

No default is provided by the engine
==== idling ====
This animation is called when the unit has been using its standing animation for a random duration.

''value='' is not used, and always contains 0

''value_second='' is not used, and always contains 0

No default is provided by the engine

==== draw_weapon ====
This animation is played before a fight

''hit='' is set to HIT for the attacker and MISS for the defender

No default is provided by the engine

==== sheath_weapon ====
This animation is played after a fight simultaneously for all surviving units

No default is provided by the engine

==== default ====

This animation is never triggered, but is used as a base to create new animations

''value='' is used depending of the type of animation it replaces

''value_second='' is used depending of the type of animation it replaces

A single animation made of the base frame is provided by the engine if no default animation is available

==== extra animations ====
Other values are never called by the engine. However they can be triggered by WML events allowing custom animations.

Note that WML events can also trigger standard animations.
''value='' is set from the WML event

''value_second='' is set from the WML event

== Shortcuts, tricks and quirks ==

=== ''[if]'' and ''[else]'' ===

Often, you need to do very slight variations in an animation (like a different sound depending on whether the unit hits or misses its attack), the '''[if]''' and '''[else]''' tags are meant to help you do that. ('''Attention:''' These do not have the same syntax as the action tag [if] and its subtag [else] in [[ConditionalActionsWML]].)

Using these in an animation is equivalent to having multiple animations, one with the '''[if]''' block and one with each of the ''[else]'' blocks. Any filtering flags in these blocks will replace the toplevel filters. You can have multiple '''[if]''' blocks in an animation, but you can't nest an '''[if]''' inside another. These should be written directly inside the '''[animation]''' block. The following example would make the '''[frame]''' inside the '''[if]''' be played when the attack misses, and the '''[frame]''' inside the '''[else]''' be played when the attack hits (producing a different sound):

[if]
hits=no
[frame]
begin=-100
end=100
image="units/dwarves/lord-attack.png"
sound={SOUND_LIST:MISS}
[/frame]
[/if]
[else]
hits=yes
[frame]
begin=-100
end=100
image="units/dwarves/lord-attack.png"
sound=axe.ogg
[/frame]
[/else]

note that this is very close to preprocessing and should be considered as such, especially with regard to scoring and animation selection

=== Simplified animation blocks ===
To simplify the most common animation cases, you can use different blocks instead of the generic '''[animation]''' block. These are also here for backward compatibility, but are not deprecated and fully supported

some of these use extra tags which are translated in the normal ''value='' tag

some of these define '''[xxx_frame]''' blocks where the frame prefix starts with an underscore. This is not allowed in normal WML (prefix starting with underscore is reserved for the engine internal use). It is here for clarity purpose

* '''[leading_anim]''' is an animation with the following parameters automatically set
apply_to=leading
* '''[recruit_anim]''' is an animation with the following parameters automatically set
apply_to=recruited
* '''[recruiting_anim]''' is an animation with the following parameters automatically set
apply_to=recruiting
* '''[standing_anim]''' is an animation with the following parameters automatically set
apply_to=standing,default
note for 1.4 :''default'' doesn't exist in 1.4, but the semantic is the same.

i.e: the animation will be used to build default animations
* '''[idle_anim]''' is an animation with the following parameters automatically set
apply_to=idling
* '''[levelout_anim]''' is an animation with the following parameters automatically set
apply_to=levelout
* '''[levelin_anim]''' is an animation with the following parameters automatically set
apply_to=levelin
* '''[healing_anim]''' is an animation with the following parameters automatically set
apply_to=healing
value=<damage= value>
* '''[healed_anim]''' is an animation with the following parameters automatically set
apply_to=healed
value=<healing= value>
[_healed_sound_frame]
sound=heal.wav
[/_healed_sound_frame]
* '''[poison_anim]''' is an animation with the following parameters automatically set
apply_to=poisoned
value=<damage= value>
[_poison_sound_frame]
sound=poison.ogg
[/_poison_sound_frame]
* '''[movement_anim]''' is an animation with the following parameters automatically set
apply_to=movement
offset="0~1:150,0~1:150,0~1:150,0~1:150,0~1:150,0~1:150,0~1:150"
* '''[pre_movement_anim]''' is an animation with the following parameters automatically set
apply_to=pre_movement
* '''[post_movement_anim]''' is an animation with the following parameters automatically set
apply_to=post_movement
* '''[draw_weapon_anim]''' is an animation with the following parameters automatically set
apply_to=draw_weapon
* '''[sheath_weapon_anim]''' is an animation with the following parameters automatically set
apply_to=sheath_weapon_movement
* '''[defend]''' is an animation with the following parameters automatically set
apply_to=defend
value=<damage= value>
<WML content>
[frame]
blend_color=255,0,0
blend_ratio="0.5:50,0.0:50"
[/frame]

there are some subtil change compared to what is described above to avoid the red flash when value=0, but it should work as expected as far as WML author are concerned

* '''[attack_anim]''' is an animation with the following parameters automatically set
if the animation contains a missile frame

apply_to=attack
missile_offset="0~0.8"

else

apply_to=attack
offset="0~0.6,0.6~0"

* '''[death]''' is an animation with the following parameters automatically set
apply_to=death
[_death_sound_frame]
sound=<die_sound= of the enclosing [unit] tag>
[/_death_sound_frame]
* '''[victory_anim]''' is an animation with the following parameters automatically set
apply_to=victory
* '''[extra_anim]''' is an animation with the following parameters automatically set
apply_to=<flag= value of the anim>
* '''[teleport_anim]''' will be cut into two at the clock-time 0
everything before zero becomes an animation with the following parameters automatically set
apply_to=pre_teleport
everything after zero becomes an animation with the following parameters automatically set
apply_to=post_teleport

== Layering ==
The ''layer'' progressive parameter allows the animation writer to choose in what order the animation should be drawn.

this value must be between 0 and 100

* the back of haloes is drawn with a value of 10
* when unspecified, a animation is drawn with a value of 40
* terrain elements that are supposed to go in front of units (castles) are drawn with a value of 50
* orbs and status bars are drawn on layer 80
* when unspecified missile frames are drawn on layer 90

by changing these values, it is easy to have the unit display the way you want

== Optimization ==

there is a special flag that goes into the animation block (not the frame)

* ''offscreen'' a boolean saying if the unit's animation should be played when the unit is offscreen. You want the animation to play offscreen if the animation contains some usefull sound effects.This attribute defaults to true (play offscreen) except for standing and idle animations where it defaults to false

== Cycling ==

there is a special boolean parameter that can be put in an animation block (not the frame)

* ''cycles'' a boolean value. if set to true the animation will cycles forever until it is replaced. That animation will not influence the end time of all related animations (for example a cycling defense animation will play normally but the overall duration of the fight animation will be only decided by the attack animation)

== See Also ==

* [[UnitTypeWML]]
* [[ReferenceWML]]

[[Category: WML Reference]]

AnimationWML

2012-10-07T20:50:45Z

Tr0ll: grammar

{{WML Tags}}

== Introduction ==

This page covers unit animations. At any point in game, units are playing an animation. Even when the unit is standing, it is actually playing a single frame animation.

This page will deal with the two problems of animations
* How are animations chosen
* What exactly is drawn

== How animations are drawn ==
=== Animations ===
Any unit has a huge set of animations to choose from. Animations are WML blocks in the unit type, enclosed in either the generic type '''[animation]''' or some more specific tags such as '''[attack_anim]''' '''[idle_anim]''' and the like. An animation is what a unit displays when a given event is triggered, and a certain set of conditions are met such as
* unit is attacking
* unit is idling
* unit is attacking (event) and uses a melee weapon (condition)
* unit is attacking (event) and uses a melee weapon (condition) and opponent can't retaliate (condition)

events and conditions are described entirely in the [animation] block, and will be discussed in the animation choice section.

=== Frames ===

An animation is cut in frames. Frames are WML blocks that are contained either in '''[frame]''' WML blocks or in generic '''[xxx_frame]''' block. (the xxx part can be any string not starting with an underscore) the xxx part in the frame name is called the frame prefix. frames of the type '''[frame]''' are said to have an empty prefix

A frame typically describes an image, where an how to render it. It can contain such things as
* the image to display
* how transparent should that image be
* where to draw that image.

At any given time, an animation will display one frame for each frame prefix it can find. I.e if your animation has both '''[frame]''' and '''[missile_frame]''' blocks, both will be displayed at the same time

The frame with the empty prefix is special in many way. It is assumed to contain the image representing the unit itself, and as such the engine will heavily temper with it in multiple ways, such as providing a default image if none is available, or forcing the image to be green when the unit is poisoned

=== Timing, Clock, Multiple animations ===
When an animation is played it has an internal clock that is run. The step of this clock is the milisecond, and each frame is played for a given duration. Each animation also has a starting time which tells the animation engine at what value the animation clock should start

This starting time is very important when multiple animations from different units are played synchronously Typically a fight involves a unit playing its defense animation while the opponent plays its attack animation (and a third might play its leading animation, too). In that case all animations have a common clock, and are played concurrently.

The convention is that the "important time" (usually the time of the hit) is at time 0. everything before should be at negative time, everything after at positive time. This is a WML convention that is not enforced by the engine

In that case, it is very important that these animations (which can have different lengths) be synchronized. Fight animations are synchronized around the point of impact, so they all reach time 0 when the attack lands (or misses). This is accomplished through the use of the '''start_time''' key of the '''[animation]''' tag.

Just like the '''[frame]''' tag can have a prefix, so can the '''start_time''' key. A '''start_time''' key without prefix will affect a '''[frame]''' tag without prefix, while a '''start_time''' key with a prefix will affect a '''[frame]''' tag with the same prefix.

==== Example Syntax ====
[attack_anim]
[filter_attack]
name=bow
[/filter_attack]
'''start_time'''=-350
'''missile_start_time'''=-150
[missile_frame]
duration=150
image="projectiles/missile-n.png"
image_diagonal="projectiles/missile-ne.png"
[/missile_frame]
[if]
hits=yes
[frame]
duration=350
sound=bow.ogg
[/frame]
[/if]
[else]
hits=no
[frame]
duration=350
sound=bow-miss.ogg
[/frame]
[/else]
[/attack_anim]

=== The content of a frame ===
==== Syntax summary ====
[frame]
duration=<integer>
begin=<deprecated,integer>
end=<deprecated,integer>
image=<string>
image_diagonal=<string>
image_mod=<string>
sound=<string>
halo=<progressive string>
halo_x=<progressive int>
halo_y=<progressive int>
halo_mod=<string>
alpha=<progressive float>
offset=<progressive float>
blend_color=<red, green, blue>
blend_ratio=<progressive float>
text=<string>
text_color=< red, green, blue >
submerge=<progressive float>
x=<progressive int>
y=<progressive int>
directional_x=<dev feature 1.9,progressive int>
directional_y=<dev feature 1.9,progressive int>
layer=<progressive int>
auto_hflip=<dev feature 1.9, boolean>
auto_vflip=<dev feature 1.9, boolean>
primary=<dev feature 1.9, boolean>
[/frame]

==== Progressive parameters ====

Some parameters above are marked as ''progressive'' This means that you can specify that during the time the frame is displayed, the parameter should smoothly slide from one value to an other.

A typical example would be a unit progressively fading out, becoming transparent

To do that, you could use:

alpha=1~0

To make a frame, which is 900ms long, slide to transparent for 300ms, stay transparent for another 300ms and finally fade back to normal for 300ms, use:

alpha=1~0:300,0:300,0~1:300

you could also specify it like that

alpha=1~0,0,0~1

when a timing is missing, the engine will do its best to fill in in a fair way.

a progressive string has a similar syntax

halo=halo1.png:300,halo2.png:300,halo2.png:300

==== Field Description ====

** '''begin''': (deprecated) will be replaced by '''duration= <end - begin >'''
** '''end''': (deprecated) see '''begin''' and also [[AnimationWML#Timing.2C_Clock.2C_Multiple_animations|Timing, Clock, Multiple animations]] section for coverage of '''start_time''' which combines with '''duration''' to replace '''begin=''' '''end='''.
** '''duration''': how long the frame should be displayed. Use instead of '''begin=''' and '''end='''.
** '''image''': the image to display during the frame.
** '''image_diagonal''': the image to display when the attack occurs diagonally (directions ne,se,sw,nw).
** '''image_mod''': a string modifications (see [[ImagePathFunctionWML]] ) that will be applied to all images
** '''sound''': the sound to play when the frame begins. Can be a comma-separated list of sounds, in which case one of them is chosen randomly every time.
** '''halo''': the halo to display at the time.
** '''halo_x''': the position the halo is displayed in pixel relative to the unit's center.
** '''halo_y''': the position the halo is displayed in pixel relative to the unit's center.
** '''halo_mod''': a string modifications (see [[ImagePathFunctionWML]] ) that will be applied to all haloes
** '''alpha''': transparency level to apply to the frame. This is a floating point progressive parameter ranging from 0.0 to 1.0.
** '''offset''': the position of the image relative to the hex the unit is facing, 0.0 will display the unit in the center of the hex, 1.0 in the center of the faced hex, -1.0 at the center of the hex behind you. This is a progressive parameter.
** '''blend_color''': a comma separated list of numbers representing a color in RGB (0-255); this color will be mixed to the frame to give it a tint.
** '''blend_ratio''': this is a progressive parameter ranging from 0 to 1: 0 means no tint, 1 means target color only.
** '''text''': if specified, floats a label with the given text above the unit (identical to the floating damage and healing numbers).
** '''text_color''': the color of the above floating label.
** '''submerge''': the part of the unit that should drawn with 50% opacity (for units in water)
** '''x''': x offset applied to the frame
** '''y''': y offset applied to the frame
** '''directional_x''': the x offset, in pixels, applied to the frame in the direction the unit is facing
** '''directional_y''': the y offset, in pixels, applied to the frame in the direction the unit is facing
** '''layer''': layer used to draw the frame, see discussion bellow
** '''auto_hflip''': should the image flip horizontally depending on sprite orientation
** '''auto_vflip''': should the image flip vertically depending on sprite orientation
** '''primary''': should the engine consider that frame as a primary frame (affected by visual effects like stone and poison)

=== Drawing related animation content ===
==== Syntax summary ====
[animation]
<animation choice related content>
[frame]
<frame content>
[/frame]
[frame]
<frame content>
[/frame]
start_time=<integer>
offset=<progressive float>
image_mod=<string>
blend_color=<r,g,b>
blend_ratio=<progressive float>
halo=<progressive_string>
halo_x=<progressive int>
halo_y=<progressive int>
halo_mod=<string>
submerge=<progressive float>
x=<progressive int>
y=<progressive int>
directional_x=<dev1.9,progressive int>
directional_y=<dev1.9,progressive int>
layer=<progressive int>

[xxx_frame]
<frame content>
[/xxx_frame]
xxx_start_time=<integer>
xxx_image_mod=<string>
xxx_offset=<progressive float>
xxx_blend_color=<r,g,b>
xxx_blend_ratio=<progressive float>
xxx_halo=<progressive_string>
xxx_halo_x=<progressive int>
xxx_halo_y=<progressive int>
xxx_halo_mod=<string>
xxx_submerge=<progressive float>
xxx_x=<progressive int>
xxx_y=<progressive int>
xxx_directional_x=<dev1.9,progressive int>
xxx_directional_y=<dev1.9,progressive int>
xxx_layer=<progressive int>

[/animation]

==== Parameter handling ====
All drawing related parameters in '''[animation]''' can be matched with a corresponding parameter in a '''[frame]''' block (or a '''[xxx_frame]''' block) The value provided in the animation will be used if no value is provided in the frame.

The point of these two level of parameters is to easily be able to specify a parameter at the animation level and override it for a special case of frame.

== How animations are chosen ==
Within a unit description block there are multiple animations. Each animation is meant to be played in a very special set of circumstances. We will discuss here how to tell the animation engine when a given animation should be played.

Let's take an example. Suppose we have a unit which has the skirmisher ability. We have the following movement animations :
* a normal walking animation
* a swimming animation when the unit is in water
* a tiptoeing animation when moving next to an enemy unit

Ok. most of the time it's easy to guess what animation should be. However if you are both in water and next to an enemy unit, the animation to play is not obvious.

To solve that question, each animation has a number of filtering criteria. The engine follow the following rules to select an animation
* Start with all animations
* Drop all animations with a criteria that fails on the current situation
* Take the animations that have the most matching criteria
* If there are more than one animation remaining, take an animation randomly
* If all animations have been dropped, the engine will provide a smart default.

here is a pseudo-code explanation of this algorithm:

foreach animation
animation_score = 0
foreach filter-criteria
if <criteria-fails>
animation_score = -1;
break;
elsif <criteria-matches>
animation_score++
endfor
if animation_score > max_score
<empty animation list>
max_score = animation_score;
push(animation,animation_list);
elsif animation_score = max_score
push(animation,animation_list);
endfor
<choose an animation randomly from animation_list>

Note that all animations don't have all the filters...

so, if we have a unit with
# an animation for water terrain
# an animation for SE on grassland
# an animation with no criteria
# an animation for N,NE,NW,S,SW,SE
# an animation for NW

* 3. will never be taken, because 4. will always trump it
* on water going NW, it can be 1. 4. 5.
* on water, any direction but NW, it will be 1. or 4.
* on SE grassland it will be 2.
* on other grasslands, it will be 4. (4. or 5. if NW)

=== Generic animation filters available for all animations ===
* '''apply_to''': a list of comma separated keywords describing what event should trigger the animation (movement, attack...) the complete list is given below
* '''value''': a list of comma separated integer, the meaning depends on the triggering event. the meaning is given with the list of event
* '''value_second''': a list of comma separated integer, the meaning depends on the triggering event. the meaning is given with the list of event
* '''terrain''': a list of comma separated terrain letters, the animation will only be used on these terrains. See [[FilterWML#Filtering Terrains|Filtering Terrains]]. this has been replaced by '''terrain_type'''
* '''terrain_type''': a list of comma separated terrain codes, the animation will only be used on matching terrains. See [[FilterWML#Filtering Terrains|Filtering Terrains]].
* '''[filter]''': this will filter using a [[StandardUnitFilter|standard unit filter]] on the animated unit. Note that matching all criterias in the filter will only earn you one point for animation selection, but that you can have multiple '''[filter]''' blocks in an animation.
* '''[filter_second]''': this will filter using a [[StandardUnitFilter|standard unit filter]] on the unit in the hex faced. Note that matching all criteria in the filter will only earn you one point for animation selection, but that you can have multiple '''[filter_second]''' blocks in an animation. Also note that if the faced hex is empty, the whole filter will fail.
* '''direction''': a list of directions (n,ne,se,s,sw,nw), the animation will only be used when acting or moving in this direction (the attack direction for attack animations, moving direction for movement animations, direction of lead unit for leading animations, and so on).
* '''frequency''': this integer value allows to easily tweak the matching frequency of animations. The filter will fail n-1 times out of n, randomly. Note that unlike every other filter, matching this filter won't give an extra point.
* '''[filter_attack]''': a standard attack filter to match on the attacker's attack. See [[FilterWML#Filtering Weapons|Filtering Weapons]].
* '''[filter_second_attack]''': a standard attack filter to match on the defender's attack. See [[FilterWML#Filtering Weapons|Filtering Weapons]]. Also note that if the defender doesn't have any weapon to retaliate with, this filter will always fail.
* '''hits''': filters attack animations based on whether the attack hits, misses or kills. Accepts a list of the following:
** '''hit''': the attack hits, defender survives.
** '''no''' or '''miss''': the attack misses.
** '''kill''': the attack hits, defender dies.
** '''yes''': is an alias of '''hit,kill'''.
* '''swing''': a list of numbers representing the swing numbers this animation should match (numbered from 1). this has been replaced by value_second
* '''base_score''': a number that will always be added to the score. Use with caution

=== Events triggering animations and default animations ===
==== standing ====
This animation is triggered whenever any other animation is finished, and is played in loop until another animation is triggered

this is the default "standing image" for the unit

''value='' is not used, and always contains 0

''value_second='' is not used, and always contains 0

if no standing animation is set a single frame animation based on the enclosing unit's '''image=''' field is used
==== selected ====
This animation is triggered whenever the unit is selected

''value='' is not used, and always contains 0

''value_second='' is not used, and always contains 0

if no animation is available, the default uses the standing animation(s) with ''blend_ratio="0.0~0.3:100,0.3~0.0:200" blend_color=255,255,255''
==== recruited ====
This animation is triggered whenever the unit is recruited or recalled

''value='' is not used, and always contains 0

''value_second='' is not used, and always contains 0

if no animation is available, the default uses the standing animation(s) with ''alpha=0~1:600''

==== recruiting ====

This animation is triggered for the leader when a unit is recruited or recalled

''value='' is not used, and always contains 0

''value_second='' is not used, and always contains 0

no default animation is needed

note that is not triggered for WML triggered animations

==== levelout ====
This animation is triggered whenever the unit levels, before the unit is replaced by the new unit.

''value='' is not used, and always contains 0

''value_second='' is not used, and always contains 0

if no animation is available, the default uses the standing animation(s) with ''blend_ratio="0~1:600" blend_color=255,255,255''

==== levelin ====
This animation is triggered whenever the unit levels, after the unit is replaced by the new unit.

''value='' is not used, and always contains 0

''value_second='' is not used, and always contains 0

if no animation is available, the default uses the standing animation(s) with ''blend_ratio="1~0:600" blend_color=255,255,255''

==== movement ====
This animation is used whenever a unit moves. There are multiple things to consider when dealing with movement animation
* unit stay ''exactly'' 150ms in each hex. so you typically want to have an offset of ''0~1:150,0~1:150,0~1:150,0~1:150,0~1:150'' or something similar
* when a unit enters a hex, the current anim is tested again.
** if the current animation is still valid (i.e it passes all its filter) it is kept, whatever the final score is
** if it fails, a new movement anim is searched

''value='' contains the number of steps already taken

''value_second='' contains the number of steps left

if no animation is available, the default uses the standing animation(s) with ''offset="0~1:150,0~1:150,0~1:150,0~1:150,0~1:150,0~1:150,0~1:150,0~1:150,0~1:150,0~1:150"''

==== pre_movement ====
This animation is used before any unit movement

''value='' is not used, and always contains 0

''value_second='' is not used, and always contains 0

==== post_movement ====
This animation is used after any unit movement

''value='' is not used, and always contains 0

''value_second='' is not used, and always contains 0

==== pre_teleport ====
This animation is triggered whenever the unit teleports, but before it has moved to the target hex

''value='' is not used, and always contains 0

''value_second='' is not used, and always contains 0

if no animation is available, the default uses the standing animation(s) with ''blend_ratio="1~0:150" blend_color=255,255,255''
==== post_teleport ====
This animation is triggered whenever the unit teleports, but after it has moved to the target hex

''value='' is not used, and always contains 0

''value_second='' is not used, and always contains 0

if no animation is available, the default uses the standing animation(s) with ''blend_ratio="0~1:150" blend_color=255,255,255''
==== healing ====
This animation is triggered when the unit has healing powers and uses them

''value='' is the number of points healed

''value_second='' is not used, and always contains 0

No default is provided by the engine
==== healed ====
This animation is triggered whenever the unit is healed for any reason

''value='' is the number of points healed

''value_second='' is not used, and always contains 0

if no animation is available, the default uses the standing animation(s) with ''blend_ratio="0:30,0.5:30,0:30,0.5:30,0:30,0.5:30,0:30,0.5:30,0:30" blend_color=255,255,255''
and plays the sound ''heal.wav''
==== poisoned ====
This animation is triggered whenever the unit suffers poison dammage

''value='' is the number of points lost

''value_second='' is not used, and always contains 0

if no animation is available, the default uses the standing animation(s) with ''blend_ratio="0:30,0.5:30,0:30,0.5:30,0:30,0.5:30,0:30,0.5:30,0:30" blend_color=0,255,0''
and plays the sound 'poison.ogg''
==== defend ====
This animation is triggered during a strike, of the unit receiving the blow

''value='' is the number of point lost, if any

''value_second='' is the number of the swing, starting from 1

No default is provided by the engine
==== attack ====
This animation is triggered during a strike, of the unit giving the blow

''value='' is the number of damage dealt, if any

''value_second='' is the number of the swing, starting from 1

if no animation is available, the default uses the standing animation(s) with ''offset="0~0.6:150,0.6~0:150"'' for melee attacks
No default is provided for range attacks
==== leading ====
This animation is triggered for units with the leading special ability, when the unit they are leading is attacking

''value='' is not used, and always contains 0

''value_second='' is the number of the swing, starting from 1

No default is provided by the engine

==== resistance ====
This animation is triggered for units with the resistance special ability affecting neighbouring fights, when the unit they are helping is defending

''value='' is not used, and always contains 0

''value_second='' is the number of the swing, starting from 1

No default is provided by the engine

==== death ====
This animation is triggered when a unit die.

''value='' is not used, and always contains 0

''value_second='' is not used, and always contains 0

if no animation is available, the default uses the standing animation(s) with ''alpha=1~0:600'' and plays the sound in ''die_sound='' of the enclosing unit
==== victory ====
This animation is triggered when a unit finishes a fight by killing the other unit

''value='' is not used, and always contains 0

''value_second='' is not used, and always contains 0

No default is provided by the engine
==== idling ====
This animation is called when the unit has been using its standing animation for a random duration.

''value='' is not used, and always contains 0

''value_second='' is not used, and always contains 0

No default is provided by the engine

==== draw_weapon ====
This animation is played before a fight

''hit='' is set to HIT for the attacker and MISS for the defender

No default is provided by the engine

==== sheath_weapon ====
This animation is played after a fight simultaneously for all surviving units

No default is provided by the engine

==== default ====

This animation is never triggered, but is used as a base to create new animations

''value='' is used depending of the type of animation it replaces

''value_second='' is used depending of the type of animation it replaces

A single animation made of the base frame is provided by the engine if no default animation is available

==== extra animations ====
Other values are never called by the engine. However they can be triggered by WML events allowing custom animations.

Note that WML events can also trigger standard animations.
''value='' is set from the WML event

''value_second='' is set from the WML event

== Shortcuts, tricks and quirks ==

=== ''[if]'' and ''[else]'' ===

Often, you need to do very slight variations in an animation (like a different sound depending on whether the unit hits or misses its attack), the '''[if]''' and '''[else]''' tags are meant to help you do that. ('''Attention:''' These do not have the same syntax as the action tag [if] and its subtag [else] in [[ConditionalActionsWML]].)

Using these in an animation is equivalent to having multiple animations, one with the '''[if]''' block and one with each of the ''[else]'' blocks. Any filtering flags in these blocks will replace the toplevel filters. You can have multiple '''[if]''' blocks in an animation, but you can't nest an '''[if]''' inside another. These should be written directly inside the '''[animation]''' block. The following example would make the '''[frame]''' inside the '''[if]''' be played when the attack misses, and the '''[frame]''' inside the '''[else]''' be played when the attack hits (producing a different sound):

[if]
hits=no
[frame]
begin=-100
end=100
image="units/dwarves/lord-attack.png"
sound={SOUND_LIST:MISS}
[/frame]
[/if]
[else]
hits=yes
[frame]
begin=-100
end=100
image="units/dwarves/lord-attack.png"
sound=axe.ogg
[/frame]
[/else]

note that this is very close to preprocessing and should be considered as such, especially with regard to scoring and animation selection

=== Simplified animation blocks ===
To simplify the most common animation cases, you can use different blocks instead of the generic '''[animation]''' block. These are also here for backward compatibility, but are not deprecated and fully supported

some of these use extra tags which are translated in the normal ''value='' tag

some of these define '''[xxx_frame]''' blocks where the frame prefix starts with an underscore. This is not allowed in normal WML (prefix starting with underscore is reserved for the engine internal use). It is here for clarity purpose

* '''[leading_anim]''' is an animation with the following parameters automatically set
apply_to=leading
* '''[recruit_anim]''' is an animation with the following parameters automatically set
apply_to=recruited
* '''[recruiting_anim]''' is an animation with the following parameters automatically set
apply_to=recruiting
* '''[standing_anim]''' is an animation with the following parameters automatically set
apply_to=standing,default
note for 1.4 :''default'' doesn't exist in 1.4, but the semantic is the same.

i.e: the animation will be used to build default animations
* '''[idle_anim]''' is an animation with the following parameters automatically set
apply_to=idling
* '''[levelout_anim]''' is an animation with the following parameters automatically set
apply_to=levelout
* '''[levelin_anim]''' is an animation with the following parameters automatically set
apply_to=levelin
* '''[healing_anim]''' is an animation with the following parameters automatically set
apply_to=healing
value=<damage= value>
* '''[healed_anim]''' is an animation with the following parameters automatically set
apply_to=healed
value=<healing= value>
[_healed_sound_frame]
sound=heal.wav
[/_healed_sound_frame]
* '''[poison_anim]''' is an animation with the following parameters automatically set
apply_to=poisoned
value=<damage= value>
[_poison_sound_frame]
sound=poison.ogg
[/_poison_sound_frame]
* '''[movement_anim]''' is an animation with the following parameters automatically set
apply_to=movement
offset="0~1:150,0~1:150,0~1:150,0~1:150,0~1:150,0~1:150,0~1:150"
* '''[pre_movement_anim]''' is an animation with the following parameters automatically set
apply_to=pre_movement
* '''[post_movement_anim]''' is an animation with the following parameters automatically set
apply_to=post_movement
* '''[draw_weapon_anim]''' is an animation with the following parameters automatically set
apply_to=draw_weapon
* '''[sheath_weapon_anim]''' is an animation with the following parameters automatically set
apply_to=sheath_weapon_movement
* '''[defend]''' is an animation with the following parameters automatically set
apply_to=defend
value=<damage= value>
<WML content>
[frame]
blend_color=255,0,0
blend_ratio="0.5:50,0.0:50"
[/frame]

there are some subtil change compared to what is described above to avoid the red flash when value=0, but it should work as expected as far as WML author are concerned

* '''[attack_anim]''' is an animation with the following parameters automatically set
if the animation contains a missile frame

apply_to=attack
missile_offset="0~0.8"

else

apply_to=attack
offset="0~0.6,0.6~0"

* '''[death]''' is an animation with the following parameters automatically set
apply_to=death
[_death_sound_frame]
sound=<die_sound= of the enclosing [unit] tag>
[/_death_sound_frame]
* '''[victory_anim]''' is an animation with the following parameters automatically set
apply_to=victory
* '''[extra_anim]''' is an animation with the following parameters automatically set
apply_to=<flag= value of the anim>
* '''[teleport_anim]''' will be cut into two at the clock-time 0
everything before zero becomes an animation with the following parameters automatically set
apply_to=pre_teleport
everything after zero becomes an animation with the following parameters automatically set
apply_to=post_teleport

== Layering ==
The ''layer'' progressive parameter allows the animation writer to choose in what order the animation should be drawn.

this value must be between 0 and 100

* the back of haloes is drawn with a value of 10
* when unspecified, a animation is drawn with a value of 40
* terrain elements that are supposed to go in front of units (castles) are drawn with a value of 50
* orbs and status bars are drawn on layer 80
* when unspecified missile frames are drawn on layer 90

by changing these values, it is easy to have the unit display the way you want

== Optimization ==

there is a special flag that goes into the animation block (not the frame)

* ''offscreen'' a boolean saying if the unit's animation should be played when the unit is offscreen. You want the animation to play offscreen if the animation contains some usefull sound effects.This attribute defaults to true (play offscreen) except for standing and idle animations where it defaults to false

== Cycling ==

there is a special boolean parameter that can be put in an animation block (not the frame)

* ''cycles'' a boolean value. if set to true the animation will cycles forever until it is replaced. That animation will not influence the end time of all related animations (for example a cycling defense animation will play normally but the overall duration of the fight animation will be only decided by the attack animation)

== See Also ==

* [[UnitTypeWML]]
* [[ReferenceWML]]

[[Category: WML Reference]]

BuildingScenariosSimple

2012-10-07T17:36:21Z

Tr0ll:

{{BuildingScenariosNav}}

= Learning things step by step =

Here we will show you a very simple scenario file and explain each line of it.
The file is not fully functional, but it will show the basics needed to describe what a scenario is all about.

'''Before reading this, it might prove useful to read something about the syntax of the Wesnoth Markup Language: [[SyntaxWML]]'''

== First part ==

<blockquote>
<pre>
<nowiki>
#textdomain wesnoth-Simple_Campaign
[scenario]

id=01_test-1
next_scenario=02_test-more

name= _ "A Simple Test Scenario"
map_data="{~add-ons/Test_Campaign/maps/testmap.map}"
turns=20

{DAWN}
{MORNING}
{AFTERNOON}
{DUSK}
{FIRST_WATCH}
{SECOND_WATCH}

music=battle.ogg

[event]
name=prestart
[objectives]
side=1
[objective]
description= _ "Defeat Enemy Leader"
condition=win
[/objective]
[objective]
description= _ "Death of Konrad"
condition=lose
[/objective]
[objective]
description= _ "Turns run out"
condition=lose
[/objective]
[/objectives]
[/event]
</nowiki>
</pre>

''continued below''
     ↓ ↓ ↓
</blockquote>
* <code>#textdomain</code> must be provided at the start of your scenario file if you want it to be translated. Format is <code>#textdomain wesnoth-Name_of_your_campaign</code>, as defined in your _main.cfg file.

Every scenario must be enclosed in a tag; the <code>[scenario]</code> tag is used for campaign scenarios. The first set of attributes in the scenario tag describe the very basics of this scenario:

* <code>id</code> (short for ''identifier'') is the computer's name for your scenario and is not displayed during the game. However, it will be used to display game statistics (they will be graphed at http://stats.wesnoth.org in numerical order, so it's also a good idea to give the <code>id</code>'s a number). This name is also referenced in other tags and files, ''e.g.,'' inside a <code>[campaign]</code> tag using the <code>first_scenario</code> attribute (see [[BuildingCampaignsTheCampaignFile]]) or inside a <code>[scenario]</code> tag using the <code>next_scenario</code> attribute (see below).

* The value of the <code>next_scenario</code> attribute is the <code>id</code> (see above) of the scenario that is played after this one is won. Units from this scenario will be available for recall (unless you modify the recall list, but that's stuff for later). If your scenario is not part of a campaign, or if this is the last scenario you should either skip this line or put <code>next_scenario=null</code> inside the file. This will tell the game to display the ''End'' screen when this scenario is won.

* The value of the <code>name</code> attribute is shown on the introduction screen before each scenario is played (this may contain a picture of a map or anything else you fancy. See [[BuildingScenariosIntermediate]] for an explanation on how to do that). It's also used to generate the default names of saved files for the level. The underscore before the name marks it as translatable.

* The next attribute, <code>map_data</code> is a little tricky. Normally, the map data (the text that is used to generate a map) goes directly inside of the quotation marks. However, it is often useful to keep that map data in a separate file, and then include that file (still inside the quotation marks) using a [[PreprocessorRef|preprocesser]] command. The code <code>{~add-ons/Test_Campaign/maps/testmap.map}</code> does just that, telling the wesnoth engine to look in the file <code>add-ons/Test_Campaign/maps/testmap</code> for the map data. The <code>~</code> symbol tells Wesnoth to search for the map file in the ''userdata'' directory (see [[EditingWesnoth]] and [[PreprocessorRef]] for more information). You can create and edit map files using Wesnoth's built-in [[Editor2|map editor]] (see [[BuildingMaps]] for more information).

* Finally, the last attribute in the top set of keys is <code>turns</code>. This is the number of turns a player is given to finish the scenario (it can be changed during the game, but again, that is stuff for later). If the player fails to finish the scenario in the given time, he has lost (''i.e.,'' the ''defeat'' event is triggered. See [[EventWML]] for more.)

The next section is a group of macros which will be processed by Wesnoth's [[PreprocessorRef|preprocesser]]. Macros are essentially [[WML]] shortcuts. They allow you to define certain pieces of code which can be re-used whenever they are needed. Wesnoth provides you with a whole series of standard, pre-written macros to make life easier, but you yourself can write them too (again, stuff for later).
Let's get back to this example! The macros listed above describe how a day in this scenario will progress. The list of macros above is the normal day used throughout Wesnoth. If you want the entire scenario to take place at night, remove all the macros except for <code>{SECOND_WATCH}</code>. Doing this might, for example, be useful if you've set Konrad to fight the Undead and also want the Undead to have the upper hand throughout the scenario. Remember, though, by setting this to a single time of day rather than the normal diurnal progression shown above, your scenario will effectively take place during one day (or night) rather than across many days as most scenarios do.

The <code>music</code> attribute takes for its value the name of a music file (see [[MusicListWML]] for more). This file must be in the <code>music/</code> directory and must be in [http://en.wikipedia.org/wiki/Ogg Ogg] format.

A tag you'll get to know very well when making scenarios is <code>[event]...[/event]</code>. <code>event</code> tags are used to describe what should be done when various sorts of ''events'' take place. The specific type of event is stated in the <code>event</code>'s <code>name</code> attribute. In this case we're describing the so-called <code>prestart</code> event. This event occurs just ''after'' all the introduction screens for the scenario have been shown but just ''before'' the map itself is displayed. This prestart event is used to set the scenario's objectives, i.e. the contents of the ''Scenario Objectives Dialog'' that will appear once the scenario begins. The purpose of the Scenario Objectives Dialog is to inform the player what must be accomplished to win the scenario and what circumstances bring about defeat. These winning and losing circumstances are defined using the <code>[objectives]</code> tag (N.B. that <code>objectives</code> is plural). Further, each circumstance is defined in its own <code>[objective]</code> (N.B. the singular here) tag with winning circumstances setting <code>condition</code> to <code>win</code>, and with losing circumstances setting it to <code>lose</code>. In the example above, <code>objectives</code> states victory to be "Defeat Enemy Leader". For defeat, however, <code>[objectives]</code> gives the player ''two'' possibilities: either "Death of Konrad" or "Turns run out" (any number of either winning or losing <code>[objective]</code> tags may be given). Accordingly, the Scenario Objectives Dialog will look vaguely like:

<table border=1><tr><td>
'''A Simple Test Scenario'''
 '''Victory:'''
 Defeat Enemy Leader
 '''Defeat:'''
 Death of Konrad
 Turns run out
 
        
        
      [ OK ]
</td></tr></table>

Note that the <code>[objectives]</code> tag doesn't define the circumstances of victory or defeat to the game engine. It merely tells the player what they are. Special victory or defeat conditions will have to be coded into the scenario using various [event]s.

The <code>side</code> attribute in <code>[objectives]</code> indicates that the conditions defined here by the <code>[objective]</code> tags are for the faction or alliance ''side 1'' alone (see below). In a single-player game, side 1 would usually indicate the player's faction or alliance). The underscore ("_") facilitates translation using [[GetText|Gettext]].

== Second part ==
So far so good! The last necessary part describes what the players (both human and
computer) start with, what they can do, and what they can't do. Each of the players is described in a <code>[side]</code> tag with the word ''side'' referring to a player's faction, band, or horde.

<blockquote>
    ↑ ↑ ↑
 ''continued from above''
<pre>
<nowiki>
[side]
side=1
controller=human
team_name=2
user_team_name= _ "Konrad's forces"

type=Commander
id=Konrad
name= _ "Konrad"
canrecruit=yes

recruit=Elvish Fighter,Elvish Archer,Horseman,Mage,Elvish Shaman

{GOLD 100 50 0}
{INCOME 10 5 0}
[/side]
[/scenario]
</nowiki>
</pre>
</blockquote>

Above you can see a sample <code>[side]</code> for the human player, Konrad. The first group of attributes in the <code>[side]</code> tag pertains to the side generally:
* <code>side</code>: the leader of this side is placed on the tile represented by this digit (see [[BuildingMaps]]). It's a number from 1 to 9.
* <code>controller</code> takes either of two possible values: <code>human</code> or <code>ai</code> (''i.e.,'' ''artificial intelligence'', meaning your computer). If you don't specify this attribute, <code>ai</code> is the default.
* <code>team_name</code> describes which team the side is on. It defaults to the same number as <code>side</code>, but setting it to <code>2</code> allies this side with side 2 (if you haven't changed the <code>team_name</code> of side 2).
* <code>user_team_name</code> is the name displayed when you view the side stats (by pressing <tt>alt+s</tt> during gameplay). The underscore ("_") facilitates translation using [[GetText|Gettext]].

The next group of attributes describe the leader of this side:
* <code>canrecruit</code>: This attribute can be set to <code>yes</code> or <code>no</code> (the boolean equivalents <code>1</code> and <code>0</code> or <code>true</code> and <code>false</code> also work). If this is set to <code>no</code>, the leader won't be able to recruit (not much of a leader then, is he?). Any side without a <code>canrecruit=yes</code> attribute statement automatically loses, so be sure to include this attribute.
* <code>type</code> describes what type of unit the leader will be. The possible values are listed in [http://units.wesnoth.org the Wesnoth unit tables].
* <code>id</code> is the identifier of the leader, as used by the engine, and is not visible by the player.
* <code>name</code> is the name of the leader, as visible to the player. The underscore marks it as translatable.

In a campaign, all of these "leader-describing" attributes are ignored for human players (except <code>canrecruit</code>), since the leader from the previous scenario is carried over into the current one. The exception to this is, of course, the first scenario, because there is no leader from previous scenarios. However, the <code>type</code> attribute is still necessary to prevent the scenario from crashing, so be sure to include it.

The last attribute, <code>recruit</code>, is a comma-separated list of [http://units.wesnoth.org unit types]. These types will become the side's recruitment list. This too is only necessary in a human player's first scenario, because the recruit list is carried over from one scenario to the next.

Finally, two macros are called. The first, <code>GOLD</code> takes three positive numbers. These indicate the amount of money the player will start with on the <var>easy</var>, <var>normal</var>, and <var>hard</var> difficulty levels, respectively. For a human-controlled side (<code>controller=human</code>), this specifies only the minimum amount of gold. The actual amount the player starts with can be larger if the player has retained gold from previous scenarios. The second macro, <code>INCOME</code>, is analogous to <code>GOLD</code> but for the base income. The defaults values for <code>GOLD</code> and <code>INCOME</code> are 100 gold and 2 base income, respectively.

== Making it all work ==
To make this scenario playable, we need to make a campaign for it (see [[BuildingCampaignsTheCampaignFile]]).
This should '''not''' be stored in the main directory <tt>data/campaigns</tt> but rather inside <tt>userdata/data/campaigns</tt>. This prevents the breaking of mainline campaigns or, even worse, the entire game (see [[BuildingCampaignsDirectoryStructure]]).
Please note that all files (''i.e.'', the campaign file and the scenario files for each level) must be saved with the file extension <tt>.cfg</tt> (''e.g.'', <tt>_main.cfg</tt>).
The following is a short, example campaign file:

[campaign]
name= _ "Test Campaign"
first_scenario=test-1
define=CAMPAIGN_TEST_CAMPAIGN
difficulties=EASY,NORMAL,HARD
difficulty_descriptions={MENU_IMG_TXT2 "units/elves-wood/fighter.png" _"Fighter" _"(Beginner)"} +
";*" + {MENU_IMG_TXT2 "units/elves-wood/hero.png" _"Hero" _"(Normal)"} +
";" + {MENU_IMG_TXT2 "units/elves-wood/champion.png" _"Champion" _"(Hard)"}
icon="units/elves-wood/hero.png"
[/campaign]
#ifdef CAMPAIGN_TEST_CAMPAIGN
{~add-ons/test_campaign/scenarios}
#endif

The <code>[campaign]</code> tag describes the campaign. The first attribute, <code>name</code>, is displayed in the campaign selector box during gameplay. The second, <code>first_scenario</code>, is set to the ID number of the first scenario of the campaign. Subsequent scenarios are referenced by the <code>next_scenario</code> attribute of their immediately preceding scenarios (see above in the first part of this tutorial). Since the first scenario, obviously, doesn't have a predecessor, it is referenced here in the <code>campaign</code> tag. To allow wesnoth to actually find the first scenario we need to include the scenarios directory of our campaign. The last statement of the campaign file does that. The inclusion is best guarded by a preprocessor symbol ([[PreprocessorRef]]) that is unique to this campaign so all the scenarios get only included when this campaign is actually selected by the player. The preprocessor symbol for a campaign is given by the <code>define</code> key.

The attribute <code>difficulties=EASY,NORMAL,HARD</code> tells Wesnoth to use the value <code>EASY</code> if the first difficulty choice is chosen during gameplay, <code>NORMAL</code> if the second is chosen, and <code>HARD</code> if the third is chosen.
The expression <code>#ifdef</code> can be used later to test the value of this attribute (see [[PreprocessorRef]]).
It is recommended that you do not use any names other than <code>EASY</code>, <code>NORMAL</code>, or <code>HARD</code> for your macros because doing so will cause some standard macros, such as <code>{GOLD}</code> and <code>{INCOME}</code>, to not work properly.

Two optional attributes are <code>difficulty_descriptions</code> and <code>icon</code>.
As its value, <code>icon</code> holds the filename of an image to represent this campaign which will be displayed in the campaign list during gameplay.

The <code>difficulty_descriptions</code> uses a standard syntax. You provide an image, difficulty name, and a level. Unsurprising, in our example during gameplay <tt>elvish-fighter.png</tt> would display associated with the easy level, <tt>elvish-hero.png</tt> with normal, and <tt>elvish-champion.png</tt> with hard. You can use whatever names you want, and don't need to stick with easy, normal and hard here. You do need to do this in the <code>difficulties</code> section, because many macros are based off this.

Each list item in <code>difficulty_description</code> begins with the macro <code>MENU_IMG_TEXT2</code> which simplifies the syntax (see [[DescriptionWML]]). This is followed by the filename of the image, then an equal sign ("="), and finally the text to display (i.e., "Easy". Take note that text displayed for the easy level is not "EASY": the text used is that in <code>difficulty_descriptions</code>, not <code>difficulties</code>. Similary, the normal level's text is "Medium").

Optionally you may place an asterisk ("*") before one of list items of <code>difficulty_desciptions</code> which will cause that corresponding difficulty level to be selected as the default during gameplay. In the example above, the normal level (along with its elvish hero) is selected as the default.

== See Also ==
* [[BuildingMaps]] & [[WesnothMapEditor]]
* [[ScenarioWML]] & [[SyntaxWML]]
* [[BuildingScenarios]]

[[Category:Create]]

BuildingScenariosSimple

2012-10-07T17:35:20Z

Tr0ll:

{{BuildingScenariosNav}}

= Learning things step by step =

Here we will show you a very simple scenario file and explain each line of it.
The file is not fully functional, but it will show the basics needed to describe what a scenario is all about.

'''Before reading this, it might prove useful to read something about the syntax of the Wesnoth Markup Language: [[SyntaxWML]]'''

== First part ==

<blockquote>
<pre>
<nowiki>
#textdomain wesnoth-Simple_Campaign
[scenario]

id=01_test-1
next_scenario=02_test-more

name= _ "A Simple Test Scenario"
map_data="{~add-ons/Test_Campaign/maps/testmap.map}"
turns=20

{DAWN}
{MORNING}
{AFTERNOON}
{DUSK}
{FIRST_WATCH}
{SECOND_WATCH}

music=battle.ogg

[event]
name=prestart
[objectives]
side=1
[objective]
description= _ "Defeat Enemy Leader"
condition=win
[/objective]
[objective]
description= _ "Death of Konrad"
condition=lose
[/objective]
[objective]
description= _ "Turns run out"
condition=lose
[/objective]
[/objectives]
[/event]
</nowiki>
</pre>

''continued below''
     ↓ ↓ ↓
</blockquote>
* <code>#textdomain</code> must be provided at the start of your scenario file if you want it to be translated. Format is <code>#textdomain wesnoth-Name_of_your_campaign</code>, as defined in your _main.cfg file.

Every scenario must be enclosed in a tag; the <code>[scenario]</code> tag is used for campaign scenarios. The first set of attributes in the scenario tag describe the very basics of this scenario:

* <code>id</code> (short for ''identifier'') is the computer's name for your scenario and is not displayed during the game. However, it will be used to display game statistics (they will be graphed at http://stats.wesnoth.org in numerical order, so it's also a good idea to give the <code>id</code>'s a number). This name is also referenced in other tags and files, ''e.g.,'' inside a <code>[campaign]</code> tag using the <code>first_scenario</code> attribute (see [[BuildingCampaignsTheCampaignFile]]) or inside a <code>[scenario]</code> tag using the <code>next_scenario</code> attribute (see below).

* The value of the <code>next_scenario</code> attribute is the <code>id</code> (see above) of the scenario that is played after this one is won. Units from this scenario will be available for recall (unless you modify the recall list, but that's stuff for later). If your scenario is not part of a campaign, or if this is the last scenario you should either skip this line or put <code>next_scenario=null</code> inside the file. This will tell the game to display the ''End'' screen when this scenario is won.

* The value of the <code>name</code> attribute is shown on the introduction screen before each scenario is played (this may contain a picture of a map or anything else you fancy. See [[BuildingScenariosIntermediate]] for an explanation on how to do that). It's also used to generate the default names of saved files for the level. The underscore before the name marks it as translatable.

* The next attribute, <code>map_data</code> is a little tricky. Normally, the map data (the text that is used to generate a map) goes directly inside of the quotation marks. However, it is often useful to keep that map data in a separate file, and then include that file (still inside the quotation marks) using a [[PreprocessorRef|preprocesser]] command. The code <code>{~add-ons/Test_Campaign/maps/testmap.map}</code> does just that, telling the wesnoth engine to look in the file <code>add-ons/Test_Campaign/maps/testmap</code> for the map data. The <code>~</code> symbol tells Wesnoth to search for the map file in the ''userdata'' directory (see [[EditingWesnoth]] and [[PreprocessorRef]] for more information). You can create and edit map files using Wesnoth's built-in [[Editor2|map editor]] (see [[BuildingMaps]] for more information).

* Finally, the last attribute in the top set of keys is <code>turns</code>. This is the number of turns a player is given to finish the scenario (it can be changed during the game, but again, that is stuff for later). If the player fails to finish the scenario in the given time, he has lost (''i.e.,'' the ''defeat'' event is triggered. See [[EventWML]] for more.)

The next section is a group of macros which will be processed by Wesnoth's [[PreprocessorRef|preprocesser]]. Macros are essentially [[WML]] shortcuts. They allow you to define certain pieces of code which can be re-used whenever they are needed. Wesnoth provides you with a whole series of standard, pre-written macros to make life easier, but you yourself can write them too (again, stuff for later).
Let's get back to this example! The macros listed above describe how a day in this scenario will progress. The list of macros above is the normal day used throughout Wesnoth. If you want the entire scenario to take place at night, remove all the macros except for <code>{SECOND_WATCH}</code>. Doing this might, for example, be useful if you've set Konrad to fight the Undead and also want the Undead to have the upper hand throughout the scenario. Remember, though, by setting this to a single time of day rather than the normal diurnal progression shown above, your scenario will effectively take place during one day (or night) rather than across many days as most scenarios do.

The <code>music</code> attribute takes for its value the name of a music file (see [[MusicListWML]] for more). This file must be in the <code>music/</code> directory and must be in [http://en.wikipedia.org/wiki/Ogg Ogg] format.

A tag you'll get to know very well when making scenarios is <code>[event]...[/event]</code>. <code>event</code> tags are used to describe what should be done when various sorts of ''events'' take place. The specific type of event is stated in the <code>event</code>'s <code>name</code> attribute. In this case we're describing the so-called <code>prestart</code> event. This event occurs just ''after'' all the introduction screens for the scenario have been shown but just ''before'' the map itself is displayed. This prestart event is used to set the scenario's objectives, i.e. the contents of the ''Scenario Objectives Dialog'' that will appear once the scenario begins. The purpose of the Scenario Objectives Dialog is to inform the player what must be accomplished to win the scenario and what circumstances bring about defeat. These winning and losing circumstances are defined using the <code>[objectives]</code> tag (N.B. that <code>objectives</code> is plural). Further, each circumstance is defined in its own <code>[objective]</code> (N.B. the singular here) tag with winning circumstances setting <code>condition</code> to <code>win</code>, and with losing circumstances setting it to <code>lose</code>. In the example above, <code>objectives</code> states victory to be "Defeat Enemy Leader". For defeat, however, <code>[objectives]</code> gives the player ''two'' possibilities: either "Death of Konrad" or "Turns run out" (any number of either winning or losing <code>[objective]</code> tags may be given). Accordingly, the Scenario Objectives Dialog will look vaguely like:

<table border=1><tr><td>
'''A Simple Test Scenario'''
 '''Victory:'''
 Defeat Enemy Leader
 '''Defeat:'''
 Death of Konrad
 Turns run out
 
        
        
      [ OK ]
</td></tr></table>

Note that the <code>[objectives]</code> tag doesn't define the circumstances of victory or defeat to the game engine. It merely tells the player what they are. Special victory or defeat conditions will have to be coded into the scenario using various [event]s.

The <code>side</code> attribute in <code>[objectives]</code> indicates that the conditions defined here by the <code>[objective]</code> tags are for the faction or alliance ''side 1'' alone (see below). In a single-player game, side 1 would usually indicate the player's faction or alliance). The underscore ("_") facilitates translation using [[GetText|Gettext]].

== Second part ==
So far so good! The last necessary part describes what the players (both human and
computer) start with, what they can do, and what they can't do. Each of the players is described in a <code>[side]</code> tag with the word ''side'' referring to a player's faction, band, or horde.

<blockquote>
    ↑ ↑ ↑
 ''continued from above''
<pre>
<nowiki>
[side]
side=1
controller=human
team_name=2
user_team_name= _ "Konrad's forces"

type=Commander
id=Konrad
name= _ "Konrad"
canrecruit=yes

recruit=Elvish Fighter,Elvish Archer,Horseman,Mage,Elvish Shaman

{GOLD 100 50 0}
{INCOME 10 5 0}
[/side]
[/scenario]
</nowiki>
</pre>
</blockquote>

Above you can see a sample <code>[side]</code> for the human player, Konrad. The first group of attributes in the <code>[side]</code> tag pertains to the side generally:
* <code>side</code>: the leader of this side is placed on the tile represented by this digit (see [[BuildingMaps]]). It's a number from 1 to 9.
* <code>controller</code> takes either of two possible values: <code>human</code> or <code>ai</code> (''i.e.,'' ''artificial intelligence'', meaning your computer). If you don't specify this attribute, <code>ai</code> is the default.
* <code>team_name</code> describes which team the side is on. It defaults to the same number as <code>side</code>, but setting it to <code>2</code> allies this side with side 2 (if you haven't changed the <code>team_name</code> of side 2).
* <code>user_team_name</code> is the name displayed when you view the side stats (by pressing <tt>alt+s</tt> during gameplay). The underscore ("_") facilitates translation using [[GetText|Gettext]].

The next group of attributes describe the leader of this side:
* <code>canrecruit</code>: This attribute can be set to <code>yes</code> or <code>no</code> (the boolean equivalents <code>1</code> and <code>0</code> or <code>true</code> and <code>false</code> also work). If this is set to <code>no</code>, the leader won't be able to recruit (not much of a leader then, is he?). Any side without a <code>canrecruit=yes</code> attribute statement automatically loses, so be sure to include this attribute.
* <code>type</code> describes what type of unit the leader will be. The possible values are listed in [http://units.wesnoth.org the Wesnoth unit tables].
* <code>id</code> is the identifier of the leader, as used by the engine, and is not visible by the player.
* <code>name</code> is the name of the leader, as visible to the player. The underscore marks it as translatable.

In a campaign, all of these "leader-describing" attributes are ignored for human players (except <code>canrecruit</code>), since the leader from the previous scenario is carried over into the current one. The exception to this is, of course, the first scenario, because there is no leader from previous scenarios. However, the <code>type</code> attribute is still necessary to prevent the scenario from crashing, so be sure to include it.

The last attribute, <code>recruit</code>, is a comma-separated list of [http://units.wesnoth.org unit types]. These types will become the side's recruitment list. This too is only necessary in a human player's first scenario, because the recruit list is carried over from one scenario to the next.

Finally, two macros are called. The first, <code>GOLD</code> takes three positive numbers. These indicate the amount of money the player will start with on the <var>easy</var>, <var>normal</var>, and <var>hard</var> difficulty levels, respectively. For a human-controlled side (<code>controller=human</code>), this specifies only the minimum amount of gold. The actual amount the player starts with can be larger if the player has retained gold from previous scenarios. The second macro, <code>INCOME</code>, is analogous to <code>GOLD</code> but for the base income. The defaults values for <code>GOLD</code> and <code>INCOME</code> are 100 gold and 2 base income, respectively.

== Making it all work ==
To make this scenario playable, we need to make a campaign for it (see [[BuildingCampaignsTheCampaignFile]]).
This should '''not''' be stored in the main directory <tt>data/campaigns</tt> but rather inside <tt>userdata/data/campaigns</tt>. This prevents the breaking of mainline campaigns or, even worse, the entire game (see [[BuildingCampaignsDirectoryStructure]]).
Please note that all files (''i.e.'', the campaign file and the scenario files for each level) must be saved with the file extension <tt>.cfg</tt> (''e.g.'', <tt>_main.cfg</tt>).
The following is a short, example campaign file:

[campaign]
name= _ "Test Campaign"
first_scenario=test-1
define=CAMPAIGN_TEST_CAMPAIGN
difficulties=EASY,NORMAL,HARD
difficulty_descriptions={MENU_IMG_TXT2 "units/elves-wood/fighter.png" _"Fighter" _"(Beginner)"} +
";*" + {MENU_IMG_TXT2 "units/elves-wood/hero.png" _"Hero" _"(Normal)"} +
";" + {MENU_IMG_TXT2 "units/elves-wood/champion.png" _"Champion" _"(Hard)"}
icon="units/elves-wood/hero.png"
[/campaign]
#ifdef CAMPAIGN_TEST_CAMPAIGN
{~add-ons/test_campaign/scenarios}
#endif

The <code>[campaign]</code> tag describes the campaign. The first attribute, <code>name</code>, is displayed in the campaign selector box during gameplay. The second, <code>first_scenario</code>, is set to the ID number of the first scenario of the campaign. Subsequent scenarios are referenced by the <code>next_scenario</code> attribute of their immediately preceding scenarios (see above in the first part of this tutorial). Since the first scenario, obviously, doesn't have a predecessor, it is referenced here in the <code>campaign</code> tag. To allow wesnoth to actually find the first scenario we need to include the scenarios directory of our campaign. The last statement of the campaign file does that. The inclusion is best guarded by a preprocessor symbol ([[PreprocessorRef]]) that is unique to this campaign so all the scenarios get only included when this campaign is actually selected by the player. The preprocessor symbol for a campaign is given by the <code>define</code> key.

The attribute <code>difficulties=EASY,NORMAL,HARD</code> tells Wesnoth to use the value <code>EASY</code> if the first difficulty choice is chosen during gameplay, <code>NORMAL</code> if the second is chosen, and <code>HARD</code> if the third is chosen.
The expression <code>#ifdef</code> can be used later to test the value of this attribute (see [[PreprocessorRef]]).
It is recommended that you do not use any names other than <code>EASY</code>, <code>NORMAL</code>, or <code>HARD</code> for your macros because doing so will cause some standard macros, such as <code>{GOLD}</code> and <code>{INCOME}</code>, to not work properly.

Two optional attributes are <code>difficulty_descriptions</code> and <code>icon</code>.
As its value, <code>icon</code> holds the filename of an image to represent this campaign which will be displayed in the campaign list during gameplay.

The <code>difficulty_descriptions</code> uses a standard syntax. You provide an image, difficulty name, and a level. Unsurprising, in our example during gameplay <tt>elvish-fighter.png</tt> would display associated with the easy level, <tt>elvish-hero.png</tt> with normal, and <tt>elvish-champion.png</tt> with hard. You can use whatever names you want, and don't need to stick with easy, normal and hard here. You do need to do this in the <code>difficulties</code> section, because many macros are based off this.

Each list item in <code>difficulty_description</code> begins with the macro <code>MENU_IMG_TEXT2</code> which simplifies the syntax that follows (see [[DescriptionWML]]). This is followed by the filename of the image, then an equal sign ("="), and finally the text to display (i.e., "Easy". Take note that text displayed for the easy level is not "EASY": the text used is that in <code>difficulty_descriptions</code>, not <code>difficulties</code>. Similary, the normal level's text is "Medium").

Optionally you may place an asterisk ("*") before one of list items of <code>difficulty_desciptions</code> which will cause that corresponding difficulty level to be selected as the default during gameplay. In the example above, the normal level (along with its elvish hero) is selected as the default.

== See Also ==
* [[BuildingMaps]] & [[WesnothMapEditor]]
* [[ScenarioWML]] & [[SyntaxWML]]
* [[BuildingScenarios]]

[[Category:Create]]

BuildingScenariosSimple

2012-10-07T17:33:18Z

Tr0ll: replace confusing reference to nonexistent ampersand with reference to macro

{{BuildingScenariosNav}}

= Learning things step by step =

Here we will show you a very simple scenario file and explain each line of it.
The file is not fully functional, but it will show the basics needed to describe what a scenario is all about.

'''Before reading this, it might prove useful to read something about the syntax of the Wesnoth Markup Language: [[SyntaxWML]]'''

== First part ==

<blockquote>
<pre>
<nowiki>
#textdomain wesnoth-Simple_Campaign
[scenario]

id=01_test-1
next_scenario=02_test-more

name= _ "A Simple Test Scenario"
map_data="{~add-ons/Test_Campaign/maps/testmap.map}"
turns=20

{DAWN}
{MORNING}
{AFTERNOON}
{DUSK}
{FIRST_WATCH}
{SECOND_WATCH}

music=battle.ogg

[event]
name=prestart
[objectives]
side=1
[objective]
description= _ "Defeat Enemy Leader"
condition=win
[/objective]
[objective]
description= _ "Death of Konrad"
condition=lose
[/objective]
[objective]
description= _ "Turns run out"
condition=lose
[/objective]
[/objectives]
[/event]
</nowiki>
</pre>

''continued below''
     ↓ ↓ ↓
</blockquote>
* <code>#textdomain</code> must be provided at the start of your scenario file if you want it to be translated. Format is <code>#textdomain wesnoth-Name_of_your_campaign</code>, as defined in your _main.cfg file.

Every scenario must be enclosed in a tag; the <code>[scenario]</code> tag is used for campaign scenarios. The first set of attributes in the scenario tag describe the very basics of this scenario:

* <code>id</code> (short for ''identifier'') is the computer's name for your scenario and is not displayed during the game. However, it will be used to display game statistics (they will be graphed at http://stats.wesnoth.org in numerical order, so it's also a good idea to give the <code>id</code>'s a number). This name is also referenced in other tags and files, ''e.g.,'' inside a <code>[campaign]</code> tag using the <code>first_scenario</code> attribute (see [[BuildingCampaignsTheCampaignFile]]) or inside a <code>[scenario]</code> tag using the <code>next_scenario</code> attribute (see below).

* The value of the <code>next_scenario</code> attribute is the <code>id</code> (see above) of the scenario that is played after this one is won. Units from this scenario will be available for recall (unless you modify the recall list, but that's stuff for later). If your scenario is not part of a campaign, or if this is the last scenario you should either skip this line or put <code>next_scenario=null</code> inside the file. This will tell the game to display the ''End'' screen when this scenario is won.

* The value of the <code>name</code> attribute is shown on the introduction screen before each scenario is played (this may contain a picture of a map or anything else you fancy. See [[BuildingScenariosIntermediate]] for an explanation on how to do that). It's also used to generate the default names of saved files for the level. The underscore before the name marks it as translatable.

* The next attribute, <code>map_data</code> is a little tricky. Normally, the map data (the text that is used to generate a map) goes directly inside of the quotation marks. However, it is often useful to keep that map data in a separate file, and then include that file (still inside the quotation marks) using a [[PreprocessorRef|preprocesser]] command. The code <code>{~add-ons/Test_Campaign/maps/testmap.map}</code> does just that, telling the wesnoth engine to look in the file <code>add-ons/Test_Campaign/maps/testmap</code> for the map data. The <code>~</code> symbol tells Wesnoth to search for the map file in the ''userdata'' directory (see [[EditingWesnoth]] and [[PreprocessorRef]] for more information). You can create and edit map files using Wesnoth's built-in [[Editor2|map editor]] (see [[BuildingMaps]] for more information).

* Finally, the last attribute in the top set of keys is <code>turns</code>. This is the number of turns a player is given to finish the scenario (it can be changed during the game, but again, that is stuff for later). If the player fails to finish the scenario in the given time, he has lost (''i.e.,'' the ''defeat'' event is triggered. See [[EventWML]] for more.)

The next section is a group of macros which will be processed by Wesnoth's [[PreprocessorRef|preprocesser]]. Macros are essentially [[WML]] shortcuts. They allow you to define certain pieces of code which can be re-used whenever they are needed. Wesnoth provides you with a whole series of standard, pre-written macros to make life easier, but you yourself can write them too (again, stuff for later).
Let's get back to this example! The macros listed above describe how a day in this scenario will progress. The list of macros above is the normal day used throughout Wesnoth. If you want the entire scenario to take place at night, remove all the macros except for <code>{SECOND_WATCH}</code>. Doing this might, for example, be useful if you've set Konrad to fight the Undead and also want the Undead to have the upper hand throughout the scenario. Remember, though, by setting this to a single time of day rather than the normal diurnal progression shown above, your scenario will effectively take place during one day (or night) rather than across many days as most scenarios do.

The <code>music</code> attribute takes for its value the name of a music file (see [[MusicListWML]] for more). This file must be in the <code>music/</code> directory and must be in [http://en.wikipedia.org/wiki/Ogg Ogg] format.

A tag you'll get to know very well when making scenarios is <code>[event]...[/event]</code>. <code>event</code> tags are used to describe what should be done when various sorts of ''events'' take place. The specific type of event is stated in the <code>event</code>'s <code>name</code> attribute. In this case we're describing the so-called <code>prestart</code> event. This event occurs just ''after'' all the introduction screens for the scenario have been shown but just ''before'' the map itself is displayed. This prestart event is used to set the scenario's objectives, i.e. the contents of the ''Scenario Objectives Dialog'' that will appear once the scenario begins. The purpose of the Scenario Objectives Dialog is to inform the player what must be accomplished to win the scenario and what circumstances bring about defeat. These winning and losing circumstances are defined using the <code>[objectives]</code> tag (N.B. that <code>objectives</code> is plural). Further, each circumstance is defined in its own <code>[objective]</code> (N.B. the singular here) tag with winning circumstances setting <code>condition</code> to <code>win</code>, and with losing circumstances setting it to <code>lose</code>. In the example above, <code>objectives</code> states victory to be "Defeat Enemy Leader". For defeat, however, <code>[objectives]</code> gives the player ''two'' possibilities: either "Death of Konrad" or "Turns run out" (any number of either winning or losing <code>[objective]</code> tags may be given). Accordingly, the Scenario Objectives Dialog will look vaguely like:

<table border=1><tr><td>
'''A Simple Test Scenario'''
 '''Victory:'''
 Defeat Enemy Leader
 '''Defeat:'''
 Death of Konrad
 Turns run out
 
        
        
      [ OK ]
</td></tr></table>

Note that the <code>[objectives]</code> tag doesn't define the circumstances of victory or defeat to the game engine. It merely tells the player what they are. Special victory or defeat conditions will have to be coded into the scenario using various [event]s.

The <code>side</code> attribute in <code>[objectives]</code> indicates that the conditions defined here by the <code>[objective]</code> tags are for the faction or alliance ''side 1'' alone (see below). In a single-player game, side 1 would usually indicate the player's faction or alliance). The underscore ("_") facilitates translation using [[GetText|Gettext]].

== Second part ==
So far so good! The last necessary part describes what the players (both human and
computer) start with, what they can do, and what they can't do. Each of the players is described in a <code>[side]</code> tag with the word ''side'' referring to a player's faction, band, or horde.

<blockquote>
    ↑ ↑ ↑
 ''continued from above''
<pre>
<nowiki>
[side]
side=1
controller=human
team_name=2
user_team_name= _ "Konrad's forces"

type=Commander
id=Konrad
name= _ "Konrad"
canrecruit=yes

recruit=Elvish Fighter,Elvish Archer,Horseman,Mage,Elvish Shaman

{GOLD 100 50 0}
{INCOME 10 5 0}
[/side]
[/scenario]
</nowiki>
</pre>
</blockquote>

Above you can see a sample <code>[side]</code> for the human player, Konrad. The first group of attributes in the <code>[side]</code> tag pertains to the side generally:
* <code>side</code>: the leader of this side is placed on the tile represented by this digit (see [[BuildingMaps]]). It's a number from 1 to 9.
* <code>controller</code> takes either of two possible values: <code>human</code> or <code>ai</code> (''i.e.,'' ''artificial intelligence'', meaning your computer). If you don't specify this attribute, <code>ai</code> is the default.
* <code>team_name</code> describes which team the side is on. It defaults to the same number as <code>side</code>, but setting it to <code>2</code> allies this side with side 2 (if you haven't changed the <code>team_name</code> of side 2).
* <code>user_team_name</code> is the name displayed when you view the side stats (by pressing <tt>alt+s</tt> during gameplay). The underscore ("_") facilitates translation using [[GetText|Gettext]].

The next group of attributes describe the leader of this side:
* <code>canrecruit</code>: This attribute can be set to <code>yes</code> or <code>no</code> (the boolean equivalents <code>1</code> and <code>0</code> or <code>true</code> and <code>false</code> also work). If this is set to <code>no</code>, the leader won't be able to recruit (not much of a leader then, is he?). Any side without a <code>canrecruit=yes</code> attribute statement automatically loses, so be sure to include this attribute.
* <code>type</code> describes what type of unit the leader will be. The possible values are listed in [http://units.wesnoth.org the Wesnoth unit tables].
* <code>id</code> is the identifier of the leader, as used by the engine, and is not visible by the player.
* <code>name</code> is the name of the leader, as visible to the player. The underscore marks it as translatable.

In a campaign, all of these "leader-describing" attributes are ignored for human players (except <code>canrecruit</code>), since the leader from the previous scenario is carried over into the current one. The exception to this is, of course, the first scenario, because there is no leader from previous scenarios. However, the <code>type</code> attribute is still necessary to prevent the scenario from crashing, so be sure to include it.

The last attribute, <code>recruit</code>, is a comma-separated list of [http://units.wesnoth.org unit types]. These types will become the side's recruitment list. This too is only necessary in a human player's first scenario, because the recruit list is carried over from one scenario to the next.

Finally, two macros are called. The first, <code>GOLD</code> takes three positive numbers. These indicate the amount of money the player will start with on the <var>easy</var>, <var>normal</var>, and <var>hard</var> difficulty levels, respectively. For a human-controlled side (<code>controller=human</code>), this specifies only the minimum amount of gold. The actual amount the player starts with can be larger if the player has retained gold from previous scenarios. The second macro, <code>INCOME</code>, is analogous to <code>GOLD</code> but for the base income. The defaults values for <code>GOLD</code> and <code>INCOME</code> are 100 gold and 2 base income, respectively.

== Making it all work ==
To make this scenario playable, we need to make a campaign for it (see [[BuildingCampaignsTheCampaignFile]]).
This should '''not''' be stored in the main directory <tt>data/campaigns</tt> but rather inside <tt>userdata/data/campaigns</tt>. This prevents the breaking of mainline campaigns or, even worse, the entire game (see [[BuildingCampaignsDirectoryStructure]]).
Please note that all files (''i.e.'', the campaign file and the scenario files for each level) must be saved with the file extension <tt>.cfg</tt> (''e.g.'', <tt>_main.cfg</tt>).
The following is a short, example campaign file:

[campaign]
name= _ "Test Campaign"
first_scenario=test-1
define=CAMPAIGN_TEST_CAMPAIGN
difficulties=EASY,NORMAL,HARD
difficulty_descriptions={MENU_IMG_TXT2 "units/elves-wood/fighter.png" _"Fighter" _"(Beginner)"} +
";*" + {MENU_IMG_TXT2 "units/elves-wood/hero.png" _"Hero" _"(Normal)"} +
";" + {MENU_IMG_TXT2 "units/elves-wood/champion.png" _"Champion" _"(Hard)"}
icon="units/elves-wood/hero.png"
[/campaign]
#ifdef CAMPAIGN_TEST_CAMPAIGN
{~add-ons/test_campaign/scenarios}
#endif

The <code>[campaign]</code> tag describes the campaign. The first attribute, <code>name</code>, is displayed in the campaign selector box during gameplay. The second, <code>first_scenario</code>, is set to the ID number of the first scenario of the campaign. Subsequent scenarios are referenced by the <code>next_scenario</code> attribute of their immediately preceding scenarios (see above in the first part of this tutorial). Since the first scenario, obviously, doesn't have a predecessor, it is referenced here in the <code>campaign</code> tag. To allow wesnoth to actually find the first scenario we need to include the scenarios directory of our campaign. The last statement of the campaign file does that. The inclusion is best guarded by a preprocessor symbol ([[PreprocessorRef]]) that is unique to this campaign so all the scenarios get only included when this campaign is actually selected by the player. The preprocessor symbol for a campaign is given by the <code>define</code> key.

The attribute <code>difficulties=EASY,NORMAL,HARD</code> tells Wesnoth to use the value <code>EASY</code> if the first difficulty choice is chosen during gameplay, <code>NORMAL</code> if the second is chosen, and <code>HARD</code> if the third is chosen.
The expression <code>#ifdef</code> can be used later to test the value of this attribute (see [[PreprocessorRef]]).
It is recommended that you do not use any names other than <code>EASY</code>, <code>NORMAL</code>, or <code>HARD</code> for your macros because doing so will cause some standard macros, such as <code>{GOLD}</code> and <code>{INCOME}</code>, to not work properly.

Two optional attributes are <code>difficulty_descriptions</code> and <code>icon</code>.
As its value, <code>icon</code> holds the filename of an image to represent this campaign which will be displayed in the campaign list during gameplay.

The <code>difficulty_descriptions</code> uses a standard syntax. You provide an image, difficulty name, and a level. Unsurprising, in our example during gameplay <tt>elvish-fighter.png</tt> would display associated with the easy level, <tt>elvish-hero.png</tt> with normal, and <tt>elvish-champion.png</tt> with hard. You can use whatever names you want, and don't need to stick with easy, normal and hard here. You do need to do this in the <code>difficulties</code> section, because many macros are based off this.

Each list item in <code>difficulty_description</code> begins with the macro <code>MENU_ITEM_TEXT2</code> which simplifies the syntax that follows (see [[DescriptionWML]]). This is followed by the filename of the image, then an equal sign ("="), and finally the text to display (i.e., "Easy". Take note that text displayed for the easy level is not "EASY": the text used is that in <code>difficulty_descriptions</code>, not <code>difficulties</code>. Similary, the normal level's text is "Medium").

Optionally you may place an asterisk ("*") before one of list items of <code>difficulty_desciptions</code> which will cause that corresponding difficulty level to be selected as the default during gameplay. In the example above, the normal level (along with its elvish hero) is selected as the default.

== See Also ==
* [[BuildingMaps]] & [[WesnothMapEditor]]
* [[ScenarioWML]] & [[SyntaxWML]]
* [[BuildingScenarios]]

[[Category:Create]]

Talk:Screenshots

2012-10-07T00:10:16Z

Tr0ll: Created page with 'Should screenshots only show mainline campaigns?'

Should screenshots only show mainline campaigns?

Download

2011-09-11T20:05:45Z

Tr0ll: fix link to md5

{{Download/Translations}}
Welcome to the Battle for Wesnoth downloads page. The BFW project team only officially releases the source code. Binary packages are only provided by community volunteers and hosted here. Torrents are also unofficial.

If the latest binaries are not currently available for your OS, please check back in a few days to see if they have been placed here. Packagers have been informed of the release, please be patient. In the meantime, read the [[FAQ#A_new_version_is_out.2C_but_where_is_the_download_for_.5BWindows.2C_Mac_OS.2C_etc..5D.3F|FAQ]].

__NOTOC__
Jump to: [[Download#Stable_.281.8_branch.29|Stable Branch]] | [[Download#Stable_.28older_versions.29|Stable Branch (older versions)]] | [[Download#Development_.281.9_branch.29|Development Branch]]

== Stable (1.8 branch) ==
The stable files are meant to be used as a stable and rather balanced version of the game. Each version of the 1.8 branch is compatible to each other.

Version 1.8.6 is the latest stable version. This version is recommended for most players since the 1.8 online multiplayer community is very large and user-made campaign server has a robust content selection.

==== Source code ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.8/wesnoth-1.8.6/wesnoth-1.8.6.tar.bz2/download Current Version] (1.8.6, 288.2 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.8/wesnoth-1.8.5/wesnoth-1.8.5.tar.bz2/download Previous Version] (1.8.5, 287.1 MB)
* [[CompilingWesnoth|Compiling Guide]] - how to compile the source code

==== MS Windows ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.8/wesnoth-1.8.6/wesnoth-1.8.6-win32.exe/download Current Version] (1.8.6, 268.6 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.8/wesnoth-1.8.5/wesnoth-1.8.5-win32.exe/download Previous Version] (1.8.5, 267.5 MB)

==== Mac OS X (10.4+) ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.8/wesnoth-1.8.6/Wesnoth_1.8.6.dmg/download Current Version] (1.8.6, 292.7MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.8/wesnoth-1.8.5/Wesnoth_1.8.5.dmg/download Previous Version] (1.8.5, 291.2MB)

==== GNU/Linux ====
* There are binaries for many different GNU/Linux Distributions. Not all are always up to date with the current release. Please have a look at the [[WesnothBinariesLinux|Linux binary page]] for more information about the binaries for your Distribution.

==== OpenPandora ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.8/wesnoth-1.8.6/wesnoth-1.8.6-1.pnd/download Current Version] (1.8.6-1, 289.3 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.8/wesnoth-1.8.5/wesnoth-1.8.5-1.pnd/download Previous Version] (1.8.5-1, 286.2 MB)

==== Miscellaneous ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.8/wesnoth-1.8.6/wesnoth-1.8.6.tar.bz2.md5/download md5sum for current source code]
* [http://www.wesnoth.org/wiki/Download_Xdeltas#Stable_Version_1.8.x Xdelta for the source code]
* [http://sourceforge.net/projects/wesnoth/files/ SourceForge page for current and all previous versions]

== Stable (older versions) ==
Several operating systems do not offer a binary of the latest stable release. Here is a list of the latest known (stable version) binaries for various systems. For those older versions there often is no (official) multiplayer or addon server available anymore.

==== (Open)Solaris ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.4/wesnoth-1.4.5/wesnoth-solaris-i386-1.4.5.pkg.bz2/download Older Version] (1.4.5, 145.6 MB), not compatible with 1.6.x

==== AmigaOS4 ====
* [http://os4depot.net/index.php?function=showfile&file=game/strategy/wesnoth.lha Older Version] (1.4.7, 140 MB), not compatible with 1.6.x

==== OS/2 & eComStation ====
* [http://download.smedley.info/wesnoth-1.4.5-os2-20080828.zip Older Version] (1.4.5, 160 MB), not compatible with 1.6.x

==== RISC OS ====
*[http://www.riscos.info/packages/arm/Games/wesnoth_1.4.5-1.zip Older version] (1.4.5-1, 140MB), not compatible with 1.6.x

==== Syllable ====
* [http://downloads.syllable.org/Syllable/i586/applications/contributed/Battle-for-Wesnoth/Battle-for-Wesnoth-1.2.6.application Older Version] (1.2.6, 60.8 MB), not compatible with 1.6.x

== Development (1.9 branch) ==
Version 1.9.x is the latest development version, boasting updated graphics and new exciting features. However, there may be occasional bugs or performance problems in the development versions since heavy changes are taking place all the time. For balanced and stable gaming, it is recommended you use the latest version of the 1.8.x branch. This version is recommended for coders and campaign developers, as well as those who want to preview the future of Wesnoth. People familiar with SVN and compiling can follow the latest development by checking [[WesnothSVN]].

==== Source code ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.9.9/wesnoth-1.9.9.tar.bz2/download Current Version] (1.9.9, 324.8 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.9.8/wesnoth-1.9.8.tar.bz2/download Previous Version] (1.9.8, 323.2 MB)

* [[CompilingWesnoth|Compiling Guide]] - how to compile the source code

==== MS Windows ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.9.9/wesnoth-1.9.9-win32.exe/download Current Version] (1.9.9, 299.0 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.9.8/wesnoth-1.9.8-win32.exe/download Previous Version] (1.9.8, 297.5 MB)

==== Mac OS X (10.4+) ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.9.9/Wesnoth_1.9.9.dmg/download Current Version (for OSX 10.5+)] (1.9.9, 323.7 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.9.8/Wesnoth_1.9.8.dmg/download Previous Version (for OSX 10.5+)] (1.9.8, 322.0 MB)

==== GNU/Linux ====
* There are binaries for many different GNU/Linux Distributions. Not all are always up to date with the current release. Please have a look at the [[WesnothBinariesLinux|Linux binary page]] for more information about the binaries for your Distribution.

==== OpenPandora ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.9.9/wesnoth-1.9.9-1.pnd/download Current Version] (1.9.9-1, 315.4 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.9.8/wesnoth-1.9.8-1.pnd/download Previous Version] (1.9.8-1, 313.7 MB)

==== Miscellaneous ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.9.9/wesnoth-1.9.9.tar.bz2.md5/download md5sum for current source code]
* [http://www.wesnoth.org/wiki/Download_Xdeltas#Development_Version_1.9.x Xdelta for the source code]
* [http://sourceforge.net/projects/wesnoth/files/ SourceForge page for current and all previous versions]
* [http://sourceforge.net/projects/wesnoth/files/unofficial/Mac%20Compile%20Stuff/wesnoth_compile_mac_1.9.zip/download MacCompileStuff for 1.9]

== License ==
''Main article: [[Wesnoth:Copyrights]]

This program is free software; you can redistribute it and/or modify it under the terms of the [http://www.fsf.org/copyleft/gpl.html GNU General Public License version 2], as published by the [http://www.fsf.org Free Software Foundation].
This program is distributed in the hope that it will be useful, but without any warranty; without even the implied warranty of merchantability or fitness for a particular purpose. See the GNU General Public License for more details.

== UMC Editor ==
This is available just with Wesnoth 1.9.x.
Details and installation steps can be found at: http://eclipse.wesnoth.org

== See also ==
* [http://changelog.wesnoth.org Changelog]
* [[WesnothBinaries| More binaries]]
* [[WesnothSVN]] - bleeding edge version from SVN

[[Category:Building and Installing]]

Download

2010-10-21T19:56:50Z

Tr0ll: update Stable version minor number

Welcome to the Battle for Wesnoth downloads page. The BFW project team only officially releases the source code. Binary packages are only provided by community volunteers and hosted here. Torrents are also unofficial.

If the latest binaries are not currently available for your OS, please check back in a few days to see if they have been placed here. Packagers have been informed of the release, please be patient. In the meantime, read the [[FAQ#A_new_version_is_out.2C_but_where_is_the_download_for_.5BWindows.2C_Mac_OS.2C_etc..5D.3F|FAQ]].

__NOTOC__
Jump to: [[Download#Stable_.281.8_branch.29|Stable Branch]] | [[Download#Stable_.28older_versions.29|Stable Branch (older versions)]] | [[Download#Development_.281.9_branch.29|Development Branch]]

== Stable (1.8 branch) ==
The stable files are meant to be used as a stable and rather balanced version of the game. Each version of the 1.8 branch is compatible to each other.

Version 1.8.5 is the latest stable version. This version is recommended for most players since the 1.8 online multiplayer community is very large and user-made campaign server has a robust content selection.

==== Source code ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.8/wesnoth-1.8.5/wesnoth-1.8.5.tar.bz2/download Current Version] (1.8.5, 287.1 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.8/wesnoth-1.8.4/wesnoth-1.8.4.tar.bz2/download Previous Version] (1.8.4, 286.6 MB)
* [[CompilingWesnoth|Compiling Guide]] - how to compile the source code

==== MS Windows ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.8/wesnoth-1.8.5/wesnoth-1.8.5-win32.exe/download Current Version] (1.8.5, 267.5 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.8/wesnoth-1.8.4/wesnoth-1.8.4-win32.exe/download Previous Version] (1.8.4, 267.1 MB)

==== Mac OS X (10.4+) ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.8/wesnoth-1.8.5/Wesnoth_1.8.5.dmg/download Current Version] (1.8.5, 291.2MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.8/wesnoth-1.8.4/Wesnoth_1.8.4.dmg/download Previous Version] (1.8.4, 290.5MB)

==== GNU/Linux ====
* There are binaries for many different GNU/Linux Distributions. Not all are always up to date with the current release. Please have a look at the [[WesnothBinariesLinux|Linux binary page]] for more information about the binaries for your Distribution.

==== OpenPandora ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.8/wesnoth-1.8.5/wesnoth-1.8.5-1.pnd/download Current Version] (1.8.5-1, 286.2 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.8/wesnoth-1.8.4/wesnoth-1.8.4-1.pnd/download Previous Version] (1.8.4-1, 286.3 MB)

==== Miscellaneous ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.8/wesnoth-1.8.5/wesnoth-1.8.5.tar.bz2.md5/download md5sum for current source code]
* [http://www.wesnoth.org/wiki/Download_Xdeltas#Stable_Version_1.8.x Xdelta for the source code]
* [http://sourceforge.net/projects/wesnoth/files/ SourceForge page for current and all previous versions]

== Stable (older versions) ==
Several operating systems do not offer a binary of the latest stable release. Here is a list of the latest known (stable version) binaries for various systems. For those older versions there often is no (official) multiplayer or addon server available anymore.

==== (Open)Solaris ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth-1.4/wesnoth-1.4.5/wesnoth-solaris-i386-1.4.5.pkg.bz2/download Older Version] (1.4.5, 145.6 MB), not compatible with 1.6.x

==== AmigaOS4 ====
* [http://os4depot.net/index.php?function=showfile&file=game/strategy/wesnoth.lha Older Version] (1.4.7, 140 MB), not compatible with 1.6.x

==== OS/2 & eComStation ====
* [http://download.smedley.info/wesnoth-1.4.5-os2-20080828.zip Older Version] (1.4.5, 160 MB), not compatible with 1.6.x

==== RISC OS ====
*[http://www.riscos.info/packages/arm/Games/wesnoth_1.4.5-1.zip Older version] (1.4.5-1, 140MB), not compatible with 1.6.x

==== Syllable ====
* [http://downloads.syllable.org/Syllable/i586/applications/contributed/Battle-for-Wesnoth/Battle-for-Wesnoth-1.2.6.application Older Version] (1.2.6, 60.8 MB), not compatible with 1.6.x

== Development (1.9 branch) ==
Version 1.9.x is the latest development version, boasting updated graphics and new exciting features. However, there may be occasional bugs or performance problems in the development versions since heavy changes are taking place all the time. For balanced and stable gaming, it is recommended you use the latest version of the 1.8.x branch. This version is recommended for coders and campaign developers, as well as those who want to preview the future of Wesnoth. People familiar with SVN and compiling can follow the latest development by checking [[WesnothSVN]].

==== Source code ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.9.1/wesnoth-1.9.1.tar.bz2/download Current Version] (1.9.1, 311.6 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.9.0/wesnoth-1.9.0.tar.bz2/download Current Version] (1.9.0, 304.0 MB)

* [[CompilingWesnoth|Compiling Guide]] - how to compile the source code

==== MS Windows ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.9.1/wesnoth-1.9.1-win32.exe/download Current Version] (1.9.1, 288.2 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.9.0/wesnoth-1.9.0-win32.exe/download Current Version] (1.9.0, 282.3 MB)

==== Mac OS X (10.4+) ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.9.1/Wesnoth_1.9.1.dmg/download Current Version] (1.9.1, 311.7 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.9.0/Wesnoth_1.9.0a.dmg/download Current Version] (1.9.0a, 306.8 MB)

==== GNU/Linux ====
* There are binaries for many different GNU/Linux Distributions. Not all are always up to date with the current release. Please have a look at the [[WesnothBinariesLinux|Linux binary page]] for more information about the binaries for your Distribution.

==== OpenPandora ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.9.1/wesnoth-1.9.1-1.pnd/download Current Version] (1.9.1-1, 306.0 MB)

==== Miscellaneous ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.9.1/wesnoth-1.9.1.tar.bz2.md5/download md5sum for current source code]
* [http://www.wesnoth.org/wiki/Download_Xdeltas#Development_Version_1.9.x Xdelta for the source code]
* [http://sourceforge.net/projects/wesnoth/files/ SourceForge page for current and all previous versions]
* [http://sourceforge.net/projects/wesnoth/files/unofficial/Mac%20Compile%20Stuff/wesnoth_compile_mac_1.9.zip/download MacCompileStuff for 1.9]

== License ==
''Main article: [[Wesnoth:Copyrights]]

This program is free software; you can redistribute it and/or modify it under the terms of the [http://www.fsf.org/copyleft/gpl.html GNU General Public License version 2], as published by the [http://www.fsf.org Free Software Foundation].
This program is distributed in the hope that it will be useful, but without any warranty; without even the implied warranty of merchantability or fitness for a particular purpose. See the GNU General Public License for more details.

== UMC Editor ==
This is available just with Wesnoth 1.9.x.
Details and installation steps can be found at: http://eclipse.wesnoth.org

== See also ==
* [http://changelog.wesnoth.org Changelog]
* [[WesnothBinaries| More binaries]]
* [[WesnothSVN]] - bleeding edge version from SVN

[[Category:Building and Installing]]

SpellingMistakes

2010-09-06T00:34:35Z

Tr0ll: add typo in LOW22

This page is meant to be a list of spelling mistakes in campaigns and other translatable texts in the en_US development version of the game.

Note: The house style of Wesnoth uses a good many words and constructions that are archaic, poetic, or dialectal. If you speak modern English as a second language you may incorrectly read these as errors. Please see [[NotSpellingMistakes]] for a list of things you will encounter that may look like spelling or usage errors but are not. Note that the mainline campaigns are now using correct typography, including sexed quotes and en and em dashes. These will appear as three byte sequences if you are not using a viewer that supports UTF-8.

==Mainline Campaigns==

===An Orcish Incursion===

===Dead Water===

[[Category:Troubleshooting and Bugs]]
In _main.cfg:
"you will need cunning and bravery to be survive" -> "you will need cunning and bravery to survive"

In 08_Talking_to_Tyegea.cfg:
"but I seems" -> "but it seems"

===Delfador's Memoirs===

===Descent into Darkness===

* Scenario 7: ''“For your final test as my apprentice, you will aid me in retrieving a book,” the necromancer says. ‘The book was... stolen from me long ago. Since it has personal value to me, think of the task as a small favor. I should warn you that it will require you to act against your countrymen of Wesnoth, since it was one of them who stole it from me.”'' – Replace ‘ with “

* Scenario 9:318: ''Phew! Let’s get out of here'' (Period is missing at the end of the sentence.)

===Eastern Invasion===

===Heir to the Throne===

===Liberty===

===Northern Rebirth===

===Sceptre of Fire===

===Son of the Black Eye===
Hush, Vraurk, <del>We</del> must trust [...]
:Hush, Vraurk, <ins>we</ins> must trust [...]

[...] you should have eaten that Grüü, you don't look so good.
:[...] you should have eaten that<ins>,</ins> Grüü, you don't look so good.

Now, as his son, it’s up to you to thwart the selfish designs 
2byte character "it's" 

with enemy orcs during the fourth year of his leadership. 
with enemy orcs during the <ins>4th</ins> year of his leadership. 
Can't translate.

the local earls and the orcish tribes and didn’t have any direct connection 
2byte character "didn't" 

===The Hammer of Thursagan===

===The Legend of Wesmere===

* Let us pursue the '''ORC WH'''o murdered El'Isomithir! 

* Gentlemen, don't squabble. We cannot go back now. But be watchful; I don’t like the feel of this country one bit. 
The　2nd "don't" has a 2byte character. 

* We will follow you, Kalenz ? '?' -> '.' Can't translate. 

* Very well, Kalenz ? lead us! '?' -> '.' Can't translate. 

* Let us give them aid ? '?' -> '.' Can't translate. 

* Cleodil bore Kalenz children who were tall, and beautiful, and inherited in full measure both their mother’s healing gifts and their father’s talented and searching mind. In the fullness of time, after a long life full of accomplishment and love and laughter, Cleodil died after the manner of Elves, aging swiftly to a peaceful end. -> 2byte character : "mother's" "father's" 

* Farewell $unit.name. Your loyal service won’t be forgotten. -> 2byte character "won't"

* in 22_Northern_Battle.cfg "It was clear to Kalenz and Cleodil that there would be no sanctuary for them while Landar lived. But during their years in seclusion '''thee''' fame of their deeds had only grown...."

===The Rise of Wesnoth===

"Lady Outlaw" states:
He must mean the Ruby of Fire. It was our most powerful artifact. We brought it with us from the *east*. We thought it was lost in the war with your people, when Lich-Lord Lenvan fell!

Should it not be "WEST" as the wesfolk and their lich lords come from there?
-Crommy-

===The South Guard===

===Two Brothers===

===Under the Burning Suns===

==Wesnoth Game==

===Editor===

===Tutorial===
"After this dialog, hold the mouse over the landscape image below the minimap " 
below -> above (1.9.0 development) 

===Manual===

===Manpages===

===Units===

* Dwarvish Pathfinder

They are powerful '''pathfinders in a melee'''

===1.10 Announcement===

===Other (ingame help, ...)===

* ― Haldric II, 42 YW, from Handbook of Tactical Analysis: Volume I

Remove space after 42. (There is already such string, so there is no need to use pofix here).

* Accuracy : (''src/generate_report.cpp:457'')

Should be Accuracy: (with space after ':')

===Multiplayer maps===

===Translation code bugs===

==Unofficial campaigns==

===Invasion from the unknown===

==Common Errors==

* '''alright''' – Technically, 'alright' ''is'' correct; it's a back formation, derived in the same way as 'already', and it can be traced back for decades. But it looks very modern. As we usually want a more archaic tone for Wesnoth, please use '''all right''' as two words instead.

* '''anymore''' – No, this ''is'' wrong. '''any more''' should be two words.

* 'being through with' – Constructs such as 'I am through dealing with these people' are also modern. Use sparingly.

* 'Great.' – Not necessarily wrong, but very modern, especially when used ironically.

* '''guys''' – Very modern usage. Please avoid.

* '''OK, okay''' – Modern; avoid.

* 'Princess' – Addressing a princess as 'Princess' is an egregious, tin-eared piece of George Lucas-level modern phrasing. It's not even correct in the real world. Correct Earth etiquette is to call her 'Your Royal Highness' when you first meet her, thereafter, 'Ma'am' (pronounced 'mam'). Search for 'Correct terms of address' if you have characters in your campaign for whom you need to get it right, or check this (and other) etiquette link(s) on Wikipedia: [http://en.wikipedia.org/wiki/Forms_of_address_in_the_United_Kingdom]. Any character born a noble ''will'' know this stuff, and will automatically get it right; to them, it's ingrained habit. Other characters might not, unless they're higher-level, better-educated, or have been briefed on what to do. But in formal encounters, such as meeting a (potential) enemy noble for the first time, characters will often at least try to be polite. Of course, Wesnoth etiquette is not necessarily the same as Earth etiquette. We haven't defined the rules for Wesnoth etiquette yet, and the Wikipedia article linked above is far more detailed than we'll ever need. Nevertheless, when we eventually do define our etiquette rules, they will be mostly Earth-like, and not George Lucas-like. Also look up the rules on lèse majesté (although those rules do only apply to sovereigns, not mere princesses), and bear in mind that any poor ignoramus who did address a princess as "Princess" would probably be taken away and flogged. This applies to other noble titles as well, to a greater or lesser degree. At least use phrases such as 'milady', 'my lord' and so on.

* 'Right.' – Not necessarily wrong, and preferable to 'Great.', but still very modern, especially when used ironically. Try 'Aye', or 'Yes', or 'Yea' instead.

* 'technically' – Modern; use sparingly.

* 'Uh, Um, Er,' – When they appear, these noises tend to be used in a modern way. You'll find 'O' and 'Oh' and 'Ah' and 'Ho' and 'Ha' in Shakespeare, but not 'Uh'. Instead of starting a sentence with 'Uh,' try to find a more archaic way of phrasing it.

* ''Yeah.' – Modern phrasing.

===Fantasy or archaic terms often confused===

* '''behold'''

Behold means 'see'. This means you can't behold sounds, or smells.

* '''besieged/beset'''

You can only be besieged if you're on some sort of defensible structure, but you don't have to be outmatched.

You can be beset in the middle of a flat featureless plain, but only if you're outmatched or close to it.

* '''breech/breach'''

A breach is a break. Breach can also be a verb.

'Once more unto the breach, dear friends!', as King Henry V once said.

A breech is part of a gun. Breech can't be a verb.

* '''Hear hear'''

Never 'Here here'. 'Hear hear' is short for 'Hear him, hear him', and originated in the British parliament in the 18th century.

* '''horde/hoard'''

A horde of barbarians.

A hoard of treasure. Hoard can also be a verb.

*'''march/marsh'''

See [[NotSpellingMistakes]]

*'''prey/pray'''

Predators prey on their prey. (verb and noun)

Priests pray prayers. (verb and noun)

The insects are known as ''praying mantises''.

* '''ravish/ravage'''

Ravish has sexual connotations which ravage does not.

You can ravish a fair maiden, and an old crone could have ravaged features.

You can ravage the land. You can't ravish the land, however.

* '''rise up'''

'Rise up' usually means 'rebel', and it is a rather inelegant term for 'advance'.

LegendofWesmere

2010-08-29T18:58:56Z

Tr0ll: grammar typo

General Note: Throughout this campaign, if your elves need to make a stand and you have a choice of options, choose the one that will put most of them in the woods. Not only will this give you the best chance of survival, it will ensure that the AI playing your allies will do useful things. This matters a lot, because many of the scenarios in this campaign involve allies you cannot control whose death results in your defeat.

Strategical Note: This is a long campaign where you play elves. So take a look at the top level units: There are two units capable of flight! One of them is a curing healer +8, the other one is level 4. Both of them can do magic, and both of them can slow their enemies! If you can team up two shydes and two sylves, you get a magically hard hitting, regenerating, slowing air force that can ZoC-lock an enemy. As if that wasn't enough, late in the campaign you'll lose access to most of your veteran troops, but not your sylves and shydes. So it really pays to level shamans, level shamans and level shamans.

Loyal troops are even more valuable in this campaign than in most others, partially because they get three traits, but mainly because you'll get to keep them when your other troops are unavailable. With that in mind, you should strongly consider leveling one (or both!) of your loyal fighters into a grand marshal. His leadership skills will prove invaluable when you are stuck with a level 1 army.

== The Uprooting ==
* Objectives: Move Kalenz to the signpost
* Lose if: Kalenz or Landar dies or turns run out
* Turns: 16/14/12 (easy/medium/hard)
* Starting units: Kalenz, Landar and Anduilas

Like the first scenario in Heir to the Throne, this scenario begins with the hero in a forest with enemies preparing to close in on all sides. You can't beat the enemy leaders (you have too little gold, only first level units, and a stringent turn limit) and you're not expected to try. Recruit just enough units to screen Kalenz and Landar (about a keep or a keep and a half's worth) and run everybody to the signpost at the southwestern corner of the map. Try to send at least one rider to grab villages, including one to the north of your ally's keep—if the orcs attack him before the scenario ends, you will inherit the ally's units (and you'll keep them for future recall if you run them south to join the rest of your army).

'''Alternate strategy: '''
As with the first scenario in HttT, an effective strategy is to split your leader from your main army. Send Kalenz due west and then south to the sign-post, while the rest of your army moves more southwest to distract the south-west orcs. Since the starting time of day means you will meet the orcs just as day is ending, it is both possible and a good idea to keep engagements to a minimum - just lure the orcs away from Kalenz without getting into a fight. From my experience, the AI has difficulty making up its mind what to do with the southwestern orcs, especially if you grab the eastern villages, and Kalenz should be able to easily sneak by on the western edge of the map to the signpost without any obstructions. I was able to finish the scenario on hard difficulty on turn 6 with 0 losses and level Anduilas, your loyal elf fighter to level 2. One full castle of recruits is probably more than enough. Remember your goal is only to distract, not kill, and the combined upkeep of your units and your ally's that he gives you on turn 3 or so will give you negative income if you recruit too much.

== Hostile Mountains ==
* Objectives: Move Kalenz to the signpost or defeat the troll leader
* Lose if: Kalenz, Landar or Olurf dies or turns run out
* Turns: 32/28/24 (easy/medium/hard)
* Starting units: Kalenz, Landar and any surviving loyal units

The most important thing to do is get the dwarves to fight the trolls. Send a disposable unit or two to the middle island. Put a unit in the water where a troll will go to the east bank in order to attack. The unit won't live but you'll get a bunch of allies.

Because your units will be mostly first level, you need as many of them as you can afford to survive this scenario. Archers will be the most useful to recall/recruit because the trolls do not have a ranged attack. Though archers are needed to deal enough damage to the trolls it is a good idea to recall/recruit a number of shamans as well. On the one hand they can level quite easily fighting the high-level trolls, and on the other hand they make your enemies a lot less dangerous through their slowing attack.

Do not, under any circumstances, cross the river—if you do, Olurf will attack you, and the trolls will cut both you and the dwarves to pieces. (You can have units stand in the river if necessary to reach a particular unit, but since your enemies are more powerful than your units avoid doing so if you are likely to be counterattacked.) Instead, send a rider or two out to grab the villages in the far northern reaches of the board while you move your troops onto the wooded island in the middle of the river, directly south of your keep. From here, you can help the dwarves whittle down the trolls while you slowly wend your way southwest toward the troll keep. The scenario will end if you succeed in killing the troll leader. Note: Olurf's death counts as a defeat.

Some Observations (for Hardest Difficulty, but also applicable to other levels):
# It's not necessary to lure the trolls to step onto the dwarf side of the river by sacrificing a unit. It seems the trolls will go visit the dwarves on their own without needing any encouragement.
# There is a reason the middle island has so much forest. The western bank of the river has a narrow swath of forest surrounded by mountains and hills. This is not ideal terrain for fighting trolls. Trolls move faster than elves on hills and mountains and have comparable defense. A much better idea is to try to occupy the middle island, forcing the trolls to attack from water. Chances are you'll only be able to claim the northern tip of the island at first, so half your army will spill over to the forest on the west bank. Use shamans to slow and don't be afraid to put one unit in water if you can get a kill and then block. The dwarves help by putting units in water and doing other things to distract the trolls and draw fire away from you.
# Sorceresses are very effective at killing trolls, since arcane is the only attack type trolls have negative resistance to. Try to get a few by feeding kills to shamans. They also become incredibly useful later in the campaign, so it will be well worth the effort.

== Ka'lian Under Attack ==
* Objectives: Survive the initial attack with Galtrid, then defeat the enemy leaders
* Lose if: Kalenz, Landar or Galtrid dies or turns run out
* Turns: 5/7/9 initially, then 35/30/25 extra (easy/medium/hard)
* Starting units: Kalenz, Landar and any surviving loyal units

Take careful note of this map; you'll be fighting on it again later.

For the first seven turns you are controlling the defenders of the Ka'lian. See all those Orcish Assassins in the water? You probably don't want to have all your units poisoned to death. Recruit Shamans to sit behind the defenders. They won't be able to cure, but they will prevent the loss of 8 HP per turn. If an Elvish Archer is poisoned, go ahead and use its ranged attack on an Assassin, otherwise try to manage your poisoned units somewhat prudently. Don't just hit Ctrl-R to recruit; you have a massive keep so put your new units in the right place. Don't let the orcs in good defense terrain and you should be fine. When turn 7 is done Kalenz arrives and you lose control of these defenders. If you can, move some units as far west as you can (if the attack has wound down). This seems to help the AI attack the westernmost orc leader, which is useful.

When you take over with Kalenz make your stand in the woods just to the southwest of your keep and to the immediate north of the Ka'lian. Use Elvish Shamans to slow powerful units, and recruit lots of archers. Send some riders to grab villages— it should be relatively low-risk and the gold will be useful for the next scenario (note that you can't cross the river on the far eastern edge of the map). If you manage your troops correctly, you can level a number of them which is a very good idea to get through the next few scenarios.

== The Elvish Treasury ==
* Objectives: Defeat the enemy leaders
* Lose if: Kalenz, Landar or Cleodil dies or turns run out
* Turns: 35/30/25 (easy/medium/hard)
* Starting units: Kalenz, Landar and any surviving loyal units

Send your army en masse to the keep in the northwest first; that's where the Shyde and the gold are. Then turn east to take out the other saurian. When fighting the saurians, there are three things to remember: 1) Don't send out isolated units, because they'll be swarmed and killed; 2) Try not to position any units where a saurian can attack them from swampy ground; and 3) watch the day/night cycle (it doesn't affect your elves, but the saurians are significantly weaker by day and you can turn that fact to great advantage). Try and kill the Augurs with your fighter line and if possible slow the Skirmishers. The Skirmishers have a lot of movement points; make sure that wounded units are safe.

== The Saurian Treasury ==
* Objectives: Defeat the enemy leaders
* Lose if: Kalenz, Landar or Cleodil dies or turns run out
* Turns: 24/20/18 (easy/medium/hard)
* Starting units: Kalenz, Landar, Cleodil and any surviving loyal units

This scenario is much trickier than the last one because here you have to fight the saurians on terrain that's hostile to your elves (desert and swamp). Try and keep on good terrain (or at least keep the saurians out of good terrain) and form a defensive line (against Skirmishers) each turn. Kill the southern leader first. See that temple? That's the treasury. DO NOT go in there. When you go in saurians pop out. Wait until you are ready to kill them to trigger this trap.

When you've dealt with the southern leader and the treasury you can either take an Elvish Scout to the treasury to pick up the gold and return it to the sign post or just go kill the northern leader. Killing the leader is preferable. You'll get XP and any loss in gold from early finish is dwarfed by the 1800 gold you get for beating the level.

== Acquaintance in Need ==
* Objectives: Defeat the enemy leaders
* Lose if: Kalenz, Landar, Cleodil or Olurf dies or turns run out
* Turns: 35/30/25 (easy/medium/hard)
* Starting units: Kalenz, Landar, Cleodil and any surviving loyal units

This is another leveling opportunity for your shamans, as there is another troll leader to kill. Also you need to make sure that you neither overrecruit nor underrecruit. With too few units, you will take too long to finish your enemies (as always), while too many units won't help you in the fight, and you will need the money!

Start with the green enemy, who's the closest one to you. The dwarves, who are your allies for this scenario, should provide substantial help in doing so. While you finish off the first orc, you should start sending a fair amount of relatively unexperienced archers/shamans west to take on the troll. Then move north over the mountains in a broad line to take out the orcs. A broad front line will help you to quickly overrun the orcs and allow you to finish in good time. Of course, you need sufficient numbers to do this without overstretching yourself.

The dwarves will get a lot of kills/occupy the enemy quite a bit. Their high mountain defense and mobility ensure this. You may need to resign yourself to softening the orcs up and letting the dwarves get the kills.

== Elves' Last Stand ==
* Objectives: Defeat all of the enemy leaders
* Lose if: Kalenz, Landar, Cleodil or Galtrid dies or turns run out
* Turns: 35/30/25 (easy/medium/hard)
* Starting units: Kalenz, Landar, Cleodil and any surviving loyal units

[NOTE: This scenario gives you the option of choosing to give orders to the AI that controls your allies. Because of bug issues, I ended up playing the scenario through without using this option. The advice that follows is for playing the scenario with the AI making automatic choices.--cathyr19355]

This is the same map as in Kal'ian Under Attack, but with many more enemies. Don't do the obvious thing here—i.e., attacking the trolls first, because they're the nearest enemy—that will just get Galtrid, your ally holding the Kal'ian, killed, causing defeat. Instead, make your stand in the woods just north of the Kal'ian, taking care to assume a position that will let you defend both against the trolls and against Urug-Pir's and Mordrum's orc troops that will be coming east from the other side of the river. (If you have enough troops, this time it will be useful to move some of them to the river bank to attack the orcs while they're still in the water.) If you're careful, you can use the heavy fighting to level units. As you kill off the aforementioned trolls and orcs, move the main body of your army south through the Kal'ian to Grubr's keep, then west and north again to kill the remaining enemies. Meanwhile, recruit/recall a bunch of riders and other fast-moving units, send them directly south of your keep to grab the villages on the eastern side of the board; if they make it far enough south, you can aim them at Grubr's keep to take some of the pressure off the Kal'ian. Even though you have a lot of gold and can recruit a lot of units, your enemies are numerous, and Olurf and his dwarves won't show up until the third day, so don't get sloppy about formation and protecting the wounded.

Note for directing the AI:
Your south-westmost ally is too weak to survive unaided where he is. So it is a good idea to wait until he has recruited as much as he can before telling him to move his leader to Kal'ian. I tried to get both my allies to swarm the sourthern orc, they should be able to defeat him, but unfortunately the AI does not really listen to this kind of order (bug?), so once I had the trolls under control I send a select few units south through Kal'ian to help mop up the remaining orcs there. This should leave you enough time to concentrate on the nothern battle.
(At the moment, you will have to debug the scenario before playing it, since Galtrid does not recruit at all. Hopefully it won't take long until a debuged version is shipped with the game.)

== Council of Hard Choices ==

Story only.

== Bounty Hunters ==
* Objectives: Move Kalenz across the river
* Lose if: Kalenz, Landar, Cleodil or Olurf dies or turns run out
* Turns: 32/28/24 (easy/medium/hard)
* Starting units: Kalenz, Landar, Cleodil and any surviving loyal units

The only thing you gain from defeating the saurians is experience. Since you just left a lot of your troops at the Ka'lian, experience may be worth your effort. Nonetheless, if you are having trouble beating this level just run north as fast as you can. You should be able to cross the river with little trouble. You probably don't even need to recruit.

As for experience, the enemy recruits some relatively low HP level 2s and 3s. You can level units quickly after killing a couple of Saurian Oracles. Of course those Oracles have strong magical attacks (especially at night) negating your high defense. Luckily for you the battles start during the day. Recruit just one keepful of troops. Send a dwarf-heavy squad to the left (closer mountains) and an elf-heavy one to the right (more forest). If you recruit more than one keepful Kalenz will have a much tougher time crossing the river.

Focus on killing the Oracles and Augurs first. They are easy to kill and do a lot of damage. Instead of throwing 3 or 4 units at a level 3 Flanker, just slow it and rack up kills. Try and kill as many units as you can before nightfall, when the attacks become much more ferocious.

You can distract the serpent by having an Elvish Scout make his way to the western edge of the river bank. When the serpent shows up the rider can distract it with his bow.

== Cliffs of Thoria ==
* Objectives: Move Kalenz to the signpost and defeat the enemy leaders
* Lose if: Kalenz, Landar, Cleodil or Olurf dies or turns run out
* Turns: 32/28/24 (easy/medium/hard)
* Starting units: Kalenz, Landar, Cleodil, Olurf and any surviving loyal units

There are three tricky elements about this one. First, you have to climb to your destination (the signpost at the top northeast corner of the map) over high mountains, so the going will be very slow for your elves; watch the turn clock carefully. Second, the "fog of war" applies so you won't know much about your enemies until you actually bump into them. Third, some of your enemies are level 4 Yetis. Split your forces, sending one group west. The other group, with Kalenz, goes directly north, deals with the nearest enemy, and continues to the signpost. This group should be large enough that you can peel off 4-6 units once you get most of the way north to take out the enemy in the far northwestern keep. Note: dwarves do well in the mountains, but don't recruit a lot of ulfserkers, not even the second-level ones—they tend to take out the unit they attack but then are very vulnerable to attacks by other units.

== Battle of the Book ==
* Objectives: Defeat Aquagar the drake wizard
* Lose if: Kalenz, Landar, Cleodil or Olurf dies or turns run out
* Turns: 30/34/38 (easy/medium/hard)
* Starting units: Kalenz, Landar, Cleodil, Olurf and any surviving loyal units

Your enemies here are drakes and trolls. This is in your favor because the scenario starts at night, when drakes are weakest. Be careful about using archers, since some of the drakes breathe fire and do more damage that way than your units can with their arrows. A good mix of impact and ranged fighters is essential. Split your forces. Send half of your troops east along the road first to Crelanu's keep (if you don't, he may get killed before you can kill off the drakes) to save him and kill the troll leader (whose keep is close by). Take the remaining troops west to kill the drake leader.

== Revelations ==

Story only.

== News from the Front ==

Story only.

== Human Alliance ==
* Objectives: Survive until the end of turns
* Lose if: Kalenz, Landar, Cleodil, Olurf or Aldar (the human leader) dies or turns run out
* Turns: 14/16/18 (easy/medium/hard)
* Starting units: Kalenz, Landar, Cleodil, Olurf and any surviving loyal units

The enemy is in three places: the northwest, the northeast (trolls) and the southwest. Only the northeast trolls won't get reinforcements. So the only leaders to focus on eliminating are the trolls. Your recruits/recalls need to do three things: contain the northwest orcs (this is not that hard due to favorable terrain), aid your human allies to the south and eliminate the trolls.

The trolls should be pretty easy to kill. Their leader doesn't have much money so their aren't a lot of trolls. Slow with some shaman, use the forest to your benefit and you should defeat them soon. Send the units to reinforce your other two fronts.

Your allies can hold their own against the first wave of southern attackers but after that they'll be toast. A much better outcome is to team up with them and crush the first wave. When the reinforcements come you should be in a good position to defeat them (especially with your victorious anti-troll army coming to help).

The northwest orcs are numerous but should be kept in check by strong units in the bottlenecks. You'll need some tanks (Champions/Marshals or Steelclads) and healers. When the orc reinforcements arrive you may get swarmed. By this time you should have some help coming from your anti-troll army. Also, three elves will arrive along the western edge of the map. Have them come and help out.

You may want to recruit a scout or two at the beginning. Along with the horseman you get they can capture a village almost every turn. Don't bother leaving villages for your ally. The money is better in your hands.

== The Treaty ==

Story only.

== The Chief Must Die ==
* Objectives: Kill the orc chief then return to the signpost
* Lose if: Kalenz or Landar dies or turns run out
* Turns: 32/32/32 (easy/medium/hard)
* Starting units: Kalenz and Landar

You get no keep, and no chance to recruit, in this one. The only units you have are Kalenz and Landar, and their only task is to assassinate the Orc Sovereign (in the middle) and then return to the signpost at the southwestern corner of the map. Your units will have special attributes (invisible, 80% dodge) for this scenario only that will make this fairly easy, particularly if you have managed to get Landar to level 3. When Kalenz takes the potion he changes into an Elvish Lord. You should easily be able to get him to level up during this scenario.

You should have plenty of turns. The only units that will attack you are the Wolf Rider line. They don't pose much threat thanks to Landar's bow and your 80% dodge. Go to the orc leader, kill him and return to the signpost. There is no point in grabbing villages as you get no income from them. There is also no point in finishing early so go ahead and level Kalenz.

== Breaking the Siege ==
* Objectives: Defeat all enemy leaders
* Lose if: Kalenz, Landar, Cleodil, Olurf or Uradredia (the elf leader) dies or turns run out
* Turns: 40/36/32 (easy/medium/hard)
* Starting units: Kalenz, Landar, Cleodil, Olurf and any surviving loyal units

Stick to recruiting units with lots of mobility, since the map is large and mostly snow-covered, hampering most of your unit types (don't even bother to recruit dwarves—they won't get to the scene of the action in time to strike any blows). Slyphs and Shydes are best, of course.

It is essential that you reach your ally quickly. Otherwise he might be dead before you even see him. Despite the fact that fog of war is turned on for this scenario, it's pretty simple to figure out from the geography which keep belongs to your ally (the one in the middle of the forest). You will want to finish this level quickly to have lots of gold for the next scenario (on medium you'll probably want at least 500 gold). Send some fast units north to keep your ally alive and send the rest straight west. The western units can sweep up after taking out the southern orc boss. A bunch of Direwolf Riders come as reinforcements when you get to close to the southern orc, so be careful. Alternatively just send everyone north and fan out from there.

With good units this level shouldn't be tough to beat. Just make sure you beat it in good standing for the next scenario.

== Hour of Glory ==

Story only.

== Costly Revenge ==
* Objectives: Defeat all enemy units and destroy all enemy villages
* Lose if: Kalenz, Landar dies or turns run out
* Turns: 40/36/32 (easy/medium/hard)
* Starting units: Kalenz, Landar and any surviving loyal units
* Other

This is the same map as The Saurian Treasury, but with most of the terrain snow-covered. Since you're fighting the saurians again, most of the advice from that scenario still applies. Mobility is not a great issue, even though one of the enemy keeps is near the top northeastern corner of the map, because by the time you can dispose of your southern enemy he will have already sent most of his troops south after you. Numbers are an issue, however. So, whatever you do, do not underrecruit!

The best place to make a stand is probably near the patch of forest in the middle. You have to put units in the swamp to keep the saurians out of there. The only poor-defense terrain for the saurians is the ice, so keep them on it. The Oracles/Soothsayers will use their ranged attack on your melee units and the Skirmishers/Flankers will use their melee attack on your archers. You will take heavy losses but this is actually good (more on that in a second).

I like to send Kalenz and a couple of fast units (Scouts/Riders) along the northern forest and then have them cut across the top of the map. This accomplishes three things: one, you torch some out of the way villages; two, you can distract the northern saurians long enough to keep your main force (in the middle of the map) in control; three, you can move them over to kill the northern leader at the end.

There is a weird twist to this level. After this the elvish civil war breaks out. All your units except loyal ones defect and serve Landar. So, see that Elvish Champion racking up the kills? Next time he's in battle he will be killing ''your'' units. After the tide of the battle has turned try and get the non-loyal high level units killed (attack those last two Oracles with ranged attack, etc). Save any units from the shaman line - they will stay on your side and be usable later

If you have enough gold your main worries will be getting to the villages in time (scouts come in handy), getting to the northern leader in time and leaving as few good units for the civil war as possible.

== Council Ruling ==

Story only.

== Elvish Assassins ==
* Objectives: Move Kalenz to the signpost
* Lose if: Kalenz or Cleodil dies or turns run out
* Turns: 20/16/12 (easy/medium/hard)
* Starting units: Kalenz, Cleodil and Anduilas

This is another running game, on the same map as the first scenario; since Landar has betrayed Kalenz, most elves' hands have turned against our hero. The Landar and Olurf units gone, and so is most of your recall list. Recruit enough units to screen Kalenz and Cleodil and run for the signpost at the southwestern corner of the map.Because most of the units ranged against you will be second level or higher, this will take a bit of ingenuity unless you can recruit a lot of units for guard duty. The best choice is probably to recruit Elvish Scouts. You are using their ZoC to keep the attackers away from Kalenz. Don't try and be fancy.

== Northern Battle ==
* Objectives: Defeat all enemy leaders or survive for six days
* Lose if: Kalenz, Cleodil or Uradredia dies or turns run out
* Turns: 40/36/32 (easy/medium/hard)
* Starting units: Kalenz, Cleodil and Anduilas

This is the same map as Breaking the Siege, but since it's not winter, most of the board is grassland and woods, and much easier for your elves to fight on. Landar, now one of your enemies, will be in the far southwest, while another enemy elf has a keep in the far southeast. If you have been building a formidable "air force" (shaman line) you can beat this level very easily.
* The AI leader southeast of your starting keep will make a severe tactical blunder, capturing the only village in range on turn 1, leaving him utterly exposed with enemies nearby. With the select group of loyal troops (and any Slyphs available for recall) and proper positioning on turn 1, it is trivial to eliminate the enemy leader on turn 2. If you can't kill him or ZoC him in turn 2, slow him. That will prevent him from getting to back to the keep to recruit. The battle is over as soon as one of your units moves next to Landar, so let him march his troops north to attack your ally. Recruit a squad of scouts (or quick units) and send them west, timing it so that they reach Landar's keep the turn after he moves his troops out of range. Reach Landar's keep and you'll have plenty of gold to finish the game.

If you don't have enough units from the shaman line for the quick kill, try this:
* Because of Landar's betrayal and the loss of most of your veterans, you will be working mostly with first level units. Consequently, don't try to take on either enemy on the naked grasslands where their keeps lie; recruit as much as you can, then head for your ally's keep in the north central region of the board, taking as many villages during the process as possible. If necessary, leave a few units at the river bank to slow the brown elf units that will pursue you; there is a village on a peninsula in the river near your keep that may be useful in this regard. If you need to, make a stand in and about your ally's keep, though depending upon how well you delay the brown enemy you may be able to pick off your enemy a few at a time in the forest long enough to survive until the end of the scenario.

Remember you don't have to kill all the enemies. Just kill the southeast leader and then sneak a fast unit in next to Landar.

== End of War ==
* Objectives: Defeat Landar
* Lose if: Kalenz or Cleodil dies or turns run out
* Turns: 24/21/18 (easy/medium/hard)
* Starting units: Kalenz, Cleodil and any surviving loyal units

Recall any remaining veteran troops, then recruit an army of level 1 elves. Send out riders to grab villages early, and form up your line of battle at the edge of the forest to maximize the difference in defense (70% vs. 40%, while trying to hold the shore is only 40% vs. 20%). The forest defense bonus also means that your level 1 troops stand a good chace of surviving at least one round of two level 2 attacks (which they are unlikely to survive on open ground). If any enemy elves make it into the forest the best approach is to use magic attacks to smoke them out (a slyph works wonders). Once Landar's army has been dealt with, sweep your troops down to the enemy keep to deliver the coup de grace.

== Epilogue ==

Story only.

Download

2010-07-06T03:00:22Z

Tr0ll: /* Miscellaneous */ fix md5 link for 1.8.3

Welcome to the Battle for Wesnoth downloads page. The BFW project team only officially releases the source code. Binary packages are only provided by community volunteers and hosted here. Torrents are also unofficial.

If the latest binaries are not currently available for your OS, please check back in a few days to see if they have been placed here. Packagers have been informed of the release, please be patient. In the meantime, read the [[FAQ#A_new_version_is_out.2C_but_where_is_the_download_for_.5BWindows.2C_Mac_OS.2C_etc..5D.3F|FAQ]].

__NOTOC__
Jump to: [[Download#Stable_.281.8_branch.29|Stable Branch]] | [[Download#Stable_.28older_versions.29|Stable Branch (older versions)]] | [[Download#Development_.281.7_branch.29|Development Branch]]

== Stable (1.8 branch) ==
The stable files are meant to be used as a stable and rather balanced version of the game. Each version of the 1.8 branch is compatible to each other.

Version 1.8.3 is the latest stable version. This version is recommended for most players since the 1.8 online multiplayer community is very large and user-made campaign server has a robust content selection.

==== Source code ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.8.3.tar.bz2/download Current Version] (1.8.3, 285.1 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.8.2.tar.bz2/download Previous Version] (1.8.2, 284.9 MB)
* [[CompilingWesnoth|Compiling Guide]] - how to compile the source code

==== MS Windows ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.8.3-win32.exe/download Current Version] (1.8.3, 265.8 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.8.2-win32.exe/download Previous Version] (1.8.2, 265.8 MB)

==== Mac OS X (10.4+) ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/Wesnoth_1.8.3.dmg/download Current Version] (1.8.3, 289.3MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/Wesnoth_1.8.2.dmg/download Previous Version] (1.8.2, 289.2 MB)

==== GNU/Linux ====
* There are binaries for many different GNU/Linux Distributions. Not all are always up to date with the current release. Please have a look at the [[WesnothBinariesLinux|Linux binary page]] for more information about the binaries for your Distribution.

==== OpenPandora ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.8.3-1.pnd/download Current Version] (1.8.3, 285.2 MB)

==== Miscellaneous ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.8.3.tar.bz2.md5/download md5sum for current source code]
* [http://www.wesnoth.org/wiki/Download_Xdeltas#Stable_Version_1.8.x Xdelta for the source code]
* [http://sourceforge.net/projects/wesnoth/files/ SourceForge page for current and all previous versions]

== Stable (older versions) ==
Several operating systems do not offer a binary of the latest stable release. Here is a list of the latest known (stable version) binaries for various systems. For those older versions there often is no (official) multiplayer or addon server available anymore.

==== (Open)Solaris ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-solaris-i386-1.4.5.pkg.bz2/download Older Version] (1.4.5, 145.6 MB), not compatible with 1.6.x

==== AmigaOS4 ====
* [http://os4depot.net/index.php?function=showfile&file=game/strategy/wesnoth.lha Older Version] (1.4.7, 140 MB), not compatible with 1.6.x

==== OS/2 & eComStation ====
* [http://download.smedley.info/wesnoth-1.4.5-os2-20080828.zip Older Version] (1.4.5, 160 MB), not compatible with 1.6.x

==== RISC OS ====
*[http://www.riscos.info/packages/arm/Games/wesnoth_1.4.5-1.zip Older version] (1.4.5-1, 140MB), not compatible with 1.6.x

==== Syllable ====
* [http://downloads.syllable.org/Syllable/i586/applications/contributed/Battle-for-Wesnoth/Battle-for-Wesnoth-1.2.6.application Older Version] (1.2.6, 60.8 MB), not compatible with 1.6.x

== Development (1.7 branch) ==
Version 1.7.x was the previous development version.
At the moment the stable 1.8.x branch offers all the new features known from 1.7.x. The next development release will take some more time and be known as 1.9.x. In the mean time, people familiar with SVN can follow its development by checking [[WesnothSVN]].

==== Source code ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.7.15.tar.bz2/download Current Version] (1.7.15-1.8rc1, 270.4 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.7.14.tar.bz2/download Previous Version] (1.7.14-1.8beta7, 264.8 MB)

* [[CompilingWesnoth|Compiling Guide]] - how to compile the source code

==== MS Windows ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.7.15-1.8rc1-win32.exe/download Current Version] (1.7.15-1.8rc1, 253.1 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.7.14-1.8beta7-win32.exe/download Previous Version] (1.7.14-1.8beta7, 247.6 MB)

==== Mac OS X (10.4+) ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/Wesnoth_1.7.15.dmg/download Current Version] (1.7.15-1.8rc1, 275.3 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/Wesnoth_1.7.14.dmg/download Previous Version] (1.7.14-1.8beta7, 269.4 MB)

==== GNU/Linux ====
* There are binaries for many different GNU/Linux Distributions. Not all are always up to date with the current release. Please have a look at the [[WesnothBinariesLinux|Linux binary page]] for more information about the binaries for your Distribution.

==== Miscellaneous ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.7.15.tar.bz2.md5/download md5sum for current source code]
* [http://www.wesnoth.org/wiki/Download_Xdeltas#Development_Version_1.7.x Xdelta for the source code]
* [http://sourceforge.net/projects/wesnoth/files/ SourceForge page for current and all previous versions]
* [http://downloads.sourceforge.net/wesnoth/Mac_Compile_Stuff_1.5.3.tar.bz2/download MacCompileStuff for 1.5.3]

== License ==
''Main article: [[Wesnoth:Copyrights]]

This program is free software; you can redistribute it and/or modify it under the terms of the [http://www.fsf.org/copyleft/gpl.html GNU General Public License version 2], as published by the [http://www.fsf.org Free Software Foundation].
This program is distributed in the hope that it will be useful, but without any warranty; without even the implied warranty of merchantability or fitness for a particular purpose. See the GNU General Public License for more details.

== See also ==
* [http://changelog.wesnoth.org Changelog]
* [[WesnothBinaries| More binaries]]
* [[WesnothSVN]] - bleeding edge version from SVN
* [http://www.essaywriter.co.uk/ Essay Writing]

[[Category:Building and Installing]]

SpellingMistakes

2010-04-14T04:21:39Z

Tr0ll: /* Delfador's Memoirs */

Download

2009-10-04T16:17:31Z

Tr0ll: /* Miscellaneous */

Welcome to the Battle for Wesnoth downloads page. The BFW project team only officially releases the source code. Binary packages are only provided by community volunteers and hosted here. Torrents are also unofficial.

If the latest binaries are not currently available for your OS, please check back in a few days to see if they have been placed here. Packagers have been informed of the release, please be patient. In the meantime, read the [[FAQ#A_new_version_is_out.2C_but_where_is_the_download_for_.5BWindows.2C_Mac_OS.2C_etc..5D.3F|FAQ]].

__NOTOC__
Jump to: [[Download#Stable_.281.6_branch.29|Stable Branch]] | [[Download#Development_.281.7_branch.29|Development Branch]]

== Stable (1.6 branch) ==

The stable files are meant to be used as a stable and rather balanced version of the game. Each version of the 1.6 branch is compatible to each other.

Version 1.6.5 is the latest stable version. This version is recommended for most players since the 1.6 online multiplayer community is very large and user-made campaign server has a robust content selection.

==== Source code ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.6.5.tar.bz2/download Current Version] (1.6.5, 219.6 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.6.4.tar.bz2/download Previous Version] (1.6.4, 219.2 MB)
* [[CompilingWesnoth|Compiling Guide]] - how to compile the source code

==== MS Windows ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.6.5-win32.exe/download Current Version] (1.6.5, 207.2 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.6.4-win32.exe/download Previous Version] (1.6.4, 204.6 MB)

==== Mac OS X (10.4+) ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/Wesnoth_1.6.5.dmg/download Current Version] (1.6.5, 222.6 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/Wesnoth_1.6.4.dmg/download Previous Version] (1.6.4, 222.3 MB)

==== GNU/Linux ====
* There are binaries for many different GNU/Linux Distributions. Not all are always up to date with the current release. Please have a look at the [[WesnothBinariesLinux|Linux binary page]] for more information about the binaries for your Distribution.

==== (Open)Solaris ====
* The current version (1.6.5) is not available yet.
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-solaris-i386-1.4.5.pkg.bz2/download Older Version] (1.4.5, 145.6 MB), not compatible with 1.6.x

==== AmigaOS4 ====
* The current version (1.6.5) is not available yet.
* [http://os4depot.net/index.php?function=showfile&file=game/strategy/wesnoth.lha Older Version] (1.4.7, 140 MB), not compatible with 1.6.x

==== OS/2 & eComStation ====
* The current version (1.6.5) is not available yet.
* [http://download.smedley.info/wesnoth-1.4.5-os2-20080828.zip Older Version] (1.4.5, 160 MB), not compatible with 1.6.x

==== RISC OS ====
* The current version (1.6.5) is not available yet.
*[http://www.riscos.info/packages/arm/Games/wesnoth_1.4.5-1.zip Previous version] (1.4.5-1 140MB), not compatible with 1.6.x

==== Miscellaneous ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.6.5.tar.bz2.md5/download md5sum for current source code]
* [http://www.wesnoth.org/wiki/Download_Xdeltas#Stable_Version_1.6.x Xdelta for the source code]
* [http://sourceforge.net/projects/wesnoth/files/ SourceForge page for current and all previous versions]

== Development (1.7 branch) ==

Version 1.7.x is the latest development version, boasting updated graphics and new exciting features. However, there may be occasional bugs or performance problems in the development versions since heavy changes are taking place all the time. For balanced and stable gaming, it is recommended you use the latest version of the 1.6.x branch. This version is recommended for coders and campaign developers, as well as those who want to preview the future of Wesnoth.

==== Source code ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.7.6.tar.bz2/download Current Version] (1.7.6, 256.7 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.7.5.tar.bz2/download Previous Version] (1.7.5, 249.7 MB)

* [[CompilingWesnoth|Compiling Guide]] - how to compile the source code

==== MS Windows ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.7.6-win32.exe/download Current Version] (1.7.6, 239.9 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.7.5-win32.exe/download Previous Version] (1.7.5, 233.4 MB)

==== Mac OS X (10.4+) ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/Wesnoth_1.7.6.dmg/download Current Version] (1.7.6, 260.7 MB)
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/Wesnoth_1.7.5.dmg/download Previous Version] (1.7.5, 252.8 MB)

==== GNU/Linux ====
* There are binaries for many different GNU/Linux Distributions. Not all are always up to date with the current release. Please have a look at the [[WesnothBinariesLinux|Linux binary page]] for more information about the binaries for your Distribution.

==== (Open)Solaris ====
* The current version (1.7.5) is not available yet.
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.5.1.solaris.i386.pkg.bz2/download Older Version] (1.5.1, 130.4 MB)

==== AmigaOS4 ====
* The current version (1.7.5) is not available yet.
* [http://os4depot.net/index.php?function=showfile&file=game/strategy/wesnoth-devel.lha Older Version] (1.3.12, 105.0 MB)

==== OS/2 & eComStation ====
* The current version (1.7.5) is not available yet.
* [http://download.smedley.info/wesnoth-1.1.8-os2.zip Older Version] (1.1.8, 66 MB)

==== Syllable ====
* The current version (1.7.5) is not available yet.
* [http://www.syllable-software.info/download.php?view.32 Older Version] (1.3.8, 82.2 MB)

==== Miscellaneous ====
* [http://sourceforge.net/projects/wesnoth/files/wesnoth/wesnoth-1.7.6.tar.bz2.md5/download md5sum for current source code]
* [http://www.wesnoth.org/wiki/Download_Xdeltas#Development_Version_1.7.x Xdelta for the source code]
* [http://sourceforge.net/projects/wesnoth/files/ SourceForge page for current and all previous versions]
* [http://downloads.sourceforge.net/wesnoth/Mac_Compile_Stuff_1.5.3.tar.bz2/download MacCompileStuff for 1.5.3]

== License ==
''Main article: [[Wesnoth:Copyrights]]

This program is free software; you can redistribute it and/or modify it under the terms of the [http://www.fsf.org/copyleft/gpl.html GNU General Public License version 2], as published by the [http://www.fsf.org/ Free Software Foundation].
This program is distributed in the hope that it will be useful, but without any warranty; without even the implied warranty of merchantability or fitness for a particular purpose. See the GNU General Public License for more details.

== See also ==
* [http://changelog.wesnoth.org Changelog]
* [[WesnothBinaries| More binaries]]
* [[WesnothSVN]] - bleeding edge version from SVN

[[Category:Building and Installing]]

SpellingMistakes

2007-12-07T22:54:39Z

Tr0ll:

This page is meant to be a list for mistakes in campaigns and other texts in the en_US version of the game.

==An Orcish Incursion==
Linaera's scenario: trepasses -> treSpasses

==Descent into Darkness==

==Eastern Invasion==

==Heir to the Throne==

#: data/campaigns/Heir_To_The_Throne/scenarios/18_A_Choice_Must_Be_Made.cfg:377
msgid ""
"If you want to choose the river path later , move a merman to the right end "
"of the river again."

later , move -> later, move

joe (danish t.)

==Northern Rebirth==

#: data/campaigns/Northern_Rebirth/scenarios/07a_Settling_Disputes.cfg:1069
msgid ""
"I have the power to control many creatures, such as Gryphons, Trolls and "
"Ogres. So while I am with you you they shall be at your command."

I am with you you they -> I am with you they
(double you)

==Sceptre of Fire==

==Son of the Black Eye==

==The Rise of Wesnoth==

==The South Guard==

==Two Brothers==

==Under the Burning Suns==

==Liberty==

==Editor==

==Other (ingame help, ...)==