Changes for page Mission Director Guide

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -84,6 +84,7 @@
84	84	* **Waiting**: Either this is a root cue, or the parent has become active. The cue is checking its conditions and will become active when they are met.
85	85	* **Active**: The cue is about to perform the actions. Child cues have entered the waiting state.
86	86
	87	+
87	87	* **Complete**: The cue has finished performing its actions.
88	88	* **Cancelled**: The cue has been cancelled. This state cannot normally be reached but only if a cue actively cancels itself or another cue. No condition checks or actions are performed in this cue or any sub-(sub-)cue.
89	89
...	...	@@ -155,6 +155,7 @@
155	155
156	156	* Use //onfail// if the conditions should be checked only once. The possible attribute values are "//cancel//" and "//complete//". If the conditions are met, the cue will activate and perform the cue actions. Otherwise it's a failure and the cue will be cancelled or completed, based on the onfail attribute. Typically //onfail="cancel"// is used to prevent any further action. //onfail="complete"// can be used to continue with the sub-cues even in case of failure (but skipping the current cue actions).
157	157
	159	+
158	158	* With //checkinterval//, you can specify a constant time interval between condition checks. The conditions will be checked regularly forever until they are met, unless the cue's state is changed explicitly by an external event.
159	159
160	160	Additionally, you can use the attribute **checktime** to set the time of the first condition check (also possible in combination with //onfail//). The //checktime// can be an expression with variables and is evaluated when the cue is enabled (when the condition checks would normally start ΓÇô for root cues that happens at game start, otherwise after the parent cue becomes active).
...	...	@@ -575,6 +575,7 @@
575	575	\\{{code language="xml"}}'T'{{/code}}|Conditional operator ("inline if")
576	576	)))
577	577
	580	+
578	578	=== Operator precedence rules ===
579	579
580	580	You can group sub-expressions using parentheses, but if you don't, the following order of operations is applied, so that 5-1+2*3 == 10 as you would expect. The order is the same as in the table above, but there are operators with the same precedence - these are applied from left to right.
...	...	@@ -589,6 +589,7 @@
589	589	* or
590	590	* if/then/else (lowest precedence)
591	591
	595	+
592	592	=== Type conversion ===
593	593
594	594	When a binary arithmetic operator is used on numbers of different types, they will be converted to a suitable output type. The resulting type depends on whether a unit data type is involved (types that are not plain integers or floats). The following cases may occur:
...	...	@@ -630,6 +630,7 @@
630	630	* Unlike != and ==, the comparison operators <, <=, >, >= are only supported **for numeric values**, **difficulty levels**, and **attention levels**. Comparing other non-numeric values will result in an error and an undefined result.
631	631	* <, <=, >, >= cannot be used in XML directly, so lt, le, gt, ge are provided as alternatives. In some cases you won't have to use them, though - using [[range checks>>MediaWiki.NULL]] with additional XML attributes can be more readable.
632	632
	637	+
633	633	(% id="categorybroken_macroanchorstrings-and-formatting" %)== Strings and formatting==
634	634
635	635
...	...	@@ -693,16 +693,19 @@
693	693	* null cannot be used as table key (but the number 0 is valid)
694	694	* Lists, tables, groups and buildplans cannot be used as table keys
695	695
	701	+
696	696	These restrictions only apply to the keys, there are no restrictions for values that you assign to them. For example:
697	697
698	698	* {{code language="xml"}}table[]{{/code}} ⟹ creates an empty table
699	699	* {{code language="xml"}}table[{0} = null]{{/code}} ⟹ creates a table that maps the number 0 to null
700	700
	707	+
701	701	* {{code language="xml"}}table[{'$foo'} = 'bar']{{/code}} ⟹ a table that maps the string '$foo' to the string 'bar'
702	702	* {{code language="xml"}}table[$foo = 'bar']{{/code}} ⟹ exactly the same, just a shorter notation for string keys
703	703	* {{code language="xml"}}table[foo = 'bar']{{/code}} ⟹ error, 'foo' does not start with a '$'
704	704	* {{code language="xml"}}table[{1} = [], {2} = table[]] {{/code}} ⟹ a table that maps 1 to an empty list and 2 to an empty table
705	705
	713	+
706	706	Just like lists, tables are stored as references, so it's possible that multiple variables reference the same table (see above).
707	707
708	708	== Value properties ==
...	...	@@ -727,6 +727,7 @@
727	727	* {{code language="xml"}}[].{'count'}{{/code}} ⟹ 0
728	728	* {{code language="xml"}}table[{21} = 42].{21}{{/code}} ⟹ 42
729	729
	738	+
730	730	In most cases the property key is a fixed string, like "name" or "class". You can write this like above:
731	731
732	732	* {{code language="xml"}}[42].{'count'}{{/code}}
...	...	@@ -734,6 +734,7 @@
734	734	* {{code language="xml"}}$ship.{'class'}{{/code}}
735	735	* {{code language="xml"}}table[$foo='bar'].{'$foo'}{{/code}}
736	736
	746	+
737	737	But it is easier just to write the property key without braces, which is equivalent:
738	738
739	739	* {{code language="xml"}}[0].count{{/code}}
...	...	@@ -741,6 +741,7 @@
741	741	* {{code language="xml"}}$ship.class{{/code}}
742	742	* {{code language="xml"}}table[$foo='bar'].$foo{{/code}}
743	743
	754	+
744	744	(In this case, $ship is a variable. All variables start with a "$", so they cannot be confused with keywords.)
745	745
746	746	A list has even more properties:
...	...	@@ -774,6 +774,7 @@
774	774
775	775	* {{code language="xml"}}$table.keys.list{{/code}}: Yields a list of all keys in the table (reliably sorted by key if all keys are numeric)
776	776
	788	+
777	777	* {{code language="xml"}}$table.keys.sorted{{/code}}: Yields a list of all keys in the table, sorted by their associated values (which requires that all values are numeric)
778	778	* {{code language="xml"}}$table.keys.random{{/code}}: A randomly chosen key (which requires that the table is non-empty)
779	779
...	...	@@ -789,6 +789,7 @@
789	789	* {{code language="xml"}}$list.{5}?{{/code}} ⟹ true if $list exists and has the property 5, false otherwise
790	790	* {{code language="xml"}}$table.$key?{{/code}} ⟹ Analogously, true if $table exists and has the string property '$key'
791	791
	804	+
792	792	The question mark can even be applied to variables:
793	793
794	794	* {{code language="xml"}}$list{{/code}} ⟹ The value stored under the name $list, or an error if there is no such variable
...	...	@@ -877,9 +877,11 @@
877	877	* player.**money**: The money in the player's account
878	878	* player.**ship**: The ship the player is currently on (not necessarily the player's ship), or null if the player is on a station
879	879
	893	+
880	880	* player.**primaryship**: The player's own ship (but the player is not necessarily on board)
881	881	* player.**entity**: The actual player object
882	882
	897	+
883	883	* player.**zone**, player.**sector**, player.**cluster**, player.**galaxy**: Location of the player entity
884	884	* player.**copilot**: The co-pilot NPC
885	885
...	...	@@ -906,6 +906,7 @@
906	906	* {{code language="xml"}}$money.formatted.{'formatstring'}{{/code}}
907	907	* {{code language="xml"}}$money.formatted.default{{/code}} (using default format string '%s')
908	908
	924	+
909	909	* {{code language="xml"}}$time.formatted.{'formatstring'}{{/code}}
910	910	* {{code language="xml"}}$time.formatted.default{{/code}} (using default format string '%T')
911	911
...	...	@@ -929,6 +929,7 @@
929	929	* %Cr: Localised "Cr" string
930	930	* %%: A % sign
931	931
	948	+
932	932	Examples:
933	933
934	934	* {{code language="xml"}}(1234Cr).formatted.{'%s'}{{/code}}⟹{{code language="xml"}}'1,234'{{/code}}