Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 64.1
edited by florian
on 2020/05/04 10:53
Change comment: There is no comment for this version
To version 104.5
edited by Volodymyr Boichuk
on 2023/08/15 12:09
Change comment: Update document after refactoring.

Summary

Details

Page properties
Parent
... ... @@ -1,0 +1,1 @@
1 +X4 Foundations Wiki.Modding Support.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.florian
1 +xwiki:XWiki.Volodymyr
Content
... ... @@ -18,6 +18,7 @@
18 18  
19 19  = Breaking Changes =
20 20  
21 +(% class="wrapped" %)
21 21  |=(((
22 22  Type
23 23  )))|=(((
... ... @@ -27,6 +27,361 @@
27 27  )))
28 28  |(% colspan="3" %)(% colspan="3" %)
29 29  (((
31 +== 6.00 ==
32 +)))
33 +|(((
34 +Libraries
35 +)))|(((
36 +6.00 Beta 7
37 +)))|(((
38 +Updated weights for ship groups in shipgroups.xml libraries of base game and all DLCs.
39 +)))
40 +|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
41 +(((
42 +//Previously some entries were lacking "weight" parameter, causing it to default to "1", which prevent adding new ships to the group with appropriate/configurable granularity.
43 +//
44 +
45 +//All groups should now have "weight" parameter added and old "weights" were updated to not have single-digit numbers.//
46 +)))
47 +|(% colspan="1" %)(% colspan="1" %)
48 +(((
49 +Scripts
50 +)))|(% colspan="1" %)(% colspan="1" %)
51 +(((
52 +6.00 Beta 4
53 +)))|(% colspan="1" %)(% colspan="1" %)
54 +(((
55 +Changed conditions for **<event_player_travelmode_started> <event_player_travelmode_stopped> <event_player_travelmode_charge_started> <event_player_travelmode_charge_aborted>** to be raised.
56 +)))
57 +|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
58 +(((
59 +//The <event_player_travelmode_started>, <event_player_travelmode_stopped>, <event_player_travelmode_charge_started> and <event_player_travelmode_charge_aborted> events will no longer be raised if the player is a passenger on board a ship which enters or leaves travel mode. Previously these events would be raised whether the player was the pilot or a passenger. //
60 +
61 +//Scripts that need to check whether the player exits travel mode may also need to consider checking whether the player leaves the control seat using <event_player_stopped_control> since this will also result in travel mode stopping.//
62 +)))
63 +|(% colspan="1" %)(% colspan="1" %)
64 +(((
65 +Scripts
66 +)))|(% colspan="1" %)(% colspan="1" %)
67 +(((
68 +6.00 Beta 3
69 +)))|(% colspan="1" %)(% colspan="1" %)
70 +(((
71 +Changed result of **<find_object_surface>** action in the case of a failure
72 +)))
73 +|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
74 +(((
75 +//The 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.//
76 +
77 +//Previously, it returned null only if there was a physics error. It however returned a valid, somewhat-random, position if physics were fine but it was still unable to find a suitable surface position. This position was often unsuitable to use for gameplay purposes so it is now null so the caller can handle the situation.//
78 +
79 +//The action itself has been improved to increase the chance of finding suitable surface positions.//
80 +)))
81 +|(% colspan="1" %)(% colspan="1" %)
82 +(((
83 +Scripts
84 +)))|(% colspan="1" %)(% colspan="1" %)
85 +(((
86 +6.00 Beta 1
87 +)))|(% colspan="1" %)(% colspan="1" %)
88 +(((
89 +Behaviour change for **<match_dock>** script component filter
90 +)))
91 +|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
92 +(((
93 +//<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes.
94 +This has introduced a new potential pitfall: If finding or counting contained components be wary that there may be multiple positive results, even if there is only one dockingbay. e.g. matching contents for a station will include the dockingbay but also its containing walkable module as that also contains the dockingbay. To only account for docking bays, also filter by dockingbay class.//
95 +)))
96 +|(% colspan="1" %)(% colspan="1" %)
97 +(((
98 +Scripts
99 +)))|(% colspan="1" %)(% colspan="1" %)
100 +(((
101 +6.00 Beta 1
102 +)))|(% colspan="1" %)(% colspan="1" %)
103 +(((
104 +Changed result attribute location for **<get_attackstrength>**
105 +)))
106 +|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
107 +(((
108 +//The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.//
109 +)))
110 +|(((
111 +Assets
112 +)))|(((
113 +6.00 Beta 1
114 +)))|(((
115 +Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons
116 +)))
117 +|(% 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" %)
118 +(((
119 +//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.
120 +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.//
121 +)))
122 +|(% colspan="1" %)(% colspan="1" %)
123 +(((
124 +Scripts
125 +)))|(% colspan="1" %)(% colspan="1" %)
126 +(((
127 +6.00 Beta 1
128 +)))|(% colspan="1" %)(% colspan="1" %)
129 +(((
130 +Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects
131 +)))
132 +|(% 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" %)
133 +(((
134 +//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.//
135 +)))
136 +|(((
137 +Scripts
138 +)))|(((
139 +6.00 Beta 1
140 +)))|(((
141 +**<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards.
142 +)))
143 +|(% 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" %)
144 +(((
145 +//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.//
146 +)))
147 +|(((
148 +Cutscenes
149 +)))|(((
150 +6.00 Beta 1
151 +)))|(((
152 +Changed behaviour of **<angles>** in cutscenes
153 +)))
154 +|(% 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" %)
155 +(((
156 +//The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.//
157 +)))
158 +|(% colspan="3" %)(% colspan="3" %)
159 +(((
160 +== 5.00 ==
161 +)))
162 +|(((
163 +Parameters
164 +)))|(((
165 +5.00 Beta 1
166 +)))|(((
167 +**<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration
168 +)))
169 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
170 +(((
171 +//'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.//
172 +)))
173 +|(% colspan="3" %)(% colspan="3" %)
174 +(((
175 +== 4.10 ==
176 +)))
177 +|(% colspan="1" %)(% colspan="1" %)
178 +(((
179 +UI extensions
180 +)))|(% colspan="1" %)(% colspan="1" %)
181 +(((
182 +4.10 Beta 7
183 +)))|(% colspan="1" %)(% colspan="1" %)
184 +(((
185 +**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
186 +)))
187 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
188 +(((
189 +//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.//
190 +)))
191 +|(% colspan="1" %)(% colspan="1" %)
192 +(((
193 +UI extensions
194 +)))|(% colspan="1" %)(% colspan="1" %)
195 +(((
196 +4.10 Beta 6
197 +)))|(% colspan="1" %)(% colspan="1" %)
198 +(((
199 +**FFI**: CustomGameStartPlayerProperty2 changed
200 +)))
201 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
202 +(((
203 +//This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.//
204 +)))
205 +|(% colspan="1" %)(% colspan="1" %)
206 +(((
207 +Parameters
208 +)))|(% colspan="1" %)(% colspan="1" %)
209 +(((
210 +4.10 Beta 3
211 +)))|(% colspan="1" %)(% colspan="1" %)
212 +(((
213 +Renamed **<stationinfobox>** to **<infobox>**
214 +)))
215 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
216 +(((
217 +//Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.//
218 +)))
219 +|(% colspan="1" %)(% colspan="1" %)
220 +(((
221 +UI extensions
222 +)))|(% colspan="1" %)(% colspan="1" %)
223 +(((
224 +4.10 Beta 2
225 +)))|(% colspan="1" %)(% colspan="1" %)
226 +(((
227 +**FFI**: SetMacroMapPlayerSectorOffset() deprecated
228 +)))
229 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
230 +(((
231 +//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.//
232 +)))
233 +|(((
234 +UI extensions
235 +)))|(((
236 +4.10 Beta 2
237 +)))|(((
238 +**FFI**: (% style="color: rgb(0,0,0);" %)FilterComponentForMapMode(%%)() and (% style="color: rgb(0,0,0);" %)SetMapObjectFilter() changed
239 +)))
240 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
241 +(((
242 +//These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.//
243 +)))
244 +|(((
245 +Scripts
246 +)))|(((
247 +4.10 Beta 1
248 +)))|(((
249 +People related attributes of mission** <delivery> **node moved
250 +)))
251 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
252 +(((
253 +//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.//
254 +)))
255 +|(% colspan="1" %)(% colspan="1" %)
256 +(((
257 +Scripts
258 +)))|(% colspan="1" %)(% colspan="1" %)
259 +(((
260 +4.10 Beta 1
261 +)))|(% colspan="1" %)(% colspan="1" %)
262 +(((
263 +**$destructible.productions** replaced with $defensible.productions
264 +)))
265 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
266 +(((
267 +//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.//
268 +)))
269 +|(((
270 +Scripts
271 +)))|(((
272 +4.10 Beta 1
273 +)))|(((
274 +Removed script property **$object.spawnsourceseed**
275 +)))
276 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
277 +(((
278 +//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.//
279 +)))
280 +|(% colspan="3" %)(% colspan="3" %)
281 +(((
282 +== 4.00 ==
283 +)))
284 +|(% colspan="1" %)(% colspan="1" %)
285 +(((
286 +UI core
287 +)))|(% colspan="1" %)(% colspan="1" %)
288 +(((
289 +4.00 Beta 10
290 +)))|(% colspan="1" %)(% colspan="1" %)
291 +(((
292 +Controlled ship can change without a **gameplanchange-event** occurring.
293 +)))
294 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
295 +(((
296 +//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).
297 +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.
298 +//
299 +)))
300 +|(((
301 +Scripts
302 +)))|(((
303 +4.00 Beta 7
304 +)))|(((
305 +Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** 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 = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects?
310 +New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits
311 +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//
312 +)))
313 +|(% colspan="1" %)(% colspan="1" %)
314 +(((
315 +UI core
316 +)))|(% colspan="1" %)(% colspan="1" %)
317 +(((
318 +4.00 Beta 6
319 +)))|(% colspan="1" %)(% colspan="1" %)
320 +(((
321 +**FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed
322 +)))
323 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
324 +(((
325 +//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.
326 +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).//
327 +
328 +//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.
329 +//
330 +)))
331 +|(% colspan="1" %)(% colspan="1" %)
332 +(((
333 +UI core
334 +)))|(% colspan="1" %)(% colspan="1" %)
335 +(((
336 +4.00 Beta 5
337 +)))|(% colspan="1" %)(% colspan="1" %)
338 +(((
339 +**FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed
340 +)))
341 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
342 +(((
343 +//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.//
344 +
345 +//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).
346 +)))
347 +|(((
348 +Parameters
349 +)))|(((
350 +4.00 Beta 1
351 +)))|(((
352 +**requiresconstructionvessel** parameter moved
353 +)))
354 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
355 +(((
356 +//The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.//
357 +)))
358 +|(((
359 +Scripts
360 +)))|(((
361 +4.00 Beta 1
362 +)))|(((
363 +Changed behaviour of **gatedistance** script property
364 +)))
365 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
366 +(((
367 +//The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.//
368 +)))
369 +|(% colspan="3" %)(% colspan="3" %)
370 +(((
371 +== 3.30 ==
372 +)))
373 +|(((
374 +UI extensions
375 +)))|(((
376 +3.30 Beta 3
377 +)))|(((
378 +**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()**
379 +)))
380 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
381 +(((
382 +//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()//
383 +)))
384 +|(% colspan="3" %)(% colspan="3" %)
385 +(((
30 30  == 3.20 ==
31 31  )))
32 32  |(((
... ... @@ -42,6 +42,20 @@
42 42  //New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon]
43 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 44  )))
401 +|(% colspan="1" %)(% colspan="1" %)
402 +(((
403 +Scripts
404 +)))|(% colspan="1" %)(% colspan="1" %)
405 +(((
406 +3.20 Beta 1
407 +)))|(% colspan="1" %)(% colspan="1" %)
408 +(((
409 +Removed script property $trade.**restriction.faction**
410 +)))
411 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
412 +(((
413 +//$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.//
414 +)))
45 45  |(((
46 46  UI extensions
47 47  )))|(((
... ... @@ -581,7 +581,7 @@
581 581  )))|(((
582 582  2.00 Beta 1
583 583  )))|(((
584 -**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% class="confluenceTd" %)
954 +**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.
585 585  )))
586 586  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
587 587  (((
... ... @@ -614,7 +614,7 @@
614 614  )))|(((
615 615  2.00 Beta 1
616 616  )))|(((
617 -**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" %)
987 +**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.
618 618  )))
619 619  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
620 620  (((
... ... @@ -629,7 +629,7 @@
629 629  )))|(((
630 630  1.50 Beta 3
631 631  )))|(((
632 -**Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %)
1002 +**Lua: GetComponentData() **changed behavior of "docksizes" property.
633 633  )))
634 634  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
635 635  (((
... ... @@ -655,7 +655,7 @@
655 655  )))|(((
656 656  1.50 Beta 2
657 657  )))|(((
658 -**FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %)
1028 +**FFI: UpgradeGroupInfo **datatype was changed.
659 659  )))
660 660  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
661 661  (((
... ... @@ -683,7 +683,7 @@
683 683  )))|(((
684 684  1.50 Beta 1
685 685  )))|(((
686 -**FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %)
1056 +**FFI: CancelConstruction() **changed its return value.
687 687  )))
688 688  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
689 689  (((
... ... @@ -713,7 +713,7 @@
713 713  )))|(((
714 714  1.20
715 715  )))|(((
716 -**FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %)
1086 +**FFI: GetAAOption()** got a new "useconfig" parameter.
717 717  )))
718 718  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
719 719  (((
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -91949663
1 +78577854
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/91949663/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/78577854/Breaking Changes