Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 61.1
edited by florian
on 2020/04/30 09:16
Change comment: There is no comment for this version
To version 33.1
edited by stefan
on 2019/06/26 12:02
Change comment: added setup_conversation_minigame note

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.florian
1 +xwiki:XWiki.stefan
Content
... ... @@ -25,193 +25,20 @@
25 25  )))|=(((
26 26  Summary
27 27  )))
28 -|(% colspan="3" %)(% colspan="3" %)
29 -(((
30 -== 3.20 ==
31 -)))
32 -|(((
33 -Scripts
34 -)))|(((
35 -3.20 Beta 1
36 -)))|(((
37 -Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed
38 -)))
39 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
40 -(((
41 -//Old params: param = attacked object, param2 = attack method, param3 = attacked component//
42 -//New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon]
43 -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//
44 -)))
45 -|(((
46 -UI extensions
47 -)))|(((
48 -3.20 Beta 1
49 -)))|(((
50 -**FFI**: Deprecated the following functions: **GetContainerAllowedBuildFactions()**, **GetNumContainerAllowedBuildFactions()**, **IsContainerFactionBuildRescricted()**, **IsContainerFactionTradeRescricted()**, **SetContainerBuildAllowedFactions()**, **SetContainerFactionBuildRescricted()**
51 -)))
52 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
53 -(((
54 -With the addition of the Trade Rule feature the given functions are considered deprecated and should not be used anymore. Consider GetAllTradeRules(), GetContainerTradeRuleID(), SetContainerTradeRule() and similar trade rule functions for replacement.
55 -)))
56 -|(((
57 -UI extensions
58 -)))|(((
59 -3.20 Beta 1
60 -)))|(((
61 -**Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete!
62 -)))
63 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
64 -(((
65 -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.
66 -)))
67 -|(% colspan="3" %)(% colspan="3" %)
68 -(((
69 -== 3.10 ==
70 -)))
71 71  |(% colspan="1" %)(% colspan="1" %)
72 72  (((
73 73  Scripts
74 74  )))|(% colspan="1" %)(% colspan="1" %)
75 75  (((
76 -3.10 Beta 1
77 -)))|(% colspan="1" %)(% colspan="1" %)
78 -(((
79 -Removed script action **<add_build/>**
80 -)))
81 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
82 -(((
83 -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.
84 -)))
85 -|(% colspan="3" %)(% colspan="3" %)
86 -(((
87 -== 3.00 ==
88 -)))
89 -|(% colspan="1" %)(% colspan="1" %)
90 -(((
91 -Scripts
92 -)))|(% colspan="1" %)(% colspan="1" %)
93 -(((
94 -3.0 Beta 6
95 -)))|(% colspan="1" %)(% colspan="1" %)
96 -(((
97 -Changed behaviour of script action **<get_suitable_job/>**
98 -)))
99 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
100 -(((
101 -<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.
102 -)))
103 -|(% colspan="1" %)(% colspan="1" %)
104 -(((
105 -Scripts
106 -)))|(% colspan="1" %)(% colspan="1" %)
107 -(((
108 -3.0 Beta 6
109 -)))|(% colspan="1" %)(% colspan="1" %)
110 -(((
111 -Changed behaviour of script action **<get_ware_definition/>**
112 -)))
113 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
114 -(((
115 -//<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.//
116 -)))
117 -|(% colspan="1" %)(% colspan="1" %)
118 -(((
119 -Global
120 -)))|(% colspan="1" %)(% colspan="1" %)
121 -(((
122 -3.0 Beta 5
123 -)))|(% colspan="1" %)(% colspan="1" %)
124 -(((
125 -Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case
126 -)))
127 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
128 -(((
129 -//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.)\\
130 -
131 -//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).//
132 -)))
133 -|(% colspan="1" %)(% colspan="1" %)
134 -(((
135 -Scripts
136 -)))|(% colspan="1" %)(% colspan="1" %)
137 -(((
138 -3.0 Beta 5
139 -)))|(% colspan="1" %)(% colspan="1" %)
140 -(((
141 -Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions>
142 -)))
143 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
144 -(((
145 -//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.//
146 -)))
147 -|(% colspan="1" %)(% colspan="1" %)
148 -(((
149 -Scripts
150 -)))|(% colspan="1" %)(% colspan="1" %)
151 -(((
152 -3.0 Beta 5
153 -)))|(% colspan="1" %)(% colspan="1" %)
154 -(((
155 -Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos**
156 -)))
157 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
158 -(((
159 -//Before the change, positions are relative to $dockingbay.parent.
160 -After the change, positions are relative to $dockingbay as specified in the documentation.//
161 -)))
162 -|(% colspan="1" %)(% colspan="1" %)
163 -(((
164 -Global
165 -)))|(% colspan="1" %)(% colspan="1" %)
166 -(((
167 -3.0 Beta 2
168 -)))|(% colspan="1" %)(% colspan="1" %)
169 -(((
170 -Support for entity flag "**skillsvisible**" dropped
171 -)))
172 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
173 -(((
174 -//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().//
175 -)))
176 -|(((
177 -Scripts
178 -)))|(((
179 -3.0 Beta 2
180 -)))|(((
181 -Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**.
182 -)))
183 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
184 -(((
185 -//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.
186 -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.
187 -If in your scripts you make use of the <event_object_changed_owner> condition you need to verify that you indeed want to work with the "effective" component owner or whether your script code actually should work with the true owner of an object and update your code accordingly.
188 -On top of that the 3rd parameter of <event_object_changed_owner> (trueprevious) was dropped as the event is no longer triggered upon a change of the true owner alone (i.e. only if the change of the true owner has also an effect on the "effective" component owner).
189 -)))
190 -|(% colspan="1" %)(% colspan="1" %)
191 -(((
192 -Global
193 -)))|(% colspan="1" %)(% colspan="1" %)
194 -(((
195 195  3.0 Beta 1
196 196  )))|(% colspan="1" %)(% colspan="1" %)
197 197  (((
198 -**MissionBoard** support dropped
36 +<setup_conversation_minigame/> script action removed
199 199  )))
200 200  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
201 201  (((
202 -//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.//
40 +//The script action was a left over 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.//
203 203  )))
204 -|(((
205 -Job/God
206 -)))|(((
207 -3.0 Beta 1
208 -)))|(((
209 -By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined
210 -)))
211 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
212 -(((
213 -//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.//
214 -)))
215 215  |(% colspan="1" %)(% colspan="1" %)
216 216  (((
217 217  Scripts
... ... @@ -220,94 +220,10 @@
220 220  3.0 Beta 1
221 221  )))|(% colspan="1" %)(% colspan="1" %)
222 222  (((
223 -Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'**
50 +<hack_via_control_panel/> script action removed
224 224  )))
225 225  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
226 226  (((
227 -//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.//
228 -)))
229 -|(% colspan="1" %)(% colspan="1" %)
230 -(((
231 -Scripts
232 -)))|(% colspan="1" %)(% colspan="1" %)
233 -(((
234 -3.0 Beta 1
235 -)))|(% colspan="1" %)(% colspan="1" %)
236 -(((
237 -Script action **<set_doors_locked/>** attribute **'group'** changed
238 -)))
239 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
240 -(((
241 -//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.//
242 -)))
243 -|(% colspan="1" %)(% colspan="1" %)
244 -(((
245 -Scripts
246 -)))|(% colspan="1" %)(% colspan="1" %)
247 -(((
248 -3.0 Beta 1
249 -)))|(% colspan="1" %)(% colspan="1" %)
250 -(((
251 -Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed
252 -)))
253 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
254 -(((
255 -//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.//
256 -)))
257 -|(% colspan="1" %)(% colspan="1" %)
258 -(((
259 -Scripts
260 -)))|(% colspan="1" %)(% colspan="1" %)
261 -(((
262 -3.0 Beta 1
263 -)))|(% colspan="1" %)(% colspan="1" %)
264 -(((
265 -Script actions **<set_hack_target/>** and **<abort_hack/>** removed
266 -)))
267 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
268 -(((
269 -//These actions had no effect and were removed.//
270 -)))
271 -|(% colspan="1" %)(% colspan="1" %)
272 -(((
273 -Scripts
274 -)))|(% colspan="1" %)(% colspan="1" %)
275 -(((
276 -3.0 Beta 1
277 -)))|(% colspan="1" %)(% colspan="1" %)
278 -(((
279 -**<setup_conversation_minigame/>** script action removed
280 -)))
281 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
282 -(((
283 -//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.//
284 -)))
285 -|(% colspan="1" %)(% colspan="1" %)
286 -(((
287 -Scripts
288 -)))|(% colspan="1" %)(% colspan="1" %)
289 -(((
290 -3.0 Beta 1
291 -)))|(% colspan="1" %)(% colspan="1" %)
292 -(((
293 -<add_player_choice_*> **confidence** attribute removed
294 -)))
295 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
296 -(((
297 -//The default confidence of player options is another leftover from the XR era and had no effect in X4.//
298 -)))
299 -|(% colspan="1" %)(% colspan="1" %)
300 -(((
301 -Scripts
302 -)))|(% colspan="1" %)(% colspan="1" %)
303 -(((
304 -3.0 Beta 1
305 -)))|(% colspan="1" %)(% colspan="1" %)
306 -(((
307 -**<hack_via_control_panel/>** script action removed
308 -)))
309 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
310 -(((
311 311  //Unused script action <hack_via_control_panel/> was removed.//
312 312  )))
313 313  |(% colspan="1" %)(% colspan="1" %)
... ... @@ -324,30 +324,20 @@
324 324  (((
325 325  //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.//
326 326  )))
327 -|(((
328 -UI core
329 -)))|(((
330 -3.0 Beta 1
331 -)))|(((
332 -**FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders
333 -)))
334 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
335 -(((
336 -//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.//
337 -)))
338 338  |(% colspan="1" %)(% colspan="1" %)
339 339  (((
340 -UI extensions
72 +Scripts
341 341  )))|(% colspan="1" %)(% colspan="1" %)
342 342  (((
343 343  3.0 Beta 1
344 344  )))|(% colspan="1" %)(% colspan="1" %)
345 345  (((
346 -**FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor
78 +$ware.illegal updated
347 347  )))
348 348  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
349 349  (((
350 -//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.//
82 +$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.
83 +\\It now returns true if $ware is illegal to any faction in the game.
351 351  )))
352 352  |(% colspan="1" %)(% colspan="1" %)
353 353  (((
... ... @@ -357,12 +357,13 @@
357 357  3.0 Beta 1
358 358  )))|(% colspan="1" %)(% colspan="1" %)
359 359  (((
360 -**$ware.illegal** updated
93 +'checkoperational' filter behaviour changed
361 361  )))
362 362  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
363 363  (((
364 -//$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.//
365 -//It now returns true if $ware is illegal to any faction in the game.//
97 +//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.//
98 +
99 +//Sub nodes such as match_child will have checkoperational default to false. Existing uses may find that results now include non-operational components.//
366 366  )))
367 367  |(% colspan="1" %)(% colspan="1" %)
368 368  (((
... ... @@ -380,77 +380,6 @@
380 380  )))
381 381  |(% colspan="1" %)(% colspan="1" %)
382 382  (((
383 -Scripts
384 -)))|(% colspan="1" %)(% colspan="1" %)
385 -(((
386 -3.0 Beta 1
387 -)))|(% colspan="1" %)(% colspan="1" %)
388 -(((
389 -parameters of **<event_venture_mission_completed/>** changed
390 -)))
391 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
392 -(((
393 -//old params: param = venture details, param2 = ships involved, param3 = duration//
394 -//new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration//
395 -)))
396 -|(((
397 -Scripts
398 -)))|(((
399 -3.0 Beta 1
400 -)))|(((
401 -**<set_object_wing_name/>** removed,
402 -**<set_object_fleet_name/>** added
403 -)))
404 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
405 -(((
406 -//The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>//
407 -)))
408 -|(((
409 -Scripts
410 -)))|(((
411 -3.0 Beta 1
412 -)))|(((
413 -**$controllable.wing.*** removed,
414 -**$controllable.fleet.*** added
415 -)))
416 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
417 -(((
418 -$controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander
419 -)))
420 -|(% colspan="3" %)(% colspan="3" %)
421 -(((
422 -== 2.60 ==
423 -)))
424 -|(((
425 -Scripts
426 -)))|(((
427 -2.60 Beta 1
428 -)))|(((
429 -'**checkoperational**' filter behaviour changed
430 -)))
431 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
432 -(((
433 -//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.//
434 -
435 -//Sub nodes such as match_child will have checkoperational default to false. Existing uses may find that results now include non-operational components.//
436 -)))
437 -|(((
438 -Scripts
439 -)))|(((
440 -2.60 Beta 1
441 -)))|(((
442 -$container.**supplyresources** behavior changed
443 -)))
444 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
445 -(((
446 -//The script keyword $container.supplyresources now includes reserved wares.//
447 -)))
448 -|(% colspan="3" %)(% colspan="3" %)
449 -(((
450 -== 2.20 ==
451 -)))
452 -|(% colspan="1" %)(% colspan="1" %)
453 -(((
454 454  UI core
455 455  )))|(% colspan="1" %)(% colspan="1" %)
456 456  (((
... ... @@ -481,10 +481,6 @@
481 481  (((
482 482  //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.//
483 483  )))
484 -|(% colspan="3" %)(% colspan="3" %)
485 -(((
486 -== 2.00 ==
487 -)))
488 488  |(% colspan="1" %)(% colspan="1" %)
489 489  (((
490 490  Scripts
... ... @@ -631,10 +631,6 @@
631 631  (((
632 632  //Changed return value type to const char* to better identify failure reasons in Lua script.//
633 633  )))
634 -|(% colspan="3" %)(% colspan="3" %)
635 -(((
636 -== 1.50 ==
637 -)))
638 638  |(((
639 639  UI extensions
640 640  )))|(((
... ... @@ -700,10 +700,6 @@
700 700  (((
701 701  (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. //
702 702  )))
703 -|(% colspan="3" %)(% colspan="3" %)
704 -(((
705 -== 1.32 ==
706 -)))
707 707  |(((
708 708  UI extensions
709 709  )))|(((
... ... @@ -715,10 +715,6 @@
715 715  (((
716 716  //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.//
717 717  )))
718 -|(% colspan="3" %)(% colspan="3" %)
719 -(((
720 -== 1.20 ==
721 -)))
722 722  |(((
723 723  UI extensions
724 724  )))|(((
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -91947560
1 +83460874
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/91947560/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/83460874/Breaking Changes