Changes for page Breaking Changes
Last modified by Michael Baumgardt on 2026/04/17 12:03
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -xwiki:XWiki. cbj1 +xwiki:XWiki.matthias - Content
-
... ... @@ -24,22 +24,239 @@ 24 24 Version 25 25 )))|=((( 26 26 Summary 27 +)))|=(% colspan="1" %)(% colspan="1" %) 28 +((( 29 + 27 27 ))) 28 -|(% colspan=" 3" %)(% colspan="3" %)31 +|(% colspan="4" %)(% colspan="4" %) 29 29 ((( 33 +== 4.00 == 34 +))) 35 +|((( 36 +Parameters 37 +)))|((( 38 +4.00 Beta 1 39 +)))|((( 40 +**requiresconstructionvessel** parameter moved 41 +)))|((( 42 + 43 +))) 44 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 45 +((( 46 +//The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.// 47 +))) 48 +|((( 49 +Scripts 50 +)))|((( 51 +4.00 Beta 1 52 +)))|((( 53 +Changed behaviour of **gatedistance** script property 54 +)))|((( 55 + 56 +))) 57 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 58 +((( 59 +//The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.// 60 +)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %) 61 +((( 62 + 63 +))) 64 +|(% colspan="4" %)(% colspan="4" %) 65 +((( 66 +== 3.30 == 67 +))) 68 +|((( 69 +UI extensions 70 +)))|((( 71 +3.30 Beta 3 72 +)))|((( 73 +**FFI: **Removed** (% style="color: rgb(0,0,0);" %)GetMissionLimit() (%%)**(% style="color: rgb(0,0,0);" %)and** **(% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)**IsMissionLimit**(%%)**Enabled()** 74 +)))|(% colspan="1" %)(% colspan="1" %) 75 +((( 76 + 77 +))) 78 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 79 +((( 80 +//These mission limit-related functions (added in 3.30 Beta 1 and 2) are replaced with FFI (% style="color: rgb(0,0,0);" %)IsMissionLimit(%%)Reach(% style="color: rgb(0,0,0);" %)ed()// 81 +))) 82 +|(% colspan="4" %)(% colspan="4" %) 83 +((( 84 +== 3.20 == 85 +))) 86 +|((( 87 +Scripts 88 +)))|((( 89 +3.20 Beta 1 90 +)))|((( 91 +Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed 92 +)))|(% colspan="1" %)(% colspan="1" %) 93 +((( 94 + 95 +))) 96 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 97 +((( 98 +//Old params: param = attacked object, param2 = attack method, param3 = attacked component// 99 +//New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon] 100 +Note that this also means the component attribute to the events is no longer available, so scripts checking the attacked component need to use event.param3.{1} instead// 101 +))) 102 +|(% colspan="1" %)(% colspan="1" %) 103 +((( 104 +Scripts 105 +)))|(% colspan="1" %)(% colspan="1" %) 106 +((( 107 +3.20 Beta 1 108 +)))|(% colspan="1" %)(% colspan="1" %) 109 +((( 110 +Removed script property $trade.**restriction.faction** 111 +)))|(% colspan="1" %)(% colspan="1" %) 112 +((( 113 + 114 +))) 115 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 116 +((( 117 +//$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.// 118 +))) 119 +|((( 120 +UI extensions 121 +)))|((( 122 +3.20 Beta 1 123 +)))|((( 124 +**Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete! 125 +)))|(% colspan="1" %)(% colspan="1" %) 126 +((( 127 + 128 +))) 129 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 130 +((( 131 +//With the addition of the Trade Rule feature the given functions are obsolete and do not function anymore. This set of functions will return dummy values to avoid breaking scripts. Use GetAllTradeRules(), GetContainerTradeRuleID(), SetContainerTradeRule() and similar trade rule functions as replacement.// 132 +))) 133 +|(% colspan="4" %)(% colspan="4" %) 134 +((( 135 +== 3.10 == 136 +))) 137 +|(% colspan="1" %)(% colspan="1" %) 138 +((( 139 +Scripts 140 +)))|(% colspan="1" %)(% colspan="1" %) 141 +((( 142 +3.10 Beta 1 143 +)))|(% colspan="1" %)(% colspan="1" %) 144 +((( 145 +Removed script action **<add_build/>** 146 +)))|(% colspan="1" %)(% colspan="1" %) 147 +((( 148 + 149 +))) 150 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 151 +((( 152 +//Removed <add_build/> action which was no longer needed and would result in builds being added in unsupported ways. Use other <add_build_xxx/> actions.// 153 +))) 154 +|(% colspan="4" %)(% colspan="4" %) 155 +((( 30 30 == 3.00 == 31 31 ))) 32 32 |(% colspan="1" %)(% colspan="1" %) 33 33 ((( 160 +Scripts 161 +)))|(% colspan="1" %)(% colspan="1" %) 162 +((( 163 +3.0 Beta 6 164 +)))|(% colspan="1" %)(% colspan="1" %) 165 +((( 166 +Changed behaviour of script action **<get_suitable_job/>** 167 +)))|(% colspan="1" %)(% colspan="1" %) 168 +((( 169 + 170 +))) 171 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 172 +((( 173 +//<get_suitable_job/> previously did not respect job quotas or the current number of job ships. It now does, only returning job IDs which are not exceeding the maxgalaxy quota. Using 'exceedquota' allows the action to behave as before.// 174 +))) 175 +|(% colspan="1" %)(% colspan="1" %) 176 +((( 177 +Scripts 178 +)))|(% colspan="1" %)(% colspan="1" %) 179 +((( 180 +3.0 Beta 6 181 +)))|(% colspan="1" %)(% colspan="1" %) 182 +((( 183 +Changed behaviour of script action **<get_ware_definition/>** 184 +)))|(% colspan="1" %)(% colspan="1" %) 185 +((( 186 + 187 +))) 188 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 189 +((( 190 +//<get_ware_definition/> previously filtered for equipment wares by default. This is now not the case and existing cases now use flags="equipment". Additional filter attributes for group and tags has also been added.// 191 +))) 192 +|(% colspan="1" %)(% colspan="1" %) 193 +((( 34 34 Global 35 35 )))|(% colspan="1" %)(% colspan="1" %) 36 36 ((( 197 +3.0 Beta 5 198 +)))|(% colspan="1" %)(% colspan="1" %) 199 +((( 200 +Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case 201 +)))|(% colspan="1" %)(% colspan="1" %) 202 +((( 203 + 204 +))) 205 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 206 +((( 207 +//All MD, UI, and cutscene files have been renamed as lower-case. For most users this should have no effect since files packed in catalogs are essentially case-insensitive. However, this change can affect users on Linux systems when running a mod that contains single files instead of a catalog, and/or when playing with unpacked base game files//. If your mod has XML patch files that are not packed in a catalog, the filenames must be lower-case to match the filenames in the base game. (For info on using mod catalogs, see the Readme of the X Catalog Tool.)\\ 208 + 209 +//Note that this change has no effect on the actual content of scripts or cutscenes. The MD script/cutscene names are stored in the files, regardless of the filenames, so that references to them remain unchanged (e.g., "md.Setup.Start" references a cue in setup.xml).// 210 +))) 211 +|(% colspan="1" %)(% colspan="1" %) 212 +((( 213 +Scripts 214 +)))|(% colspan="1" %)(% colspan="1" %) 215 +((( 216 +3.0 Beta 5 217 +)))|(% colspan="1" %)(% colspan="1" %) 218 +((( 219 +Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions> 220 +)))|(% colspan="1" %)(% colspan="1" %) 221 +((( 222 + 223 +))) 224 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 225 +((( 226 +//Some MD library cues in the base game that were previously used with <include_actions> have been adjusted, so they must now be used with the new MD action <run_actions> instead. Mods that use such a library with <include_actions> will have to switch to <run_actions> as well. A list of affected libraries is not provided here. Note: Additional library cues may be adjusted in future builds without further warning.// 227 +))) 228 +|(% colspan="1" %)(% colspan="1" %) 229 +((( 230 +Scripts 231 +)))|(% colspan="1" %)(% colspan="1" %) 232 +((( 233 +3.0 Beta 5 234 +)))|(% colspan="1" %)(% colspan="1" %) 235 +((( 236 +Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos** 237 +)))|(% colspan="1" %)(% colspan="1" %) 238 +((( 239 + 240 +))) 241 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 242 +((( 243 +//Before the change, positions are relative to $dockingbay.parent. 244 +After the change, positions are relative to $dockingbay as specified in the documentation.// 245 +))) 246 +|(% colspan="1" %)(% colspan="1" %) 247 +((( 248 +Global 249 +)))|(% colspan="1" %)(% colspan="1" %) 250 +((( 37 37 3.0 Beta 2 38 38 )))|(% colspan="1" %)(% colspan="1" %) 39 39 ((( 40 40 Support for entity flag "**skillsvisible**" dropped 255 +)))|(% colspan="1" %)(% colspan="1" %) 256 +((( 257 + 41 41 ))) 42 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)259 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 43 43 ((( 44 44 //Entity skills are always visible; that flag was a leftover from XR. We removed support for the script property .skillsvisible, the attribute "skillsvisible" of <set_entity_traits> and <set_npc_template_traits>, and the parameter "skillsvisible" of Lua function GetComponentData().// 45 45 ))) ... ... @@ -49,8 +49,11 @@ 49 49 3.0 Beta 2 50 50 )))|((( 51 51 Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**. 269 +)))|(% colspan="1" %)(% colspan="1" %) 270 +((( 271 + 52 52 ))) 53 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)273 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 54 54 ((( 55 55 //Before 3.0 Beta 2 there was just a single <event_object//_changed_owner> condition. This condition was triggered in multiple cases when an owner change occurred. However, the exact cases were inconsistent and also the event could have been triggered w/o an effective owner change having been applied. 56 56 3.0 Beta 2 fixes these inconsistencies and ensures that the event is only fired, if the "effective" component owner of the object changed. To handle cases where the script actually needs to be informed if the "true" owner of a component was changed (i.e. not taking the cover faction into account) a new <event_object_changed_true_owner> was introduced. ... ... @@ -65,9 +65,12 @@ 65 65 3.0 Beta 1 66 66 )))|(% colspan="1" %)(% colspan="1" %) 67 67 ((( 68 -MissionBoard support dropped 288 +**MissionBoard** support dropped 289 +)))|(% colspan="1" %)(% colspan="1" %) 290 +((( 291 + 69 69 ))) 70 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)293 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 71 71 ((( 72 72 //MissionBoards was a dummy asset type which was only used during early development and never meant to be shipped in the released version. If any mod tried to make use of this asset type, undefined behaviour would occur. Therefore we cleaned things up in 3.0 Beta 1 including deprecating/removing any related UI/script function.// 73 73 ))) ... ... @@ -76,11 +76,14 @@ 76 76 )))|((( 77 77 3.0 Beta 1 78 78 )))|((( 79 -By default, job/god entries now only spawn objects in space added by the extension in which they are defined 302 +By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined 303 +)))|(% colspan="1" %)(% colspan="1" %) 304 +((( 305 + 80 80 ))) 81 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)307 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 82 82 ((( 83 -//To better support extensions which extend the map, a job/god entry now defaults to only spawning objects in areas of the map that are added by the extension in which that entry is defined. You can override this behaviour by adding a matchextension="false" attribute to the job/god entry definition. This allows the entry to spawn objects anywhere that matches the entry's other criteria.//309 +//To better support extensions which add to the base game map, a job/god entry now defaults to only spawning objects in areas of the map that are added by the extension in which that entry is defined. You can override this behaviour by adding a matchextension="false" attribute to the job/god entry definition. This allows the entry to spawn objects anywhere that matches the entry's other criteria.// 84 84 ))) 85 85 |(% colspan="1" %)(% colspan="1" %) 86 86 ((( ... ... @@ -91,8 +91,11 @@ 91 91 )))|(% colspan="1" %)(% colspan="1" %) 92 92 ((( 93 93 Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'** 320 +)))|(% colspan="1" %)(% colspan="1" %) 321 +((( 322 + 94 94 ))) 95 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)324 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 96 96 ((( 97 97 //Due to engine changes, script action <add_actor_to_room/> has had the attribute 'room' changed to 'object', which is more accurate. Most likely requires a 'position' if a slot is not provided.// 98 98 ))) ... ... @@ -105,8 +105,11 @@ 105 105 )))|(% colspan="1" %)(% colspan="1" %) 106 106 ((( 107 107 Script action **<set_doors_locked/>** attribute **'group'** changed 337 +)))|(% colspan="1" %)(% colspan="1" %) 338 +((( 339 + 108 108 ))) 109 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)341 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 110 110 ((( 111 111 //The 'group' attribute of <set_doors_locked/> can no longer be a list. It must be a single tag value. Previously, a list containing one tag was accepted, which was redundant.// 112 112 ))) ... ... @@ -119,8 +119,11 @@ 119 119 )))|(% colspan="1" %)(% colspan="1" %) 120 120 ((( 121 121 Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed 354 +)))|(% colspan="1" %)(% colspan="1" %) 355 +((( 356 + 122 122 ))) 123 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)358 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 124 124 ((( 125 125 //These events were never triggered, with the exception of <event_hack_started/> on the player entity for instant control panel hacks. Use <event_player_hacked_object> instead.// 126 126 ))) ... ... @@ -133,8 +133,11 @@ 133 133 )))|(% colspan="1" %)(% colspan="1" %) 134 134 ((( 135 135 Script actions **<set_hack_target/>** and **<abort_hack/>** removed 371 +)))|(% colspan="1" %)(% colspan="1" %) 372 +((( 373 + 136 136 ))) 137 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)375 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 138 138 ((( 139 139 //These actions had no effect and were removed.// 140 140 ))) ... ... @@ -147,8 +147,11 @@ 147 147 )))|(% colspan="1" %)(% colspan="1" %) 148 148 ((( 149 149 **<setup_conversation_minigame/>** script action removed 388 +)))|(% colspan="1" %)(% colspan="1" %) 389 +((( 390 + 150 150 ))) 151 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)392 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 152 152 ((( 153 153 //The script action was a leftover from the XR era and was never supported in X4 and couldn't be used in a meaningful way. It was therefore decided to better drop it altogether as it's not expected having been used by any mods.// 154 154 ))) ... ... @@ -161,8 +161,11 @@ 161 161 )))|(% colspan="1" %)(% colspan="1" %) 162 162 ((( 163 163 <add_player_choice_*> **confidence** attribute removed 405 +)))|(% colspan="1" %)(% colspan="1" %) 406 +((( 407 + 164 164 ))) 165 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)409 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 166 166 ((( 167 167 //The default confidence of player options is another leftover from the XR era and had no effect in X4.// 168 168 ))) ... ... @@ -175,8 +175,11 @@ 175 175 )))|(% colspan="1" %)(% colspan="1" %) 176 176 ((( 177 177 **<hack_via_control_panel/>** script action removed 422 +)))|(% colspan="1" %)(% colspan="1" %) 423 +((( 424 + 178 178 ))) 179 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)426 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 180 180 ((( 181 181 //Unused script action <hack_via_control_panel/> was removed.// 182 182 ))) ... ... @@ -189,8 +189,11 @@ 189 189 )))|(% colspan="1" %)(% colspan="1" %) 190 190 ((( 191 191 **Lua: **GetMiniGameCursorPosition() removed 439 +)))|(% colspan="1" %)(% colspan="1" %) 440 +((( 441 + 192 192 ))) 193 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)443 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 194 194 ((( 195 195 //GetMiniGameCursorPosition() was a left over from the XR era and never supposed to be shipped with X4. The function practically always returned 0 and hence we don't expect the removal of this obsolete function causing any actual mod to break.// 196 196 ))) ... ... @@ -200,8 +200,11 @@ 200 200 3.0 Beta 1 201 201 )))|((( 202 202 **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders 453 +)))|(% colspan="1" %)(% colspan="1" %) 454 +((( 455 + 203 203 ))) 204 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)457 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 205 205 ((( 206 206 //In 3.0 Beta 1 we added support to display icons for keyboard bindings, if an icon is available for the specified keys. This results in GetLocalizedInteractiveNotificationKey() potentially returning a different text now if such an icon is assigned to the mapped key/button.// 207 207 ))) ... ... @@ -214,8 +214,11 @@ 214 214 )))|(% colspan="1" %)(% colspan="1" %) 215 215 ((( 216 216 **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor 470 +)))|(% colspan="1" %)(% colspan="1" %) 471 +((( 472 + 217 217 ))) 218 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)474 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 219 219 ((( 220 220 //In 3.0 Beta 1 we added support for a new weapon mod property "SurfaceElementFactor" to allow weapons to deal increased damage to surface elements such as Shield Generators, Turrets or Engines.// 221 221 ))) ... ... @@ -228,8 +228,11 @@ 228 228 )))|(% colspan="1" %)(% colspan="1" %) 229 229 ((( 230 230 **$ware.illegal** updated 487 +)))|(% colspan="1" %)(% colspan="1" %) 488 +((( 489 + 231 231 ))) 232 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)491 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 233 233 ((( 234 234 //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.// 235 235 //It now returns true if $ware is illegal to any faction in the game.// ... ... @@ -243,8 +243,11 @@ 243 243 )))|(% colspan="1" %)(% colspan="1" %) 244 244 ((( 245 245 MD script **RML_Flight_Along_Path** removed 505 +)))|(% colspan="1" %)(% colspan="1" %) 506 +((( 507 + 246 246 ))) 247 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)509 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 248 248 ((( 249 249 //The MD script RML_Flight_Along_Path was not referened and was removed.// 250 250 ))) ... ... @@ -257,8 +257,11 @@ 257 257 )))|(% colspan="1" %)(% colspan="1" %) 258 258 ((( 259 259 parameters of **<event_venture_mission_completed/>** changed 522 +)))|(% colspan="1" %)(% colspan="1" %) 523 +((( 524 + 260 260 ))) 261 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)526 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 262 262 ((( 263 263 //old params: param = venture details, param2 = ships involved, param3 = duration// 264 264 //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration// ... ... @@ -270,8 +270,11 @@ 270 270 )))|((( 271 271 **<set_object_wing_name/>** removed, 272 272 **<set_object_fleet_name/>** added 538 +)))|(% colspan="1" %)(% colspan="1" %) 539 +((( 540 + 273 273 ))) 274 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)542 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 275 275 ((( 276 276 //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>// 277 277 ))) ... ... @@ -282,12 +282,15 @@ 282 282 )))|((( 283 283 **$controllable.wing.*** removed, 284 284 **$controllable.fleet.*** added 553 +)))|(% colspan="1" %)(% colspan="1" %) 554 +((( 555 + 285 285 ))) 286 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)557 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 287 287 ((( 288 288 $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander 289 289 ))) 290 -|(% colspan=" 3" %)(% colspan="3" %)561 +|(% colspan="4" %)(% colspan="4" %) 291 291 ((( 292 292 == 2.60 == 293 293 ))) ... ... @@ -297,8 +297,11 @@ 297 297 2.60 Beta 1 298 298 )))|((( 299 299 '**checkoperational**' filter behaviour changed 571 +)))|(% colspan="1" %)(% colspan="1" %) 572 +((( 573 + 300 300 ))) 301 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)575 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 302 302 ((( 303 303 //Actions and conditions which use the 'checkoperational' filter now behave differently. Instead of changing how 'class' and 'exactclass' behave, checkoperational == true adds an additional filter for the components being of state operational, equivalent to state="componentstate.operational". This is implicitly enabled in action elements (e.g. <find_.../>) or condition elements (e.g. <count_...>), meaning that find_ship will only find operational ships. Using such actions/conditions with checkoperational="false" will include non-operational components such as wrecked and constructions. Existing uses may find that results now exclude non-operational components.// 304 304 ... ... @@ -310,12 +310,15 @@ 310 310 2.60 Beta 1 311 311 )))|((( 312 312 $container.**supplyresources** behavior changed 587 +)))|(% colspan="1" %)(% colspan="1" %) 588 +((( 589 + 313 313 ))) 314 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)591 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 315 315 ((( 316 316 //The script keyword $container.supplyresources now includes reserved wares.// 317 317 ))) 318 -|(% colspan=" 3" %)(% colspan="3" %)595 +|(% colspan="4" %)(% colspan="4" %) 319 319 ((( 320 320 == 2.20 == 321 321 ))) ... ... @@ -328,8 +328,11 @@ 328 328 )))|(% colspan="1" %)(% colspan="1" %) 329 329 ((( 330 330 **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined. 608 +)))|(% colspan="1" %)(% colspan="1" %) 609 +((( 610 + 331 331 ))) 332 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)612 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 333 333 ((( 334 334 //2.20 Beta 3 introduced the new direct mouse steering mode. The mode was however not integrated as a first level mode and hence GetControllerInfo() returned the "gamepad" mode while direct mouse steering was active. 335 335 In 2.20 Beta 4 we improved the situation slightly so that a call to GetControllerInfo() will return either "mouseCursor" or "mouseSteering" in any of the 3 mouse modes.// ... ... @@ -346,12 +346,15 @@ 346 346 )))|(% colspan="1" %)(% colspan="1" %) 347 347 ((( 348 348 Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor' 629 +)))|(% colspan="1" %)(% colspan="1" %) 630 +((( 631 + 349 349 ))) 350 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)633 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 351 351 ((( 352 352 //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.// 353 353 ))) 354 -|(% colspan=" 3" %)(% colspan="3" %)637 +|(% colspan="4" %)(% colspan="4" %) 355 355 ((( 356 356 == 2.00 == 357 357 ))) ... ... @@ -364,8 +364,11 @@ 364 364 )))|(% colspan="1" %)(% colspan="1" %) 365 365 ((( 366 366 **<event_build_finished/> **param2 now returns null instead of a construction sequence 650 +)))|(% colspan="1" %)(% colspan="1" %) 651 +((( 652 + 367 367 ))) 368 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)654 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 369 369 ((( 370 370 //The construction sequence which was finished should now be accessed via the buildtask provided via param3.// 371 371 ))) ... ... @@ -378,8 +378,11 @@ 378 378 )))|(% colspan="1" %)(% colspan="1" %) 379 379 ((( 380 380 **param.boarding.{...}** strength parameters removed 667 +)))|(% colspan="1" %)(% colspan="1" %) 668 +((( 669 + 381 381 ))) 382 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)671 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 383 383 ((( 384 384 //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.// 385 385 ))) ... ... @@ -392,8 +392,11 @@ 392 392 )))|(% colspan="1" %)(% colspan="1" %) 393 393 ((( 394 394 **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed 684 +)))|(% colspan="1" %)(% colspan="1" %) 685 +((( 686 + 395 395 ))) 396 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)688 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 397 397 ((( 398 398 //Due to changes to boarding in X4, the boarding connections accessed by these script properties and actions became redundent and thus, removed. Any connections set by these actions in a savegame will not survive loading.// 399 399 ))) ... ... @@ -403,8 +403,11 @@ 403 403 2.00 Beta 1 404 404 )))|((( 405 405 **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals 698 +)))|(% colspan="1" %)(% colspan="1" %) 699 +((( 700 + 406 406 ))) 407 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)702 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 408 408 ((( 409 409 //Before 2.0 Beta 1 using GetUpgradeSlotCurrentComponent() or GetUpgradeSlotGroup() only performed on operational objects (i.e. not wrecked objects or objects under construction). Since this is inconsistent with the rest of the UI functions, this was considered a bug and fixed in 2.0 Beta 1. If you require the old behavior, use the FFI function: IsComponentOperational() to check the passed object's state before making the call.// 410 410 ))) ... ... @@ -414,8 +414,11 @@ 414 414 2.00 Beta 1 415 415 )))|((( 416 416 **FFI: SetFormationShape()** no longer indicates an error upon certain error cases 712 +)))|(% colspan="1" %)(% colspan="1" %) 713 +((( 714 + 417 417 ))) 418 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)716 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 419 419 ((( 420 420 //Before 2.0 Beta 1 a call to SetFormationShape() indicated an error state to the caller in certain cases where setting a formation shape (potentially) failed. Due to a design flaw in the handling of formations, this however doesn't do any good, since the function by itself doesn't really set the formation shape in all cases. On top of that the call can fail at random. Hence, at the moment an indication of an error case that setting a formation potentially fails is no good to the caller and he has no means to distinguish that case from a real error case.// 421 421 //Therefore, in 2.0 Beta 1 we drop the error indication in case of an attempt to set the formation fails. We are currently working on a better solution to the underlying problem and hope to have it ready as part of a following beta.// ... ... @@ -426,8 +426,11 @@ 426 426 2.00 Beta 1 427 427 )))|((( 428 428 **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated. 727 +)))|(% colspan="1" %)(% colspan="1" %) 728 +((( 729 + 429 429 ))) 430 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)731 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 431 431 ((( 432 432 //This now enforces a leader and at least one follower in order to create or change a formation. Former implementation made it possible to create formations without any followers which led to issues.// 433 433 ))) ... ... @@ -437,8 +437,11 @@ 437 437 2.00 Beta 1 438 438 )))|((( 439 439 **<event_player_changed_target/>** now fires and returns null if the player deselects a target. 741 +)))|(% colspan="1" %)(% colspan="1" %) 742 +((( 743 + 440 440 ))) 441 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)745 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 442 442 ((( 443 443 //For prior behavior, check for event.param being non-null.// 444 444 ))) ... ... @@ -448,8 +448,11 @@ 448 448 2.00 Beta 1 449 449 )))|((( 450 450 **<shoot/>/<shoot_at/>** attribute changes. 755 +)))|(% colspan="1" %)(% colspan="1" %) 756 +((( 757 + 451 451 ))) 452 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)759 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 453 453 ((( 454 454 //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.// 455 455 //New attribute: "secondary" is an optional attribute that defines whether weapons from the ship's active secondary weapon group will be fired. Defaults to true.// ... ... @@ -463,8 +463,11 @@ 463 463 2.00 Beta 1 464 464 )))|((( 465 465 **FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% class="confluenceTd" %) 773 +)))|(% colspan="1" %)(% colspan="1" %) 774 +((( 775 + 466 466 ))) 467 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)777 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 468 468 ((( 469 469 //Added possibility to query build tasks of a certain buildmodule.// 470 470 ))) ... ... @@ -474,8 +474,11 @@ 474 474 2.00 Beta 1 475 475 )))|((( 476 476 **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field. 787 +)))|(% colspan="1" %)(% colspan="1" %) 788 +((( 789 + 477 477 ))) 478 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)791 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 479 479 ((( 480 480 //Added list of resources a buildmodule needs to build.// 481 481 ))) ... ... @@ -485,8 +485,11 @@ 485 485 2.00 Beta 1 486 486 )))|((( 487 487 (% style="color: rgb(0,0,0);" %)**Lua:**(% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)** CalculateTotalHullFraction()**(% style="color: rgb(0,0,0);" %)** **(%%)was removed.(% style="color: rgb(0,0,0);" %) 801 +)))|(% colspan="1" %)(% colspan="1" %) 802 +((( 803 + 488 488 ))) 489 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)805 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 490 490 ((( 491 491 //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.// 492 492 ))) ... ... @@ -496,12 +496,15 @@ 496 496 2.00 Beta 1 497 497 )))|((( 498 498 **FFI: (% style="color: rgb(0,0,0);" %)RequestDockAtReason()/(% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)UndockPlayerShip()(%%) **changed their return values.(% style="color: rgb(0,0,0);" class="confluenceTd" %) 815 +)))|(% colspan="1" %)(% colspan="1" %) 816 +((( 817 + 499 499 ))) 500 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)819 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 501 501 ((( 502 502 //Changed return value type to const char* to better identify failure reasons in Lua script.// 503 503 ))) 504 -|(% colspan=" 3" %)(% colspan="3" %)823 +|(% colspan="4" %)(% colspan="4" %) 505 505 ((( 506 506 == 1.50 == 507 507 ))) ... ... @@ -511,8 +511,11 @@ 511 511 1.50 Beta 3 512 512 )))|((( 513 513 **Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %) 833 +)))|(% colspan="1" %)(% colspan="1" %) 834 +((( 835 + 514 514 ))) 515 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)837 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 516 516 ((( 517 517 //The "docksizes" property no longer includes internal ship storage docks.// 518 518 ))) ... ... @@ -522,8 +522,11 @@ 522 522 1.50 Beta 2 523 523 )))|((( 524 524 **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR). 847 +)))|(% colspan="1" %)(% colspan="1" %) 848 +((( 849 + 525 525 ))) 526 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)851 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 527 527 ((( 528 528 //Shipyards (formerly also known as Capital Shipyards) can build capital ships, while Wharfs only build non-capital ships. To check whether a station is a Shipyard or a Wharf, check whether the station "can build ships".// 529 529 ... ... @@ -537,8 +537,11 @@ 537 537 1.50 Beta 2 538 538 )))|((( 539 539 **FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %) 865 +)))|(% colspan="1" %)(% colspan="1" %) 866 +((( 867 + 540 540 ))) 541 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)869 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 542 542 ((( 543 543 //Added new "operational" field to retrieve information about number of operational upgrades in a group.// 544 544 ))) ... ... @@ -551,8 +551,11 @@ 551 551 )))|(% colspan="1" %)(% colspan="1" %) 552 552 ((( 553 553 **FFI: SetGuidance()** removed useinfopoint argument. 882 +)))|(% colspan="1" %)(% colspan="1" %) 883 +((( 884 + 554 554 ))) 555 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)886 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 556 556 ((( 557 557 //In X Rebirth "info points" existed (which were mainly used as interaction points to scan stations/access information about modules). These were removed in X4 but this left-over property here was missed to be removed in-time for release. It was therefore removed now in order to move towards a stable/clean UI API. 558 558 // ... ... @@ -565,12 +565,15 @@ 565 565 1.50 Beta 1 566 566 )))|((( 567 567 **FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %) 899 +)))|(% colspan="1" %)(% colspan="1" %) 900 +((( 901 + 568 568 ))) 569 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)903 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 570 570 ((( 571 571 (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. // 572 572 ))) 573 -|(% colspan=" 3" %)(% colspan="3" %)907 +|(% colspan="4" %)(% colspan="4" %) 574 574 ((( 575 575 == 1.32 == 576 576 ))) ... ... @@ -580,12 +580,15 @@ 580 580 1.32 581 581 )))|((( 582 582 **Lua: GetComponentData() **removed the "nextdestname" property. 917 +)))|(% colspan="1" %)(% colspan="1" %) 918 +((( 919 + 583 583 ))) 584 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)921 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 585 585 ((( 586 586 //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.// 587 587 ))) 588 -|(% colspan=" 3" %)(% colspan="3" %)925 +|(% colspan="4" %)(% colspan="4" %) 589 589 ((( 590 590 == 1.20 == 591 591 ))) ... ... @@ -595,8 +595,11 @@ 595 595 1.20 596 596 )))|((( 597 597 **FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %) 935 +)))|(% colspan="1" %)(% colspan="1" %) 936 +((( 937 + 598 598 ))) 599 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)939 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 600 600 ((( 601 601 //The AA setting was changed to check the new setting with the user. In order to restore the old setting (% style="color: rgb(0,0,0);" %)GetAAOption() gets the option to retrieve the config settings.// 602 602 )))
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 - 891323861 +100860788 - url
-
... ... @@ -1,1 +1,1 @@ 1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/ 89132386/Breaking Changes1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/100860788/Breaking Changes