Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 54.1
edited by klaus
on 2020/01/14 19:05
Change comment: There is no comment for this version
To version 97.1
edited by klaus
on 2023/01/04 13:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -18,6 +18,7 @@
18 18  
19 19  = Breaking Changes =
20 20  
21 +(% class="wrapped" %)
21 21  |=(((
22 22  Type
23 23  )))|=(((
... ... @@ -27,23 +27,378 @@
27 27  )))
28 28  |(% colspan="3" %)(% colspan="3" %)
29 29  (((
31 +== 6.00 ==
32 +)))
33 +|(((
34 +Assets
35 +)))|(((
36 +6.00 Beta 1
37 +)))|(((
38 +Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons
39 +)))
40 +|(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)
41 +(((
42 +//Connection tags used to specify compatibilities in component templates between a ship or station module and engines or shields now additionally require the use of the "standard" tag matching weapon or turret logic. For weapons that are neither Missile Launcher nor Mining Laser, the tag "combat" is also required.
43 +Exception: special equipment that is deliberately not compatible with the majority of slots may use another tag instead of "standard", e.g. "highpower" for certain Terran weapons.//
44 +)))
45 +|(% colspan="1" %)(% colspan="1" %)
46 +(((
47 +Scripts
48 +)))|(% colspan="1" %)(% colspan="1" %)
49 +(((
50 +6.00 Beta 1
51 +)))|(% colspan="1" %)(% colspan="1" %)
52 +(((
53 +Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects
54 +)))
55 +|(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)
56 +(((
57 +//When finding components with attribute "sortbygatedistanceto", e.g. in <find_object>, any objects with a negative gatedistance (i.e. unreachable objects) are automatically excluded from the result.//
58 +)))
59 +|(((
60 +Scripts
61 +)))|(((
62 +6.00 Beta 1
63 +)))|(((
64 +**<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards.
65 +)))
66 +|(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)
67 +(((
68 +//The order of events was adjusted, allowing handlers of <event_player_owned_killed_object> and <event_player_owned_destroyed> to access commander/subordinate relationship of the destroyed object.//
69 +)))
70 +|(% colspan="3" %)(% colspan="3" %)
71 +(((
72 +== 5.00 ==
73 +)))
74 +|(((
75 +Parameters
76 +)))|(((
77 +5.00 Beta 1
78 +)))|(((
79 +**<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration
80 +)))
81 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
82 +(((
83 +//'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.//
84 +)))
85 +|(% colspan="3" %)(% colspan="3" %)
86 +(((
87 +== 4.10 ==
88 +)))
89 +|(% colspan="1" %)(% colspan="1" %)
90 +(((
91 +UI extensions
92 +)))|(% colspan="1" %)(% colspan="1" %)
93 +(((
94 +4.10 Beta 7
95 +)))|(% colspan="1" %)(% colspan="1" %)
96 +(((
97 +**FFI**: (% style="color: rgb(0,0,0);" %)SetMapRenderCargoContents(%%)(), (% style="color: rgb(0,0,0);" %)SetMapRenderWorkForceInfo(), (% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)SetMapRenderCrewInfo() and (% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)SetMapRenderDockedShipInfos()(%%) deprecated
98 +)))
99 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
100 +(((
101 +//The functionality represented by (% style="color: rgb(0,0,0);" %)SetMapRenderCargoContents(%%)(), (% style="color: rgb(0,0,0);" %)SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos()(%%) has been removed and the function was therefore stubbed.//
102 +)))
103 +|(% colspan="1" %)(% colspan="1" %)
104 +(((
105 +UI extensions
106 +)))|(% colspan="1" %)(% colspan="1" %)
107 +(((
108 +4.10 Beta 6
109 +)))|(% colspan="1" %)(% colspan="1" %)
110 +(((
111 +**FFI**: CustomGameStartPlayerProperty2 changed
112 +)))
113 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
114 +(((
115 +//This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.//
116 +)))
117 +|(% colspan="1" %)(% colspan="1" %)
118 +(((
119 +Parameters
120 +)))|(% colspan="1" %)(% colspan="1" %)
121 +(((
122 +4.10 Beta 3
123 +)))|(% colspan="1" %)(% colspan="1" %)
124 +(((
125 +Renamed **<stationinfobox>** to **<infobox>**
126 +)))
127 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
128 +(((
129 +//Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.//
130 +)))
131 +|(% colspan="1" %)(% colspan="1" %)
132 +(((
133 +UI extensions
134 +)))|(% colspan="1" %)(% colspan="1" %)
135 +(((
136 +4.10 Beta 2
137 +)))|(% colspan="1" %)(% colspan="1" %)
138 +(((
139 +**FFI**: SetMacroMapPlayerSectorOffset() deprecated
140 +)))
141 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
142 +(((
143 +//The functionality represented by SetMacroMapPlayerSectorOffset() has been removed and the function was therefore stubbed. Setting the gamestart properties "sector" and "offset" will affect the universe macro map instead directly.//
144 +)))
145 +|(((
146 +UI extensions
147 +)))|(((
148 +4.10 Beta 2
149 +)))|(((
150 +**FFI**: (% style="color: rgb(0,0,0);" %)FilterComponentForMapMode(%%)() and (% style="color: rgb(0,0,0);" %)SetMapObjectFilter() changed
151 +)))
152 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
153 +(((
154 +//These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.//
155 +)))
156 +|(((
157 +Scripts
158 +)))|(((
159 +4.10 Beta 1
160 +)))|(((
161 +People related attributes of mission** <delivery> **node moved
162 +)))
163 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
164 +(((
165 +//The <delivery> node of <create_mission> and <update_mission> has been changed to support a new <wares> subnode. The people related attributes: 'people' and 'skills' have been moved from the <delivery> node itself to a <people> subnode.//
166 +)))
167 +|(% colspan="1" %)(% colspan="1" %)
168 +(((
169 +Scripts
170 +)))|(% colspan="1" %)(% colspan="1" %)
171 +(((
172 +4.10 Beta 1
173 +)))|(% colspan="1" %)(% colspan="1" %)
174 +(((
175 +**$destructible.productions** replaced with $defensible.productions
176 +)))
177 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
178 +(((
179 +//The $destructible.productions script property was removed and reimplemented as $defensible.productions meaning some old uses may no longer work unless the destructible is also a defensible. The old implementation functioned by finding the containing object of the destructible (including itself) to query for the production modules.//
180 +)))
181 +|(((
182 +Scripts
183 +)))|(((
184 +4.10 Beta 1
185 +)))|(((
186 +Removed script property **$object.spawnsourceseed**
187 +)))
188 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
189 +(((
190 +//The spawnsource seed is no longer directly accessible by scripts. Use $component.seed, which will internally use the spawnsource seed if able. Note: An improvement is that .seed on objects without a spawnsource seed will now result in a value that differs between objects of the same macro, meaning it can now reliably be used for player property or job ships.//
191 +)))
192 +|(% colspan="3" %)(% colspan="3" %)
193 +(((
194 +== 4.00 ==
195 +)))
196 +|(% colspan="1" %)(% colspan="1" %)
197 +(((
198 +UI core
199 +)))|(% colspan="1" %)(% colspan="1" %)
200 +(((
201 +4.00 Beta 10
202 +)))|(% colspan="1" %)(% colspan="1" %)
203 +(((
204 +Controlled ship can change without a **gameplanchange-event** occurring.
205 +)))
206 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
207 +(((
208 +//Before 4.00 Beta 10 it was ensured that there is no direct transition between the 'cockpit ui mode' of one ship to another. Instead, it was always ensured that the UI first transitions into the firstperson mode and then back into the cockpit mode (controlling then the other ship).
209 +In order to support the new emergency eject feature which was added in 4.00 Beta 7, this assurance was dropped. As of 4.00 Beta 10 it is now possible that the ship the player controls can swap without the gameplanchange-event being risen which one could rely upon in previous versions. If your addon relied on the fact that the ship would not change without first going into first person mode, you will have to adjust your addon accordingly.
210 +//
211 +)))
212 +|(((
213 +Scripts
214 +)))|(((
215 +4.00 Beta 7
216 +)))|(((
217 +Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed
218 +)))
219 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
220 +(((
221 +//Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects?
222 +New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits
223 +Note: param3 only exists in <event_terraforming_project_succeeded> and not in <event_terraforming_project_failed>, but both now have the booleans in a list for consistency//
224 +)))
225 +|(% colspan="1" %)(% colspan="1" %)
226 +(((
227 +UI core
228 +)))|(% colspan="1" %)(% colspan="1" %)
229 +(((
230 +4.00 Beta 6
231 +)))|(% colspan="1" %)(% colspan="1" %)
232 +(((
233 +**FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed
234 +)))
235 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
236 +(((
237 +//In order to keep consistency with regards to the new behvior 'hostile' relation state and the older (deprecated) UI functions, the behavior of the deprecated GetFactionRelationStatus() function was changed according to the behavior of the GetRelationStatus()/GetRelationStatus2() functions which was done in the previous beta.
238 +Factions with a relation rating between -20 and -10 will now report a relation status of 'neutral' (aka: 1) instead of 'hostile'/'enemy' (aka: 0).//
239 +
240 +//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.
241 +//
242 +)))
243 +|(% colspan="1" %)(% colspan="1" %)
244 +(((
245 +UI core
246 +)))|(% colspan="1" %)(% colspan="1" %)
247 +(((
248 +4.00 Beta 5
249 +)))|(% colspan="1" %)(% colspan="1" %)
250 +(((
251 +**FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed
252 +)))
253 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
254 +(((
255 +//4.00 Beta 5// //introduces a new 'hostile' relation status and the game now distinguishes between hostile and enemy relation states. Objects not yet 'hostile' with the player are now visualized differently and therefore distinguishable from real hostile ones. Because of that, several related changes were made for these objects to bring them more in line with how 'neutral' objects behave (f.e. no automatic attacking of these objects by the player property anymore, no target selection when targeting the closest enemy, etc.). To reflect this, these objects are now returning 1 (neutral) as the relation status by the GetRelationStatus()/GetRelationStatus2() functions.//
256 +
257 +//If you rely on a handling where they are treated like enemies, please use the new GetRelationStatus3() //function which returns the new range for these objects: 1 (meaning 'enemy' (aka: not yet hostile) here with following relations having been shifted up).
258 +)))
259 +|(((
260 +Parameters
261 +)))|(((
262 +4.00 Beta 1
263 +)))|(((
264 +**requiresconstructionvessel** parameter moved
265 +)))
266 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
267 +(((
268 +//The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.//
269 +)))
270 +|(((
271 +Scripts
272 +)))|(((
273 +4.00 Beta 1
274 +)))|(((
275 +Changed behaviour of **gatedistance** script property
276 +)))
277 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
278 +(((
279 +//The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.//
280 +)))
281 +|(% colspan="3" %)(% colspan="3" %)
282 +(((
283 +== 3.30 ==
284 +)))
285 +|(((
286 +UI extensions
287 +)))|(((
288 +3.30 Beta 3
289 +)))|(((
290 +**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()**
291 +)))
292 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
293 +(((
294 +//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()//
295 +)))
296 +|(% colspan="3" %)(% colspan="3" %)
297 +(((
298 +== 3.20 ==
299 +)))
300 +|(((
301 +Scripts
302 +)))|(((
303 +3.20 Beta 1
304 +)))|(((
305 +Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed
306 +)))
307 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
308 +(((
309 +//Old params: param = attacked object, param2 = attack method, param3 = attacked component//
310 +//New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon]
311 +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//
312 +)))
313 +|(% colspan="1" %)(% colspan="1" %)
314 +(((
315 +Scripts
316 +)))|(% colspan="1" %)(% colspan="1" %)
317 +(((
318 +3.20 Beta 1
319 +)))|(% colspan="1" %)(% colspan="1" %)
320 +(((
321 +Removed script property $trade.**restriction.faction**
322 +)))
323 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
324 +(((
325 +//$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.//
326 +)))
327 +|(((
328 +UI extensions
329 +)))|(((
330 +3.20 Beta 1
331 +)))|(((
332 +**Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete!
333 +)))
334 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
335 +(((
336 +//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.//
337 +)))
338 +|(% colspan="3" %)(% colspan="3" %)
339 +(((
340 +== 3.10 ==
341 +)))
342 +|(% colspan="1" %)(% colspan="1" %)
343 +(((
344 +Scripts
345 +)))|(% colspan="1" %)(% colspan="1" %)
346 +(((
347 +3.10 Beta 1
348 +)))|(% colspan="1" %)(% colspan="1" %)
349 +(((
350 +Removed script action **<add_build/>**
351 +)))
352 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
353 +(((
354 +//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.//
355 +)))
356 +|(% colspan="3" %)(% colspan="3" %)
357 +(((
30 30  == 3.00 ==
31 31  )))
32 32  |(% colspan="1" %)(% colspan="1" %)
33 33  (((
34 -MD Scripts, Cutscenes
362 +Scripts
35 35  )))|(% colspan="1" %)(% colspan="1" %)
36 36  (((
365 +3.0 Beta 6
366 +)))|(% colspan="1" %)(% colspan="1" %)
367 +(((
368 +Changed behaviour of script action **<get_suitable_job/>**
369 +)))
370 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
371 +(((
372 +//<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.//
373 +)))
374 +|(% colspan="1" %)(% colspan="1" %)
375 +(((
376 +Scripts
377 +)))|(% colspan="1" %)(% colspan="1" %)
378 +(((
379 +3.0 Beta 6
380 +)))|(% colspan="1" %)(% colspan="1" %)
381 +(((
382 +Changed behaviour of script action **<get_ware_definition/>**
383 +)))
384 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
385 +(((
386 +//<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.//
387 +)))
388 +|(% colspan="1" %)(% colspan="1" %)
389 +(((
390 +Global
391 +)))|(% colspan="1" %)(% colspan="1" %)
392 +(((
37 37  3.0 Beta 5
38 38  )))|(% colspan="1" %)(% colspan="1" %)
39 39  (((
40 -Renamed all files in the **md** and **cutscenes** folders to lower-case
396 +Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case
41 41  )))
42 42  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
43 43  (((
44 -//All MD 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.)\\
400 +//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.)\\
45 45  
46 -//Note that this change has no effect on the actual content of scripts or cutscenes. The 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).//
402 +//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).//
47 47  )))
48 48  |(% colspan="1" %)(% colspan="1" %)
49 49  (((
... ... @@ -507,7 +507,7 @@
507 507  )))|(((
508 508  2.00 Beta 1
509 509  )))|(((
510 -**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% class="confluenceTd" %)
866 +**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.
511 511  )))
512 512  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
513 513  (((
... ... @@ -540,7 +540,7 @@
540 540  )))|(((
541 541  2.00 Beta 1
542 542  )))|(((
543 -**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" %)
899 +**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.
544 544  )))
545 545  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
546 546  (((
... ... @@ -555,7 +555,7 @@
555 555  )))|(((
556 556  1.50 Beta 3
557 557  )))|(((
558 -**Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %)
914 +**Lua: GetComponentData() **changed behavior of "docksizes" property.
559 559  )))
560 560  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
561 561  (((
... ... @@ -581,7 +581,7 @@
581 581  )))|(((
582 582  1.50 Beta 2
583 583  )))|(((
584 -**FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %)
940 +**FFI: UpgradeGroupInfo **datatype was changed.
585 585  )))
586 586  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
587 587  (((
... ... @@ -609,7 +609,7 @@
609 609  )))|(((
610 610  1.50 Beta 1
611 611  )))|(((
612 -**FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %)
968 +**FFI: CancelConstruction() **changed its return value.
613 613  )))
614 614  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
615 615  (((
... ... @@ -639,7 +639,7 @@
639 639  )))|(((
640 640  1.20
641 641  )))|(((
642 -**FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %)
998 +**FFI: GetAAOption()** got a new "useconfig" parameter.
643 643  )))
644 644  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
645 645  (((
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -89818026
1 +135856732
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/89818026/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/135856732/Breaking Changes