Changes for page Mission Director Guide
Last modified by Klaus Meyer on 2025/03/31 16:39
From version 31071.1
edited by Daniel Turner
on 2023/04/14 17:02
on 2023/04/14 17:02
Change comment:
There is no comment for this version
To version 31073.1
edited by Daniel Turner
on 2023/04/14 17:10
on 2023/04/14 17:10
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -80,13 +80,26 @@ 80 80 81 81 (% style="color: rgb(0,0,0);text-decoration: none;" %)The XML root node of an MD file is called “mdscript” and looks like this: 82 82 83 -{{code}}<?xml version="1.0" encoding="utf-8"?><mdscript name="ScriptName" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="md.xsd">{{/code}} 83 +{{code language="xml"}} 84 +<?xml version="1.0" encoding="utf-8"?> 85 +<mdscript name="ScriptName" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="md.xsd"> 86 +{{/code}} 84 84 85 85 (% style="color: rgb(0,0,0);text-decoration: none;" %)“ScriptName” is the name used for this script regardless of the file name. It (%%)**(% style="color: rgb(0,0,0);text-decoration: none;" %)has to start with an upper case letter and must be unique(%%)**(% style="color: rgb(0,0,0);text-decoration: none;" %) among all MD script names. It also should not contain spaces, so other MD scripts can use it as an identifier to access this script’s contents easily. 86 86 87 87 (% style="color: rgb(0,0,0);text-decoration: none;" %)The only allowed sub-node of <mdscript> is <cues>, which can only contain <cue> sub-nodes: 88 88 89 -{{code}}<?xml version="1.0" encoding="utf-8"?><mdscript name="ScriptName" ...>  <cues>    <cue name="RootCue1"> [...]    </cue>    <cue name="RootCue2"> [...]    </cue>  </cues></mdscript>{{/code}} 92 +{{code language="xml"}} 93 +<?xml version="1.0" encoding="utf-8"?> 94 +<mdscript name="ScriptName" ...> 95 + <cues> 96 + <cue name="RootCue1"> [...] 97 + </cue> 98 + <cue name="RootCue2"> [...] 99 + </cue> 100 + </cues> 101 +</mdscript> 102 +{{/code}} 90 90 91 91 (% style="color: rgb(0,0,0);text-decoration: none;" %)  92 92 ... ... @@ -147,15 +147,35 @@ 147 147 148 148 (% style="color: rgb(0,0,0);text-decoration: none;" %)Example for an event condition: 149 149 150 -{{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}} 151 151 152 152 (% style="color: rgb(0,0,0);text-decoration: none;" %)Example for an event condition with an additional (non-event) check: 153 153 154 -{{code}}<conditions>  <event_player_killed_object/>  <check_value value="event.param.isclass.turret"/></conditions>{{/code}} 171 +{{code language="xml"}} 172 +<conditions> 173 + <event_player_killed_object/> 174 + <check_value value="event.param.isclass.turret"/> 175 +</conditions> 176 +{{/code}} 155 155 156 156 (% style="color: rgb(0,0,0);text-decoration: none;" %)Example for an event condition with two alternative events and a common additional check: 157 157 158 -{{code}}<conditions>  <check_any>    <event_cue_completed cue="Cue1"/>    <check_all>      <event_player_killed_object/>      <check_value value="event.param.isclass.turret"/>    </check_all>  </check_any>  <check_age min="$starttime"/></conditions>{{/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}} 159 159 160 160 (% style="color: rgb(0,0,0);text-decoration: none;" %)For more information about expressions and event parameters, see below. 161 161