Skip to Content

Changes for page Mission Director Guide

Last modified by Klaus Meyer on 2025/03/31 16:39
From version 32970.5
edited by Owen Lake
on 2023/10/10 15:55
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
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.Owen
1 +xwiki:XWiki.Daniel
Content
... ... @@ -157,7 +157,7 @@
157 157  
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 -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).
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).
161 161  
162 162  Examples:
163 163  
... ... @@ -326,7 +326,7 @@
326 326  </cue>
327 327  {{/code}}
328 328  
329 -The values (including default values) can be variable expressions and will be evaluated when the cue is enabled, i.e. when it starts checking the conditions. They will be available to the cue as variables, using the parameter name with a '$' prefix. In the example above, the variables $foo, $bar, and $baz would be created.
329 +The values (including default values) can be variable expressions and will be evaluated when the cue is enabled, i.e. when it starts checking the conditions. They will be available to the cue as variables, using the parameter name with a ΓÇÿ$' prefix. In the example above, the variables $foo, $bar, and $baz would be created.
330 330  
331 331  {{code language="xml"}}
332 332  <library name="Lib">
... ... @@ -517,41 +517,7 @@
517 517  {{code language="xml"}}cos(60deg){{/code}}
518 518  \\{{code language="xml"}}cos(pi){{/code}}|
519 519  {{code language="xml"}}0.5{{/code}}
520 -\\{{code language="xml"}}-1.0{{/code}}|Cosine (function-style, parentheses required)
521 -|tan|unary|
522 -{{code language="xml"}}tan(-45deg){{/code}}
523 -\\{{code language="xml"}}tan(45deg){{/code}}|
524 -{{code language="xml"}}-1.0{{/code}}
525 -\\{{code language="xml"}}1.0{{/code}}|(((
526 -Tangent (function-style, parentheses required)
527 -
528 -Available from X4 v7.0
529 -)))
530 -|asin|unary|
531 -{{code language="xml"}}asin(-0.5f){{/code}}
532 -\\{{code language="xml"}}asin(1){{/code}}|
533 -{{code language="xml"}}-0.523599rad{{/code}}
534 -\\{{code language="xml"}}1.5708rad{{/code}}|(((
535 -Inverse sine (function-style, parentheses required)
536 -
537 -Available from X4 v7.0
538 -)))
539 -|acos|unary|
540 -{{code language="xml"}}acos(-0.5f){{/code}}
541 -\\{{code language="xml"}}acos(1.0f){{/code}}|
542 -{{code language="xml"}}2.0944rad{{/code}}
543 -\\{{code language="xml"}}0rad{{/code}}|(((
544 -Inverse cosine (function-style, parentheses required)
545 -
546 -Available from X4 v7.0
547 -)))
548 -|atan|unary|
549 -{{code language="xml"}}atan(1.0f){{/code}}|
550 -{{code language="xml"}}0.785398rad{{/code}}|(((
551 -Inverse tangent (function-style, parentheses required)
552 -
553 -Available from X4 v7.0
554 -)))
520 +\\{{code language="xml"}}0.0{{/code}}|Cosine (function-style, parentheses required)
555 555  |sqrt|unary|{{code language="xml"}}sqrt(2){{/code}}|{{code language="xml"}}1.414213LF{{/code}}|Square root (function-style, parentheses required)
556 556  |exp|unary|{{code language="xml"}}exp(1){{/code}}|{{code language="xml"}}2.71828LF{{/code}}|Exponential function (function-style, parentheses required)
557 557  |log|unary|{{code language="xml"}}log(8) / log(2){{/code}}|{{code language="xml"}}3.0LF{{/code}}|Natural logarithm (function-style, parentheses required)
... ... @@ -581,7 +581,7 @@
581 581  gt
582 582  \\> (>)|binary|
583 583  {{code language="xml"}}1 gt 3{{/code}}
584 -\\{{code language="xml"}}1 > 3{{/code}}|{{code language="xml"}}false{{/code}}|Greater than
550 +\\{{code language="xml"}}1 < 3{{/code}}|{{code language="xml"}}false{{/code}}|Greater than
585 585  |
586 586  ge
587 587  \\>=|binary|
... ... @@ -666,7 +666,7 @@
666 666  
667 667  See also the section about [[value properties>>doc:||anchor="HValueproperties" style="outline-width: 0px !important; user-select: auto !important;"]].
668 668  
669 -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'.
635 +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'.
670 670  \\To get a percent character in the result string, use '%%' in the format string.
671 671  \\\\\\If you need a more sophisticated method for text substitution, try **<substitute_text>**. See the XML schema documentation for this script action.
672 672  \\**[New as of X Rebirth 4.0]**