The Battle for Wesnoth Wiki - User contributions [en]

ScenarioWML

2007-12-12T19:26:07Z

Dacyn:

{{WML Tags}}
== the toplevel tags [multiplayer], [test], [tutorial], [scenario] ==

The top level tags '''[multiplayer]''', '''[test]''', '''[tutorial]''' and '''[scenario]''' are all formatted the same way.
The difference between these tags is the way that the scenarios they describe are accessed.

The keys ''id'' and ''next_scenario'' affect how scenarios can be accessed.
Whenever a scenario is won, the scenario with id=''next_scenario'' of the same tag type will be played.
Units from the first scenario will be available for recall in the second.

Some scenarios can be played without playing other scenarios first
(in this case there is nothing on the recall list).
These scenarios are called ''initial scenario''s.

A list of initial scenarios, and how to access them:

* All '''[multiplayer]''' scenarios are initial scenarios listed in the multiplayer scenario selector screen (accessed by the "multiplayer" button).

* The '''[test]''' scenario with the attribute '''id=test''' is an initial scenario. This test scenario can be accessed by running the game in test mode. (note: this is NOT the same as debug mode. It can be accessed using -t or --test) You can speed up scenario development a lot by this when used in a clever way: Move a scenario into ~campaigns (so that it will be read even without its campaign being loaded), change it to a [test] scenario, and change the ID to 'test'. Then run Wesnoth in test mode. This saves about a minute for each time you want to test changes to your scenario. However it should not be used for balancing as there will be no recallable units...

* The '''[tutorial]''' scenario with the attribute '''id=tutorial''' is an initial scenario. The tutorial is accessed by clicking on the "tutorial" button.

* Any '''[scenario]''' scenario with an id listed in the value of ''first_scenario'' in a campaign tag (see [[CampaignWML]]) is an initial scenario accessed by selecting that campaign after clicking on the "campaign" button.

== The [scenario] tag ==

The following keys and tags are recognized in '''[scenario]''' tags:

* ''id'' A unique identifier for this scenario.

* ''next_scenario'' The id of the scenario to load when the current one is won. This can be changed dynamically, to build non-linear campaigns.

* ''description'' (translatable) only for multiplayer maps. Will show up as a tooltip when mousing over the minimap in the multiplayer setup screen.

* ''objectives'' (obsolete) sets the objectives for all sides. Useful for giving information about a MP scenario.

* ''name'' (translatable) is shown in several places in the level, including the intro screen. It is also the default name for saves on the level.

* ''map_data'' inputs valid Wesnoth map data. See [[BuildingMaps]] for a description of the Wesnoth map syntax.

* ''turns'' sets an event on turn ''turns'' causing the player to lose. Use ''-1'' to have no turn limit. See also [[EventWML]]

* ''turn_at'' the turn to start on (default=1)

* ''random_start_time'' controls random starting time of day. Possible values are yes and no or list of possible start times; starting from 1 to number of times. for example ''random_starting_time=2,3,5,6'' (default=no) {{DevFeature}}

* ''music'' the music file relative to ''./music/'' to play during the scenario

* '''[music]''' specifies the music tracks to play during this scenario, see [[MusicListWML]].

* ''theme'' the UI theme that should be used when playing this scenario. See [[Using_custom_themes_in_campaigns]]

* ''victory_when_enemies_defeated'' when this is set to 'yes'(default), the player wins once all non-allied units with '''canrecruit=1''' (aka leaders) are killed. (Currently this only controls the win condition for when all enemies are defeated; it does not prevent the player from losing if he has no leader.) When this value is true the following keys can be used:{{DevFeature}}
** ''carryover_percentage'' by default 80% of the gold is carried over to the next scenario, with this key the amount can be changed.
** ''carryover_add'' if true the gold will be added to the starting gold the next scenario, if false the next scenario will start with the amount of the current scenario (after taxes) or the minimum in the next scenario. Default is false.

* ''disallow_recall'' when this is set to 'no'(default), the player is allowed to recall units from previous scenarios.

* ''experience_modifier'' the percentage that required XP to level up (for all units in the scenario) is multiplied by. Default 100. Note that when used in a campaign, weird things (like units being above the required XP to level up) can happen if this value is different for different scenarios.

* '''[story]''' describes the intro screen. See [[IntroWML]]

* '''[label]''' sets a label
** ''x'', ''y'' location to set label
** ''text'' the label

* '''[time]''', '''[illuminated_time]''' how a day should progress. See [[TimeWML]]

* '''[time_area]''' how a day should progress in a given area. Everywhere not specified in a [time_area] tag is affected by the [time] and [illuminated_time] tags in the [scenario] tag
** standard location filter
** '''[time]''', '''[illuminated_time]''' how a day should progress in those locations. See [[TimeWML]]

* '''[side]''' describes one player. See [[SideWML]]

* '''[event]''' describes an event that may be triggered at a certain point of the scenario. See [[EventWML]]

* ''map_generation'' another way to generate a map. The map will be generated randomly
** "default" the default random map generator

* '''[generator]''' if this is present, the map and scenario will be generated randomly. See [[MapGeneratorWML]]

the following key is additionally recognized in '''[multiplayer]''' scenarios:
* ''allow_new_game'' {{DevFeature}} (default=yes) allow/prevent the scenario to be listed in the game creation interface. This is intended for extra scenarios in multiplayer campaigns

== See Also ==

* [[EventWML]]
* [[ReferenceWML]]

[[Category: WML Reference]]

ScenarioWML

2007-12-12T19:23:59Z

Dacyn:

{{WML Tags}}
== the toplevel tags [multiplayer], [test], [tutorial], [scenario] ==

The top level tags '''[multiplayer]''', '''[test]''', '''[tutorial]''' and '''[scenario]''' are all formatted the same way.
The difference between these tags is the way that the scenarios they describe are accessed.

The keys ''id'' and ''next_scenario'' affect how scenarios can be accessed.
Whenever a scenario is won, the scenario with id=''next_scenario'' of the same tag type will be played.
Units from the first scenario will be available for recall in the second.

Some scenarios can be played without playing other scenarios first
(in this case there is nothing on the recall list).
These scenarios are called ''initial scenario''s.

A list of initial scenarios, and how to access them:

* All '''[multiplayer]''' scenarios are initial scenarios listed in the multiplayer scenario selector screen (accessed by the "multiplayer" button).

* The '''[test]''' scenario with the attribute '''id=test''' is an initial scenario. This test scenario can be accessed by running the game in test mode. (note: this is NOT the same as debug mode. It can be accessed using -t or --test) You can speed up scenario development a lot by this when used in a clever way: Move a scenario into ~campaigns (so that it will be read even without its campaign being loaded), change it to a [test] scenario, and change the ID to 'test'. Then run Wesnoth in test mode. This saves about a minute for each time you want to test changes to your scenario. However it should not be used for balancing as there will be no recallable units...

* The '''[tutorial]''' scenario with the attribute '''id=tutorial''' is an initial scenario. The tutorial is accessed by clicking on the "tutorial" button.

* Any '''[scenario]''' scenario with an id listed in the value of ''first_scenario'' in a campaign tag (see [[CampaignWML]]) is an initial scenario accessed by selecting that campaign after clicking on the "campaign" button.

== The [scenario] tag ==

The following keys and tags are recognized in '''[scenario]''' tags:

* ''id'' A unique identifier for this scenario.

* ''next_scenario'' The id of the scenario to load when the current one is won. This can be changed dynamically, to build non-linear campaigns.

* ''description'' (translatable) only for multiplayer maps. Will show up as a tooltip when mousing over the minimap in the multiplayer setup screen.

* ''objectives'' sets the objectives for all sides. Useful for giving information about a MP scenario.

* ''name'' (translatable) is shown in several places in the level, including the intro screen. It is also the default name for saves on the level.

* ''map_data'' inputs valid Wesnoth map data. See [[BuildingMaps]] for a description of the Wesnoth map syntax.

* ''turns'' sets an event on turn ''turns'' causing the player to lose. Use ''-1'' to have no turn limit. See also [[EventWML]]

* ''turn_at'' the turn to start on (default=1)

* ''random_start_time'' controls random starting time of day. Possible values are yes and no or list of possible start times; starting from 1 to number of times. for example ''random_starting_time=2,3,5,6'' (default=no) {{DevFeature}}

* ''music'' the music file relative to ''./music/'' to play during the scenario

* '''[music]''' specifies the music tracks to play during this scenario, see [[MusicListWML]].

* ''theme'' the UI theme that should be used when playing this scenario. See [[Using_custom_themes_in_campaigns]]

* ''victory_when_enemies_defeated'' when this is set to 'yes'(default), the player wins once all non-allied units with '''canrecruit=1''' (aka leaders) are killed. (Currently this only controls the win condition for when all enemies are defeated; it does not prevent the player from losing if he has no leader.) When this value is true the following keys can be used:{{DevFeature}}
** ''carryover_percentage'' by default 80% of the gold is carried over to the next scenario, with this key the amount can be changed.
** ''carryover_add'' if true the gold will be added to the starting gold the next scenario, if false the next scenario will start with the amount of the current scenario (after taxes) or the minimum in the next scenario. Default is false.

* ''disallow_recall'' when this is set to 'no'(default), the player is allowed to recall units from previous scenarios.

* ''experience_modifier'' the percentage that required XP to level up (for all units in the scenario) is multiplied by. Default 100. Note that when used in a campaign, weird things (like units being above the required XP to level up) can happen if this value is different for different scenarios.

* '''[story]''' describes the intro screen. See [[IntroWML]]

* '''[label]''' sets a label
** ''x'', ''y'' location to set label
** ''text'' the label

* '''[time]''', '''[illuminated_time]''' how a day should progress. See [[TimeWML]]

* '''[time_area]''' how a day should progress in a given area. Everywhere not specified in a [time_area] tag is affected by the [time] and [illuminated_time] tags in the [scenario] tag
** standard location filter
** '''[time]''', '''[illuminated_time]''' how a day should progress in those locations. See [[TimeWML]]

* '''[side]''' describes one player. See [[SideWML]]

* '''[event]''' describes an event that may be triggered at a certain point of the scenario. See [[EventWML]]

* ''map_generation'' another way to generate a map. The map will be generated randomly
** "default" the default random map generator

* '''[generator]''' if this is present, the map and scenario will be generated randomly. See [[MapGeneratorWML]]

the following key is additionally recognized in '''[multiplayer]''' scenarios:
* ''allow_new_game'' {{DevFeature}} (default=yes) allow/prevent the scenario to be listed in the game creation interface. This is intended for extra scenarios in multiplayer campaigns

== See Also ==

* [[EventWML]]
* [[ReferenceWML]]

[[Category: WML Reference]]

DirectActionsWML

2006-08-25T18:43:27Z

Dacyn: /* Direct actions */

{{WML Tags}}
== Direct actions ==

Direct actions are actions that have a direct effect on gameplay.

The following tags are actions:
* '''[endlevel]''' ends the scenario.
** ''result'' before the scenario is over, all events with ''name=result'' are triggered. The message ''result_message'' with the heading ''result_heading'' (see [[LanguageWML]]) are displayed. If ''result=victory'', the player progresses to the next level; if ''result=defeat'', the game returns to the main menu. These last two are rarely used: ''result=continue'' behaves identically to ''result=victory'' except the player's gold is not reduced to 80%, and it does not bring up a "Victory" message or the gold changing message (since it doesn't change); ''result=continue_no_save'' works similarly, except the player is not asked whether to save the game, and is taken directly to the next scenario without any messages. Unless ''result=defeat'', the following keys can also be used:
** ''bonus'' whether the player should get bonus gold (maximum possible gold that could have been earned by waiting the level out). The default is bonus=yes.
** ''next_scenario'' (default specified in '''[scenario]''' tag) the ID of the next scenario that should be played. All units that side 1 controls at this point become available for recall in ''next_scenario''.
* '''[unit]''' places a unit on the map. For syntax see [[SingleUnitWML]].
* '''[recall]''' recalls a unit. The unit is recalled free of charge, and is placed near the leader.
** ''standard unit filter'' the first matching unit will be recalled. If no units match this tag is ignored.
** ''x,y'' the unit is placed here instead of next to the leader.
** ''show'' if not "no", display the unit being recalled.
* '''[teleport]''' teleports a unit on map.
** '''[filter]''' (standard unit filter) all units matching the filter will be teleported.
** ''x,y'' the position to teleport to.
* '''[terrain_mask]''' changes the terrain on the map. See [[TerrainMaskWML]].
* '''[terrain]''' changes the terrain on the map.
** ''letter'' the character of the terrain to use. See [[TerrainLettersWML]] to see what letter a type of terrain uses.
** standard location filter- the area to change the terrain of.
* '''[gold]''' give one side gold.
** ''amount'' the amount of gold to give.
** ''side'' (default=1) the number of the side to give the gold to.
* '''[unstore_unit]''' creates a unit from a game variable, and activates it on the playing field. This must be a specific variable describing a unit, and may not be an array -- to unstore an entire array, iterate over it. The variable is not cleared. See also [store_unit], [while] and [clear_variable] in [[InternalActionsWML]].
** ''variable'' the name of the variable.
** ''find_vacant'' whether the unit should be placed on the nearest vacant tile to its specified location. If this is set to 'no'(default), then any unit on the same tile as the unit being unstored will be destroyed.
** ''text'' {{DevFeature}} (translatable) floating text to display above the unit, such as a damage amount
** ''red'', ''green'', ''blue'' {{DevFeature}} (default=0,0,0) the color to display the text in. Values vary from 0-255. You may find it convenient to use the {COLOR_HARM} or {COLOR_HEAL} macro instead.
* '''[allow_recruit]''' allows a side to recruit units it couldn't previously recruit.
** ''type'' the types of units that the side can now recruit.
** ''side'' (default=1) the number of the side that is being allowed to recruit the units.
* '''[disallow_recruit]''' prevents a side from recruiting units it could previously recruit.
** ''type'' the types of units that the side can no longer recruit.
** ''side'' (default=1) the number of the side that may no longer recruit the units.
* '''[set_recruit]''' sets the units a side can recruit.
** ''recruit'' the types of units that the side can now recruit.
** ''side'' (default=1) the number of the side that is having its recruitment set.
* '''[modify_side]''' modifies some details of a given side in the middle of a scenario. '''The following listed properties are the only properties that [modify_side] can affect!'''
** ''side'' (default=1) the number of the side that is to be changed.
** ''income'' the income given at the begining of each turn.
** ''team_name'' the team in which the side plays the scenario.
** ''gold'' the amount of gold the side owns.
* '''[modify_turns]''' {{DevFeature}} modifies the turn limit in the middle of a scenario.
** ''value'' the new turn limit.
** ''add'' if used instead of ''value'', specifies the number of turns to add to the current limit (can be negative).
* '''[capture_village]''' changes the ownership of a village.
** ''side'' the side that takes control of the village. If not given, the village will become neutral.
** ''x, y'' the location of the village.
* '''[kill]''' Removes all units (including units in a recall list) that match the filter from the game.
** standard unit filter
** ''animate'' if 'yes', displays the unit dying (fading away).
** ''fire_event'' if 'yes', triggers any appropriate 'die' events (See [[EventWML]]).
* '''[unstone]''' Unstones all units that match the filter.
** '''[filter]''' (standard unit filter) all units matching the filter will be unstoned. If no unit matches the filter, then nothing happens (probably). If absent, all units on the map are unstoned.
* '''[object]''' gives some unit an object and removes all items on the tile the unit is on.
** ''id'' when the object is picked up, a flag is set for ''id''. The object cannot be picked up if a flag for ''id'' has been set. This means that any object with an id can only be used once, even if first_time_only=no is set for the event. This restriction is per level. In a campaign objects with the same id can be assigned once per level.
** '''[effect]''' one or more effect elements may be listed. See [[EffectWML]] for a description of [effect].
** ''duration'' if 'level', effects only last until the end of the level (note : 'level' is the scenario, so this doesn't mean it last until the unit levels-up).
** '''[filter]''' (standard unit filter) the first unit found that matches the filter will be given the object. If no unit matches the filter, then a message is displayed and the object is not removed.
** '''[then]''' a subtag that lets you execute actions if the filter conditions are met. The most common action that should be inside here is a '''[removeitem]''' tag, but you could probably put any tags that otherwise work in a [then] tag.
** ''silent'' whether or not messages should be suppressed. Default is "no".
** ''image'' the displayed image of the object.
** ''name'' (translatable) displayed as a caption of the image.
** ''description'' (translatable) displayed as a message of the image.
** ''cannot_use_message'' (translatable) displayed instead of '''description''' if no unit passes the filter test.
** Currently the object action is only supposed to be called by moveto events. If you try to call it from other events you may have problems.
** If you do not supply a filter, the object action will be applied to a unit at the location of the moveto event. Currently this isn't recommended as it is not clear that this will continue working this way. Instead it is better to explicitly include a location filter.
** The object action does not act on units in the recall list. There is a feature request in to allow this, but it is not clear whether or not it will be accepted.
* '''[remove_shroud]''' removes some shroud from the map for a certain side (only relevant for sides that have shroud=yes).
** ''side'' (default=1) the side for which to remove shroud.
** standard location filter- the range of tiles for which shroud should be removed.
* '''[place_shroud]''' places some shroud on the map for a certain side (only relevant for sides that have shroud=yes).
** ''side'' (default=1) the side for which to place shroud.
** standard location filter- the range of tiles on which shroud should be placed.
* '''[allow_undo]''' allows the player to undo the event that this tag is inside. Has an effect only inside moveto events. If the move is undone, only the position of the unit will be restored; any altered variables or changes to the game will remain changed after the move is undone. Therefore, it is advised that you do not use '''[allow_undo]''' before or after usage of other actions from [[DirectActionsWML]]. If you modify a variable(i.e. [[InternalActionsWML]]), set it back before using '''[allow_undo]'''. However, you can check a conditional, and only allow undo if you do not use the actions.

== See Also ==

* [[InternalActionsWML]]
* [[InterfaceActionsWML]]
* [[EventWML]]
* [[ReferenceWML]]

[[Category: WML Reference]]

FAQ

2006-08-17T17:02:17Z

Dacyn: /* There's too much luck in this game! */

=Frequently Asked Questions=

== General ==

===What is Battle for Wesnoth?===
Battle for Wesnoth is a fantasy turn-based strategy game.

===What license is the game distributed under?===
The project is distributed under the [http://www.fsf.org/copyleft/gpl.html GPL]. All contributors retain copyright on the portions of the project that they contribute.

===How to get informed about new releases?===
Subscribe to new releases at [http://freshmeat.net/subscribe/38720/?url=%2Fprojects%2Fwesnoth%2F Freshmeat].

===A new version is out, but where is the download for [Windows, Mac OS, etc.]?===
The downloads are NOT part of the official project. The BFW team only releases the game's source code. Binary executables or applications are always contributed by community volunteers. If not for these volunteers, there would never be any downloads for us to enjoy. The volunteers compile the game and upload it on their own time, and sometimes they cannot do this in a timely fashion (or at all, at times) Although there are usual packagers designated for each operating system, there are times when other members of the community are asked to step in and contribute when the usual people cannot.

Every time a new version is released, the usual volunteers are always notified by the project leaders. '''Please refrain from making forum posts asking where your download is''' because it doesn't help anything - the packagers already know, and they will get to it as soon as they can. In the past, the Windows and Mac communities have come together to produce home-grown unofficial builds for the community to use, and the renewed interest in community and learning how to compile is generally a good thing.

===Why doesn't Wesnoth have my favorite feature?===
Because we are building this game for ourselves, to suit our own preferences. We're not building the game for you, in large part because this is our hobby, not our job; whether you like it or not is immaterial to us.
You may wonder, then, what the point is of soliciting ideas, as we do on the forum. We, the developers, have certainly come up with many good ideas on our own, but our players often do as well, and generally ones we don't think of ourselves. If a player comes up with an idea we like, we might implement it. Not because they asked for it, but because of its own merits as an addition to our game.

The beautiful thing about the license our game is distributed under, as compared to closed-source, commercial games, is that if you want that feature badly enough, you can take the code and art of our game and modify it yourself; you are free to re-use any work in Wesnoth, as long as you follow the rules of the [http://www.fsf.org/copyleft/gpl.html GPL]. From this, you can build a game exactly the way that you like. Just don't expect us to build that game for you. Building this game is our hobby, not our profession, and you did not pay us to make it; rather, we are the ones who have paid for it, in time and labor.

===Do you want help making this game? How can I help?===
Yes, we want your help. Whether you're a programmer, artist, musician, writer, translator, level designer, playtester, or just have some great suggestions, you're welcome to contribute. How? You can:
* join the [http://www.wesnoth.org/wiki/Project Project]
* share your point of view at the [http://www.wesnoth.org/forum/ Forum]
* talk with us on [irc://irc.wesnoth.org/wesnoth IRC]
* report bugs you find at [[ReportingBugs]]
* update the wiki
* play against us via the Multiplayer menu
* vote for Wesnoth at your favorite gaming web site
* Spread the word!

=== What are the system requirements? ===

We are not completely certain, but an x86 running at 333MHz with 128MB RAM should be adequate. Slower machines will have trouble scrolling large maps or processing AI turns with many units. See the [http://www.wesnoth.org/forum/viewtopic.php?t=7384 forum thread] about minimum and recommended system requirements.

=== I'm bored; how do I speed the game up? ===

There are several preferences you can change to shorten the time that the AI takes to make its moves. "Accelerated Speed" will make units move and fight faster. "Skip AI Moves" will not show the AI's units moving from hex to hex. Finally, you can turn off all combat animations via the "Show Combat" option on the Advanced tab.

=== My computer is too slow; how do I speed the game up? ===

First, turn off the music and sound effects. Turning off the color cursors will make your cursor respond faster. If scrolling the map is slow, run the game in "Full Screen" mode, not in a window. Turn off combat animations via the "Show Combat" option on the Advanced tab. You can try turning off halos and combat results, but this might make gameplay more difficult.

== Gameplay and Controls ==

=== How do I learn to play? ===

If you just want to jump right in, start the game and play the tutorial. If you like reading documentation, see [[WesnothManual]], which is also distributed as a PDF file. At any time while playing, you can select help from the menu button (or hit F1). The online help is quite extensive and provides information on terrains, weapons, traits, abilities, units and a good overview of how to play.

=== My unit leveled up but didn't improve. What happened? ===

This is called "After Maximum Level Advancement" or AMLA for short. While most level 0, 1, and 2 units can advance, some cannot. However, some level 3 units can advance to level 4, or even 5. You can see whether a unit can advance further by right clicking and selecting "description."

After a unit reaches the highest level it can get, every time it gains 100 experience it gains 3 hitpoints. It does not heal when this happens. This is a minor bonus so that experience gained by maxed out units is not altogether wasted. It is generally better to give experience to lower level units, rather than continue to advanced units that have reached their maximum level.

If the unit in question is the Necrophage, this is not a bug. The Necrophage eats the corpses of the dead, allowing it to periodically completely heal. Leveling into itself is how this is carried out.

=== I tried to trap an enemy with several weak units, but it still escaped. What happened? ===

Most units exert a zone of control (or ZOC). IF an enemy moves into one of the six adjacent hexes, the zone of control will prevent it from moving any farther. However some weak units are level 0, meaning they are so weak that they do not have a ZOC. You can still surround an enemy unit entirely with level 0 units to keep it from escaping, but if there is any gap in your ranks, it could escape.

Also, some units have the "skirmish" ability, which allows them to ignore ZOCs.

=== How can I see where an enemy unit can move next turn? ===

During you turn you can click on an enemy unit. Wesnoth will highlight all the hexes the unit can move to in the next turn. This is useful when trying to arrange your units to block an enemy's movement.

=== There's too much luck in this game! ===

Sooner or later, you will become frustrated when your archmage with four 70% attacks misses all four times. This does not mean that the AI is cheating or the random number generator is futzed. It means you are noticing random negative events more than positive ones. During the development of the game, many mathematicians have done sophisticated statistical analysis of the combat system. Likewise, programmers have examined the random number generator. No flaws have been found, so streaks of "bad" and "good" luck should just be accepted as part of having randomness in Wesnoth.

Since Wesnoth is GPLed, it is possible that a new development team will someday "fork" the source and produce a version more like Heroes of Might & Magic, with less or no randomness. Until then, don't charge with your horsemen against troll rocklobbers at night...

=== The (random unit) is overpowered/underpowered! ===

The development team has spent years tweaking the units in the game. Each unit has had its gold cost, attack types, combat damage, defensive values, resistances, upgrade paths, and other stats carefully scrutinized and loudly discussed in the forum. However, the game code and the units were being modified right up until the 1.0 release, so some unbalanced units may have slipped through.

If you have evidence to back up your claim, search the forum for past discussions about this unit, and then try posting.

=== The (random scenario) is too hard/easy! ===

See above answer about random units.

=== What do the different difficulty levels do? ===

That depends on the scenario. Usually, the opponent will get more money and be able to recruit higher-level units at higher difficulty levels, and you will have fewer turns available.

== Maps, Scenarios and Campaigns ==

=== How do I beat scenario _______ ? ===

If you are stuck on a scenario in a campaign, you'll probably find a walkthrough at [[MainlineScenarios]]. Or check out the "Strategies and Tips" forum at http://www.wesnoth.org/forum/viewforum.php?f=3

=== Are there any tools to help me create maps and scenarios? ===
Yes, there is a tool called wesnoth_editor. It is a normal map-editor that should be a good help for creating the plain maps. For creating the scenarios there already is a scenario-editor included in the mac build. But this editor is rather outdated and it exists only for MacOS X. At the moment some community members are working on creating a nice and working scenario editor. You can have a look at the [http://www.wesnoth.org/forum/viewtopic.php?t=6925 forum post] about this tool. You will also find more info at [[CampGen]].

=== How do I download user campaigns? ===
Choose "Campaigns" in the main Wesnoth menu. Then scroll down to the bottom and choose "Get More Campaigns..." or since 1.1.5 there is a "Get add-ons" button in the main menu. This connects you to the campaign server. In the campaign server you can view a list of all available campaigns and download them, as well as posting or deleting your own campaigns.

If you are behind a firewall you may not be able to connect to the campaign server. In this case try to download the campaign directly from the campaign server through the web interface at http://campaigns.wesnoth.org. If you know how to change your firewall settings, then you should open port 15003 (version 1.1.1 and up) or port 15002 (versions 1.1.0 and lower). For added security, you can restrict traffic over those ports to the campaign server's IP address (currently 129.241.104.165).

=== I already created a campaign and published it on the campaign server. How can I get translations for the campaign? ===
Just have a look at [[WesCamp]]. This project is the easiest way to get translations for your campaign. All the info you need you can find at [[WesCamp]].

===How do I place an object or unit on my map with the map editor?===
You can't. You need to make a multiplayer scenario file. There are more details on the [[BuildingMaps|maps]] page.

== Multiplayer ==

===How do i connect to a multiplayer server, when i sit behind a restrictive Firewall?===
You have to open port 14999 to play multiplayer games over the internet. For added security, you can restrict access to the server's IP address (currently 84.207.24.9 for the official server).

===How to find players for multiplayer game?===
Hang around for a while on multiplayer servers and you might find someone to play with. If you observe other people playing you will get informed when someone joins the servers. Maybe you find someone willing to play in the irc channel dedicated to mp: #wesnoth-mp at irc.freenode.net.
You can also join #wesnoth at irc.freenode.net.

===How can I make my computer into a dedicated Wesnoth server?===

To setup a dedicated Wesnoth server, you have to compile the game with the "--enable-server" flag, and after you install, simply run wesnothd from the console. This will start the server, listening on TCP port 15000. To compile the server only you can use the flags "--disable-game --enable server". If you aren't using a linux or mac operating system, there are a few ways you can compile on Windows...here is one way http://www.wesnoth.org/wiki/CompilingWesnoth/CrossCompiling

===Which versions of Wesnoth can play together?===

I'm on a MAC, and my friends are on XP. I would like to play together with them. Is this currently possible?

YES! All you need is to have the same version number.

For a list of Mac-XP-compatible games (including BfW) see: http://www.insidemacgames.com/forum/index.php?showtopic=21818

== Translations ==

===I selected an asian translation and am not able to see the letters correctly. What happened?===

Since the size of the necessary fonts is too large, you'll need to download them separately (if you don't already have them). After that, simply copy the font to the '''fonts/''' directory in your wesnoth installation.
* Chinese font: [ftp://cle.linux.org.tw/pub/fonts/ttf/unicode/Arphic/gkai00mp.ttf gkai00mp.ttf]
* Japanese font: [http://cvs.sourceforge.jp/cgi-bin/viewcvs.cgi/sqs-xml/sqs-font/sazanami-gothic.ttf sazanami-gothic.ttf]

If you have futher questions have a look at [[WesnothAsianLanguages|this]] page.

== Other Questions You Have ==

The best way to get answers to less-frequently asked questions is by visiting the [http://www.wesnoth.org/forum BFW forum]. There are plenty of people willing to help. Make sure you read ALL of the forum sticky notes and announcements before posting.

SideWML

2006-05-15T18:39:08Z

Dacyn:

{{WML Tags}}
== the [side] tag ==

The [side] tag is used to describe a side in a particular scenario.

The following keys are recognized:

* ''description'' the sides non translateable name.

* ''user_description'' the sides translateable name.

* ''persistent'' whether the side exists in any other scenarios. If '1'(yes), then ''save_id''(see below) becomes active for this side. Default '0'(no); when '''controller=human''', this is always '1'.

* ''save_id'' default ''description'' if available, 'Unknown' otherwise. The ID of the side with respect to the previous and next scenarios. Used to carry over the side's recall list (including the side's leader), recruitment list, and starting gold from scenario to scenario. Also used for the side's displayed name in the victory gold-calculation dialog.

* ''side'' a digit. The leader of this side is placed on the tile represented by this digit (see [[BuildingMaps]]). When defining sides, they must be defined in order since the side number is checked against the number of sides seen so far.

* ''controller'' how moves for this side should be inputted.
** 'ai' the Wesnoth AI makes this side's moves. This is the default setting.
** 'human' a player controls this side's moves.
** 'null' the side doesn't get a turn to move and doesn't have a leader generated from the contents of the [side] tag. (It still can get units from [unit] tags in the [side] tag.)

* ''allow_player'' if equal to 'no', then the game creation will not allow this player to be modified. {{DevFeature}}

* ''team_name'' a non translatable string representing the teams description. Sides with the same team_name are allied. Default ''side''.

* ''user_team_name'' a translatable string representing the teams description. This has no effect on alliances. Default ''team_name''.

* ''colour'' if you want side 4 to be the same colour as side 2 normally is, put colour=2.
** The default list of numbers and corresponding colors can be found in data/team_colors.cfg.

* ''flag'' a custom flag animation to use instead of the default one to mark captured villages.
** Example animation that has three frames and loops every 750ms: ''flag=misc/myflag-1.png:250,misc/myflag-2.png:250,misc/myflag-3.png:250''

* ''recruit'' a list of unit types. At the beginning of the scenario, the side gains recruitment of these units.

* ''gold'' the starting gold for this side. Default 100. (If gold is carried over from a previous scenario, this value is the minimum starting gold.)

* ''income'' the base income for this side, default 0. This is added to ''base_income'', '''[game_config]''' to determine the side's base income. (see [[GameConfigWML]]).

* ''fog'' if 'yes', this side cannot see any tiles it is not within vision of, except at the start.

* ''shroud'' if 'yes', this side cannot see any tiles it has not moved within sight of.

* ''shroud_data'' describes the area which this team has de-shrouded.

* ''village_gold'' the amount of gold given to this side per village it controls per turn. Default specified in ''village_gold'', '''[game_config]''' ([[GameConfigWML]]).

* ''share_maps'' whether sides allied with this side see all terrains that this side sees, if they are on shroud.

* ''share_view'' whether sides allied with this side see the units that this side sees, if they are on FoW (fog).

* ''name'', ''id'', ''leader'' not used; see [[EraWML]].

* ''music'' music to play for this player. Default specified in [scenario] (see [[ScenarioWML]]).

* '''[ai]''' if '''controller=ai''', gives parameters to the AI. See [[AiWML]].

* '''[village]''' describes a village the side begins in control of.
** ''x'', ''y'' the location of the village.

* '''[unit]''' describes a unit which begins on the side. See [[SingleUnitWML]]. If the side has a recall list and the unit is not given a location, it will start on the recall list. Note that the ''side'' attribute under '''[unit]''' will be ignored, as the side will come from the ''side'' attribute of '''[side]'''.

* ''no_leader'' if "no" (default), then keys describing a unit which will begin on the side's keep will be described in the remainder of the '''[side]''' tag, See [[SingleUnitWML]]. Note that if the keys ''x'', ''y'' are included, the leader will begin there regardless of keep location. If this side has a recall list from a previous level, then the recall list will be searched for a leader (using canrecruit) and if one is found it will be used instead of the one described in the '''[side]''' tag.

== See Also ==
* [[EraWML]]
* [[ScenarioWML]]
* [[ReferenceWML]]

[[Category: WML Reference]]

SideWML

2006-05-15T18:38:38Z

Dacyn:

{{WML Tags}}
== the [side] tag ==

The [side] tag is used to describe a side in a particular scenario.

The following keys are recognized:

* ''description'' the sides non translateable name.

* ''user_description'' the sides translateable name.

* ''persistent'' whether the side exists in any other scenarios.
If '1'(yes), then ''save_id''(see below) becomes active for this side.
Default '0'(no); when '''controller=human''', this is always '1'.

* ''save_id'' default ''description'' if available, 'Unknown' otherwise. The ID of the side with respect to the previous and next scenarios. Used to carry over the side's recall list (including the side's leader), recruitment list, and starting gold from scenario to scenario. Also used for the side's displayed name in the victory gold-calculation dialog.

* ''side'' a digit. The leader of this side is placed on the tile represented by this digit (see [[BuildingMaps]]). When defining sides, they must be defined in order since the side number is checked against the number of sides seen so far.

* ''controller'' how moves for this side should be inputted.
** 'ai' the Wesnoth AI makes this side's moves. This is the default setting.
** 'human' a player controls this side's moves.
** 'null' the side doesn't get a turn to move and doesn't have a leader generated from the contents of the [side] tag. (It still can get units from [unit] tags in the [side] tag.)

* ''allow_player'' if equal to 'no', then the game creation will not allow this player to be modified. {{DevFeature}}

* ''team_name'' a non translatable string representing the teams description. Sides with the same team_name are allied. Default ''side''.

* ''user_team_name'' a translatable string representing the teams description. This has no effect on alliances. Default ''team_name''.

* ''colour'' if you want side 4 to be the same colour as side 2 normally is, put colour=2.
** The default list of numbers and corresponding colors can be found in data/team_colors.cfg.

* ''flag'' a custom flag animation to use instead of the default one to mark captured villages.
** Example animation that has three frames and loops every 750ms: ''flag=misc/myflag-1.png:250,misc/myflag-2.png:250,misc/myflag-3.png:250''

* ''recruit'' a list of unit types. At the beginning of the scenario, the side gains recruitment of these units.

* ''gold'' the starting gold for this side. Default 100. (If gold is carried over from a previous scenario, this value is the minimum starting gold.)

* ''income'' the base income for this side, default 0. This is added to ''base_income'', '''[game_config]''' to determine the side's base income. (see [[GameConfigWML]]).

* ''fog'' if 'yes', this side cannot see any tiles it is not within vision of, except at the start.

* ''shroud'' if 'yes', this side cannot see any tiles it has not moved within sight of.

* ''shroud_data'' describes the area which this team has de-shrouded.

* ''village_gold'' the amount of gold given to this side per village it controls per turn. Default specified in ''village_gold'', '''[game_config]''' ([[GameConfigWML]]).

* ''share_maps'' whether sides allied with this side see all terrains that this side sees, if they are on shroud.

* ''share_view'' whether sides allied with this side see the units that this side sees, if they are on FoW (fog).

* ''name'', ''id'', ''leader'' not used; see [[EraWML]].

* ''music'' music to play for this player. Default specified in [scenario] (see [[ScenarioWML]]).

* '''[ai]''' if '''controller=ai''', gives parameters to the AI. See [[AiWML]].

* '''[village]''' describes a village the side begins in control of.
** ''x'', ''y'' the location of the village.

* '''[unit]''' describes a unit which begins on the side. See [[SingleUnitWML]]. If the side has a recall list and the unit is not given a location, it will start on the recall list. Note that the ''side'' attribute under '''[unit]''' will be ignored, as the side will come from the ''side'' attribute of '''[side]'''.

* ''no_leader'' if "no" (default), then keys describing a unit which will begin on the side's keep will be described in the remainder of the '''[side]''' tag, See [[SingleUnitWML]]. Note that if the keys ''x'', ''y'' are included, the leader will begin there regardless of keep location. If this side has a recall list from a previous level, then the recall list will be searched for a leader (using canrecruit) and if one is found it will be used instead of the one described in the '''[side]''' tag.

== See Also ==
* [[EraWML]]
* [[ScenarioWML]]
* [[ReferenceWML]]

[[Category: WML Reference]]

Wesnoth Acronyms and Slang

2005-12-17T15:52:45Z

Dacyn: /* Forum Language */

Use the following list to demystify the various (mostly wesnoth specific) acronyms you may run into at the forum.



== Official Campaigns ==

*EI - "The Eastern Invasion" (campaign name)
*HttT - "Heir to the Throne" (campaign name)
** BoP - "Bay of Pearls" (scenario in "Heir to the Throne" campaign)
** DD - "Dwarven Doors" (scenario in "Heir to the Throne" campaign)
** HotNE - "Home of the North Elves" (scenario in "Heir to the Throne" campaign)
** IotD - "Isle of the Damned" (scenario in "Heir to the Throne" campaign)
** RtW - "Return to Wesnoth" (scenario in "Heir to the Throne" campaign)
** SoE - "Siege of Elensefar" (scenario in "Heir to the Throne" campaign)
** SoF - "Scepter of Fire" (scenario in "Heir to the Throne" campaign)
** TotC - "Test of the Clans" (scenario in "Heir to the Throne" campaign)
** VoD - "Valley of Death" (scenario in "Heir to the Throne" campaign)
*SotBE - "Son of the Black Eye" (campaign name)
*TDH - "The Dark Hordes" (campaign name)
*TRoW - "The Rise of Wesnoth" (campaign name)

== Unofficial Campaigns ==

*FtF - "Flight to Freedom" (campaign name)
*LOW - "Legends of Wesmere" (campaign name)
*SE - "Saving Elensefar" (campaign name)
*SG - "The South Guard" (campaign name)
*SoF - "Scepter of Fire" (campaign name)
*UtBS - "Under the Burning Suns" (campaign name)

== Forum Language ==

*AMLA - After Maximum Level Advancement
*BfW - Battle for Wesnoth (the name of the game)
*BWH - Been suggested before. We think it's a good idea. Hope to add it eventually.
*CtH - Chance to Hit (also C2H)
*CtbH - Chance to be Hit (also C2bH)
*CtK - Chance to Kill (also C2K)
*CtbK - Chance to be Killed (also C2bK)
*CVS - Old term for up-to-date Wesnoth: [[WesnothCVS]]
*EP - Elvish Pillager, moderator and great man :) at forum
*FoW - Fog of War (i.e. fog)
*FFA - Free For All (playing a map with >2 players without teams)
*HAPMA - Hexes Are Possibly Miles Across - http://www.wesnoth.org/forum/viewtopic.php?t=1882
*HP - Hit points
*IIRWIIR - It Is Ready When It Is Ready
*KISS - Keep It Simple, Stupid: Applies to coding, not game rules (although indirectly it does): see [[WesnothPhilosophy]]
*MP - Movement points
*MP - Multiplayer
*MoL - Mage of Light
*OAB - Options are Bad; In reference to gameplay, not user interface options. mostly used by Turin. See also [[FrequentlyProposedIdeas]] (idea #1)
*OFWRA - Old Flame War Revival Alert
*OT - Off Topic: can refer to either the forum (http://www.wesnoth.org/forum/viewforum.php?f=11) or spam
*RIPLIB - Reduction In Power when Leveling Is Bad: means that when a unit upgrades, at least one of its options should be strictly superior to the original unit. [http://www.wesnoth.org/forum/viewtopic.php?t=1423 Reference 1] / [http://www.wesnoth.org/forum/viewtopic.php?t=7205 Reference 2]
*RPG - Role Playing Game - Wesnoth's experience system: http://www.wesnoth.org/forum/viewtopic.php?t=4385
*RTFM - Read The Manual
*RTS - Real Time Strategy Game - not Wesnoth
*SP - Single Player (Campaigns)
*SVN - Term for up-to-date Wesnoth [[WesnothSVN]]
*TBS - Turn Based Strategy Game - Wesnoth
*TWP - The Wesnoth Philosophy: [[WesnothPhilosophy]]
*WC - Walking Corpses
*WINR - Wesnoth Is Not Realistic
*WIN_ - Wesnoth Is Not... (Warcraft, Lord of the Rings, medieval Europe, an RPG, etc.)
*WML - Wesnoth Markup Language: [[ReferenceWML]]
*XP - Experience
*ZOC - Zone of Control

== General Acronyms ==

*AFAICT - As Far As I Can Tell(A statement with a disclaimer on truthfulness)
*AFAIK - As Far As I Know (A statement with a disclaimer on truthfulness)
*BTW - By the Way (A statement with a disclaimer on relevance)
*OtOH - On the Other Hand (A contrast)
*EV - Expected Value
*IIRC - If I Recall Correctly (A statement with a disclaimer on truthfulness)
*IMHO - In My Humble Opinion (A statement with a disclaimer on objectiveness)
*IMO - In My Opinion (A statement with a disclaimer on objectiveness)
*NYSPOS - No, you stupid piece of **** (An impolite refutation hidden in an acronym)

== See Also ==

* http://www.wesnoth.org/forum/viewtopic.php?t=1786 for links to general-acronym search engines.