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 scenarios.
A list of initial scenarios, and how to access them:
- All [multiplayer] scenarios (without allow_new_game=no) are initial scenarios listed in the multiplayer scenario selector screen (accessed by the "multiplayer" button).
- Any [test] scenario is an initial scenario. A 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 followed by an optional scenario ID which defaults to 'test'.) (Version 1.13.8 and later only) It can also be accessed by assigning a hotkey to the "Test Scenario" command in hotkey preferences, then pressing that hotkey at the title screen. This will bring up a list of interactive test scenarios to choose from. (Automated test scenarios used for unit testing are excluded from this list but can still be run from the command-line.)
- The [tutorial] scenario with the attribute id=tutorial is an initial scenario. The tutorial is accessed by clicking on the "tutorial" button.
- (Version 1.15.3 and later only) the tutorial's scenarios now use [scenario] instead of tutorial [tutorial].
- 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. All scenarios must have an id. Can't clash with id used in [multiplayer] tags.
- 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.
- 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.
- map_file: (Version 1.14.3 and later only) path to a file containing Wesnoth map data. This is the recommended way to reference a map in a scenario. The version number 1.14.3 is not a typo; it was included but buggy in earlier 1.14.x releases.
- * (Version 1.15.3 and later only) the file can be found via [binary_path], as documented for [replace_map].
- * (Version 1.15.4 and later only) the file can be a WML file with the contents of a [scenario] tag, which will be merged in to the current scenario. For example, the map file can include named [time_area]s. There's more detail in PR #4999.
- turns: sets an event on turn turns causing the player to lose. Use -1 to have no turn limit. Default value is -1 on wesnoth-1.13 and 100 on wesnoth-1.12. See also EventWML
- turn_at: the turn to start on (default=1)
- Note that none of the regular start-of-turn behavior, including poison damage, healing, income and refreshing unit movement and status, will occur before the start of turn 2. All start-of-turn WML events will still be fired, however.
- 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_start_time=2,3,5,6 (default depends on version and mp/sp, better include this key)
- music: the music file relative to ./music/ to play during the scenario
- [music]: specifies the music tracks to play during this scenario, see MusicListWML.
- defeat_music: specifies a comma-separated list of music tracks which may be chosen to play on defeat. If not provided, the default in GameConfigWML is used instead. May be overridden by endlevel clauses.
- victory_music: specifies a comma-separated list of music tracks which may be chosen to play on victory. If not provided, the default in GameConfigWML is used instead. May be overridden by endlevel clauses.
- theme: the name of the UI theme that should be used when playing this scenario. Valid ids to use can be found in the files in data/themes. Cutscene and Cutscene_Minimal can be useful for dialog only scenarios.
- victory_when_enemies_defeated: when this is set to yes (default), the player wins once all non-allied units with canrecruit=yes (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.) See Also SideWML. When this value is true the following keys can be used:
- 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.
- remove_from_carryover_on_defeat: when this is set to yes (default), for sides who got defeated (according to the side.defeat_condition), carryover will be removed.
- 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.
- do_healing: (Version 1.15.0 and later only) when set to yes, the engine will not skip healing at the first sides turn and will do the healing just like every other turn.
- [story]: describes the intro screen. See IntroWML
- [label]: sets a label
- x, y: location to set label
- text: the label
- [item]: places an item on map. See InterfaceActionsWML.
- [time]: how a day should progress. See TimeWML
- current_time: The time of day slot number (starting from zero) active at scenario start.
- [time_area]: how a day should progress in a given area. Everywhere not specified in a [time_area] tag is affected by the [time] tags in the [scenario] tag
- takes x and y coordinates.
- [time]: how a day should progress in those locations. See TimeWML
- current_time: The time slot number (starting with zero) active at the creation of the area.
- time areas can be used in events, assigned identifiers, and removed at discretion. They also accept complete Standard Location Filters. See DirectActionsWML.
- [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
- TerrainGraphicsWML: Scenarios can define custom terrain rules for the rendering of the map.
- Color palettes
- [lua]: code in Lua. See LuaWML
The [tutorial] tag
The only difference between [tutorial] and [scenario] is the name of the tag. They are not interchangeable because the C++ code looks for the specific tag name.
(Version 1.15.3 and later only) Tutorial scenarios use [scenario], and that's the tag name the C++ code looks for. There is no [tutorial] tag any more.
The [multiplayer] tag
The following keys and subtags are additionally recognized in [multiplayer] scenarios:
- force_lock_settings: provides a default value for SideWML lock attributes and forces the "Use map settings" to be checked and disabled. This is useful if author wants to limit game customization in order to keep the scenario/campaign balanced. Individual options can still be enabled if this key is set to yes. E.g. color selection can be enabled by explicitly setting color_lock=yes in SideWML.
- new_game_title: if provided will be used instead of name for campaign entry points.
- allow_new_game: (default=yes) allow/prevent the scenario to be listed in the game configuration screen. This is intended for multiplayer campaigns with multiple entry points.
- allow_era: a list of era ids. Only the eras with matching ids will be allowed to be played with this scenario.
- disallow_era: a list of era ids. Eras with matching ids will not be allowed to be played with this scenario. Cannot be used in parallel with allow_era.
- ignore_incompatible_era: a list of era ids. The eras with matching ids will be considered compatible with this scenario regardless their dependencies.
- allow_modification: same as allow_era, but for modifications.
- disallow_modification: same as disallow_era, but for modifications. Cannot be used in parallel with allow_modification.
- ignore_incompatible_modification: same as ignore_incompatible_era, but for modifications.
- force_modification: a list of modification ids (id key in [modification]). The specified modifications must be enabled to play this scenario.
- [options]: custom options. See OptionWML for details.
- require_scenario: (Version 1.13.0 and later only) In a multiplayer scenario, this indicates that the scenario file is not enough (you have custom assets like terrain or additional unit art) and other player must download the full add-on not just the scenario WML to join a game. This will also mean that the addon_min_version attribute will control the minimum version number of your add-on which is compatible with this version.
The [test] tag
The following keys and subtags are additionally recognized in [test] scenarios:
- is_unit_test: (Version 1.13.8 and later only) If set to 'yes', this scenario will not appear in the list of test scenarios. The list of test scenarios can be reached from the titlescreen via the Start Test Scenario hotkey. This hotkey is not set by default.
Scenario End Conditions
In this section we will give a more precise explanation of things that can cause a scenario to end.
- At the end of every turn, the turn number will be compared with the turn limit.
- If we pass the limit, the time over event will fire. If turns are not added by WML in response to this event, then the scenario will immediately end in defeat. EventWML#The_.27name.27_Key_.28Mandatory.29
- At the beginning of any turn, and at the end of any user or ai action, the victory conditions will be checked. This will result either in the scenario ending or continuing. The procedure for this is as follows:
- Every side will have its defeat_condition evaluated based on the units it currently has on the board. SideWML
- At this time, villages of defeated sides will be unflagged, and if remove_from_carryover_on_defeat = yes then their carryover will be cleared as well.
- If any two not-defeated sides are enemies, the scenario will continue.
- At this time, the enemies defeated event will fire.
- Furthermore, if victory_when_enemies_defeated=no and there exists a human controlled side, then the scenario will continue.
- The human controlled side may be local or remote, for networked mp play.
- If neither of these conditions is met then the scenario will end.
- In victory or defeat according to whether a local human-controlled side is not defeated.
- Every side will have its defeat_condition evaluated based on the units it currently has on the board. SideWML