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 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 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. Only in >0.8.5
- 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.
See also EventWML
- turn_at the turn to start on (default=1)
- music the music to play during this scenario relative to music/
- objectives (translatable) the text displayed in the Scenario Objectives box in-game.
Now obsolete; see [objectives], InterfaceActionsWML.
- 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.)
- 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.
- 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.