Skip to Content

Changes for page Mission Director Guide

Last modified by Klaus Meyer on 2025/03/31 16:39
From version 31072.1
edited by Daniel Turner
on 2023/04/14 17:05
Change comment: There is no comment for this version
To version 31075.1
edited by Daniel Turner
on 2023/04/14 17:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -160,15 +160,35 @@
160 160  
161 161  (% style="color: rgb(0,0,0);text-decoration: none;" %)Example for an event condition:
162 162  
163 -{{code}}<conditions>  <event_object_destroyed object="$target"/></conditions>{{/code}}
163 +{{code language="xml"}}
164 +<conditions>
165 + <event_object_destroyed object="$target"/>
166 +</conditions>
167 +{{/code}}
164 164  
165 165  (% style="color: rgb(0,0,0);text-decoration: none;" %)Example for an event condition with an additional (non-event) check:
166 166  
167 -{{code}}&lt;conditions&gt;  &lt;event_player_killed_object/&gt;  &lt;check_value value=&quot;event.param.isclass.turret&quot;/&gt;&lt;/conditions&gt;{{/code}}
171 +{{code language="xml"}}
172 +<conditions>
173 + <event_player_killed_object/>
174 + <check_value value="event.param.isclass.turret"/>
175 +</conditions>
176 +{{/code}}
168 168  
169 169  (% style="color: rgb(0,0,0);text-decoration: none;" %)Example for an event condition with two alternative events and a common additional check:
170 170  
171 -{{code}}&lt;conditions&gt;  &lt;check_any&gt;    &lt;event_cue_completed cue=&quot;Cue1&quot;/&gt;    &lt;check_all&gt;      &lt;event_player_killed_object/&gt;      &lt;check_value value=&quot;event.param.isclass.turret&quot;/&gt;    &lt;/check_all&gt;  &lt;/check_any&gt;  &lt;check_age min=&quot;$starttime&quot;/&gt;&lt;/conditions&gt;{{/code}}
180 +{{code language="xml"}}
181 +<conditions>
182 + <check_any>
183 + <event_cue_completed cue="Cue1"/>
184 + <check_all>
185 + <event_player_killed_object/>
186 + <check_value value="event.param.isclass.turret"/>
187 + </check_all>
188 + </check_any>
189 + <check_age min="$starttime"/>
190 +</conditions>
191 +{{/code}}
172 172  
173 173  (% style="color: rgb(0,0,0);text-decoration: none;" %)For more information about expressions and event parameters, see below.
174 174  
... ... @@ -186,11 +186,21 @@
186 186  
187 187  (% style="color: rgb(0,0,0);text-decoration: none;" %)Check conditions every 5 seconds, but start checking only 1 hour after game start.
188 188  
189 -{{code}}&lt;cue name=&quot;Foo&quot; checktime=&quot;1h&quot; checkinterval=&quot;5s&quot;&gt;  &lt;conditions&gt;  [...]&lt;/cue&gt;{{/code}}
209 +{{code language="xml"}}
210 +<cue name="Foo" checktime="1h" checkinterval="5s">
211 + <conditions>
212 + [...]
213 +</cue>
214 +{{/code}}
190 190  
191 191  (% style="color: rgb(0,0,0);text-decoration: none;" %)Check conditions 3 seconds after the cue is enabled, and cancel the cue in case of failure.
192 192  
193 -{{code}}&lt;cue name=&quot;Foo&quot; checktime=&quot;player.age + 3s&quot; onfail=&quot;cancel&quot;&gt;  &lt;conditions&gt;  [...]&lt;/cue&gt;{{/code}}
218 +{{code language="xml"}}
219 +<cue name="Foo" checktime="player.age + 3s" onfail="cancel">
220 + <conditions>
221 + [...]
222 +</cue>
223 +{{/code}}
194 194  
195 195  (% style="color: rgb(0,0,0);text-decoration: none;" %)(% style="color: rgb(0,0,0);text-decoration: none;" %)(% style="color: rgb(0,0,0);text-decoration: none;" %)The attributes //onfail//, //checkinterval//, //checktime// are not allowed for cues with event conditions.
196 196  
... ... @@ -210,11 +210,15 @@
210 210  
211 211  (% style="color: rgb(0,0,0);text-decoration: none;" %)The <actions> node contains the actions that are performed one after another, without any delay inbetween. You can enforce a delay after activation of the cue and actual action performance, using a <delay> node right before the <actions>:
212 212  
213 -{{code}}&lt;delay min=&quot;10s&quot; max=&quot;30s&quot;/&gt;{{/code}}
243 +{{code language="xml"}}
244 +<delay min="10s" max="30s"/>
245 +{{/code}}
214 214  
215 215  (% style="color: rgb(0,0,0);text-decoration: none;" %)Note that during the delay the cue is already in the active state, and the sub-cues have been enabled! If you want to make sure that a sub-cue only becomes active after this cue is complete, there is a useful event condition for that:
216 216  
217 -{{code}}&lt;event_cue_completed cue=&quot;parent&quot;/&gt;{{/code}}
249 +{{code language="xml"}}
250 +<event_cue_completed cue="parent"/>
251 +{{/code}}
218 218  
219 219  (% style="color: rgb(0,0,0);text-decoration: none;" %)<actions> is optional. Leaving it out may be useful if you only want to enable sub-cues after the cueΓÇÖs condition check. The state transition from active to complete will still take the <delay> node into account.
220 220  
... ... @@ -222,8 +222,18 @@
222 222  
223 223  (% style="color: rgb(0,0,0);text-decoration: none;" %)Example, which selects one of the three texts randomly:
224 224  
225 -{{code}}&lt;actions&gt; &lt;do_any&gt;   &lt;debug_text text=&quot;'Hello world'&quot;/&gt;   &lt;debug_text text=&quot;'Welcome to the MD'&quot;/&gt;   &lt;debug_text text=&quot;'And now for something completely different'&quot;/&gt; &lt;/do_any&gt;&lt;actions&gt;{{/code}}
259 +{{code language="xml"}}
260 +<actions>
261 + <do_any>
262 + <debug_text text="'Hello world'"/>
263 + <debug_text text="'Welcome to the MD'"/>
264 + <debug_text text="'And now for something completely different'"/>
265 + </do_any>
266 +<actions>
267 +{{/code}}
226 226  
269 +
270 +
227 227  {{note body="<span style=~"color: rgb(0,0,0);text-decoration: none;~">Messages printed with &lt;debug_text&gt; are usually only visible when the ΓÇ£scriptsΓÇ¥ debug filter is enabled, see [[NULL|Script debug output]].</span>"/}}
228 228  
229 229