BuildingScenariosAdvanced - Revision history

Octalot: /* GetText & Translations */ Link to the main GettextForWesnothDevelopers#Marking_up_strings_in_WML

2021-04-23T08:24:42Z

‎GetText & Translations: Link to the main GettextForWesnothDevelopers#Marking_up_strings_in_WML

Pentarctagon at 01:56, 23 January 2021

2021-01-23T01:56:34Z

Namhub at 22:07, 10 October 2018

2018-10-10T22:07:27Z

Vultraz: Removed quick index

2015-04-22T08:52:07Z

Removed quick index

Vultraz: Updated a link

2015-04-22T07:47:00Z

Updated a link

Vultraz: /* Quick Tag Index */

2014-03-16T05:40:32Z

‎Quick Tag Index

Bumbadadabum at 21:25, 23 December 2011

2011-12-23T21:25:38Z

Ceres: /* Using Variables */

2011-03-08T11:40:28Z

‎Using Variables

Ceres: /* Using Variables */

2011-03-08T11:22:07Z

‎Using Variables

Mountain King: /* GetText & Translations */

2010-11-29T20:16:12Z

‎GetText & Translations

@@ Line 192: / Line 192: @@
+  .
-The message key contains the words that will be displayed when Konrad speaks. So this is a translatable string. So it is preceded with an underscore.
+The message key contains the words that will be displayed when Konrad speaks. So this is a translatable string. So it is preceded with an underscore. For more details and examples, see [[GettextForWesnothDevelopers#Marking_up_strings_in_WML|marking up strings in WML]].
 Viliam also said:

← Older revision		Revision as of 01:56, 23 January 2021
Line 1:		Line 1:
	{{BuildingScenariosNav}}		{{BuildingScenariosNav}}
−
−	~~== '''TODO:''' ==~~
−	~~This contained a repetition of what was already inside [[BuildingScenariosIntermediate]]~~
−	~~This should contain:~~
−	* (more) information about making & using preprocessors ([[PreprocessorRef]])
−	* information on guidelines concerning the general layout of a scenario file
−	* advanced filtering
−	* ...
−
−	~~Ayone who feels like writing something, go ahead~~

	== Advanced Events ==		== Advanced Events ==

← Older revision		Revision as of 22:07, 10 October 2018
Line 1:		Line 1:
	{{BuildingScenariosNav}}		{{BuildingScenariosNav}}
−
−	~~= Building scenarios: Advanced =~~

	== '''TODO:''' ==		== '''TODO:''' ==

@@ Line 211: / Line 211: @@
   In some languages placing a word in a sentence requires more than mere string concatenation.
   Some languages use [http://en.wikipedia.org/wiki/Declension declension].
 == See Also ==

@@ Line 219: / Line 219: @@
 :* [[SideWML]] how to describe a side
 :** [[SingleUnitWML]]
-:** [[BuildingScenariosShroudData]]
+:** [[ShroudDataWML]]
 :* [[MapGeneratorWML]] the random map generator
 :* [[TimeWML]] how to describe a day

@@ Line 223: / Line 223: @@
 :* [[TimeWML]] how to describe a day
 :* [[IntroWML]] how to describe the intro screen
-:* [[UtilWML]] a set of preprocessors you can use
+:* [http://www.wesnoth.org/macro-reference.xhtml Macro Reference] a set of useful macro shortcuts you can use
 == See Also ==

← Older revision		Revision as of 21:25, 23 December 2011
Line 144:		Line 144:
	There's one tag you don't know yet, and that's the '''[unstore_unit]''' tag. To explain this tag I'll explain it's counterparts; '''[store_unit]'''. [store_unit] stores a unit, or several units, in a variable you choose. You can then manipulate those variables as described above. However, you will need to apply these changes, and this is done by using the [unstore_unit] tag. For more see [http://www.wesnoth.org/wiki/InternalActionsWML#.5Bevent.5D InternalActions].		There's one tag you don't know yet, and that's the '''[unstore_unit]''' tag. To explain this tag I'll explain it's counterparts; '''[store_unit]'''. [store_unit] stores a unit, or several units, in a variable you choose. You can then manipulate those variables as described above. However, you will need to apply these changes, and this is done by using the [unstore_unit] tag. For more see [http://www.wesnoth.org/wiki/InternalActionsWML#.5Bevent.5D InternalActions].

		+	As of version 1.9, this can also be done much easier:
		+
		+	[event]
		+	#A unit moves onto a tile:
		+	name=moveto
		+	[filter]
		+	x,y=25,26
		+	[/filter]
		+	#modify the unit
		+	[modify_unit]
		+	[filter]
		+	x,y=25,26
		+	[/filter]
		+	hitpoints=$($unit.hitpoints - 5)
		+	status.poisoned=yes
		+	[/modify_unit]
		+	[/event]
		+	#We're finished!
		+
		+	[/scenario]

	You also might have seen that there's sometimes a Dollar sign ($) in front of a variable name. This indicates that the engine will replace the '$your_variable_name' with the exact value of this variable. Example:		You also might have seen that there's sometimes a Dollar sign ($) in front of a variable name. This indicates that the engine will replace the '$your_variable_name' with the exact value of this variable. Example:

← Older revision		Revision as of 11:40, 8 March 2011
Line 142:		Line 142:
	[/scenario]		[/scenario]

−	There's one tag you don't know yet, and that's the '''[unstore_unit]''' tag. To explain this tag I'll explain it's counterparts; '''[store_unit]'''. [store_unit] stores a unit, or several units, in a ~~variables~~ you choose. You can then manipulate those variables as described above. However, you will need to apply these changes, and this is done by using the [unstore_unit] tag. For more see [http://www.wesnoth.org/wiki/InternalActionsWML#.5Bevent.5D InternalActions].	+	There's one tag you don't know yet, and that's the '''[unstore_unit]''' tag. To explain this tag I'll explain it's counterparts; '''[store_unit]'''. [store_unit] stores a unit, or several units, in a variable you choose. You can then manipulate those variables as described above. However, you will need to apply these changes, and this is done by using the [unstore_unit] tag. For more see [http://www.wesnoth.org/wiki/InternalActionsWML#.5Bevent.5D InternalActions].
		+
		+
		+	You also might have seen that there's sometimes a Dollar sign ($) in front of a variable name. This indicates that the engine will replace the '$your_variable_name' with the exact value of this variable. Example:
		+	[set_variable]
		+	name=my_variable # here you refer to the variable itself
		+	value=5
		+	[/set_variable]
		+	[message]
		+	speaker=narrator
		+	message= _ "Your variable's value: $my_variable" # will be showed as "Your variable value: 5"
		+	[/message]

@@ Line 107: / Line 107: @@
   ...
-We will use $unit in an example to show you how you can use all this:
+We will use '''unit''' in an example to show you how you can use all this:
   [scenario]
+  .
@@ Line 132: / Line 132: @@
       #We do this by using the unstore_unit tag like this:
       [unstore_unit]
-        variable=$unit
+        variable=unit
         find_vacant=no
       [/unstore_unit]

@@ Line 166: / Line 166: @@
+  .
   [message]
-    description=Konrad
+    speaker=Konrad
     message= <b>_</b> "I am mighty Konrad! I fought many dummies and now I will fight you!"
   [/message]