Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 65.1
edited by michael
on 2020/05/05 10:54
Change comment: documented $trade.restriction.factions
To version 103.1
edited by cbj
on 2023/02/20 14:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.michael
1 +xwiki:XWiki.cbj
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,347 @@
27 27  )))
28 28  |(% colspan="3" %)(% colspan="3" %)
29 29  (((
31 +== 6.00 ==
32 +)))
33 +|(% colspan="1" %)(% colspan="1" %)
34 +(((
35 +Scripts
36 +)))|(% colspan="1" %)(% colspan="1" %)
37 +(((
38 +6.00 Beta 4
39 +)))|(% colspan="1" %)(% colspan="1" %)
40 +(((
41 +Changed conditions for **<event_player_travelmode_started> <event_player_travelmode_stopped> <event_player_travelmode_charge_started> <event_player_travelmode_charge_aborted>** to be raised.
42 +)))
43 +|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
44 +(((
45 +//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. //
46 +
47 +//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.//
48 +)))
49 +|(% colspan="1" %)(% colspan="1" %)
50 +(((
51 +Scripts
52 +)))|(% colspan="1" %)(% colspan="1" %)
53 +(((
54 +6.00 Beta 3
55 +)))|(% colspan="1" %)(% colspan="1" %)
56 +(((
57 +Changed result of **<find_object_surface>** action in the case of a failure
58 +)))
59 +|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
60 +(((
61 +//The 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.//
62 +
63 +//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.//
64 +
65 +//The action itself has been improved to increase the chance of finding suitable surface positions.//
66 +)))
67 +|(% colspan="1" %)(% colspan="1" %)
68 +(((
69 +Scripts
70 +)))|(% colspan="1" %)(% colspan="1" %)
71 +(((
72 +6.00 Beta 1
73 +)))|(% colspan="1" %)(% colspan="1" %)
74 +(((
75 +Behaviour change for **<match_dock>** script component filter
76 +)))
77 +|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
78 +(((
79 +//<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes.
80 +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.//
81 +)))
82 +|(% colspan="1" %)(% colspan="1" %)
83 +(((
84 +Scripts
85 +)))|(% colspan="1" %)(% colspan="1" %)
86 +(((
87 +6.00 Beta 1
88 +)))|(% colspan="1" %)(% colspan="1" %)
89 +(((
90 +Changed result attribute location for **<get_attackstrength>**
91 +)))
92 +|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
93 +(((
94 +//The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.//
95 +)))
96 +|(((
97 +Assets
98 +)))|(((
99 +6.00 Beta 1
100 +)))|(((
101 +Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons
102 +)))
103 +|(% 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" %)
104 +(((
105 +//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.
106 +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.//
107 +)))
108 +|(% colspan="1" %)(% colspan="1" %)
109 +(((
110 +Scripts
111 +)))|(% colspan="1" %)(% colspan="1" %)
112 +(((
113 +6.00 Beta 1
114 +)))|(% colspan="1" %)(% colspan="1" %)
115 +(((
116 +Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects
117 +)))
118 +|(% 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" %)
119 +(((
120 +//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.//
121 +)))
122 +|(((
123 +Scripts
124 +)))|(((
125 +6.00 Beta 1
126 +)))|(((
127 +**<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards.
128 +)))
129 +|(% 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" %)
130 +(((
131 +//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.//
132 +)))
133 +|(((
134 +Cutscenes
135 +)))|(((
136 +6.00 Beta 1
137 +)))|(((
138 +Changed behaviour of **<angles>** in cutscenes
139 +)))
140 +|(% 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" %)
141 +(((
142 +//The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.//
143 +)))
144 +|(% colspan="3" %)(% colspan="3" %)
145 +(((
146 +== 5.00 ==
147 +)))
148 +|(((
149 +Parameters
150 +)))|(((
151 +5.00 Beta 1
152 +)))|(((
153 +**<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration
154 +)))
155 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
156 +(((
157 +//'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.//
158 +)))
159 +|(% colspan="3" %)(% colspan="3" %)
160 +(((
161 +== 4.10 ==
162 +)))
163 +|(% colspan="1" %)(% colspan="1" %)
164 +(((
165 +UI extensions
166 +)))|(% colspan="1" %)(% colspan="1" %)
167 +(((
168 +4.10 Beta 7
169 +)))|(% colspan="1" %)(% colspan="1" %)
170 +(((
171 +**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
172 +)))
173 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
174 +(((
175 +//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.//
176 +)))
177 +|(% colspan="1" %)(% colspan="1" %)
178 +(((
179 +UI extensions
180 +)))|(% colspan="1" %)(% colspan="1" %)
181 +(((
182 +4.10 Beta 6
183 +)))|(% colspan="1" %)(% colspan="1" %)
184 +(((
185 +**FFI**: CustomGameStartPlayerProperty2 changed
186 +)))
187 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
188 +(((
189 +//This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.//
190 +)))
191 +|(% colspan="1" %)(% colspan="1" %)
192 +(((
193 +Parameters
194 +)))|(% colspan="1" %)(% colspan="1" %)
195 +(((
196 +4.10 Beta 3
197 +)))|(% colspan="1" %)(% colspan="1" %)
198 +(((
199 +Renamed **<stationinfobox>** to **<infobox>**
200 +)))
201 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
202 +(((
203 +//Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.//
204 +)))
205 +|(% colspan="1" %)(% colspan="1" %)
206 +(((
207 +UI extensions
208 +)))|(% colspan="1" %)(% colspan="1" %)
209 +(((
210 +4.10 Beta 2
211 +)))|(% colspan="1" %)(% colspan="1" %)
212 +(((
213 +**FFI**: SetMacroMapPlayerSectorOffset() deprecated
214 +)))
215 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
216 +(((
217 +//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.//
218 +)))
219 +|(((
220 +UI extensions
221 +)))|(((
222 +4.10 Beta 2
223 +)))|(((
224 +**FFI**: (% style="color: rgb(0,0,0);" %)FilterComponentForMapMode(%%)() and (% style="color: rgb(0,0,0);" %)SetMapObjectFilter() changed
225 +)))
226 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
227 +(((
228 +//These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.//
229 +)))
230 +|(((
231 +Scripts
232 +)))|(((
233 +4.10 Beta 1
234 +)))|(((
235 +People related attributes of mission** <delivery> **node moved
236 +)))
237 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
238 +(((
239 +//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.//
240 +)))
241 +|(% colspan="1" %)(% colspan="1" %)
242 +(((
243 +Scripts
244 +)))|(% colspan="1" %)(% colspan="1" %)
245 +(((
246 +4.10 Beta 1
247 +)))|(% colspan="1" %)(% colspan="1" %)
248 +(((
249 +**$destructible.productions** replaced with $defensible.productions
250 +)))
251 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
252 +(((
253 +//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.//
254 +)))
255 +|(((
256 +Scripts
257 +)))|(((
258 +4.10 Beta 1
259 +)))|(((
260 +Removed script property **$object.spawnsourceseed**
261 +)))
262 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
263 +(((
264 +//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.//
265 +)))
266 +|(% colspan="3" %)(% colspan="3" %)
267 +(((
268 +== 4.00 ==
269 +)))
270 +|(% colspan="1" %)(% colspan="1" %)
271 +(((
272 +UI core
273 +)))|(% colspan="1" %)(% colspan="1" %)
274 +(((
275 +4.00 Beta 10
276 +)))|(% colspan="1" %)(% colspan="1" %)
277 +(((
278 +Controlled ship can change without a **gameplanchange-event** occurring.
279 +)))
280 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
281 +(((
282 +//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).
283 +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.
284 +//
285 +)))
286 +|(((
287 +Scripts
288 +)))|(((
289 +4.00 Beta 7
290 +)))|(((
291 +Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed
292 +)))
293 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
294 +(((
295 +//Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects?
296 +New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits
297 +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//
298 +)))
299 +|(% colspan="1" %)(% colspan="1" %)
300 +(((
301 +UI core
302 +)))|(% colspan="1" %)(% colspan="1" %)
303 +(((
304 +4.00 Beta 6
305 +)))|(% colspan="1" %)(% colspan="1" %)
306 +(((
307 +**FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed
308 +)))
309 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
310 +(((
311 +//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.
312 +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).//
313 +
314 +//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.
315 +//
316 +)))
317 +|(% colspan="1" %)(% colspan="1" %)
318 +(((
319 +UI core
320 +)))|(% colspan="1" %)(% colspan="1" %)
321 +(((
322 +4.00 Beta 5
323 +)))|(% colspan="1" %)(% colspan="1" %)
324 +(((
325 +**FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed
326 +)))
327 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
328 +(((
329 +//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.//
330 +
331 +//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).
332 +)))
333 +|(((
334 +Parameters
335 +)))|(((
336 +4.00 Beta 1
337 +)))|(((
338 +**requiresconstructionvessel** parameter moved
339 +)))
340 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
341 +(((
342 +//The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.//
343 +)))
344 +|(((
345 +Scripts
346 +)))|(((
347 +4.00 Beta 1
348 +)))|(((
349 +Changed behaviour of **gatedistance** script property
350 +)))
351 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
352 +(((
353 +//The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.//
354 +)))
355 +|(% colspan="3" %)(% colspan="3" %)
356 +(((
357 +== 3.30 ==
358 +)))
359 +|(((
360 +UI extensions
361 +)))|(((
362 +3.30 Beta 3
363 +)))|(((
364 +**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()**
365 +)))
366 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
367 +(((
368 +//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()//
369 +)))
370 +|(% colspan="3" %)(% colspan="3" %)
371 +(((
30 30  == 3.20 ==
31 31  )))
32 32  |(((
... ... @@ -50,12 +50,11 @@
50 50  3.20 Beta 1
51 51  )))|(% colspan="1" %)(% colspan="1" %)
52 52  (((
53 -**$trade.restriction.faction** removed,**
54 -$trade.restriction.factions** added
395 +Removed script property $trade.**restriction.faction**
55 55  )))
56 56  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
57 57  (((
58 -//$trade.restriction.faction has// been replaced with $trade.restriction.factions which returns a list of factions
399 +//$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.//
59 59  )))
60 60  |(((
61 61  UI extensions
... ... @@ -596,7 +596,7 @@
596 596  )))|(((
597 597  2.00 Beta 1
598 598  )))|(((
599 -**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% class="confluenceTd" %)
940 +**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.
600 600  )))
601 601  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
602 602  (((
... ... @@ -629,7 +629,7 @@
629 629  )))|(((
630 630  2.00 Beta 1
631 631  )))|(((
632 -**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" %)
973 +**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.
633 633  )))
634 634  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
635 635  (((
... ... @@ -644,7 +644,7 @@
644 644  )))|(((
645 645  1.50 Beta 3
646 646  )))|(((
647 -**Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %)
988 +**Lua: GetComponentData() **changed behavior of "docksizes" property.
648 648  )))
649 649  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
650 650  (((
... ... @@ -670,7 +670,7 @@
670 670  )))|(((
671 671  1.50 Beta 2
672 672  )))|(((
673 -**FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %)
1014 +**FFI: UpgradeGroupInfo **datatype was changed.
674 674  )))
675 675  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
676 676  (((
... ... @@ -698,7 +698,7 @@
698 698  )))|(((
699 699  1.50 Beta 1
700 700  )))|(((
701 -**FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %)
1042 +**FFI: CancelConstruction() **changed its return value.
702 702  )))
703 703  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
704 704  (((
... ... @@ -728,7 +728,7 @@
728 728  )))|(((
729 729  1.20
730 730  )))|(((
731 -**FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %)
1072 +**FFI: GetAAOption()** got a new "useconfig" parameter.
732 732  )))
733 733  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
734 734  (((
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -91949685
1 +141329146
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/91949685/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/141329146/Breaking Changes