Skip to Content

Changes for page Mission Director Guide

Last modified by Klaus Meyer on 2025/03/31 16:39
From version 32974.3
edited by Heinrich Unrau
on 2024/10/17 13:46
Change comment: There is no comment for this version
To version 32974.5
edited by Heinrich Unrau
on 2024/10/17 13:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1007,8 +1007,7 @@
1007 1007  
1008 1008  * MD scripts and cues are identified by their names. So a script can only be refreshed if it has the same script name as before (file name is irrelevant).
1009 1009  * If there are new script files or new cue nodes (i.e. scripts/cues with new names) they are created and added properly. If you remove script files or cue nodes, the corresponding scripts/cues are removed from the game, including instances.
1010 -** (!) Pitfall: Cue Removal
1011 -
1010 +** (!) Pitfall: For savegame compatibility, released cues should not be removed.
1012 1012  * As a consequence, you CANNOT rename scripts or cues if you want to refresh them. Doing so would remove the old script or cue and add a new one with the new name.
1013 1013  * You CANNOT change a <cue> to a <library> or vice versa.
1014 1014  * You CANNOT add, remove, or change the "ref" attribute of a cue. But it is possible to remove the whole cue. (If all references to a library are removed you can also remove the library itself.)
... ... @@ -1030,7 +1030,9 @@
1030 1030  When adding a variable in a new MD script version and using that variable in multiple places, be aware that the variable doesn't exist yet in older savegames. You may have to check the existence of the variable before accessing it, or add some patch logic that initiailses the variable after loading the savegame, if necessary.
1031 1031  {{/warning}}
1032 1032  
1033 -(% id="cke_bm_117445S" style="display:none" %) (%%)If you remove a cue and then later add another cue with the same name, old save files will not know that the cue has been removed inbetween. In the following example the first cue was created setting $val_1 and the game is saved.
1032 +{{warning}}
1033 +(% id="cke_bm_221021S" style="display:none" %) (%%)Cue Removal Pitfall:
1034 +If you remove a cue and then later add another cue with the same name, old save files will not know that the cue has been removed inbetween. In the following example the first cue was created setting $val_1 and the game is saved.
1034 1034  {{code language="xml"}}<cue name="Deprecated_Test1">
1035 1035   <actions>
1036 1036   <set_value name="$val_1" exact="'old value'"/>
... ... @@ -1054,6 +1054,7 @@
1054 1054  \\To avoid this, do not delete any cues (once they are public for save game compatibility), but empty them out and mark them as deprecated. This will prevent new cues with the same name in the script.
1055 1055  {{code language="xml"}}<!-- Deprecated Cues, kept to not duplicate names in future cues -->
1056 1056  <cue name="Deprecated_Test1" comment="deprecated"></cue>{{/code}}
1058 +{{/warning}}
1057 1057  
1058 1058  == Patching ==
1059 1059