[Wesnoth-wiki-changes] BuildingScenariosSimple

[wiki]

UserAgent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041007 
Debian/1.7.3-5
IP: 64.81.113.168
URI: http://wesnoth.slack.it/?BuildingScenariosSimple
 - - - - -
Index: BuildingScenariosSimple
===================================================================
RCS file: /home/wesnoth/cvsroot/wikiroot/BuildingScenariosSimple,v
retrieving revision 1.19
diff -u -r1.19 BuildingScenariosSimple
--- BuildingScenariosSimple     10 Sep 2004 22:15:29 -0000      1.19
+++ BuildingScenariosSimple     4 Nov 2004 23:43:04 -0000
@@ -1,6 +1,7 @@
-First let me show you a very simple scenario file, then I will
-explain each line. This file is not fully functional, it shows
-you the basics needed to describe what this scenario is all about.
+I will show you a very simple scenario file,
+then explain each line of it.
+This file is not fully functional, but it shows you
+the basics needed to describe what this scenario is all about.
 
  [scenario]
 
@@ -8,7 +9,7 @@
  next_scenario=test-2
 
  name=A Simple Test Scenario
- map=testmap
+ map_data="{campaigns/Test_Campaign/testmap}{~campaigns/Test_Campaign/testmap}"
  turns=20
 
  {DAWN}
@@ -27,28 +28,39 @@
  #Death of Konrad"
 
 
-First, every scenario file must be enclosed in the ||[scenario]|| tag. The 
first
-set of keys in the scenario tag are describing the very basics of this 
scenario.
-The ||id|| is the computer's name for your scenario, and is not displayed 
during
-the game. It is neccesary to put this name in another file, such as a campaign
-tag, as well, in order to actually play the scenario. The type of this file 
indicated how
-you would play this scenario in-game. For example, if your scenario is for a
-campaign, you need to list it as the scenario following another scenario in the
-campaign.
-
-The ||next_scenario|| key lists the scenario that is played after this one is
-won, with units from this scenario available for recall. The value of this key
-should be the same as the value of the ||id|| key in the scenario following it.
-If your scenario is not part of a campaign, putting ||next_scenario=null|| or
-skipping this line will cause the message "You have reached the end of the
-currently playable levels" to be displayed when you win.
+First, every scenario must be enclosed in a tag;
+the ||[scenario]|| tag is used for campaign scenarios.
+The first set of keys in the scenario tag
+describe the very basics of this scenario.
+The ||id|| is the computer's name for your scenario,
+and is not displayed during the game.
+It is neccesary to put this name somewhere else,
+such as a campaign tag, as well, in order to actually play the scenario.
+Where you put the ID for the scenario
+indicates how you would play this scenario in-game.
+For example, if your scenario is for a campaign,
+you need to list it as the scenario following another scenario in the campaign.
+
+The ||next_scenario|| key lists the scenario
+that is played after this one is won,
+with units from this scenario available for recall.
+The value of this key should be the same
+as the value of the ||id|| key in the scenario following it.
+If your scenario is not part of a campaign,
+putting ||next_scenario=null|| or skipping this line
+will cause the "End" screen to be displayed when you win.
 
 The ||name|| key is shown on the introduction screen(which usually contains the
-map graphic) before each scenario is played. It is also the default name for
-saves on the level. The next key, ||map||, is set to a filename. This file must
-be in the //data/maps/ //directory, and must be a valid Wesnoth map file. 
Finally
-the last key in the top set of keys is ||turns||. This sets an event on the
-specified turn causing the player to lose.
+map graphic) before each scenario is played.
+It is also the default name for saves on the level.
+The next key,||map_data||, is a link to the map file.
+Since we may not know exactly where this campaign will be installed we write
+two possible locations of the map data.
+The quotes are necessary because Wesnoth map data takes up multiple lines,
+so quotes are used instead to determine where the data begins and ends.
+The map file must be a valid Wesnoth map file; see BuildingMaps.
+Finally, the last key in the top set of keys is ||turns||.
+This sets an event on the specified turn causing the player to lose.
 
 The next section is a set of IDs. This section tell the game how a day should
 progress. This listing above is the normal day used throughout Wesnoth. If you
@@ -65,8 +77,9 @@
 The ||objectives|| key is nothing more than the text displayed in the Scenario 
Objectives box in-game.
 The ' _ ' facilitates translation using Gettext (see GetText).
 You can type anything you want to within this key.
-Note that having the symbol @ or # at the beginning of a line in this key
-will color the line green or red, respectively.
+Note that having one of the symbols
+'@' and '#' at the beginning of a line in this key
+will color the line green and red, respectively.
 
 Conventions for Objectives: