Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 115.4
edited by Matthias Haan
on 2024/05/22 12:17
Change comment: There is no comment for this version
To version 122.1
edited by Volodymyr Boichuk
on 2024/05/29 13:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.Matthias
1 +xwiki:XWiki.Volodymyr
Content
... ... @@ -23,9 +23,17 @@
23 23  === Version 7.00 ===
24 24  
25 25  
26 -(% class="wrapped" %)
27 -|(% colspan="1" style="width:117px" %) |(% colspan="1" style="width:119px" %) |(% colspan="2" style="width:1625px" %)
28 -|(% colspan="1" style="width:117px" %) |(% colspan="1" style="width:119px" %) |(% colspan="2" style="width:1625px" %)
26 +(% class="table-striped" %)
27 +|(% colspan="1" style="width:117px" %)Assets|(% colspan="1" style="width:119px" %)7.00 Beta 7|(% colspan="2" style="width:1625px" %)**\assets\textures\fx\highway_fx_electric_02** was deleted and replaced with **\assets\textures\fx\fx_p2_electric_01**
28 +|(% colspan="4" style="width:117px" %)highway_fx_electric_02 is still available in "legacy" folder if needed
29 +|(% 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
30 +|(% colspan="4" style="width:117px" %)(((
31 +//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.//
32 +)))
33 +|(% 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.
34 +|(% colspan="4" style="width:117px" %)(((
35 +//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.**//
36 +)))
29 29  |(% 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.
30 30  |(% colspan="4" style="width:117px" %)(((
31 31  (% 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,7 +38,7 @@
38 38  )))|(% colspan="2" style="width:1625px" %)(((
39 39  MD action **<set_presentation_cluster_persistence/>** now requires the cluster to be a presentation cluster.
40 40  )))
41 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
49 +|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
42 42  (((
43 43  // Previously it was possible to set normal clusters to be persistent presentation clusters which was an invalid state.//
44 44  )))
... ... @@ -50,7 +50,7 @@
50 50  )))|(% colspan="2" style="width:1625px" %)(((
51 51  **FFI**: RemoveBuildPlot() changed
52 52  )))
53 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
61 +|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
54 54  (((
55 55  // 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.//
56 56  )))
... ... @@ -62,16 +62,14 @@
62 62  )))|(% colspan="2" style="width:1625px" %)(((
63 63  **Some Split DLC materials moved to base game**
64 64  )))
65 -|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
73 +|(% colspan="7" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
66 66  (((
67 67  // //"spl_p1_fx" AND "split_p1_hulltexture_01" were moved from Split DLC to base game
68 68  )))
69 69  
70 -----
71 -
72 72  === Version 6.00 ===
73 73  
74 -(% class="wrapped" %)
80 +(% class="table-striped" %)
75 75  |(((
76 76  Libraries
77 77  )))|(((
... ... @@ -79,7 +79,7 @@
79 79  )))|(% colspan="2" %)(((
80 80  Updated weights for ship groups in shipgroups.xml libraries of base game and all DLCs.
81 81  )))
82 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
88 +|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
83 83  (((
84 84  //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.//
85 85  
... ... @@ -95,7 +95,7 @@
95 95  (((
96 96  Changed conditions for **<event_player_travelmode_started> <event_player_travelmode_stopped> <event_player_travelmode_charge_started> <event_player_travelmode_charge_aborted>** to be raised.
97 97  )))
98 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
104 +|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
99 99  (((
100 100  //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. //
101 101  
... ... @@ -111,7 +111,7 @@
111 111  (((
112 112  Changed result of **<find_object_surface>** action in the case of a failure
113 113  )))
114 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
120 +|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
115 115  (((
116 116  //The 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.//
117 117  
... ... @@ -129,7 +129,7 @@
129 129  (((
130 130  Behaviour change for **<match_dock>** script component filter
131 131  )))
132 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
138 +|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
133 133  (((
134 134  //<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes.
135 135  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.//
... ... @@ -144,7 +144,7 @@
144 144  (((
145 145  Changed result attribute location for **<get_attackstrength>**
146 146  )))
147 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
153 +|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
148 148  (((
149 149  //The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.//
150 150  )))
... ... @@ -155,7 +155,7 @@
155 155  )))|(% colspan="2" %)(((
156 156  Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons
157 157  )))
158 -|(% 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%" %)
164 +|(% colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
159 159  (((
160 160  //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.
161 161  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.//
... ... @@ -170,7 +170,7 @@
170 170  (((
171 171  Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects
172 172  )))
173 -|(% 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%" %)
179 +|(% colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
174 174  (((
175 175  //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.//
176 176  )))
... ... @@ -181,7 +181,7 @@
181 181  )))|(% colspan="2" %)(((
182 182  **<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards.
183 183  )))
184 -|(% 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%" %)
190 +|(% colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
185 185  (((
186 186  //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.//
187 187  )))
... ... @@ -192,7 +192,7 @@
192 192  )))|(% colspan="2" %)(((
193 193  Changed behaviour of **<angles>** in cutscenes
194 194  )))
195 -|(% 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%" %)
201 +|(% colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
196 196  (((
197 197  //The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.//
198 198  )))
... ... @@ -201,7 +201,7 @@
201 201  
202 202  === Version 5.00 ===
203 203  
204 -(% class="wrapped" %)
210 +(% class="table-striped" %)
205 205  |(((
206 206  Parameters
207 207  )))|(((
... ... @@ -209,7 +209,7 @@
209 209  )))|(% colspan="2" %)(((
210 210  **<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration
211 211  )))
212 -|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
218 +|(% colspan="7" %)(% colspan="3" %)
213 213  (((
214 214  //'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.//
215 215  )))
... ... @@ -218,7 +218,7 @@
218 218  
219 219  === Version 4.10 ===
220 220  
221 -(% class="wrapped" %)
227 +(% class="table-striped" %)
222 222  |(% colspan="1" %)(% colspan="1" %)
223 223  (((
224 224  UI extensions
... ... @@ -229,7 +229,7 @@
229 229  (((
230 230  **FFI**: SetMapRenderCargoContents(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos() deprecated
231 231  )))
232 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
238 +|(% colspan="4" %)(% colspan="3" %)
233 233  (((
234 234  //The functionality represented by SetMapRenderCargoContents(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos() has been removed and the function was therefore stubbed.//
235 235  )))
... ... @@ -243,7 +243,7 @@
243 243  (((
244 244  **FFI**: CustomGameStartPlayerProperty2 changed
245 245  )))
246 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
252 +|(% colspan="4" %)(% colspan="3" %)
247 247  (((
248 248  //This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.//
249 249  )))
... ... @@ -257,7 +257,7 @@
257 257  (((
258 258  Renamed **<stationinfobox>** to **<infobox>**
259 259  )))
260 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
266 +|(% colspan="4" %)(% colspan="3" %)
261 261  (((
262 262  //Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.//
263 263  )))
... ... @@ -271,7 +271,7 @@
271 271  (((
272 272  **FFI**: SetMacroMapPlayerSectorOffset() deprecated
273 273  )))
274 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
280 +|(% colspan="4" %)(% colspan="3" %)
275 275  (((
276 276  //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.//
277 277  )))
... ... @@ -282,7 +282,7 @@
282 282  )))|(% colspan="2" %)(((
283 283  **FFI**: FilterComponentForMapMode() and SetMapObjectFilter() changed
284 284  )))
285 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
291 +|(% colspan="4" %)(% colspan="3" %)
286 286  (((
287 287  //These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.//
288 288  )))
... ... @@ -293,7 +293,7 @@
293 293  )))|(% colspan="2" %)(((
294 294  People related attributes of mission** <delivery> **node moved
295 295  )))
296 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
302 +|(% colspan="4" %)(% colspan="3" %)
297 297  (((
298 298  //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.//
299 299  )))
... ... @@ -307,7 +307,7 @@
307 307  (((
308 308  **$destructible.productions** replaced with $defensible.productions
309 309  )))
310 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
316 +|(% colspan="4" %)(% colspan="3" %)
311 311  (((
312 312  //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.//
313 313  )))
... ... @@ -318,7 +318,7 @@
318 318  )))|(% colspan="2" %)(((
319 319  Removed script property **$object.spawnsourceseed**
320 320  )))
321 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
327 +|(% colspan="4" %)(% colspan="3" %)
322 322  (((
323 323  //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.//
324 324  )))
... ... @@ -327,7 +327,7 @@
327 327  
328 328  === Version 4.00 ===
329 329  
330 -(% class="wrapped" %)
336 +(% class="table-striped" %)
331 331  |(% colspan="1" %)(% colspan="1" %)
332 332  (((
333 333  UI core
... ... @@ -338,7 +338,7 @@
338 338  (((
339 339  Controlled ship can change without a **gameplanchange-event** occurring.
340 340  )))
341 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
347 +|(% colspan="4" %)(% colspan="3" %)
342 342  (((
343 343  //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).
344 344  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.//
... ... @@ -350,7 +350,7 @@
350 350  )))|(% colspan="2" %)(((
351 351  Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed
352 352  )))
353 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
359 +|(% colspan="4" %)(% colspan="3" %)
354 354  (((
355 355  //Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects?
356 356  New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits
... ... @@ -366,7 +366,7 @@
366 366  (((
367 367  **FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed
368 368  )))
369 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
375 +|(% colspan="4" %)(% colspan="3" %)
370 370  (((
371 371  //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.
372 372  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).//
... ... @@ -383,7 +383,7 @@
383 383  (((
384 384  **FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed
385 385  )))
386 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
392 +|(% colspan="4" %)(% colspan="3" %)
387 387  (((
388 388  //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.//
389 389  
... ... @@ -396,7 +396,7 @@
396 396  )))|(% colspan="2" %)(((
397 397  **requiresconstructionvessel** parameter moved
398 398  )))
399 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
405 +|(% colspan="4" %)(% colspan="3" %)
400 400  (((
401 401  //The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.//
402 402  )))
... ... @@ -407,7 +407,7 @@
407 407  )))|(% colspan="2" %)(((
408 408  Changed behaviour of **gatedistance** script property
409 409  )))
410 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
416 +|(% colspan="4" %)(% colspan="3" %)
411 411  (((
412 412  //The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.//
413 413  )))
... ... @@ -416,7 +416,7 @@
416 416  
417 417  === Version 3.30 ===
418 418  
419 -(% class="wrapped" %)
425 +(% class="table-striped" %)
420 420  |(((
421 421  UI extensions
422 422  )))|(((
... ... @@ -424,7 +424,7 @@
424 424  )))|(% colspan="2" %)(((
425 425  **FFI: **Removed** GetMissionLimit() **and** IsMissionLimitEnabled()**
426 426  )))
427 -|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
433 +|(% colspan="7" %)(% colspan="3" %)
428 428  (((
429 429  //These mission limit-related functions (added in 3.30 Beta 1 and 2) are replaced with FFI IsMissionLimitReached()//
430 430  )))
... ... @@ -433,7 +433,7 @@
433 433  
434 434  === Version 3.20 ===
435 435  
436 -(% class="wrapped" %)
442 +(% class="table-striped" %)
437 437  |(((
438 438  Scripts
439 439  )))|(((
... ... @@ -441,7 +441,7 @@
441 441  )))|(% colspan="2" %)(((
442 442  Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed
443 443  )))
444 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
450 +|(% colspan="4" %)(% colspan="3" %)
445 445  (((
446 446  //Old params: param = attacked object, param2 = attack method, param3 = attacked component//
447 447  //New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon]
... ... @@ -457,7 +457,7 @@
457 457  (((
458 458  Removed script property $trade.**restriction.faction**
459 459  )))
460 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
466 +|(% colspan="4" %)(% colspan="3" %)
461 461  (((
462 462  //$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.//
463 463  )))
... ... @@ -468,7 +468,7 @@
468 468  )))|(% colspan="2" %)(((
469 469  **Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete!
470 470  )))
471 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
477 +|(% colspan="4" %)(% colspan="3" %)
472 472  (((
473 473  //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.//
474 474  )))
... ... @@ -477,7 +477,7 @@
477 477  
478 478  === Version 3.10 ===
479 479  
480 -(% class="wrapped" %)
486 +(% class="table-striped" %)
481 481  |(% colspan="1" %)(% colspan="1" %)
482 482  (((
483 483  Scripts
... ... @@ -488,7 +488,7 @@
488 488  (((
489 489  Removed script action **<add_build/>**
490 490  )))
491 -|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
497 +|(% colspan="7" %)(% colspan="3" %)
492 492  (((
493 493  //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.//
494 494  )))
... ... @@ -497,7 +497,7 @@
497 497  
498 498  === Version 3.00 ===
499 499  
500 -(% class="wrapped" %)
506 +(% class="table-striped" %)
501 501  |(% colspan="1" %)(% colspan="1" %)
502 502  (((
503 503  Scripts
... ... @@ -508,7 +508,7 @@
508 508  (((
509 509  Changed behaviour of script action **<get_suitable_job/>**
510 510  )))
511 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
517 +|(% colspan="4" %)(% colspan="3" %)
512 512  (((
513 513  //<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.//
514 514  )))
... ... @@ -522,7 +522,7 @@
522 522  (((
523 523  Changed behaviour of script action **<get_ware_definition/>**
524 524  )))
525 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
531 +|(% colspan="4" %)(% colspan="3" %)
526 526  (((
527 527  //<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.//
528 528  )))
... ... @@ -536,7 +536,7 @@
536 536  (((
537 537  Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case
538 538  )))
539 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
545 +|(% colspan="4" %)(% colspan="3" %)
540 540  (((
541 541  //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.)
542 542  
... ... @@ -552,7 +552,7 @@
552 552  (((
553 553  Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions>
554 554  )))
555 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
561 +|(% colspan="4" %)(% colspan="3" %)
556 556  (((
557 557  //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.//
558 558  )))
... ... @@ -566,7 +566,7 @@
566 566  (((
567 567  Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos**
568 568  )))
569 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
575 +|(% colspan="4" %)(% colspan="3" %)
570 570  (((
571 571  //Before the change, positions are relative to $dockingbay.parent.
572 572  After the change, positions are relative to $dockingbay as specified in the documentation.//
... ... @@ -581,7 +581,7 @@
581 581  (((
582 582  Support for entity flag "**skillsvisible**" dropped
583 583  )))
584 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
590 +|(% colspan="4" %)(% colspan="3" %)
585 585  (((
586 586  //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().//
587 587  )))
... ... @@ -592,7 +592,7 @@
592 592  )))|(% colspan="2" %)(((
593 593  Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**.
594 594  )))
595 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
601 +|(% colspan="4" %)(% colspan="3" %)
596 596  (((
597 597  //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.
598 598  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.
... ... @@ -609,7 +609,7 @@
609 609  (((
610 610  **MissionBoard** support dropped
611 611  )))
612 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
618 +|(% colspan="4" %)(% colspan="3" %)
613 613  (((
614 614  //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.//
615 615  )))
... ... @@ -620,7 +620,7 @@
620 620  )))|(% colspan="2" %)(((
621 621  By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined
622 622  )))
623 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
629 +|(% colspan="4" %)(% colspan="3" %)
624 624  (((
625 625  //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.//
626 626  )))
... ... @@ -634,7 +634,7 @@
634 634  (((
635 635  Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'**
636 636  )))
637 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
643 +|(% colspan="4" %)(% colspan="3" %)
638 638  (((
639 639  //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.//
640 640  )))
... ... @@ -648,7 +648,7 @@
648 648  (((
649 649  Script action **<set_doors_locked/>** attribute **'group'** changed
650 650  )))
651 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
657 +|(% colspan="4" %)(% colspan="3" %)
652 652  (((
653 653  //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.//
654 654  )))
... ... @@ -662,7 +662,7 @@
662 662  (((
663 663  Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed
664 664  )))
665 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
671 +|(% colspan="4" %)(% colspan="3" %)
666 666  (((
667 667  //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.//
668 668  )))
... ... @@ -676,7 +676,7 @@
676 676  (((
677 677  Script actions **<set_hack_target/>** and **<abort_hack/>** removed
678 678  )))
679 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
685 +|(% colspan="4" %)(% colspan="3" %)
680 680  (((
681 681  //These actions had no effect and were removed.//
682 682  )))
... ... @@ -690,7 +690,7 @@
690 690  (((
691 691  **<setup_conversation_minigame/>** script action removed
692 692  )))
693 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
699 +|(% colspan="4" %)(% colspan="3" %)
694 694  (((
695 695  //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.//
696 696  )))
... ... @@ -704,7 +704,7 @@
704 704  (((
705 705  <add_player_choice_*> **confidence** attribute removed
706 706  )))
707 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
713 +|(% colspan="4" %)(% colspan="3" %)
708 708  (((
709 709  //The default confidence of player options is another leftover from the XR era and had no effect in X4.//
710 710  )))
... ... @@ -718,7 +718,7 @@
718 718  (((
719 719  **<hack_via_control_panel/>** script action removed
720 720  )))
721 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
727 +|(% colspan="4" %)(% colspan="3" %)
722 722  (((
723 723  //Unused script action <hack_via_control_panel/> was removed.//
724 724  )))
... ... @@ -732,7 +732,7 @@
732 732  (((
733 733  **Lua: **GetMiniGameCursorPosition() removed
734 734  )))
735 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
741 +|(% colspan="4" %)(% colspan="3" %)
736 736  (((
737 737  //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.//
738 738  )))
... ... @@ -743,7 +743,7 @@
743 743  )))|(% colspan="2" %)(((
744 744  **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders
745 745  )))
746 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
752 +|(% colspan="4" %)(% colspan="3" %)
747 747  (((
748 748  //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.//
749 749  )))
... ... @@ -757,7 +757,7 @@
757 757  (((
758 758  **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor
759 759  )))
760 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
766 +|(% colspan="4" %)(% colspan="3" %)
761 761  (((
762 762  //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.//
763 763  )))
... ... @@ -771,7 +771,7 @@
771 771  (((
772 772  **$ware.illegal** updated
773 773  )))
774 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
780 +|(% colspan="4" %)(% colspan="3" %)
775 775  (((
776 776  //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.//
777 777  //It now returns true if $ware is illegal to any faction in the game.//
... ... @@ -786,7 +786,7 @@
786 786  (((
787 787  MD script **RML_Flight_Along_Path** removed
788 788  )))
789 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
795 +|(% colspan="4" %)(% colspan="3" %)
790 790  (((
791 791  //The MD script RML_Flight_Along_Path was not referened and was removed.//
792 792  )))
... ... @@ -800,7 +800,7 @@
800 800  (((
801 801  parameters of **<event_venture_mission_completed/>** changed
802 802  )))
803 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
809 +|(% colspan="4" %)(% colspan="3" %)
804 804  (((
805 805  //old params: param = venture details, param2 = ships involved, param3 = duration//
806 806  //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration//
... ... @@ -813,7 +813,7 @@
813 813  **<set_object_wing_name/>** removed,
814 814  **<set_object_fleet_name/>** added
815 815  )))
816 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
822 +|(% colspan="4" %)(% colspan="3" %)
817 817  (((
818 818  //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>//
819 819  )))
... ... @@ -825,7 +825,7 @@
825 825  **$controllable.wing.*** removed,
826 826  **$controllable.fleet.*** added
827 827  )))
828 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
834 +|(% colspan="4" %)(% colspan="3" %)
829 829  (((
830 830  $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander
831 831  )))
... ... @@ -834,7 +834,7 @@
834 834  
835 835  === Version 2.60 ===
836 836  
837 -(% class="wrapped" %)
843 +(% class="table-striped" %)
838 838  |(((
839 839  Scripts
840 840  )))|(((
... ... @@ -842,7 +842,7 @@
842 842  )))|(% colspan="2" %)(((
843 843  '**checkoperational**' filter behaviour changed
844 844  )))
845 -|(% class="highlight-grey" colspan="10" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
851 +|(% colspan="10" %)(% colspan="3" %)
846 846  (((
847 847  //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.//
848 848  
... ... @@ -855,7 +855,7 @@
855 855  )))|(% colspan="2" %)(((
856 856  $container.**supplyresources** behavior changed
857 857  )))| | |
858 -|(% class="highlight-grey" colspan="10" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
864 +|(% colspan="10" %)(% colspan="3" %)
859 859  (((
860 860  //The script keyword $container.supplyresources now includes reserved wares.//
861 861  )))
... ... @@ -864,7 +864,7 @@
864 864  
865 865  === Version 2.20 ===
866 866  
867 -(% class="wrapped" %)
873 +(% class="table-striped" %)
868 868  |(% colspan="1" %)(% colspan="1" %)
869 869  (((
870 870  UI core
... ... @@ -875,7 +875,7 @@
875 875  (((
876 876  **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined.
877 877  )))
878 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
884 +|(% colspan="4" %)(% colspan="3" %)
879 879  (((
880 880  //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.
881 881  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.//
... ... @@ -892,7 +892,7 @@
892 892  (((
893 893  Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor'
894 894  )))
895 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
901 +|(% colspan="4" %)(% colspan="3" %)
896 896  (((
897 897  //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.//
898 898  )))
... ... @@ -901,7 +901,7 @@
901 901  
902 902  === Version 2.00 ===
903 903  
904 -(% class="wrapped" %)
910 +(% class="table-striped" %)
905 905  |(% colspan="1" %)(% colspan="1" %)
906 906  (((
907 907  Scripts
... ... @@ -912,7 +912,7 @@
912 912  (((
913 913  **<event_build_finished/> **param2 now returns null instead of a construction sequence
914 914  )))
915 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
921 +|(% colspan="4" %)(% colspan="3" %)
916 916  (((
917 917  //The construction sequence which was finished should now be accessed via the buildtask provided via param3.//
918 918  )))
... ... @@ -926,7 +926,7 @@
926 926  (((
927 927  **param.boarding.{...}** strength parameters removed
928 928  )))
929 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
935 +|(% colspan="4" %)(% colspan="3" %)
930 930  (((
931 931  //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.//
932 932  )))
... ... @@ -940,7 +940,7 @@
940 940  (((
941 941  **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed
942 942  )))
943 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
949 +|(% colspan="4" %)(% colspan="3" %)
944 944  (((
945 945  //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.//
946 946  )))
... ... @@ -951,7 +951,7 @@
951 951  )))|(% colspan="2" %)(((
952 952  **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals
953 953  )))
954 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
960 +|(% colspan="4" %)(% colspan="3" %)
955 955  (((
956 956  //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.//
957 957  )))
... ... @@ -962,7 +962,7 @@
962 962  )))|(% colspan="2" %)(((
963 963  **FFI: SetFormationShape()** no longer indicates an error upon certain error cases
964 964  )))
965 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
971 +|(% colspan="4" %)(% colspan="3" %)
966 966  (((
967 967  //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.//
968 968  //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.//
... ... @@ -974,7 +974,7 @@
974 974  )))|(% colspan="2" %)(((
975 975  **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated.
976 976  )))
977 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
983 +|(% colspan="4" %)(% colspan="3" %)
978 978  (((
979 979  //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.//
980 980  )))
... ... @@ -985,7 +985,7 @@
985 985  )))|(% colspan="2" %)(((
986 986  **<event_player_changed_target/>** now fires and returns null if the player deselects a target.
987 987  )))
988 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
994 +|(% colspan="4" %)(% colspan="3" %)
989 989  (((
990 990  //For prior behavior, check for event.param being non-null.//
991 991  )))
... ... @@ -996,7 +996,7 @@
996 996  )))|(% colspan="2" %)(((
997 997  **<shoot/>/<shoot_at/>** attribute changes.
998 998  )))
999 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1005 +|(% colspan="4" %)(% colspan="3" %)
1000 1000  (((
1001 1001  //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.//
1002 1002  //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.//
... ... @@ -1011,7 +1011,7 @@
1011 1011  )))|(% colspan="2" %)(((
1012 1012  **FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.
1013 1013  )))
1014 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1020 +|(% colspan="4" %)(% colspan="3" %)
1015 1015  (((
1016 1016  //Added possibility to query build tasks of a certain buildmodule.//
1017 1017  )))
... ... @@ -1022,7 +1022,7 @@
1022 1022  )))|(% colspan="2" %)(((
1023 1023  **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field.
1024 1024  )))
1025 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1031 +|(% colspan="4" %)(% colspan="3" %)
1026 1026  (((
1027 1027  //Added list of resources a buildmodule needs to build.//
1028 1028  )))
... ... @@ -1033,7 +1033,7 @@
1033 1033  )))|(% colspan="2" %)(((
1034 1034  **Lua: CalculateTotalHullFraction() **was removed.
1035 1035  )))
1036 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1042 +|(% colspan="4" %)(% colspan="3" %)
1037 1037  (((
1038 1038  //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.//
1039 1039  )))
... ... @@ -1044,7 +1044,7 @@
1044 1044  )))|(% colspan="2" %)(((
1045 1045  **FFI: RequestDockAtReason()/UndockPlayerShip() **changed their return values.
1046 1046  )))
1047 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1053 +|(% colspan="4" %)(% colspan="3" %)
1048 1048  (((
1049 1049  //Changed return value type to const char* to better identify failure reasons in Lua script.//
1050 1050  )))
... ... @@ -1053,7 +1053,7 @@
1053 1053  
1054 1054  === Version 1.50 ===
1055 1055  
1056 -(% class="wrapped" %)
1062 +(% class="table-striped" %)
1057 1057  |(((
1058 1058  UI extensions
1059 1059  )))|(((
... ... @@ -1061,7 +1061,7 @@
1061 1061  )))|(% colspan="2" %)(((
1062 1062  **Lua: GetComponentData() **changed behavior of "docksizes" property.
1063 1063  )))
1064 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1070 +|(% colspan="4" %)(% colspan="3" %)
1065 1065  (((
1066 1066  //The "docksizes" property no longer includes internal ship storage docks.//
1067 1067  )))
... ... @@ -1072,7 +1072,7 @@
1072 1072  )))|(% colspan="2" %)(((
1073 1073  **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR).
1074 1074  )))
1075 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1081 +|(% colspan="4" %)(% colspan="3" %)
1076 1076  (((
1077 1077  //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".//
1078 1078  
... ... @@ -1087,7 +1087,7 @@
1087 1087  )))|(% colspan="2" %)(((
1088 1088  **FFI: UpgradeGroupInfo **datatype was changed.
1089 1089  )))
1090 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1096 +|(% colspan="4" %)(% colspan="3" %)
1091 1091  (((
1092 1092  //Added new "operational" field to retrieve information about number of operational upgrades in a group.//
1093 1093  )))
... ... @@ -1101,7 +1101,7 @@
1101 1101  (((
1102 1102  **FFI: SetGuidance()** removed useinfopoint argument.
1103 1103  )))
1104 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1110 +|(% colspan="4" %)(% colspan="3" %)
1105 1105  (((
1106 1106  //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.//
1107 1107  
... ... @@ -1114,7 +1114,7 @@
1114 1114  )))|(% colspan="2" %)(((
1115 1115  **FFI: CancelConstruction() **changed its return value.
1116 1116  )))
1117 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1123 +|(% colspan="4" %)(% colspan="3" %)
1118 1118  (((
1119 1119  //CancelConstruction() now returns if the cancellation was successful. //
1120 1120  )))
... ... @@ -1123,7 +1123,7 @@
1123 1123  
1124 1124  === Version 1.32 ===
1125 1125  
1126 -(% class="wrapped" %)
1132 +(% class="table-striped" %)
1127 1127  |(((
1128 1128  UI extensions
1129 1129  )))|(((
... ... @@ -1131,7 +1131,7 @@
1131 1131  )))|(% colspan="2" %)(((
1132 1132  **Lua: GetComponentData() **removed the "nextdestname" property.
1133 1133  )))
1134 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1140 +|(% colspan="4" %)(% colspan="3" %)
1135 1135  (((
1136 1136  //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.//
1137 1137  )))
... ... @@ -1140,7 +1140,7 @@
1140 1140  
1141 1141  === Version 1.20 ===
1142 1142  
1143 -(% class="wrapped" %)
1149 +(% class="table-striped" %)
1144 1144  |(((
1145 1145  UI extensions
1146 1146  )))|(((
... ... @@ -1148,7 +1148,7 @@
1148 1148  )))|(% colspan="2" %)(((
1149 1149  **FFI: GetAAOption()** got a new "useconfig" parameter.
1150 1150  )))
1151 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1157 +|(% colspan="4" %)(% colspan="3" %)
1152 1152  (((
1153 1153  //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.//
1154 1154  )))
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