Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 114.1
edited by Owen Lake
on 2024/01/31 12:40
Change comment: There is no comment for this version
To version 120.1
edited by Daniel Turner
on 2024/05/22 14:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.Owen
1 +xwiki:XWiki.Daniel
Content
... ... @@ -23,7 +23,15 @@
23 23  === Version 7.00 ===
24 24  
25 25  
26 -(% class="wrapped" %)
26 +(% class="table-striped" %)
27 +|(% 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.
28 +|(% colspan="4" style="width:117px" %)(((
29 +//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.**//
30 +)))
31 +|(% 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.
32 +|(% colspan="4" style="width:117px" %)(((
33 +(% 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//
34 +)))
27 27  |(% colspan="1" style="width:117px" %)(% colspan="1" %)
28 28  (((
29 29  Scripts
... ... @@ -32,7 +32,7 @@
32 32  )))|(% colspan="2" style="width:1625px" %)(((
33 33  MD action **<set_presentation_cluster_persistence/>** now requires the cluster to be a presentation cluster.
34 34  )))
35 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
43 +|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
36 36  (((
37 37  // Previously it was possible to set normal clusters to be persistent presentation clusters which was an invalid state.//
38 38  )))
... ... @@ -44,7 +44,7 @@
44 44  )))|(% colspan="2" style="width:1625px" %)(((
45 45  **FFI**: RemoveBuildPlot() changed
46 46  )))
47 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
55 +|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
48 48  (((
49 49  // 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.//
50 50  )))
... ... @@ -56,16 +56,14 @@
56 56  )))|(% colspan="2" style="width:1625px" %)(((
57 57  **Some Split DLC materials moved to base game**
58 58  )))
59 -|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
67 +|(% colspan="7" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
60 60  (((
61 61  // //"spl_p1_fx" AND "split_p1_hulltexture_01" were moved from Split DLC to base game
62 62  )))
63 63  
64 -----
65 -
66 66  === Version 6.00 ===
67 67  
68 -(% class="wrapped" %)
74 +(% class="table-striped" %)
69 69  |(((
70 70  Libraries
71 71  )))|(((
... ... @@ -73,7 +73,7 @@
73 73  )))|(% colspan="2" %)(((
74 74  Updated weights for ship groups in shipgroups.xml libraries of base game and all DLCs.
75 75  )))
76 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
82 +|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
77 77  (((
78 78  //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.//
79 79  
... ... @@ -89,7 +89,7 @@
89 89  (((
90 90  Changed conditions for **<event_player_travelmode_started> <event_player_travelmode_stopped> <event_player_travelmode_charge_started> <event_player_travelmode_charge_aborted>** to be raised.
91 91  )))
92 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
98 +|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
93 93  (((
94 94  //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. //
95 95  
... ... @@ -105,7 +105,7 @@
105 105  (((
106 106  Changed result of **<find_object_surface>** action in the case of a failure
107 107  )))
108 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
114 +|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
109 109  (((
110 110  //The 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.//
111 111  
... ... @@ -123,7 +123,7 @@
123 123  (((
124 124  Behaviour change for **<match_dock>** script component filter
125 125  )))
126 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
132 +|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
127 127  (((
128 128  //<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes.
129 129  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.//
... ... @@ -138,7 +138,7 @@
138 138  (((
139 139  Changed result attribute location for **<get_attackstrength>**
140 140  )))
141 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
147 +|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
142 142  (((
143 143  //The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.//
144 144  )))
... ... @@ -149,7 +149,7 @@
149 149  )))|(% colspan="2" %)(((
150 150  Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons
151 151  )))
152 -|(% 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%" %)
158 +|(% colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
153 153  (((
154 154  //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.
155 155  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.//
... ... @@ -164,7 +164,7 @@
164 164  (((
165 165  Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects
166 166  )))
167 -|(% 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%" %)
173 +|(% colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
168 168  (((
169 169  //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.//
170 170  )))
... ... @@ -175,7 +175,7 @@
175 175  )))|(% colspan="2" %)(((
176 176  **<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards.
177 177  )))
178 -|(% 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%" %)
184 +|(% colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
179 179  (((
180 180  //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.//
181 181  )))
... ... @@ -186,7 +186,7 @@
186 186  )))|(% colspan="2" %)(((
187 187  Changed behaviour of **<angles>** in cutscenes
188 188  )))
189 -|(% 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%" %)
195 +|(% colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
190 190  (((
191 191  //The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.//
192 192  )))
... ... @@ -195,7 +195,7 @@
195 195  
196 196  === Version 5.00 ===
197 197  
198 -(% class="wrapped" %)
204 +(% class="table-striped" %)
199 199  |(((
200 200  Parameters
201 201  )))|(((
... ... @@ -203,7 +203,7 @@
203 203  )))|(% colspan="2" %)(((
204 204  **<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration
205 205  )))
206 -|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
212 +|(% colspan="7" %)(% colspan="3" %)
207 207  (((
208 208  //'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.//
209 209  )))
... ... @@ -212,7 +212,7 @@
212 212  
213 213  === Version 4.10 ===
214 214  
215 -(% class="wrapped" %)
221 +(% class="table-striped" %)
216 216  |(% colspan="1" %)(% colspan="1" %)
217 217  (((
218 218  UI extensions
... ... @@ -223,7 +223,7 @@
223 223  (((
224 224  **FFI**: SetMapRenderCargoContents(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos() deprecated
225 225  )))
226 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
232 +|(% colspan="4" %)(% colspan="3" %)
227 227  (((
228 228  //The functionality represented by SetMapRenderCargoContents(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos() has been removed and the function was therefore stubbed.//
229 229  )))
... ... @@ -237,7 +237,7 @@
237 237  (((
238 238  **FFI**: CustomGameStartPlayerProperty2 changed
239 239  )))
240 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
246 +|(% colspan="4" %)(% colspan="3" %)
241 241  (((
242 242  //This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.//
243 243  )))
... ... @@ -251,7 +251,7 @@
251 251  (((
252 252  Renamed **<stationinfobox>** to **<infobox>**
253 253  )))
254 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
260 +|(% colspan="4" %)(% colspan="3" %)
255 255  (((
256 256  //Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.//
257 257  )))
... ... @@ -265,7 +265,7 @@
265 265  (((
266 266  **FFI**: SetMacroMapPlayerSectorOffset() deprecated
267 267  )))
268 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
274 +|(% colspan="4" %)(% colspan="3" %)
269 269  (((
270 270  //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.//
271 271  )))
... ... @@ -276,7 +276,7 @@
276 276  )))|(% colspan="2" %)(((
277 277  **FFI**: FilterComponentForMapMode() and SetMapObjectFilter() changed
278 278  )))
279 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
285 +|(% colspan="4" %)(% colspan="3" %)
280 280  (((
281 281  //These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.//
282 282  )))
... ... @@ -287,7 +287,7 @@
287 287  )))|(% colspan="2" %)(((
288 288  People related attributes of mission** <delivery> **node moved
289 289  )))
290 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
296 +|(% colspan="4" %)(% colspan="3" %)
291 291  (((
292 292  //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.//
293 293  )))
... ... @@ -301,7 +301,7 @@
301 301  (((
302 302  **$destructible.productions** replaced with $defensible.productions
303 303  )))
304 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
310 +|(% colspan="4" %)(% colspan="3" %)
305 305  (((
306 306  //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.//
307 307  )))
... ... @@ -312,7 +312,7 @@
312 312  )))|(% colspan="2" %)(((
313 313  Removed script property **$object.spawnsourceseed**
314 314  )))
315 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
321 +|(% colspan="4" %)(% colspan="3" %)
316 316  (((
317 317  //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.//
318 318  )))
... ... @@ -321,7 +321,7 @@
321 321  
322 322  === Version 4.00 ===
323 323  
324 -(% class="wrapped" %)
330 +(% class="table-striped" %)
325 325  |(% colspan="1" %)(% colspan="1" %)
326 326  (((
327 327  UI core
... ... @@ -332,7 +332,7 @@
332 332  (((
333 333  Controlled ship can change without a **gameplanchange-event** occurring.
334 334  )))
335 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
341 +|(% colspan="4" %)(% colspan="3" %)
336 336  (((
337 337  //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).
338 338  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.//
... ... @@ -344,7 +344,7 @@
344 344  )))|(% colspan="2" %)(((
345 345  Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed
346 346  )))
347 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
353 +|(% colspan="4" %)(% colspan="3" %)
348 348  (((
349 349  //Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects?
350 350  New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits
... ... @@ -360,7 +360,7 @@
360 360  (((
361 361  **FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed
362 362  )))
363 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
369 +|(% colspan="4" %)(% colspan="3" %)
364 364  (((
365 365  //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.
366 366  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).//
... ... @@ -377,7 +377,7 @@
377 377  (((
378 378  **FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed
379 379  )))
380 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
386 +|(% colspan="4" %)(% colspan="3" %)
381 381  (((
382 382  //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.//
383 383  
... ... @@ -390,7 +390,7 @@
390 390  )))|(% colspan="2" %)(((
391 391  **requiresconstructionvessel** parameter moved
392 392  )))
393 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
399 +|(% colspan="4" %)(% colspan="3" %)
394 394  (((
395 395  //The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.//
396 396  )))
... ... @@ -401,7 +401,7 @@
401 401  )))|(% colspan="2" %)(((
402 402  Changed behaviour of **gatedistance** script property
403 403  )))
404 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
410 +|(% colspan="4" %)(% colspan="3" %)
405 405  (((
406 406  //The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.//
407 407  )))
... ... @@ -410,7 +410,7 @@
410 410  
411 411  === Version 3.30 ===
412 412  
413 -(% class="wrapped" %)
419 +(% class="table-striped" %)
414 414  |(((
415 415  UI extensions
416 416  )))|(((
... ... @@ -418,7 +418,7 @@
418 418  )))|(% colspan="2" %)(((
419 419  **FFI: **Removed** GetMissionLimit() **and** IsMissionLimitEnabled()**
420 420  )))
421 -|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
427 +|(% colspan="7" %)(% colspan="3" %)
422 422  (((
423 423  //These mission limit-related functions (added in 3.30 Beta 1 and 2) are replaced with FFI IsMissionLimitReached()//
424 424  )))
... ... @@ -427,7 +427,7 @@
427 427  
428 428  === Version 3.20 ===
429 429  
430 -(% class="wrapped" %)
436 +(% class="table-striped" %)
431 431  |(((
432 432  Scripts
433 433  )))|(((
... ... @@ -435,7 +435,7 @@
435 435  )))|(% colspan="2" %)(((
436 436  Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed
437 437  )))
438 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
444 +|(% colspan="4" %)(% colspan="3" %)
439 439  (((
440 440  //Old params: param = attacked object, param2 = attack method, param3 = attacked component//
441 441  //New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon]
... ... @@ -451,7 +451,7 @@
451 451  (((
452 452  Removed script property $trade.**restriction.faction**
453 453  )))
454 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
460 +|(% colspan="4" %)(% colspan="3" %)
455 455  (((
456 456  //$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.//
457 457  )))
... ... @@ -462,7 +462,7 @@
462 462  )))|(% colspan="2" %)(((
463 463  **Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete!
464 464  )))
465 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
471 +|(% colspan="4" %)(% colspan="3" %)
466 466  (((
467 467  //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.//
468 468  )))
... ... @@ -471,7 +471,7 @@
471 471  
472 472  === Version 3.10 ===
473 473  
474 -(% class="wrapped" %)
480 +(% class="table-striped" %)
475 475  |(% colspan="1" %)(% colspan="1" %)
476 476  (((
477 477  Scripts
... ... @@ -482,7 +482,7 @@
482 482  (((
483 483  Removed script action **<add_build/>**
484 484  )))
485 -|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
491 +|(% colspan="7" %)(% colspan="3" %)
486 486  (((
487 487  //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.//
488 488  )))
... ... @@ -491,7 +491,7 @@
491 491  
492 492  === Version 3.00 ===
493 493  
494 -(% class="wrapped" %)
500 +(% class="table-striped" %)
495 495  |(% colspan="1" %)(% colspan="1" %)
496 496  (((
497 497  Scripts
... ... @@ -502,7 +502,7 @@
502 502  (((
503 503  Changed behaviour of script action **<get_suitable_job/>**
504 504  )))
505 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
511 +|(% colspan="4" %)(% colspan="3" %)
506 506  (((
507 507  //<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.//
508 508  )))
... ... @@ -516,7 +516,7 @@
516 516  (((
517 517  Changed behaviour of script action **<get_ware_definition/>**
518 518  )))
519 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
525 +|(% colspan="4" %)(% colspan="3" %)
520 520  (((
521 521  //<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.//
522 522  )))
... ... @@ -530,7 +530,7 @@
530 530  (((
531 531  Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case
532 532  )))
533 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
539 +|(% colspan="4" %)(% colspan="3" %)
534 534  (((
535 535  //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.)
536 536  
... ... @@ -546,7 +546,7 @@
546 546  (((
547 547  Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions>
548 548  )))
549 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
555 +|(% colspan="4" %)(% colspan="3" %)
550 550  (((
551 551  //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.//
552 552  )))
... ... @@ -560,7 +560,7 @@
560 560  (((
561 561  Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos**
562 562  )))
563 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
569 +|(% colspan="4" %)(% colspan="3" %)
564 564  (((
565 565  //Before the change, positions are relative to $dockingbay.parent.
566 566  After the change, positions are relative to $dockingbay as specified in the documentation.//
... ... @@ -575,7 +575,7 @@
575 575  (((
576 576  Support for entity flag "**skillsvisible**" dropped
577 577  )))
578 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
584 +|(% colspan="4" %)(% colspan="3" %)
579 579  (((
580 580  //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().//
581 581  )))
... ... @@ -586,7 +586,7 @@
586 586  )))|(% colspan="2" %)(((
587 587  Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**.
588 588  )))
589 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
595 +|(% colspan="4" %)(% colspan="3" %)
590 590  (((
591 591  //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.
592 592  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.
... ... @@ -603,7 +603,7 @@
603 603  (((
604 604  **MissionBoard** support dropped
605 605  )))
606 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
612 +|(% colspan="4" %)(% colspan="3" %)
607 607  (((
608 608  //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.//
609 609  )))
... ... @@ -614,7 +614,7 @@
614 614  )))|(% colspan="2" %)(((
615 615  By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined
616 616  )))
617 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
623 +|(% colspan="4" %)(% colspan="3" %)
618 618  (((
619 619  //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.//
620 620  )))
... ... @@ -628,7 +628,7 @@
628 628  (((
629 629  Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'**
630 630  )))
631 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
637 +|(% colspan="4" %)(% colspan="3" %)
632 632  (((
633 633  //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.//
634 634  )))
... ... @@ -642,7 +642,7 @@
642 642  (((
643 643  Script action **<set_doors_locked/>** attribute **'group'** changed
644 644  )))
645 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
651 +|(% colspan="4" %)(% colspan="3" %)
646 646  (((
647 647  //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.//
648 648  )))
... ... @@ -656,7 +656,7 @@
656 656  (((
657 657  Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed
658 658  )))
659 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
665 +|(% colspan="4" %)(% colspan="3" %)
660 660  (((
661 661  //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.//
662 662  )))
... ... @@ -670,7 +670,7 @@
670 670  (((
671 671  Script actions **<set_hack_target/>** and **<abort_hack/>** removed
672 672  )))
673 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
679 +|(% colspan="4" %)(% colspan="3" %)
674 674  (((
675 675  //These actions had no effect and were removed.//
676 676  )))
... ... @@ -684,7 +684,7 @@
684 684  (((
685 685  **<setup_conversation_minigame/>** script action removed
686 686  )))
687 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
693 +|(% colspan="4" %)(% colspan="3" %)
688 688  (((
689 689  //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.//
690 690  )))
... ... @@ -698,7 +698,7 @@
698 698  (((
699 699  <add_player_choice_*> **confidence** attribute removed
700 700  )))
701 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
707 +|(% colspan="4" %)(% colspan="3" %)
702 702  (((
703 703  //The default confidence of player options is another leftover from the XR era and had no effect in X4.//
704 704  )))
... ... @@ -712,7 +712,7 @@
712 712  (((
713 713  **<hack_via_control_panel/>** script action removed
714 714  )))
715 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
721 +|(% colspan="4" %)(% colspan="3" %)
716 716  (((
717 717  //Unused script action <hack_via_control_panel/> was removed.//
718 718  )))
... ... @@ -726,7 +726,7 @@
726 726  (((
727 727  **Lua: **GetMiniGameCursorPosition() removed
728 728  )))
729 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
735 +|(% colspan="4" %)(% colspan="3" %)
730 730  (((
731 731  //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.//
732 732  )))
... ... @@ -737,7 +737,7 @@
737 737  )))|(% colspan="2" %)(((
738 738  **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders
739 739  )))
740 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
746 +|(% colspan="4" %)(% colspan="3" %)
741 741  (((
742 742  //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.//
743 743  )))
... ... @@ -751,7 +751,7 @@
751 751  (((
752 752  **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor
753 753  )))
754 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
760 +|(% colspan="4" %)(% colspan="3" %)
755 755  (((
756 756  //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.//
757 757  )))
... ... @@ -765,7 +765,7 @@
765 765  (((
766 766  **$ware.illegal** updated
767 767  )))
768 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
774 +|(% colspan="4" %)(% colspan="3" %)
769 769  (((
770 770  //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.//
771 771  //It now returns true if $ware is illegal to any faction in the game.//
... ... @@ -780,7 +780,7 @@
780 780  (((
781 781  MD script **RML_Flight_Along_Path** removed
782 782  )))
783 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
789 +|(% colspan="4" %)(% colspan="3" %)
784 784  (((
785 785  //The MD script RML_Flight_Along_Path was not referened and was removed.//
786 786  )))
... ... @@ -794,7 +794,7 @@
794 794  (((
795 795  parameters of **<event_venture_mission_completed/>** changed
796 796  )))
797 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
803 +|(% colspan="4" %)(% colspan="3" %)
798 798  (((
799 799  //old params: param = venture details, param2 = ships involved, param3 = duration//
800 800  //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration//
... ... @@ -807,7 +807,7 @@
807 807  **<set_object_wing_name/>** removed,
808 808  **<set_object_fleet_name/>** added
809 809  )))
810 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
816 +|(% colspan="4" %)(% colspan="3" %)
811 811  (((
812 812  //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>//
813 813  )))
... ... @@ -819,7 +819,7 @@
819 819  **$controllable.wing.*** removed,
820 820  **$controllable.fleet.*** added
821 821  )))
822 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
828 +|(% colspan="4" %)(% colspan="3" %)
823 823  (((
824 824  $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander
825 825  )))
... ... @@ -828,7 +828,7 @@
828 828  
829 829  === Version 2.60 ===
830 830  
831 -(% class="wrapped" %)
837 +(% class="table-striped" %)
832 832  |(((
833 833  Scripts
834 834  )))|(((
... ... @@ -836,7 +836,7 @@
836 836  )))|(% colspan="2" %)(((
837 837  '**checkoperational**' filter behaviour changed
838 838  )))
839 -|(% class="highlight-grey" colspan="10" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
845 +|(% colspan="10" %)(% colspan="3" %)
840 840  (((
841 841  //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.//
842 842  
... ... @@ -849,7 +849,7 @@
849 849  )))|(% colspan="2" %)(((
850 850  $container.**supplyresources** behavior changed
851 851  )))| | |
852 -|(% class="highlight-grey" colspan="10" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
858 +|(% colspan="10" %)(% colspan="3" %)
853 853  (((
854 854  //The script keyword $container.supplyresources now includes reserved wares.//
855 855  )))
... ... @@ -858,7 +858,7 @@
858 858  
859 859  === Version 2.20 ===
860 860  
861 -(% class="wrapped" %)
867 +(% class="table-striped" %)
862 862  |(% colspan="1" %)(% colspan="1" %)
863 863  (((
864 864  UI core
... ... @@ -869,7 +869,7 @@
869 869  (((
870 870  **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined.
871 871  )))
872 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
878 +|(% colspan="4" %)(% colspan="3" %)
873 873  (((
874 874  //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.
875 875  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.//
... ... @@ -886,7 +886,7 @@
886 886  (((
887 887  Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor'
888 888  )))
889 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
895 +|(% colspan="4" %)(% colspan="3" %)
890 890  (((
891 891  //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.//
892 892  )))
... ... @@ -895,7 +895,7 @@
895 895  
896 896  === Version 2.00 ===
897 897  
898 -(% class="wrapped" %)
904 +(% class="table-striped" %)
899 899  |(% colspan="1" %)(% colspan="1" %)
900 900  (((
901 901  Scripts
... ... @@ -906,7 +906,7 @@
906 906  (((
907 907  **<event_build_finished/> **param2 now returns null instead of a construction sequence
908 908  )))
909 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
915 +|(% colspan="4" %)(% colspan="3" %)
910 910  (((
911 911  //The construction sequence which was finished should now be accessed via the buildtask provided via param3.//
912 912  )))
... ... @@ -920,7 +920,7 @@
920 920  (((
921 921  **param.boarding.{...}** strength parameters removed
922 922  )))
923 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
929 +|(% colspan="4" %)(% colspan="3" %)
924 924  (((
925 925  //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.//
926 926  )))
... ... @@ -934,7 +934,7 @@
934 934  (((
935 935  **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed
936 936  )))
937 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
943 +|(% colspan="4" %)(% colspan="3" %)
938 938  (((
939 939  //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.//
940 940  )))
... ... @@ -945,7 +945,7 @@
945 945  )))|(% colspan="2" %)(((
946 946  **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals
947 947  )))
948 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
954 +|(% colspan="4" %)(% colspan="3" %)
949 949  (((
950 950  //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.//
951 951  )))
... ... @@ -956,7 +956,7 @@
956 956  )))|(% colspan="2" %)(((
957 957  **FFI: SetFormationShape()** no longer indicates an error upon certain error cases
958 958  )))
959 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
965 +|(% colspan="4" %)(% colspan="3" %)
960 960  (((
961 961  //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.//
962 962  //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.//
... ... @@ -968,7 +968,7 @@
968 968  )))|(% colspan="2" %)(((
969 969  **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated.
970 970  )))
971 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
977 +|(% colspan="4" %)(% colspan="3" %)
972 972  (((
973 973  //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.//
974 974  )))
... ... @@ -979,7 +979,7 @@
979 979  )))|(% colspan="2" %)(((
980 980  **<event_player_changed_target/>** now fires and returns null if the player deselects a target.
981 981  )))
982 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
988 +|(% colspan="4" %)(% colspan="3" %)
983 983  (((
984 984  //For prior behavior, check for event.param being non-null.//
985 985  )))
... ... @@ -990,7 +990,7 @@
990 990  )))|(% colspan="2" %)(((
991 991  **<shoot/>/<shoot_at/>** attribute changes.
992 992  )))
993 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
999 +|(% colspan="4" %)(% colspan="3" %)
994 994  (((
995 995  //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.//
996 996  //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.//
... ... @@ -1005,7 +1005,7 @@
1005 1005  )))|(% colspan="2" %)(((
1006 1006  **FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.
1007 1007  )))
1008 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1014 +|(% colspan="4" %)(% colspan="3" %)
1009 1009  (((
1010 1010  //Added possibility to query build tasks of a certain buildmodule.//
1011 1011  )))
... ... @@ -1016,7 +1016,7 @@
1016 1016  )))|(% colspan="2" %)(((
1017 1017  **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field.
1018 1018  )))
1019 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1025 +|(% colspan="4" %)(% colspan="3" %)
1020 1020  (((
1021 1021  //Added list of resources a buildmodule needs to build.//
1022 1022  )))
... ... @@ -1027,7 +1027,7 @@
1027 1027  )))|(% colspan="2" %)(((
1028 1028  **Lua: CalculateTotalHullFraction() **was removed.
1029 1029  )))
1030 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1036 +|(% colspan="4" %)(% colspan="3" %)
1031 1031  (((
1032 1032  //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.//
1033 1033  )))
... ... @@ -1038,7 +1038,7 @@
1038 1038  )))|(% colspan="2" %)(((
1039 1039  **FFI: RequestDockAtReason()/UndockPlayerShip() **changed their return values.
1040 1040  )))
1041 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1047 +|(% colspan="4" %)(% colspan="3" %)
1042 1042  (((
1043 1043  //Changed return value type to const char* to better identify failure reasons in Lua script.//
1044 1044  )))
... ... @@ -1047,7 +1047,7 @@
1047 1047  
1048 1048  === Version 1.50 ===
1049 1049  
1050 -(% class="wrapped" %)
1056 +(% class="table-striped" %)
1051 1051  |(((
1052 1052  UI extensions
1053 1053  )))|(((
... ... @@ -1055,7 +1055,7 @@
1055 1055  )))|(% colspan="2" %)(((
1056 1056  **Lua: GetComponentData() **changed behavior of "docksizes" property.
1057 1057  )))
1058 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1064 +|(% colspan="4" %)(% colspan="3" %)
1059 1059  (((
1060 1060  //The "docksizes" property no longer includes internal ship storage docks.//
1061 1061  )))
... ... @@ -1066,7 +1066,7 @@
1066 1066  )))|(% colspan="2" %)(((
1067 1067  **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR).
1068 1068  )))
1069 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1075 +|(% colspan="4" %)(% colspan="3" %)
1070 1070  (((
1071 1071  //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".//
1072 1072  
... ... @@ -1081,7 +1081,7 @@
1081 1081  )))|(% colspan="2" %)(((
1082 1082  **FFI: UpgradeGroupInfo **datatype was changed.
1083 1083  )))
1084 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1090 +|(% colspan="4" %)(% colspan="3" %)
1085 1085  (((
1086 1086  //Added new "operational" field to retrieve information about number of operational upgrades in a group.//
1087 1087  )))
... ... @@ -1095,7 +1095,7 @@
1095 1095  (((
1096 1096  **FFI: SetGuidance()** removed useinfopoint argument.
1097 1097  )))
1098 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1104 +|(% colspan="4" %)(% colspan="3" %)
1099 1099  (((
1100 1100  //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.//
1101 1101  
... ... @@ -1108,7 +1108,7 @@
1108 1108  )))|(% colspan="2" %)(((
1109 1109  **FFI: CancelConstruction() **changed its return value.
1110 1110  )))
1111 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1117 +|(% colspan="4" %)(% colspan="3" %)
1112 1112  (((
1113 1113  //CancelConstruction() now returns if the cancellation was successful. //
1114 1114  )))
... ... @@ -1117,7 +1117,7 @@
1117 1117  
1118 1118  === Version 1.32 ===
1119 1119  
1120 -(% class="wrapped" %)
1126 +(% class="table-striped" %)
1121 1121  |(((
1122 1122  UI extensions
1123 1123  )))|(((
... ... @@ -1125,7 +1125,7 @@
1125 1125  )))|(% colspan="2" %)(((
1126 1126  **Lua: GetComponentData() **removed the "nextdestname" property.
1127 1127  )))
1128 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1134 +|(% colspan="4" %)(% colspan="3" %)
1129 1129  (((
1130 1130  //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.//
1131 1131  )))
... ... @@ -1134,7 +1134,7 @@
1134 1134  
1135 1135  === Version 1.20 ===
1136 1136  
1137 -(% class="wrapped" %)
1143 +(% class="table-striped" %)
1138 1138  |(((
1139 1139  UI extensions
1140 1140  )))|(((
... ... @@ -1142,7 +1142,7 @@
1142 1142  )))|(% colspan="2" %)(((
1143 1143  **FFI: GetAAOption()** got a new "useconfig" parameter.
1144 1144  )))
1145 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1151 +|(% colspan="4" %)(% colspan="3" %)
1146 1146  (((
1147 1147  //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.//
1148 1148  )))
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