Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 96.1
edited by klaus
on 2023/01/04 13:23
Change comment: There is no comment for this version
To version 88.1
edited by florian
on 2021/06/17 12:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.klaus
1 +xwiki:XWiki.florian
Content
... ... @@ -18,7 +18,6 @@
18 18  
19 19  = Breaking Changes =
20 20  
21 -(% class="wrapped" %)
22 22  |=(((
23 23  Type
24 24  )))|=(((
... ... @@ -25,65 +25,12 @@
25 25  Version
26 26  )))|=(((
27 27  Summary
28 -)))
29 -|(% colspan="3" %)(% colspan="3" %)
27 +)))|=(% colspan="1" %)(% colspan="1" %)
30 30  (((
31 -== 6.00 ==
29 +
32 32  )))
33 -|(((
34 -Assets
35 -)))|(((
36 -6.00 Beta 1
37 -)))|(((
38 -Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons
39 -)))
40 -|(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)
31 +|(% colspan="4" %)(% colspan="4" %)
41 41  (((
42 -//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.
43 -//
44 -)))
45 -|(% colspan="1" %)(% colspan="1" %)
46 -(((
47 -Scripts
48 -)))|(% colspan="1" %)(% colspan="1" %)
49 -(((
50 -6.00 Beta 1
51 -)))|(% colspan="1" %)(% colspan="1" %)
52 -(((
53 -Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects
54 -)))
55 -|(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)
56 -(((
57 -//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.//
58 -)))
59 -|(((
60 -Scripts
61 -)))|(((
62 -6.00 Beta 1
63 -)))|(((
64 -**<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards.
65 -)))
66 -|(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)
67 -(((
68 -//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.//
69 -)))
70 -|(% colspan="3" %)(% colspan="3" %)
71 -(((
72 -== 5.00 ==
73 -)))
74 -|(((
75 -Parameters
76 -)))|(((
77 -5.00 Beta 1
78 -)))|(((
79 -**<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration
80 -)))
81 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
82 -(((
83 -//'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.//
84 -)))
85 -|(% colspan="3" %)(% colspan="3" %)
86 -(((
87 87  == 4.10 ==
88 88  )))
89 89  |(% colspan="1" %)(% colspan="1" %)
... ... @@ -91,76 +91,31 @@
91 91  UI extensions
92 92  )))|(% colspan="1" %)(% colspan="1" %)
93 93  (((
94 -4.10 Beta 7
40 +4.10 Beta 2
95 95  )))|(% colspan="1" %)(% colspan="1" %)
96 96  (((
97 -**FFI**: (% style="color: rgb(0,0,0);" %)SetMapRenderCargoContents(%%)(), (% style="color: rgb(0,0,0);" %)SetMapRenderWorkForceInfo(), (% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)SetMapRenderCrewInfo() and (% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)SetMapRenderDockedShipInfos()(%%) deprecated
98 -)))
99 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
100 -(((
101 -//The functionality represented by (% style="color: rgb(0,0,0);" %)SetMapRenderCargoContents(%%)(), (% style="color: rgb(0,0,0);" %)SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos()(%%) has been removed and the function was therefore stubbed.//
102 -)))
103 -|(% colspan="1" %)(% colspan="1" %)
104 -(((
105 -UI extensions
43 +FFI: SetMacroMapPlayerSectorOffset() deprecated
106 106  )))|(% colspan="1" %)(% colspan="1" %)
107 107  (((
108 -4.10 Beta 6
109 -)))|(% colspan="1" %)(% colspan="1" %)
110 -(((
111 -**FFI**: CustomGameStartPlayerProperty2 changed
46 +
112 112  )))
113 113  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
114 114  (((
115 -//This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.//
116 -)))
117 -|(% colspan="1" %)(% colspan="1" %)
118 -(((
119 -Parameters
50 +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.
120 120  )))|(% colspan="1" %)(% colspan="1" %)
121 121  (((
122 -4.10 Beta 3
123 -)))|(% colspan="1" %)(% colspan="1" %)
124 -(((
125 -Renamed **<stationinfobox>** to **<infobox>**
53 +
126 126  )))
127 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
128 -(((
129 -//Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.//
130 -)))
131 -|(% colspan="1" %)(% colspan="1" %)
132 -(((
133 -UI extensions
134 -)))|(% colspan="1" %)(% colspan="1" %)
135 -(((
136 -4.10 Beta 2
137 -)))|(% colspan="1" %)(% colspan="1" %)
138 -(((
139 -**FFI**: SetMacroMapPlayerSectorOffset() deprecated
140 -)))
141 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
142 -(((
143 -//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.//
144 -)))
145 145  |(((
146 -UI extensions
147 -)))|(((
148 -4.10 Beta 2
149 -)))|(((
150 -**FFI**: (% style="color: rgb(0,0,0);" %)FilterComponentForMapMode(%%)() and (% style="color: rgb(0,0,0);" %)SetMapObjectFilter() changed
151 -)))
152 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
153 -(((
154 -//These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.//
155 -)))
156 -|(((
157 157  Scripts
158 158  )))|(((
159 159  4.10 Beta 1
160 160  )))|(((
161 161  People related attributes of mission** <delivery> **node moved
61 +)))|(((
62 +
162 162  )))
163 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
64 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
164 164  (((
165 165  //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.//
166 166  )))
... ... @@ -173,10 +173,16 @@
173 173  )))|(% colspan="1" %)(% colspan="1" %)
174 174  (((
175 175  **$destructible.productions** replaced with $defensible.productions
77 +)))|(% colspan="1" %)(% colspan="1" %)
78 +(((
79 +
176 176  )))
177 177  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
178 178  (((
179 179  //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.//
84 +)))|(% colspan="1" %)(% colspan="1" %)
85 +(((
86 +
180 180  )))
181 181  |(((
182 182  Scripts
... ... @@ -184,12 +184,14 @@
184 184  4.10 Beta 1
185 185  )))|(((
186 186  Removed script property **$object.spawnsourceseed**
94 +)))|(((
95 +
187 187  )))
188 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
97 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
189 189  (((
190 190  //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.//
191 191  )))
192 -|(% colspan="3" %)(% colspan="3" %)
101 +|(% colspan="4" %)(% colspan="4" %)
193 193  (((
194 194  == 4.00 ==
195 195  )))
... ... @@ -202,6 +202,9 @@
202 202  )))|(% colspan="1" %)(% colspan="1" %)
203 203  (((
204 204  Controlled ship can change without a **gameplanchange-event** occurring.
114 +)))|(% colspan="1" %)(% colspan="1" %)
115 +(((
116 +
205 205  )))
206 206  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
207 207  (((
... ... @@ -208,6 +208,9 @@
208 208  //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).
209 209  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.
210 210  //
123 +)))|(% colspan="1" %)(% colspan="1" %)
124 +(((
125 +
211 211  )))
212 212  |(((
213 213  Scripts
... ... @@ -215,6 +215,8 @@
215 215  4.00 Beta 7
216 216  )))|(((
217 217  Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed
133 +)))|(((
134 +
218 218  )))
219 219  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
220 220  (((
... ... @@ -221,6 +221,9 @@
221 221  //Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects?
222 222  New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits
223 223  Note: param3 only exists in <event_terraforming_project_succeeded> and not in <event_terraforming_project_failed>, but both now have the booleans in a list for consistency//
141 +)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %)
142 +(((
143 +
224 224  )))
225 225  |(% colspan="1" %)(% colspan="1" %)
226 226  (((
... ... @@ -231,6 +231,9 @@
231 231  )))|(% colspan="1" %)(% colspan="1" %)
232 232  (((
233 233  **FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed
154 +)))|(% colspan="1" %)(% colspan="1" %)
155 +(((
156 +
234 234  )))
235 235  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
236 236  (((
... ... @@ -239,6 +239,9 @@
239 239  
240 240  //If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.
241 241  //
165 +)))|(% colspan="1" %)(% colspan="1" %)
166 +(((
167 +
242 242  )))
243 243  |(% colspan="1" %)(% colspan="1" %)
244 244  (((
... ... @@ -249,6 +249,9 @@
249 249  )))|(% colspan="1" %)(% colspan="1" %)
250 250  (((
251 251  **FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed
178 +)))|(% colspan="1" %)(% colspan="1" %)
179 +(((
180 +
252 252  )))
253 253  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
254 254  (((
... ... @@ -255,6 +255,9 @@
255 255  //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.//
256 256  
257 257  //If you rely on a handling where they are treated like enemies, please use the new GetRelationStatus3() //function which returns the new range for these objects: 1 (meaning 'enemy' (aka: not yet hostile) here with following relations having been shifted up).
187 +)))|(% colspan="1" %)(% colspan="1" %)
188 +(((
189 +
258 258  )))
259 259  |(((
260 260  Parameters
... ... @@ -262,8 +262,10 @@
262 262  4.00 Beta 1
263 263  )))|(((
264 264  **requiresconstructionvessel** parameter moved
197 +)))|(((
198 +
265 265  )))
266 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
200 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
267 267  (((
268 268  //The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.//
269 269  )))
... ... @@ -273,12 +273,17 @@
273 273  4.00 Beta 1
274 274  )))|(((
275 275  Changed behaviour of **gatedistance** script property
210 +)))|(((
211 +
276 276  )))
277 277  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
278 278  (((
279 279  //The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.//
216 +)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %)
217 +(((
218 +
280 280  )))
281 -|(% colspan="3" %)(% colspan="3" %)
220 +|(% colspan="4" %)(% colspan="4" %)
282 282  (((
283 283  == 3.30 ==
284 284  )))
... ... @@ -288,12 +288,15 @@
288 288  3.30 Beta 3
289 289  )))|(((
290 290  **FFI: **Removed** (% style="color: rgb(0,0,0);" %)GetMissionLimit() (%%)**(% style="color: rgb(0,0,0);" %)and** **(% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)**IsMissionLimit**(%%)**Enabled()**
230 +)))|(% colspan="1" %)(% colspan="1" %)
231 +(((
232 +
291 291  )))
292 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
234 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
293 293  (((
294 294  //These mission limit-related functions (added in 3.30 Beta 1 and 2) are replaced with FFI (% style="color: rgb(0,0,0);" %)IsMissionLimit(%%)Reach(% style="color: rgb(0,0,0);" %)ed()//
295 295  )))
296 -|(% colspan="3" %)(% colspan="3" %)
238 +|(% colspan="4" %)(% colspan="4" %)
297 297  (((
298 298  == 3.20 ==
299 299  )))
... ... @@ -303,8 +303,11 @@
303 303  3.20 Beta 1
304 304  )))|(((
305 305  Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed
248 +)))|(% colspan="1" %)(% colspan="1" %)
249 +(((
250 +
306 306  )))
307 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
252 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
308 308  (((
309 309  //Old params: param = attacked object, param2 = attack method, param3 = attacked component//
310 310  //New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon]
... ... @@ -319,8 +319,11 @@
319 319  )))|(% colspan="1" %)(% colspan="1" %)
320 320  (((
321 321  Removed script property $trade.**restriction.faction**
267 +)))|(% colspan="1" %)(% colspan="1" %)
268 +(((
269 +
322 322  )))
323 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
271 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
324 324  (((
325 325  //$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.//
326 326  )))
... ... @@ -330,12 +330,15 @@
330 330  3.20 Beta 1
331 331  )))|(((
332 332  **Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete!
281 +)))|(% colspan="1" %)(% colspan="1" %)
282 +(((
283 +
333 333  )))
334 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
285 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
335 335  (((
336 336  //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.//
337 337  )))
338 -|(% colspan="3" %)(% colspan="3" %)
289 +|(% colspan="4" %)(% colspan="4" %)
339 339  (((
340 340  == 3.10 ==
341 341  )))
... ... @@ -348,12 +348,15 @@
348 348  )))|(% colspan="1" %)(% colspan="1" %)
349 349  (((
350 350  Removed script action **<add_build/>**
302 +)))|(% colspan="1" %)(% colspan="1" %)
303 +(((
304 +
351 351  )))
352 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
306 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
353 353  (((
354 354  //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.//
355 355  )))
356 -|(% colspan="3" %)(% colspan="3" %)
310 +|(% colspan="4" %)(% colspan="4" %)
357 357  (((
358 358  == 3.00 ==
359 359  )))
... ... @@ -366,8 +366,11 @@
366 366  )))|(% colspan="1" %)(% colspan="1" %)
367 367  (((
368 368  Changed behaviour of script action **<get_suitable_job/>**
323 +)))|(% colspan="1" %)(% colspan="1" %)
324 +(((
325 +
369 369  )))
370 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
327 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
371 371  (((
372 372  //<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.//
373 373  )))
... ... @@ -380,8 +380,11 @@
380 380  )))|(% colspan="1" %)(% colspan="1" %)
381 381  (((
382 382  Changed behaviour of script action **<get_ware_definition/>**
340 +)))|(% colspan="1" %)(% colspan="1" %)
341 +(((
342 +
383 383  )))
384 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
344 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
385 385  (((
386 386  //<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.//
387 387  )))
... ... @@ -394,8 +394,11 @@
394 394  )))|(% colspan="1" %)(% colspan="1" %)
395 395  (((
396 396  Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case
357 +)))|(% colspan="1" %)(% colspan="1" %)
358 +(((
359 +
397 397  )))
398 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
361 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
399 399  (((
400 400  //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.)\\
401 401  
... ... @@ -410,8 +410,11 @@
410 410  )))|(% colspan="1" %)(% colspan="1" %)
411 411  (((
412 412  Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions>
376 +)))|(% colspan="1" %)(% colspan="1" %)
377 +(((
378 +
413 413  )))
414 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
380 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
415 415  (((
416 416  //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.//
417 417  )))
... ... @@ -424,8 +424,11 @@
424 424  )))|(% colspan="1" %)(% colspan="1" %)
425 425  (((
426 426  Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos**
393 +)))|(% colspan="1" %)(% colspan="1" %)
394 +(((
395 +
427 427  )))
428 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
397 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
429 429  (((
430 430  //Before the change, positions are relative to $dockingbay.parent.
431 431  After the change, positions are relative to $dockingbay as specified in the documentation.//
... ... @@ -439,8 +439,11 @@
439 439  )))|(% colspan="1" %)(% colspan="1" %)
440 440  (((
441 441  Support for entity flag "**skillsvisible**" dropped
411 +)))|(% colspan="1" %)(% colspan="1" %)
412 +(((
413 +
442 442  )))
443 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
415 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
444 444  (((
445 445  //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().//
446 446  )))
... ... @@ -450,8 +450,11 @@
450 450  3.0 Beta 2
451 451  )))|(((
452 452  Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**.
425 +)))|(% colspan="1" %)(% colspan="1" %)
426 +(((
427 +
453 453  )))
454 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
429 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
455 455  (((
456 456  //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.
457 457  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.
... ... @@ -467,8 +467,11 @@
467 467  )))|(% colspan="1" %)(% colspan="1" %)
468 468  (((
469 469  **MissionBoard** support dropped
445 +)))|(% colspan="1" %)(% colspan="1" %)
446 +(((
447 +
470 470  )))
471 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
449 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
472 472  (((
473 473  //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.//
474 474  )))
... ... @@ -478,8 +478,11 @@
478 478  3.0 Beta 1
479 479  )))|(((
480 480  By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined
459 +)))|(% colspan="1" %)(% colspan="1" %)
460 +(((
461 +
481 481  )))
482 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
463 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
483 483  (((
484 484  //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.//
485 485  )))
... ... @@ -492,8 +492,11 @@
492 492  )))|(% colspan="1" %)(% colspan="1" %)
493 493  (((
494 494  Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'**
476 +)))|(% colspan="1" %)(% colspan="1" %)
477 +(((
478 +
495 495  )))
496 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
480 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
497 497  (((
498 498  //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.//
499 499  )))
... ... @@ -506,8 +506,11 @@
506 506  )))|(% colspan="1" %)(% colspan="1" %)
507 507  (((
508 508  Script action **<set_doors_locked/>** attribute **'group'** changed
493 +)))|(% colspan="1" %)(% colspan="1" %)
494 +(((
495 +
509 509  )))
510 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
497 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
511 511  (((
512 512  //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.//
513 513  )))
... ... @@ -520,8 +520,11 @@
520 520  )))|(% colspan="1" %)(% colspan="1" %)
521 521  (((
522 522  Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed
510 +)))|(% colspan="1" %)(% colspan="1" %)
511 +(((
512 +
523 523  )))
524 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
514 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
525 525  (((
526 526  //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.//
527 527  )))
... ... @@ -534,8 +534,11 @@
534 534  )))|(% colspan="1" %)(% colspan="1" %)
535 535  (((
536 536  Script actions **<set_hack_target/>** and **<abort_hack/>** removed
527 +)))|(% colspan="1" %)(% colspan="1" %)
528 +(((
529 +
537 537  )))
538 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
531 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
539 539  (((
540 540  //These actions had no effect and were removed.//
541 541  )))
... ... @@ -548,8 +548,11 @@
548 548  )))|(% colspan="1" %)(% colspan="1" %)
549 549  (((
550 550  **<setup_conversation_minigame/>** script action removed
544 +)))|(% colspan="1" %)(% colspan="1" %)
545 +(((
546 +
551 551  )))
552 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
548 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
553 553  (((
554 554  //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.//
555 555  )))
... ... @@ -562,8 +562,11 @@
562 562  )))|(% colspan="1" %)(% colspan="1" %)
563 563  (((
564 564  <add_player_choice_*> **confidence** attribute removed
561 +)))|(% colspan="1" %)(% colspan="1" %)
562 +(((
563 +
565 565  )))
566 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
565 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
567 567  (((
568 568  //The default confidence of player options is another leftover from the XR era and had no effect in X4.//
569 569  )))
... ... @@ -576,8 +576,11 @@
576 576  )))|(% colspan="1" %)(% colspan="1" %)
577 577  (((
578 578  **<hack_via_control_panel/>** script action removed
578 +)))|(% colspan="1" %)(% colspan="1" %)
579 +(((
580 +
579 579  )))
580 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
582 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
581 581  (((
582 582  //Unused script action <hack_via_control_panel/> was removed.//
583 583  )))
... ... @@ -590,8 +590,11 @@
590 590  )))|(% colspan="1" %)(% colspan="1" %)
591 591  (((
592 592  **Lua: **GetMiniGameCursorPosition() removed
595 +)))|(% colspan="1" %)(% colspan="1" %)
596 +(((
597 +
593 593  )))
594 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
599 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
595 595  (((
596 596  //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.//
597 597  )))
... ... @@ -601,8 +601,11 @@
601 601  3.0 Beta 1
602 602  )))|(((
603 603  **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders
609 +)))|(% colspan="1" %)(% colspan="1" %)
610 +(((
611 +
604 604  )))
605 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
613 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
606 606  (((
607 607  //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.//
608 608  )))
... ... @@ -615,8 +615,11 @@
615 615  )))|(% colspan="1" %)(% colspan="1" %)
616 616  (((
617 617  **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor
626 +)))|(% colspan="1" %)(% colspan="1" %)
627 +(((
628 +
618 618  )))
619 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
630 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
620 620  (((
621 621  //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.//
622 622  )))
... ... @@ -629,8 +629,11 @@
629 629  )))|(% colspan="1" %)(% colspan="1" %)
630 630  (((
631 631  **$ware.illegal** updated
643 +)))|(% colspan="1" %)(% colspan="1" %)
644 +(((
645 +
632 632  )))
633 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
647 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
634 634  (((
635 635  //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.//
636 636  //It now returns true if $ware is illegal to any faction in the game.//
... ... @@ -644,8 +644,11 @@
644 644  )))|(% colspan="1" %)(% colspan="1" %)
645 645  (((
646 646  MD script **RML_Flight_Along_Path** removed
661 +)))|(% colspan="1" %)(% colspan="1" %)
662 +(((
663 +
647 647  )))
648 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
665 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
649 649  (((
650 650  //The MD script RML_Flight_Along_Path was not referened and was removed.//
651 651  )))
... ... @@ -658,8 +658,11 @@
658 658  )))|(% colspan="1" %)(% colspan="1" %)
659 659  (((
660 660  parameters of **<event_venture_mission_completed/>** changed
678 +)))|(% colspan="1" %)(% colspan="1" %)
679 +(((
680 +
661 661  )))
662 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
682 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
663 663  (((
664 664  //old params: param = venture details, param2 = ships involved, param3 = duration//
665 665  //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration//
... ... @@ -671,8 +671,11 @@
671 671  )))|(((
672 672  **<set_object_wing_name/>** removed,
673 673  **<set_object_fleet_name/>** added
694 +)))|(% colspan="1" %)(% colspan="1" %)
695 +(((
696 +
674 674  )))
675 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
698 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
676 676  (((
677 677  //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>//
678 678  )))
... ... @@ -683,12 +683,15 @@
683 683  )))|(((
684 684  **$controllable.wing.*** removed,
685 685  **$controllable.fleet.*** added
709 +)))|(% colspan="1" %)(% colspan="1" %)
710 +(((
711 +
686 686  )))
687 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
713 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
688 688  (((
689 689  $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander
690 690  )))
691 -|(% colspan="3" %)(% colspan="3" %)
717 +|(% colspan="4" %)(% colspan="4" %)
692 692  (((
693 693  == 2.60 ==
694 694  )))
... ... @@ -698,8 +698,11 @@
698 698  2.60 Beta 1
699 699  )))|(((
700 700  '**checkoperational**' filter behaviour changed
727 +)))|(% colspan="1" %)(% colspan="1" %)
728 +(((
729 +
701 701  )))
702 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
731 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
703 703  (((
704 704  //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.//
705 705  
... ... @@ -711,12 +711,15 @@
711 711  2.60 Beta 1
712 712  )))|(((
713 713  $container.**supplyresources** behavior changed
743 +)))|(% colspan="1" %)(% colspan="1" %)
744 +(((
745 +
714 714  )))
715 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
747 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
716 716  (((
717 717  //The script keyword $container.supplyresources now includes reserved wares.//
718 718  )))
719 -|(% colspan="3" %)(% colspan="3" %)
751 +|(% colspan="4" %)(% colspan="4" %)
720 720  (((
721 721  == 2.20 ==
722 722  )))
... ... @@ -729,8 +729,11 @@
729 729  )))|(% colspan="1" %)(% colspan="1" %)
730 730  (((
731 731  **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined.
764 +)))|(% colspan="1" %)(% colspan="1" %)
765 +(((
766 +
732 732  )))
733 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
768 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
734 734  (((
735 735  //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.
736 736  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.//
... ... @@ -747,12 +747,15 @@
747 747  )))|(% colspan="1" %)(% colspan="1" %)
748 748  (((
749 749  Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor'
785 +)))|(% colspan="1" %)(% colspan="1" %)
786 +(((
787 +
750 750  )))
751 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
789 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
752 752  (((
753 753  //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.//
754 754  )))
755 -|(% colspan="3" %)(% colspan="3" %)
793 +|(% colspan="4" %)(% colspan="4" %)
756 756  (((
757 757  == 2.00 ==
758 758  )))
... ... @@ -765,8 +765,11 @@
765 765  )))|(% colspan="1" %)(% colspan="1" %)
766 766  (((
767 767  **<event_build_finished/> **param2 now returns null instead of a construction sequence
806 +)))|(% colspan="1" %)(% colspan="1" %)
807 +(((
808 +
768 768  )))
769 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
810 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
770 770  (((
771 771  //The construction sequence which was finished should now be accessed via the buildtask provided via param3.//
772 772  )))
... ... @@ -779,8 +779,11 @@
779 779  )))|(% colspan="1" %)(% colspan="1" %)
780 780  (((
781 781  **param.boarding.{...}** strength parameters removed
823 +)))|(% colspan="1" %)(% colspan="1" %)
824 +(((
825 +
782 782  )))
783 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
827 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
784 784  (((
785 785  //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.//
786 786  )))
... ... @@ -793,8 +793,11 @@
793 793  )))|(% colspan="1" %)(% colspan="1" %)
794 794  (((
795 795  **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed
840 +)))|(% colspan="1" %)(% colspan="1" %)
841 +(((
842 +
796 796  )))
797 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
844 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
798 798  (((
799 799  //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.//
800 800  )))
... ... @@ -804,8 +804,11 @@
804 804  2.00 Beta 1
805 805  )))|(((
806 806  **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals
854 +)))|(% colspan="1" %)(% colspan="1" %)
855 +(((
856 +
807 807  )))
808 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
858 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
809 809  (((
810 810  //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.//
811 811  )))
... ... @@ -815,8 +815,11 @@
815 815  2.00 Beta 1
816 816  )))|(((
817 817  **FFI: SetFormationShape()** no longer indicates an error upon certain error cases
868 +)))|(% colspan="1" %)(% colspan="1" %)
869 +(((
870 +
818 818  )))
819 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
872 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
820 820  (((
821 821  //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.//
822 822  //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.//
... ... @@ -827,8 +827,11 @@
827 827  2.00 Beta 1
828 828  )))|(((
829 829  **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated.
883 +)))|(% colspan="1" %)(% colspan="1" %)
884 +(((
885 +
830 830  )))
831 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
887 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
832 832  (((
833 833  //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.//
834 834  )))
... ... @@ -838,8 +838,11 @@
838 838  2.00 Beta 1
839 839  )))|(((
840 840  **<event_player_changed_target/>** now fires and returns null if the player deselects a target.
897 +)))|(% colspan="1" %)(% colspan="1" %)
898 +(((
899 +
841 841  )))
842 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
901 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
843 843  (((
844 844  //For prior behavior, check for event.param being non-null.//
845 845  )))
... ... @@ -849,8 +849,11 @@
849 849  2.00 Beta 1
850 850  )))|(((
851 851  **<shoot/>/<shoot_at/>** attribute changes.
911 +)))|(% colspan="1" %)(% colspan="1" %)
912 +(((
913 +
852 852  )))
853 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
915 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
854 854  (((
855 855  //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.//
856 856  //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.//
... ... @@ -863,9 +863,12 @@
863 863  )))|(((
864 864  2.00 Beta 1
865 865  )))|(((
866 -**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.
928 +**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% class="confluenceTd" %)
929 +)))|(% colspan="1" %)(% colspan="1" %)
930 +(((
931 +
867 867  )))
868 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
933 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
869 869  (((
870 870  //Added possibility to query build tasks of a certain buildmodule.//
871 871  )))
... ... @@ -875,8 +875,11 @@
875 875  2.00 Beta 1
876 876  )))|(((
877 877  **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field.
943 +)))|(% colspan="1" %)(% colspan="1" %)
944 +(((
945 +
878 878  )))
879 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
947 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
880 880  (((
881 881  //Added list of resources a buildmodule needs to build.//
882 882  )))
... ... @@ -886,8 +886,11 @@
886 886  2.00 Beta 1
887 887  )))|(((
888 888  (% style="color: rgb(0,0,0);" %)**Lua:**(% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)** CalculateTotalHullFraction()**(% style="color: rgb(0,0,0);" %)** **(%%)was removed.(% style="color: rgb(0,0,0);" %)
957 +)))|(% colspan="1" %)(% colspan="1" %)
958 +(((
959 +
889 889  )))
890 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
961 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
891 891  (((
892 892  //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.//
893 893  )))
... ... @@ -896,13 +896,16 @@
896 896  )))|(((
897 897  2.00 Beta 1
898 898  )))|(((
899 -**FFI: (% style="color: rgb(0,0,0);" %)RequestDockAtReason()/(% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)UndockPlayerShip()(%%) **changed their return values.
970 +**FFI: (% style="color: rgb(0,0,0);" %)RequestDockAtReason()/(% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)UndockPlayerShip()(%%) **changed their return values.(% style="color: rgb(0,0,0);" class="confluenceTd" %)
971 +)))|(% colspan="1" %)(% colspan="1" %)
972 +(((
973 +
900 900  )))
901 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
975 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
902 902  (((
903 903  //Changed return value type to const char* to better identify failure reasons in Lua script.//
904 904  )))
905 -|(% colspan="3" %)(% colspan="3" %)
979 +|(% colspan="4" %)(% colspan="4" %)
906 906  (((
907 907  == 1.50 ==
908 908  )))
... ... @@ -911,9 +911,12 @@
911 911  )))|(((
912 912  1.50 Beta 3
913 913  )))|(((
914 -**Lua: GetComponentData() **changed behavior of "docksizes" property.
988 +**Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %)
989 +)))|(% colspan="1" %)(% colspan="1" %)
990 +(((
991 +
915 915  )))
916 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
993 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
917 917  (((
918 918  //The "docksizes" property no longer includes internal ship storage docks.//
919 919  )))
... ... @@ -923,8 +923,11 @@
923 923  1.50 Beta 2
924 924  )))|(((
925 925  **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR).
1003 +)))|(% colspan="1" %)(% colspan="1" %)
1004 +(((
1005 +
926 926  )))
927 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1007 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
928 928  (((
929 929  //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".//
930 930  
... ... @@ -937,9 +937,12 @@
937 937  )))|(((
938 938  1.50 Beta 2
939 939  )))|(((
940 -**FFI: UpgradeGroupInfo **datatype was changed.
1020 +**FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %)
1021 +)))|(% colspan="1" %)(% colspan="1" %)
1022 +(((
1023 +
941 941  )))
942 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1025 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
943 943  (((
944 944  //Added new "operational" field to retrieve information about number of operational upgrades in a group.//
945 945  )))
... ... @@ -952,8 +952,11 @@
952 952  )))|(% colspan="1" %)(% colspan="1" %)
953 953  (((
954 954  **FFI: SetGuidance()** removed useinfopoint argument.
1038 +)))|(% colspan="1" %)(% colspan="1" %)
1039 +(((
1040 +
955 955  )))
956 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1042 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
957 957  (((
958 958  //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.
959 959  //
... ... @@ -965,13 +965,16 @@
965 965  )))|(((
966 966  1.50 Beta 1
967 967  )))|(((
968 -**FFI: CancelConstruction() **changed its return value.
1054 +**FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %)
1055 +)))|(% colspan="1" %)(% colspan="1" %)
1056 +(((
1057 +
969 969  )))
970 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1059 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
971 971  (((
972 972  (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. //
973 973  )))
974 -|(% colspan="3" %)(% colspan="3" %)
1063 +|(% colspan="4" %)(% colspan="4" %)
975 975  (((
976 976  == 1.32 ==
977 977  )))
... ... @@ -981,12 +981,15 @@
981 981  1.32
982 982  )))|(((
983 983  **Lua: GetComponentData() **removed the "nextdestname" property.
1073 +)))|(% colspan="1" %)(% colspan="1" %)
1074 +(((
1075 +
984 984  )))
985 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1077 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
986 986  (((
987 987  //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.//
988 988  )))
989 -|(% colspan="3" %)(% colspan="3" %)
1081 +|(% colspan="4" %)(% colspan="4" %)
990 990  (((
991 991  == 1.20 ==
992 992  )))
... ... @@ -995,9 +995,12 @@
995 995  )))|(((
996 996  1.20
997 997  )))|(((
998 -**FFI: GetAAOption()** got a new "useconfig" parameter.
1090 +**FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %)
1091 +)))|(% colspan="1" %)(% colspan="1" %)
1092 +(((
1093 +
999 999  )))
1000 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1095 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1001 1001  (((
1002 1002  //The AA setting was changed to check the new setting with the user. In order to restore the old setting (% style="color: rgb(0,0,0);" %)GetAAOption() gets the option to retrieve the config settings.//
1003 1003  )))
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -135856500
1 +103612553
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/135856500/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/103612553/Breaking Changes