Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 114.8
edited by Volodymyr Boichuk
on 2024/04/10 12:52
Change comment: There is no comment for this version
To version 121.1
edited by Nick Quejada
on 2024/05/24 20:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.Volodymyr
1 +xwiki:XWiki.Nick
Content
... ... @@ -23,10 +23,19 @@
23 23  === Version 7.00 ===
24 24  
25 25  
26 -(% class="wrapped" %)
26 +(% class="table-striped" %)
27 +|(% colspan="1" style="width:117px" %)Parameters|(% colspan="1" style="width:119px" %)7.00 Beta 7|(% colspan="2" style="width:1625px" %)**<aiflight><skills>**: **strafespeed**, **strafeacc**, **steeringspeed**, **steeringacc** moved to separate nodes; added support for min and max values
28 +|(% colspan="4" style="width:117px" %)(((
29 +//The four parameters used to represent flat factors applied to ships' properties with respect to their respective pilots' skill levels. Parameters moved to separate nodes with support for min and max values which, if supplied, scales the factor linearly if the affected ship's unmodified property is within min and max. Factor does not affect the ship if that property is below min.//
30 +)))
31 +|(% colspan="1" style="width:117px" %)Scripts|(% colspan="1" style="width:119px" %)7.00 Beta 6|(% colspan="2" style="width:1625px" %)MD action **<set_holomap_target>** parameter change.
32 +|(% colspan="4" style="width:117px" %)(((
33 +//The **pantime** parameter has never actually done anything beyond turning panning on or making the transition instant. To make this clear it has been** **replaced with the boolean parameter **instant.**//
34 +)))
27 27  |(% colspan="1" style="width:117px" %)Assets|(% colspan="1" style="width:119px" %)7.00 Beta 1|(% colspan="2" style="width:1625px" %)Renamed some material names and changed file paths for textures.
28 -|(% colspan="4" style="width:117px" %)//Some material names and texture pathes were changed.
29 -Not completele list of texture pathes change~://
36 +|(% colspan="4" style="width:117px" %)(((
37 +(% style="color:#ffffff" %)//Some material names and texture paths were changed. Please DIFF the materiallibrary.xml from 6.20 with 7.0 to see the difference//
38 +)))
30 30  |(% colspan="1" style="width:117px" %)(% colspan="1" %)
31 31  (((
32 32  Scripts
... ... @@ -35,7 +35,7 @@
35 35  )))|(% colspan="2" style="width:1625px" %)(((
36 36  MD action **<set_presentation_cluster_persistence/>** now requires the cluster to be a presentation cluster.
37 37  )))
38 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
47 +|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
39 39  (((
40 40  // Previously it was possible to set normal clusters to be persistent presentation clusters which was an invalid state.//
41 41  )))
... ... @@ -47,7 +47,7 @@
47 47  )))|(% colspan="2" style="width:1625px" %)(((
48 48  **FFI**: RemoveBuildPlot() changed
49 49  )))
50 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
59 +|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
51 51  (((
52 52  // The build plot's buildstorage is no longer removed implicitly. The buildstorage will instead be cleaned-up once it is empty and no ships are docked.//
53 53  )))
... ... @@ -59,16 +59,14 @@
59 59  )))|(% colspan="2" style="width:1625px" %)(((
60 60  **Some Split DLC materials moved to base game**
61 61  )))
62 -|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
71 +|(% colspan="7" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
63 63  (((
64 64  // //"spl_p1_fx" AND "split_p1_hulltexture_01" were moved from Split DLC to base game
65 65  )))
66 66  
67 -----
68 -
69 69  === Version 6.00 ===
70 70  
71 -(% class="wrapped" %)
78 +(% class="table-striped" %)
72 72  |(((
73 73  Libraries
74 74  )))|(((
... ... @@ -76,7 +76,7 @@
76 76  )))|(% colspan="2" %)(((
77 77  Updated weights for ship groups in shipgroups.xml libraries of base game and all DLCs.
78 78  )))
79 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
86 +|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
80 80  (((
81 81  //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.//
82 82  
... ... @@ -92,7 +92,7 @@
92 92  (((
93 93  Changed conditions for **<event_player_travelmode_started> <event_player_travelmode_stopped> <event_player_travelmode_charge_started> <event_player_travelmode_charge_aborted>** to be raised.
94 94  )))
95 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
102 +|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
96 96  (((
97 97  //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. //
98 98  
... ... @@ -108,7 +108,7 @@
108 108  (((
109 109  Changed result of **<find_object_surface>** action in the case of a failure
110 110  )))
111 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
118 +|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
112 112  (((
113 113  //The 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.//
114 114  
... ... @@ -126,7 +126,7 @@
126 126  (((
127 127  Behaviour change for **<match_dock>** script component filter
128 128  )))
129 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
136 +|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
130 130  (((
131 131  //<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes.
132 132  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.//
... ... @@ -141,7 +141,7 @@
141 141  (((
142 142  Changed result attribute location for **<get_attackstrength>**
143 143  )))
144 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
151 +|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
145 145  (((
146 146  //The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.//
147 147  )))
... ... @@ -152,7 +152,7 @@
152 152  )))|(% colspan="2" %)(((
153 153  Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons
154 154  )))
155 -|(% class="highlight-grey" colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% class="highlight-grey" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
162 +|(% colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
156 156  (((
157 157  //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.
158 158  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.//
... ... @@ -167,7 +167,7 @@
167 167  (((
168 168  Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects
169 169  )))
170 -|(% class="highlight-grey" colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% class="highlight-grey" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
177 +|(% colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
171 171  (((
172 172  //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.//
173 173  )))
... ... @@ -178,7 +178,7 @@
178 178  )))|(% colspan="2" %)(((
179 179  **<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards.
180 180  )))
181 -|(% class="highlight-grey" colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% class="highlight-grey" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
188 +|(% colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
182 182  (((
183 183  //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.//
184 184  )))
... ... @@ -189,7 +189,7 @@
189 189  )))|(% colspan="2" %)(((
190 190  Changed behaviour of **<angles>** in cutscenes
191 191  )))
192 -|(% class="highlight-grey" colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% class="highlight-grey" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
199 +|(% colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
193 193  (((
194 194  //The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.//
195 195  )))
... ... @@ -198,7 +198,7 @@
198 198  
199 199  === Version 5.00 ===
200 200  
201 -(% class="wrapped" %)
208 +(% class="table-striped" %)
202 202  |(((
203 203  Parameters
204 204  )))|(((
... ... @@ -206,7 +206,7 @@
206 206  )))|(% colspan="2" %)(((
207 207  **<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration
208 208  )))
209 -|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
216 +|(% colspan="7" %)(% colspan="3" %)
210 210  (((
211 211  //'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.//
212 212  )))
... ... @@ -215,7 +215,7 @@
215 215  
216 216  === Version 4.10 ===
217 217  
218 -(% class="wrapped" %)
225 +(% class="table-striped" %)
219 219  |(% colspan="1" %)(% colspan="1" %)
220 220  (((
221 221  UI extensions
... ... @@ -226,7 +226,7 @@
226 226  (((
227 227  **FFI**: SetMapRenderCargoContents(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos() deprecated
228 228  )))
229 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
236 +|(% colspan="4" %)(% colspan="3" %)
230 230  (((
231 231  //The functionality represented by SetMapRenderCargoContents(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos() has been removed and the function was therefore stubbed.//
232 232  )))
... ... @@ -240,7 +240,7 @@
240 240  (((
241 241  **FFI**: CustomGameStartPlayerProperty2 changed
242 242  )))
243 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
250 +|(% colspan="4" %)(% colspan="3" %)
244 244  (((
245 245  //This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.//
246 246  )))
... ... @@ -254,7 +254,7 @@
254 254  (((
255 255  Renamed **<stationinfobox>** to **<infobox>**
256 256  )))
257 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
264 +|(% colspan="4" %)(% colspan="3" %)
258 258  (((
259 259  //Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.//
260 260  )))
... ... @@ -268,7 +268,7 @@
268 268  (((
269 269  **FFI**: SetMacroMapPlayerSectorOffset() deprecated
270 270  )))
271 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
278 +|(% colspan="4" %)(% colspan="3" %)
272 272  (((
273 273  //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.//
274 274  )))
... ... @@ -279,7 +279,7 @@
279 279  )))|(% colspan="2" %)(((
280 280  **FFI**: FilterComponentForMapMode() and SetMapObjectFilter() changed
281 281  )))
282 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
289 +|(% colspan="4" %)(% colspan="3" %)
283 283  (((
284 284  //These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.//
285 285  )))
... ... @@ -290,7 +290,7 @@
290 290  )))|(% colspan="2" %)(((
291 291  People related attributes of mission** <delivery> **node moved
292 292  )))
293 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
300 +|(% colspan="4" %)(% colspan="3" %)
294 294  (((
295 295  //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.//
296 296  )))
... ... @@ -304,7 +304,7 @@
304 304  (((
305 305  **$destructible.productions** replaced with $defensible.productions
306 306  )))
307 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
314 +|(% colspan="4" %)(% colspan="3" %)
308 308  (((
309 309  //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.//
310 310  )))
... ... @@ -315,7 +315,7 @@
315 315  )))|(% colspan="2" %)(((
316 316  Removed script property **$object.spawnsourceseed**
317 317  )))
318 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
325 +|(% colspan="4" %)(% colspan="3" %)
319 319  (((
320 320  //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.//
321 321  )))
... ... @@ -324,7 +324,7 @@
324 324  
325 325  === Version 4.00 ===
326 326  
327 -(% class="wrapped" %)
334 +(% class="table-striped" %)
328 328  |(% colspan="1" %)(% colspan="1" %)
329 329  (((
330 330  UI core
... ... @@ -335,7 +335,7 @@
335 335  (((
336 336  Controlled ship can change without a **gameplanchange-event** occurring.
337 337  )))
338 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
345 +|(% colspan="4" %)(% colspan="3" %)
339 339  (((
340 340  //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).
341 341  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.//
... ... @@ -347,7 +347,7 @@
347 347  )))|(% colspan="2" %)(((
348 348  Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed
349 349  )))
350 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
357 +|(% colspan="4" %)(% colspan="3" %)
351 351  (((
352 352  //Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects?
353 353  New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits
... ... @@ -363,7 +363,7 @@
363 363  (((
364 364  **FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed
365 365  )))
366 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
373 +|(% colspan="4" %)(% colspan="3" %)
367 367  (((
368 368  //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.
369 369  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).//
... ... @@ -380,7 +380,7 @@
380 380  (((
381 381  **FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed
382 382  )))
383 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
390 +|(% colspan="4" %)(% colspan="3" %)
384 384  (((
385 385  //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.//
386 386  
... ... @@ -393,7 +393,7 @@
393 393  )))|(% colspan="2" %)(((
394 394  **requiresconstructionvessel** parameter moved
395 395  )))
396 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
403 +|(% colspan="4" %)(% colspan="3" %)
397 397  (((
398 398  //The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.//
399 399  )))
... ... @@ -404,7 +404,7 @@
404 404  )))|(% colspan="2" %)(((
405 405  Changed behaviour of **gatedistance** script property
406 406  )))
407 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
414 +|(% colspan="4" %)(% colspan="3" %)
408 408  (((
409 409  //The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.//
410 410  )))
... ... @@ -413,7 +413,7 @@
413 413  
414 414  === Version 3.30 ===
415 415  
416 -(% class="wrapped" %)
423 +(% class="table-striped" %)
417 417  |(((
418 418  UI extensions
419 419  )))|(((
... ... @@ -421,7 +421,7 @@
421 421  )))|(% colspan="2" %)(((
422 422  **FFI: **Removed** GetMissionLimit() **and** IsMissionLimitEnabled()**
423 423  )))
424 -|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
431 +|(% colspan="7" %)(% colspan="3" %)
425 425  (((
426 426  //These mission limit-related functions (added in 3.30 Beta 1 and 2) are replaced with FFI IsMissionLimitReached()//
427 427  )))
... ... @@ -430,7 +430,7 @@
430 430  
431 431  === Version 3.20 ===
432 432  
433 -(% class="wrapped" %)
440 +(% class="table-striped" %)
434 434  |(((
435 435  Scripts
436 436  )))|(((
... ... @@ -438,7 +438,7 @@
438 438  )))|(% colspan="2" %)(((
439 439  Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed
440 440  )))
441 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
448 +|(% colspan="4" %)(% colspan="3" %)
442 442  (((
443 443  //Old params: param = attacked object, param2 = attack method, param3 = attacked component//
444 444  //New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon]
... ... @@ -454,7 +454,7 @@
454 454  (((
455 455  Removed script property $trade.**restriction.faction**
456 456  )))
457 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
464 +|(% colspan="4" %)(% colspan="3" %)
458 458  (((
459 459  //$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.//
460 460  )))
... ... @@ -465,7 +465,7 @@
465 465  )))|(% colspan="2" %)(((
466 466  **Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete!
467 467  )))
468 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
475 +|(% colspan="4" %)(% colspan="3" %)
469 469  (((
470 470  //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.//
471 471  )))
... ... @@ -474,7 +474,7 @@
474 474  
475 475  === Version 3.10 ===
476 476  
477 -(% class="wrapped" %)
484 +(% class="table-striped" %)
478 478  |(% colspan="1" %)(% colspan="1" %)
479 479  (((
480 480  Scripts
... ... @@ -485,7 +485,7 @@
485 485  (((
486 486  Removed script action **<add_build/>**
487 487  )))
488 -|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
495 +|(% colspan="7" %)(% colspan="3" %)
489 489  (((
490 490  //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.//
491 491  )))
... ... @@ -494,7 +494,7 @@
494 494  
495 495  === Version 3.00 ===
496 496  
497 -(% class="wrapped" %)
504 +(% class="table-striped" %)
498 498  |(% colspan="1" %)(% colspan="1" %)
499 499  (((
500 500  Scripts
... ... @@ -505,7 +505,7 @@
505 505  (((
506 506  Changed behaviour of script action **<get_suitable_job/>**
507 507  )))
508 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
515 +|(% colspan="4" %)(% colspan="3" %)
509 509  (((
510 510  //<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.//
511 511  )))
... ... @@ -519,7 +519,7 @@
519 519  (((
520 520  Changed behaviour of script action **<get_ware_definition/>**
521 521  )))
522 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
529 +|(% colspan="4" %)(% colspan="3" %)
523 523  (((
524 524  //<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.//
525 525  )))
... ... @@ -533,7 +533,7 @@
533 533  (((
534 534  Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case
535 535  )))
536 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
543 +|(% colspan="4" %)(% colspan="3" %)
537 537  (((
538 538  //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.)
539 539  
... ... @@ -549,7 +549,7 @@
549 549  (((
550 550  Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions>
551 551  )))
552 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
559 +|(% colspan="4" %)(% colspan="3" %)
553 553  (((
554 554  //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.//
555 555  )))
... ... @@ -563,7 +563,7 @@
563 563  (((
564 564  Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos**
565 565  )))
566 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
573 +|(% colspan="4" %)(% colspan="3" %)
567 567  (((
568 568  //Before the change, positions are relative to $dockingbay.parent.
569 569  After the change, positions are relative to $dockingbay as specified in the documentation.//
... ... @@ -578,7 +578,7 @@
578 578  (((
579 579  Support for entity flag "**skillsvisible**" dropped
580 580  )))
581 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
588 +|(% colspan="4" %)(% colspan="3" %)
582 582  (((
583 583  //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().//
584 584  )))
... ... @@ -589,7 +589,7 @@
589 589  )))|(% colspan="2" %)(((
590 590  Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**.
591 591  )))
592 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
599 +|(% colspan="4" %)(% colspan="3" %)
593 593  (((
594 594  //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.
595 595  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.
... ... @@ -606,7 +606,7 @@
606 606  (((
607 607  **MissionBoard** support dropped
608 608  )))
609 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
616 +|(% colspan="4" %)(% colspan="3" %)
610 610  (((
611 611  //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.//
612 612  )))
... ... @@ -617,7 +617,7 @@
617 617  )))|(% colspan="2" %)(((
618 618  By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined
619 619  )))
620 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
627 +|(% colspan="4" %)(% colspan="3" %)
621 621  (((
622 622  //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.//
623 623  )))
... ... @@ -631,7 +631,7 @@
631 631  (((
632 632  Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'**
633 633  )))
634 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
641 +|(% colspan="4" %)(% colspan="3" %)
635 635  (((
636 636  //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.//
637 637  )))
... ... @@ -645,7 +645,7 @@
645 645  (((
646 646  Script action **<set_doors_locked/>** attribute **'group'** changed
647 647  )))
648 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
655 +|(% colspan="4" %)(% colspan="3" %)
649 649  (((
650 650  //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.//
651 651  )))
... ... @@ -659,7 +659,7 @@
659 659  (((
660 660  Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed
661 661  )))
662 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
669 +|(% colspan="4" %)(% colspan="3" %)
663 663  (((
664 664  //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.//
665 665  )))
... ... @@ -673,7 +673,7 @@
673 673  (((
674 674  Script actions **<set_hack_target/>** and **<abort_hack/>** removed
675 675  )))
676 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
683 +|(% colspan="4" %)(% colspan="3" %)
677 677  (((
678 678  //These actions had no effect and were removed.//
679 679  )))
... ... @@ -687,7 +687,7 @@
687 687  (((
688 688  **<setup_conversation_minigame/>** script action removed
689 689  )))
690 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
697 +|(% colspan="4" %)(% colspan="3" %)
691 691  (((
692 692  //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.//
693 693  )))
... ... @@ -701,7 +701,7 @@
701 701  (((
702 702  <add_player_choice_*> **confidence** attribute removed
703 703  )))
704 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
711 +|(% colspan="4" %)(% colspan="3" %)
705 705  (((
706 706  //The default confidence of player options is another leftover from the XR era and had no effect in X4.//
707 707  )))
... ... @@ -715,7 +715,7 @@
715 715  (((
716 716  **<hack_via_control_panel/>** script action removed
717 717  )))
718 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
725 +|(% colspan="4" %)(% colspan="3" %)
719 719  (((
720 720  //Unused script action <hack_via_control_panel/> was removed.//
721 721  )))
... ... @@ -729,7 +729,7 @@
729 729  (((
730 730  **Lua: **GetMiniGameCursorPosition() removed
731 731  )))
732 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
739 +|(% colspan="4" %)(% colspan="3" %)
733 733  (((
734 734  //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.//
735 735  )))
... ... @@ -740,7 +740,7 @@
740 740  )))|(% colspan="2" %)(((
741 741  **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders
742 742  )))
743 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
750 +|(% colspan="4" %)(% colspan="3" %)
744 744  (((
745 745  //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.//
746 746  )))
... ... @@ -754,7 +754,7 @@
754 754  (((
755 755  **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor
756 756  )))
757 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
764 +|(% colspan="4" %)(% colspan="3" %)
758 758  (((
759 759  //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.//
760 760  )))
... ... @@ -768,7 +768,7 @@
768 768  (((
769 769  **$ware.illegal** updated
770 770  )))
771 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
778 +|(% colspan="4" %)(% colspan="3" %)
772 772  (((
773 773  //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.//
774 774  //It now returns true if $ware is illegal to any faction in the game.//
... ... @@ -783,7 +783,7 @@
783 783  (((
784 784  MD script **RML_Flight_Along_Path** removed
785 785  )))
786 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
793 +|(% colspan="4" %)(% colspan="3" %)
787 787  (((
788 788  //The MD script RML_Flight_Along_Path was not referened and was removed.//
789 789  )))
... ... @@ -797,7 +797,7 @@
797 797  (((
798 798  parameters of **<event_venture_mission_completed/>** changed
799 799  )))
800 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
807 +|(% colspan="4" %)(% colspan="3" %)
801 801  (((
802 802  //old params: param = venture details, param2 = ships involved, param3 = duration//
803 803  //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration//
... ... @@ -810,7 +810,7 @@
810 810  **<set_object_wing_name/>** removed,
811 811  **<set_object_fleet_name/>** added
812 812  )))
813 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
820 +|(% colspan="4" %)(% colspan="3" %)
814 814  (((
815 815  //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>//
816 816  )))
... ... @@ -822,7 +822,7 @@
822 822  **$controllable.wing.*** removed,
823 823  **$controllable.fleet.*** added
824 824  )))
825 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
832 +|(% colspan="4" %)(% colspan="3" %)
826 826  (((
827 827  $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander
828 828  )))
... ... @@ -831,7 +831,7 @@
831 831  
832 832  === Version 2.60 ===
833 833  
834 -(% class="wrapped" %)
841 +(% class="table-striped" %)
835 835  |(((
836 836  Scripts
837 837  )))|(((
... ... @@ -839,7 +839,7 @@
839 839  )))|(% colspan="2" %)(((
840 840  '**checkoperational**' filter behaviour changed
841 841  )))
842 -|(% class="highlight-grey" colspan="10" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
849 +|(% colspan="10" %)(% colspan="3" %)
843 843  (((
844 844  //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.//
845 845  
... ... @@ -852,7 +852,7 @@
852 852  )))|(% colspan="2" %)(((
853 853  $container.**supplyresources** behavior changed
854 854  )))| | |
855 -|(% class="highlight-grey" colspan="10" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
862 +|(% colspan="10" %)(% colspan="3" %)
856 856  (((
857 857  //The script keyword $container.supplyresources now includes reserved wares.//
858 858  )))
... ... @@ -861,7 +861,7 @@
861 861  
862 862  === Version 2.20 ===
863 863  
864 -(% class="wrapped" %)
871 +(% class="table-striped" %)
865 865  |(% colspan="1" %)(% colspan="1" %)
866 866  (((
867 867  UI core
... ... @@ -872,7 +872,7 @@
872 872  (((
873 873  **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined.
874 874  )))
875 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
882 +|(% colspan="4" %)(% colspan="3" %)
876 876  (((
877 877  //2.20 Beta 3 introduced the new direct mouse steering mode. The mode was however not integrated as a first level mode and hence GetControllerInfo() returned the "gamepad" mode while direct mouse steering was active.
878 878  In 2.20 Beta 4 we improved the situation slightly so that a call to GetControllerInfo() will return either "mouseCursor" or "mouseSteering" in any of the 3 mouse modes.//
... ... @@ -889,7 +889,7 @@
889 889  (((
890 890  Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor'
891 891  )))
892 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
899 +|(% colspan="4" %)(% colspan="3" %)
893 893  (((
894 894  //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.//
895 895  )))
... ... @@ -898,7 +898,7 @@
898 898  
899 899  === Version 2.00 ===
900 900  
901 -(% class="wrapped" %)
908 +(% class="table-striped" %)
902 902  |(% colspan="1" %)(% colspan="1" %)
903 903  (((
904 904  Scripts
... ... @@ -909,7 +909,7 @@
909 909  (((
910 910  **<event_build_finished/> **param2 now returns null instead of a construction sequence
911 911  )))
912 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
919 +|(% colspan="4" %)(% colspan="3" %)
913 913  (((
914 914  //The construction sequence which was finished should now be accessed via the buildtask provided via param3.//
915 915  )))
... ... @@ -923,7 +923,7 @@
923 923  (((
924 924  **param.boarding.{...}** strength parameters removed
925 925  )))
926 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
933 +|(% colspan="4" %)(% colspan="3" %)
927 927  (((
928 928  //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.//
929 929  )))
... ... @@ -937,7 +937,7 @@
937 937  (((
938 938  **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed
939 939  )))
940 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
947 +|(% colspan="4" %)(% colspan="3" %)
941 941  (((
942 942  //Due to changes to boarding in X4, the boarding connections accessed by these script properties and actions became redundent and thus, removed. Any connections set by these actions in a savegame will not survive loading.//
943 943  )))
... ... @@ -948,7 +948,7 @@
948 948  )))|(% colspan="2" %)(((
949 949  **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals
950 950  )))
951 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
958 +|(% colspan="4" %)(% colspan="3" %)
952 952  (((
953 953  //Before 2.0 Beta 1 using GetUpgradeSlotCurrentComponent() or GetUpgradeSlotGroup() only performed on operational objects (i.e. not wrecked objects or objects under construction). Since this is inconsistent with the rest of the UI functions, this was considered a bug and fixed in 2.0 Beta 1. If you require the old behavior, use the FFI function: IsComponentOperational() to check the passed object's state before making the call.//
954 954  )))
... ... @@ -959,7 +959,7 @@
959 959  )))|(% colspan="2" %)(((
960 960  **FFI: SetFormationShape()** no longer indicates an error upon certain error cases
961 961  )))
962 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
969 +|(% colspan="4" %)(% colspan="3" %)
963 963  (((
964 964  //Before 2.0 Beta 1 a call to SetFormationShape() indicated an error state to the caller in certain cases where setting a formation shape (potentially) failed. Due to a design flaw in the handling of formations, this however doesn't do any good, since the function by itself doesn't really set the formation shape in all cases. On top of that the call can fail at random. Hence, at the moment an indication of an error case that setting a formation potentially fails is no good to the caller and he has no means to distinguish that case from a real error case.//
965 965  //Therefore, in 2.0 Beta 1 we drop the error indication in case of an attempt to set the formation fails. We are currently working on a better solution to the underlying problem and hope to have it ready as part of a following beta.//
... ... @@ -971,7 +971,7 @@
971 971  )))|(% colspan="2" %)(((
972 972  **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated.
973 973  )))
974 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
981 +|(% colspan="4" %)(% colspan="3" %)
975 975  (((
976 976  //This now enforces a leader and at least one follower in order to create or change a formation.  Former implementation made it possible to create formations without any followers which led to issues.//
977 977  )))
... ... @@ -982,7 +982,7 @@
982 982  )))|(% colspan="2" %)(((
983 983  **<event_player_changed_target/>** now fires and returns null if the player deselects a target.
984 984  )))
985 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
992 +|(% colspan="4" %)(% colspan="3" %)
986 986  (((
987 987  //For prior behavior, check for event.param being non-null.//
988 988  )))
... ... @@ -993,7 +993,7 @@
993 993  )))|(% colspan="2" %)(((
994 994  **<shoot/>/<shoot_at/>** attribute changes.
995 995  )))
996 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1003 +|(% colspan="4" %)(% colspan="3" %)
997 997  (((
998 998  //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.//
999 999  //New attribute: "secondary" is an optional attribute that defines whether weapons from the ship's active secondary weapon group will be fired. Defaults to true.//
... ... @@ -1008,7 +1008,7 @@
1008 1008  )))|(% colspan="2" %)(((
1009 1009  **FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.
1010 1010  )))
1011 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1018 +|(% colspan="4" %)(% colspan="3" %)
1012 1012  (((
1013 1013  //Added possibility to query build tasks of a certain buildmodule.//
1014 1014  )))
... ... @@ -1019,7 +1019,7 @@
1019 1019  )))|(% colspan="2" %)(((
1020 1020  **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field.
1021 1021  )))
1022 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1029 +|(% colspan="4" %)(% colspan="3" %)
1023 1023  (((
1024 1024  //Added list of resources a buildmodule needs to build.//
1025 1025  )))
... ... @@ -1030,7 +1030,7 @@
1030 1030  )))|(% colspan="2" %)(((
1031 1031  **Lua: CalculateTotalHullFraction() **was removed.
1032 1032  )))
1033 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1040 +|(% colspan="4" %)(% colspan="3" %)
1034 1034  (((
1035 1035  //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.//
1036 1036  )))
... ... @@ -1041,7 +1041,7 @@
1041 1041  )))|(% colspan="2" %)(((
1042 1042  **FFI: RequestDockAtReason()/UndockPlayerShip() **changed their return values.
1043 1043  )))
1044 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1051 +|(% colspan="4" %)(% colspan="3" %)
1045 1045  (((
1046 1046  //Changed return value type to const char* to better identify failure reasons in Lua script.//
1047 1047  )))
... ... @@ -1050,7 +1050,7 @@
1050 1050  
1051 1051  === Version 1.50 ===
1052 1052  
1053 -(% class="wrapped" %)
1060 +(% class="table-striped" %)
1054 1054  |(((
1055 1055  UI extensions
1056 1056  )))|(((
... ... @@ -1058,7 +1058,7 @@
1058 1058  )))|(% colspan="2" %)(((
1059 1059  **Lua: GetComponentData() **changed behavior of "docksizes" property.
1060 1060  )))
1061 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1068 +|(% colspan="4" %)(% colspan="3" %)
1062 1062  (((
1063 1063  //The "docksizes" property no longer includes internal ship storage docks.//
1064 1064  )))
... ... @@ -1069,7 +1069,7 @@
1069 1069  )))|(% colspan="2" %)(((
1070 1070  **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR).
1071 1071  )))
1072 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1079 +|(% colspan="4" %)(% colspan="3" %)
1073 1073  (((
1074 1074  //Shipyards (formerly also known as Capital Shipyards) can build capital ships, while Wharfs only build non-capital ships. To check whether a station is a Shipyard or a Wharf, check whether the station "can build ships".//
1075 1075  
... ... @@ -1084,7 +1084,7 @@
1084 1084  )))|(% colspan="2" %)(((
1085 1085  **FFI: UpgradeGroupInfo **datatype was changed.
1086 1086  )))
1087 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1094 +|(% colspan="4" %)(% colspan="3" %)
1088 1088  (((
1089 1089  //Added new "operational" field to retrieve information about number of operational upgrades in a group.//
1090 1090  )))
... ... @@ -1098,7 +1098,7 @@
1098 1098  (((
1099 1099  **FFI: SetGuidance()** removed useinfopoint argument.
1100 1100  )))
1101 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1108 +|(% colspan="4" %)(% colspan="3" %)
1102 1102  (((
1103 1103  //In X Rebirth "info points" existed (which were mainly used as interaction points to scan stations/access information about modules). These were removed in X4 but this left-over property here was missed to be removed in-time for release. It was therefore removed now in order to move towards a stable/clean UI API.//
1104 1104  
... ... @@ -1111,7 +1111,7 @@
1111 1111  )))|(% colspan="2" %)(((
1112 1112  **FFI: CancelConstruction() **changed its return value.
1113 1113  )))
1114 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1121 +|(% colspan="4" %)(% colspan="3" %)
1115 1115  (((
1116 1116  //CancelConstruction() now returns if the cancellation was successful. //
1117 1117  )))
... ... @@ -1120,7 +1120,7 @@
1120 1120  
1121 1121  === Version 1.32 ===
1122 1122  
1123 -(% class="wrapped" %)
1130 +(% class="table-striped" %)
1124 1124  |(((
1125 1125  UI extensions
1126 1126  )))|(((
... ... @@ -1128,7 +1128,7 @@
1128 1128  )))|(% colspan="2" %)(((
1129 1129  **Lua: GetComponentData() **removed the "nextdestname" property.
1130 1130  )))
1131 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1138 +|(% colspan="4" %)(% colspan="3" %)
1132 1132  (((
1133 1133  //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.//
1134 1134  )))
... ... @@ -1137,7 +1137,7 @@
1137 1137  
1138 1138  === Version 1.20 ===
1139 1139  
1140 -(% class="wrapped" %)
1147 +(% class="table-striped" %)
1141 1141  |(((
1142 1142  UI extensions
1143 1143  )))|(((
... ... @@ -1145,7 +1145,7 @@
1145 1145  )))|(% colspan="2" %)(((
1146 1146  **FFI: GetAAOption()** got a new "useconfig" parameter.
1147 1147  )))
1148 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1155 +|(% colspan="4" %)(% colspan="3" %)
1149 1149  (((
1150 1150  //The AA setting was changed to check the new setting with the user. In order to restore the old setting GetAAOption() gets the option to retrieve the config settings.//
1151 1151  )))
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,0 @@
1 -78577854
space
... ... @@ -1,1 +1,0 @@
1 -X4WIKI
url
... ... @@ -1,1 +1,0 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/78577854/Breaking Changes