Skip to Content

Changes for page Mission Director Guide

Last modified by Klaus Meyer on 2025/03/31 16:39
From version 32963.1
edited by Daniel Turner
on 2023/08/24 10:05
Change comment: There is no comment for this version
To version 32965.1
edited by Daniel Turner
on 2023/08/24 10:24
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -417,8 +417,6 @@
417 417  Since octal numbers are hardly ever used (usually unknowingly), the parser is will produce a warning if an octal number is encountered."
418 418  {{/info}}
419 419  
420 -
421 -
422 422  You can write string literals by putting the string in single quotes:
423 423  
424 424  * {{code language="xml"}}'Hello world'{{/code}}
... ... @@ -509,7 +509,7 @@
509 509  \\{{code language="xml"}}typeof 'Hello world'{{/code}}|
510 510  {{code language="xml"}}datatype.null{{/code}}
511 511  \\{{code language="xml"}}datatype.integer{{/code}}
512 -\\{{code language="xml"}}datatype.string{{/code}}|Yields the [[data type of the following sub-expression>>MediaWiki.NULL]]
510 +\\{{code language="xml"}}datatype.string{{/code}}|Yields the [[data type of the following sub-expression>>||anchor="typeof" style="outline-width: 0px !important; user-select: auto !important;"]]
513 513  |sin|unary|
514 514  {{code language="xml"}}sin(30deg){{/code}}
515 515  \\{{code language="xml"}}sin(pi){{/code}}|
... ... @@ -554,7 +554,7 @@
554 554  ge
555 555  \\>=|binary|
556 556  {{code language="xml"}}1 ge 3{{/code}}
557 -\\{{code language="xml"}}1 <= 3{{/code}}|{{code language="xml"}}false{{/code}}|Greater than or equal to
555 +\\{{code language="xml"}}1 >= 3{{/code}}|{{code language="xml"}}false{{/code}}|Greater than or equal to
558 558  |(((
559 559  
560 560  )))|binary|{{code language="xml"}}1 + 1 == 2.0{{/code}}|{{code language="xml"}}true{{/code}}|Equal to
... ... @@ -623,19 +623,16 @@
623 623  * "and" and "or" use short-circuit semantics: The right side of the operation can be skipped if the left side already determines the outcome of the operation
624 624  ** Example:{{code language="xml"}} false and $foo{{/code}} ⟹ {{code language="xml"}}false{{/code}} (the value of $foo is not checked at all)
625 625  * 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.
626 -* <, <=, >, >= 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.
624 +* <, <=, >, >= 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>>doc:||anchor="HValuecomparisons"]] with additional XML attributes can be more readable.
627 627  
628 -(% id="categorybroken_macroanchorstrings-and-formatting" %)== Strings and formatting==
626 +== (% id="categorybroken_macroanchorstrings-and-formatting" %)Strings and formatting(%%) ==
629 629  
630 -
631 -{{{==}}}
632 -
633 633  You can concatenate string literals using the + operator, but there is also a printf-like formatting syntax, which is easier to use than concatenating lots of small pieces:
634 634  
635 635  * {{code language="xml"}}'The %1 %2 %3 jumps over the %5 %4'.['quick', 'brown', 'fox', 'dog', 'lazy']{{/code}}
636 636  * {{code language="xml"}}'%1 + %2 = %3'.[$a, $b, $a + $b]{{/code}}
637 637  
638 -See also the section about [[value properties>>MediaWiki.NULL]].
633 +See also the section about [[value properties>>doc:||anchor="HValueproperties" style="outline-width: 0px !important; user-select: auto !important;"]].
639 639  
640 640  Instead of ΓÇÿ%1 %2 %3', you can also use ΓÇÿ%s %s %s', which is also compatible with Lua string formatting in the UI system. However, this should only be used if you are sure that the order is the same in all supported languages. If you want to make translators aware that they can change the order of parameters, you should prefer '%1 %2 %3'.
641 641  \\To get a percent character in the result string, use '%%' in the format string.
... ... @@ -654,14 +654,14 @@
654 654  * "." must be followed by a single digit (0-9). In case of ".0" any fractional digits are discarded (rounding towards zero, not half away from zero).
655 655  
656 656  {{info}}
657 -There are also special methods to [[NULL|format money values and time values]] using the "formatted" property.
652 +There are also special methods to [[format money values and time values>>doc:||anchor="HMoneyandtimeformatting" style="outline-width: 0px !important; user-select: auto !important;"]] using the "formatted" property.
658 658  {{/info}}
659 659  
660 660  == Lists ==
661 661  
662 -Another example for a non-numeric value is a list: It is an ordered collection of other arbitrary values (called array or vector in other languages). It can be constructed within an expression using the [[~[~] syntax>>MediaWiki.NULL]]. It may also be generated by special actions and conditions, and there are actions that can [[insert or remove values>>MediaWiki.NULL]].
657 +Another example for a non-numeric value is a list: It is an ordered collection of other arbitrary values (called array or vector in other languages). It can be constructed within an expression using the [[~[~] syntax>>doc:||anchor="HOperators"]]. It may also be generated by special actions and conditions, and there are actions that can [[insert or remove values>>doc:||anchor="HCreatingandremovingvariables" style="outline-width: 0px !important; user-select: auto !important;"]].
663 663  
664 -A list can contain values of arbitrary data types, even mixed in the same list - so a list can actually contain other lists. However, some of the things that you can do with lists require that all contained elements are of a certain type. The contents of a list can be accessed via properties, see the section about [[value properties>>MediaWiki.NULL]]. Lists can be empty, these are written as "[ ]".
659 +A list can contain values of arbitrary data types, even mixed in the same list - so a list can actually contain other lists. However, some of the things that you can do with lists require that all contained elements are of a certain type. The contents of a list can be accessed via properties, see the section about [[value properties>>doc:||anchor="HValueproperties"]]. Lists can be empty, these are written as "[ ]".
665 665  
666 666  {{info}}
667 667  When accessing a list's elements, the numbering is '''1-based''', so the first element has number 1. This is intuitive but different from 0-based numbering in most programming languages."
... ... @@ -680,7 +680,7 @@
680 680  (% id="categorybroken_macroanchortables" %)
681 681  == Tables ==
682 682  
683 -Tables are associative arrays - they are like lists, but you can assign values to (almost) arbitrary keys, not just to index numbers. A table is constructed within an expression using the [[table~[~] syntax>>MediaWiki.NULL]]. See the section about [[value properties>>MediaWiki.NULL]] for how to access the contents of a table. [[Creating and removing entries>>MediaWiki.NULL]] works similarly to lists, but instead of inserting, you simply assign a value to a table key. If the key does not exist yet, it will be created.
678 +Tables are associative arrays - they are like lists, but you can assign values to (almost) arbitrary keys, not just to index numbers. A table is constructed within an expression using the [[table~[~] syntax>>doc:||anchor="HOperators" style="outline-width: 0px !important; user-select: auto !important;"]]. See the section about [[value properties>>doc:||anchor="HValueproperties" style="outline-width: 0px !important; user-select: auto !important;"]] for how to access the contents of a table. [[Creating and removing entries>>doc:||anchor="HCreatingandremovingvariables" style="outline-width: 0px !important; user-select: auto !important;"]] works similarly to lists, but instead of inserting, you simply assign a value to a table key. If the key does not exist yet, it will be created.
684 684  
685 685  Almost all values are allowed as table keys, but there are a few exceptions:
686 686  
... ... @@ -773,7 +773,7 @@
773 773  * {{code language="xml"}}$table.keys.random{{/code}}: A randomly chosen key (which requires that the table is non-empty)
774 774  
775 775  {{info}}
776 -The string formatting syntax that you have seen [[NULL|above]] is also based on the property system. You basically pass a list as property key to a string. Braces around the brackets are not required, so 'foo'.[...] is just a convenient alternative notation for 'foo'.{[...]}.
771 +The string formatting syntax that you have seen [[above>>doc:||anchor="HStringsandformatting" style="outline-width: 0px !important; user-select: auto !important;"]] is also based on the property system. You basically pass a list as property key to a string. Braces around the brackets are not required, so 'foo'.[...] is just a convenient alternative notation for 'foo'.{[...]}.
777 777  {{/info}}
778 778  
779 779  === (% id="lookup-tests-and-suppressing-errors" %)Lookup tests and suppressing errors(%%) ===
... ... @@ -825,11 +825,11 @@
825 825  |profile|
826 826  profile.flat
827 827  \\profile.increasing
828 -\\profile.bell|Probability distribution profile (see [[random ranges>>MediaWiki.NULL]])
823 +\\profile.bell|Probability distribution profile (see [[random ranges>>doc:||anchor="HRandomranges" style="outline-width: 0px !important; user-select: auto !important;"]])
829 829  |cuestate|
830 830  cuestate.waiting
831 831  \\cuestate.active
832 -\\cuestate.complete|[[Cue states>>MediaWiki.NULL]]
827 +\\cuestate.complete|[[Cue states>>||anchor="HCues" style="outline-width: 0px !important; user-select: auto !important;"]]
833 833  |level|
834 834  level.easy
835 835  \\level.medium
... ... @@ -849,7 +849,7 @@
849 849  \\faction.argongovernment|Factions
850 850  )))
851 851  
852 -{{id name="typeof" /}}
847 +{{id name="typeof"/}}
853 853  
854 854  {{info}}
855 855  With the ''typeof'' operator you can get the datatype of any expression and compare it with what you expect, for example:
... ... @@ -898,7 +898,7 @@
898 898  === (% id="categorybroken_macroanchormoney-and-time-formatting" %)Money and time formatting(%%) ===
899 899  
900 900  **[New as of X Rebirth 4.0]**
901 -\\Numbers don't have any properties, except for money and time: They have a "**formatted**" property, which allows you to get a custom string representation with more advanced options than the [[generic formatting method>>MediaWiki.NULL]] for numbers.
896 +\\Numbers don't have any properties, except for money and time: They have a "**formatted**" property, which allows you to get a custom string representation with more advanced options than the [[generic formatting method>>||anchor="HStringsandformatting" style="outline-width: 0px !important; user-select: auto !important;"]] for numbers.
902 902  
903 903  * {{code language="xml"}}$money.formatted.{'formatstring'}{{/code}}
904 904  * {{code language="xml"}}$money.formatted.default{{/code}} (using default format string '%s')
... ... @@ -934,7 +934,7 @@
934 934  * {{code language="xml"}}(1234Cr).formatted.{'%1s'}{{/code}}⟹{{code language="xml"}}'1 k'{{/code}} (rounding towards zero)
935 935  * {{code language="xml"}}(1234Cr).formatted.{'%cM'}{{/code}}⟹{{code language="xml"}}'0 M'{{/code}}
936 936  
937 -For documentation of time format strings, see the Lua function ConvertTimeString() in the [[MediaWiki.ARCHIVE.XRWIKIModding_supportUI_Modding_supportLua_function_overview]].
932 +For documentation of time format strings, see the Lua function ConvertTimeString() in the [[Lua function overview>>doc:X Rebirth Wiki.Modding support.UI Modding support.Lua function overview.WebHome||style="outline-width: 0px !important; user-select: auto !important;"]].
938 938  
939 939  Examples:
940 940  
... ... @@ -1077,7 +1077,6 @@
1077 1077   <set_value name="$foo" min="-20" max="20" profile="profile.increasing" scale="4"/>
1078 1078  {{/code}}
1079 1079  
1080 -
1081 1081  = Variables and namespaces =
1082 1082  
1083 1083  As you have seen above, you can easily access variables by writing their name (including $ prefix) in an expression. Namespaces define in which cue the variables are actually stored (and from which cue they are read).
... ... @@ -1132,7 +1132,6 @@
1132 1132  
1133 1133  Removing an entry from a list shifts all following elements down by one. If you want to clear an entry without removing it from the list, just use <set_value> instead.
1134 1134  
1135 -
1136 1136  == Accessing remote variables ==
1137 1137  
1138 1138  You can also read and write variables in other cues by using the variable name as property key: