Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 99.1
edited by owen
on 2023/01/19 19:13
Change comment: There is no comment for this version
To version 93.1
edited by florian
on 2021/08/03 11:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.owen
1 +xwiki:XWiki.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,90 +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 -|(% colspan="1" %)(% colspan="1" %)
31 +|(% colspan="4" %)(% colspan="4" %)
34 34  (((
35 -Scripts
36 -)))|(% colspan="1" %)(% colspan="1" %)
37 -(((
38 -6.00 Beta 1
39 -)))|(% colspan="1" %)(% colspan="1" %)
40 -(((
41 -Changed result attribute location for **<get_attackstrength>**
42 -)))
43 -|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
44 -(((
45 -//The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.//
46 -)))
47 -|(((
48 -Assets
49 -)))|(((
50 -6.00 Beta 1
51 -)))|(((
52 -Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons
53 -)))
54 -|(% 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" %)
55 -(((
56 -//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.
57 -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.//
58 -)))
59 -|(% colspan="1" %)(% colspan="1" %)
60 -(((
61 -Scripts
62 -)))|(% colspan="1" %)(% colspan="1" %)
63 -(((
64 -6.00 Beta 1
65 -)))|(% colspan="1" %)(% colspan="1" %)
66 -(((
67 -Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects
68 -)))
69 -|(% 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" %)
70 -(((
71 -//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.//
72 -)))
73 -|(((
74 -Scripts
75 -)))|(((
76 -6.00 Beta 1
77 -)))|(((
78 -**<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards.
79 -)))
80 -|(% 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" %)
81 -(((
82 -//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.//
83 -)))
84 -|(((
85 -Cutscenes
86 -)))|(((
87 -6.00 Beta 1
88 -)))|(((
89 -Changed behaviour of **<angles>** in cutscenes
90 -)))
91 -|(% colspan="3" %)(% colspan="3" %)
92 -(((
93 -The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.
94 -)))
95 -|(% colspan="3" %)(% colspan="3" %)
96 -(((
97 -== 5.00 ==
98 -)))
99 -|(((
100 -Parameters
101 -)))|(((
102 -5.00 Beta 1
103 -)))|(((
104 -**<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration
105 -)))
106 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
107 -(((
108 -//'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.//
109 -)))
110 -|(% colspan="3" %)(% colspan="3" %)
111 -(((
112 112  == 4.10 ==
113 113  )))
114 114  |(% colspan="1" %)(% colspan="1" %)
... ... @@ -116,28 +116,20 @@
116 116  UI extensions
117 117  )))|(% colspan="1" %)(% colspan="1" %)
118 118  (((
119 -4.10 Beta 7
120 -)))|(% colspan="1" %)(% colspan="1" %)
121 -(((
122 -**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
123 -)))
124 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
125 -(((
126 -//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.//
127 -)))
128 -|(% colspan="1" %)(% colspan="1" %)
129 -(((
130 -UI extensions
131 -)))|(% colspan="1" %)(% colspan="1" %)
132 -(((
133 133  4.10 Beta 6
134 134  )))|(% colspan="1" %)(% colspan="1" %)
135 135  (((
136 136  **FFI**: CustomGameStartPlayerProperty2 changed
44 +)))|(% colspan="1" %)(% colspan="1" %)
45 +(((
46 +
137 137  )))
138 138  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
139 139  (((
140 140  //This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.//
51 +)))|(% colspan="1" %)(% colspan="1" %)
52 +(((
53 +
141 141  )))
142 142  |(% colspan="1" %)(% colspan="1" %)
143 143  (((
... ... @@ -148,10 +148,16 @@
148 148  )))|(% colspan="1" %)(% colspan="1" %)
149 149  (((
150 150  Renamed **<stationinfobox>** to **<infobox>**
64 +)))|(% colspan="1" %)(% colspan="1" %)
65 +(((
66 +
151 151  )))
152 152  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
153 153  (((
154 154  //Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.//
71 +)))|(% colspan="1" %)(% colspan="1" %)
72 +(((
73 +
155 155  )))
156 156  |(% colspan="1" %)(% colspan="1" %)
157 157  (((
... ... @@ -162,10 +162,16 @@
162 162  )))|(% colspan="1" %)(% colspan="1" %)
163 163  (((
164 164  **FFI**: SetMacroMapPlayerSectorOffset() deprecated
84 +)))|(% colspan="1" %)(% colspan="1" %)
85 +(((
86 +
165 165  )))
166 166  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
167 167  (((
168 168  //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.//
91 +)))|(% colspan="1" %)(% colspan="1" %)
92 +(((
93 +
169 169  )))
170 170  |(((
171 171  UI extensions
... ... @@ -173,10 +173,16 @@
173 173  4.10 Beta 2
174 174  )))|(((
175 175  **FFI**: (% style="color: rgb(0,0,0);" %)FilterComponentForMapMode(%%)() and (% style="color: rgb(0,0,0);" %)SetMapObjectFilter() changed
101 +)))|(% colspan="1" %)(% colspan="1" %)
102 +(((
103 +
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  //These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.//
108 +)))|(% colspan="1" %)(% colspan="1" %)
109 +(((
110 +
180 180  )))
181 181  |(((
182 182  Scripts
... ... @@ -184,8 +184,10 @@
184 184  4.10 Beta 1
185 185  )))|(((
186 186  People related attributes of mission** <delivery> **node moved
118 +)))|(((
119 +
187 187  )))
188 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
121 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
189 189  (((
190 190  //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.//
191 191  )))
... ... @@ -198,10 +198,16 @@
198 198  )))|(% colspan="1" %)(% colspan="1" %)
199 199  (((
200 200  **$destructible.productions** replaced with $defensible.productions
134 +)))|(% colspan="1" %)(% colspan="1" %)
135 +(((
136 +
201 201  )))
202 202  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
203 203  (((
204 204  //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.//
141 +)))|(% colspan="1" %)(% colspan="1" %)
142 +(((
143 +
205 205  )))
206 206  |(((
207 207  Scripts
... ... @@ -209,12 +209,14 @@
209 209  4.10 Beta 1
210 210  )))|(((
211 211  Removed script property **$object.spawnsourceseed**
151 +)))|(((
152 +
212 212  )))
213 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
154 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
214 214  (((
215 215  //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.//
216 216  )))
217 -|(% colspan="3" %)(% colspan="3" %)
158 +|(% colspan="4" %)(% colspan="4" %)
218 218  (((
219 219  == 4.00 ==
220 220  )))
... ... @@ -227,6 +227,9 @@
227 227  )))|(% colspan="1" %)(% colspan="1" %)
228 228  (((
229 229  Controlled ship can change without a **gameplanchange-event** occurring.
171 +)))|(% colspan="1" %)(% colspan="1" %)
172 +(((
173 +
230 230  )))
231 231  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
232 232  (((
... ... @@ -233,6 +233,9 @@
233 233  //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).
234 234  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.
235 235  //
180 +)))|(% colspan="1" %)(% colspan="1" %)
181 +(((
182 +
236 236  )))
237 237  |(((
238 238  Scripts
... ... @@ -240,6 +240,8 @@
240 240  4.00 Beta 7
241 241  )))|(((
242 242  Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed
190 +)))|(((
191 +
243 243  )))
244 244  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
245 245  (((
... ... @@ -246,6 +246,9 @@
246 246  //Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects?
247 247  New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits
248 248  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//
198 +)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %)
199 +(((
200 +
249 249  )))
250 250  |(% colspan="1" %)(% colspan="1" %)
251 251  (((
... ... @@ -256,6 +256,9 @@
256 256  )))|(% colspan="1" %)(% colspan="1" %)
257 257  (((
258 258  **FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed
211 +)))|(% colspan="1" %)(% colspan="1" %)
212 +(((
213 +
259 259  )))
260 260  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
261 261  (((
... ... @@ -264,6 +264,9 @@
264 264  
265 265  //If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.
266 266  //
222 +)))|(% colspan="1" %)(% colspan="1" %)
223 +(((
224 +
267 267  )))
268 268  |(% colspan="1" %)(% colspan="1" %)
269 269  (((
... ... @@ -274,6 +274,9 @@
274 274  )))|(% colspan="1" %)(% colspan="1" %)
275 275  (((
276 276  **FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed
235 +)))|(% colspan="1" %)(% colspan="1" %)
236 +(((
237 +
277 277  )))
278 278  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
279 279  (((
... ... @@ -280,6 +280,9 @@
280 280  //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.//
281 281  
282 282  //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).
244 +)))|(% colspan="1" %)(% colspan="1" %)
245 +(((
246 +
283 283  )))
284 284  |(((
285 285  Parameters
... ... @@ -287,8 +287,10 @@
287 287  4.00 Beta 1
288 288  )))|(((
289 289  **requiresconstructionvessel** parameter moved
254 +)))|(((
255 +
290 290  )))
291 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
257 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
292 292  (((
293 293  //The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.//
294 294  )))
... ... @@ -298,12 +298,17 @@
298 298  4.00 Beta 1
299 299  )))|(((
300 300  Changed behaviour of **gatedistance** script property
267 +)))|(((
268 +
301 301  )))
302 302  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
303 303  (((
304 304  //The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.//
273 +)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %)
274 +(((
275 +
305 305  )))
306 -|(% colspan="3" %)(% colspan="3" %)
277 +|(% colspan="4" %)(% colspan="4" %)
307 307  (((
308 308  == 3.30 ==
309 309  )))
... ... @@ -313,12 +313,15 @@
313 313  3.30 Beta 3
314 314  )))|(((
315 315  **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()**
287 +)))|(% colspan="1" %)(% colspan="1" %)
288 +(((
289 +
316 316  )))
317 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
291 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
318 318  (((
319 319  //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()//
320 320  )))
321 -|(% colspan="3" %)(% colspan="3" %)
295 +|(% colspan="4" %)(% colspan="4" %)
322 322  (((
323 323  == 3.20 ==
324 324  )))
... ... @@ -328,8 +328,11 @@
328 328  3.20 Beta 1
329 329  )))|(((
330 330  Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed
305 +)))|(% colspan="1" %)(% colspan="1" %)
306 +(((
307 +
331 331  )))
332 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
309 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
333 333  (((
334 334  //Old params: param = attacked object, param2 = attack method, param3 = attacked component//
335 335  //New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon]
... ... @@ -344,8 +344,11 @@
344 344  )))|(% colspan="1" %)(% colspan="1" %)
345 345  (((
346 346  Removed script property $trade.**restriction.faction**
324 +)))|(% colspan="1" %)(% colspan="1" %)
325 +(((
326 +
347 347  )))
348 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
328 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
349 349  (((
350 350  //$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.//
351 351  )))
... ... @@ -355,12 +355,15 @@
355 355  3.20 Beta 1
356 356  )))|(((
357 357  **Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete!
338 +)))|(% colspan="1" %)(% colspan="1" %)
339 +(((
340 +
358 358  )))
359 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
342 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
360 360  (((
361 361  //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.//
362 362  )))
363 -|(% colspan="3" %)(% colspan="3" %)
346 +|(% colspan="4" %)(% colspan="4" %)
364 364  (((
365 365  == 3.10 ==
366 366  )))
... ... @@ -373,12 +373,15 @@
373 373  )))|(% colspan="1" %)(% colspan="1" %)
374 374  (((
375 375  Removed script action **<add_build/>**
359 +)))|(% colspan="1" %)(% colspan="1" %)
360 +(((
361 +
376 376  )))
377 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
363 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
378 378  (((
379 379  //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.//
380 380  )))
381 -|(% colspan="3" %)(% colspan="3" %)
367 +|(% colspan="4" %)(% colspan="4" %)
382 382  (((
383 383  == 3.00 ==
384 384  )))
... ... @@ -391,8 +391,11 @@
391 391  )))|(% colspan="1" %)(% colspan="1" %)
392 392  (((
393 393  Changed behaviour of script action **<get_suitable_job/>**
380 +)))|(% colspan="1" %)(% colspan="1" %)
381 +(((
382 +
394 394  )))
395 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
384 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
396 396  (((
397 397  //<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.//
398 398  )))
... ... @@ -405,8 +405,11 @@
405 405  )))|(% colspan="1" %)(% colspan="1" %)
406 406  (((
407 407  Changed behaviour of script action **<get_ware_definition/>**
397 +)))|(% colspan="1" %)(% colspan="1" %)
398 +(((
399 +
408 408  )))
409 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
401 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
410 410  (((
411 411  //<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.//
412 412  )))
... ... @@ -419,8 +419,11 @@
419 419  )))|(% colspan="1" %)(% colspan="1" %)
420 420  (((
421 421  Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case
414 +)))|(% colspan="1" %)(% colspan="1" %)
415 +(((
416 +
422 422  )))
423 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
418 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
424 424  (((
425 425  //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.)\\
426 426  
... ... @@ -435,8 +435,11 @@
435 435  )))|(% colspan="1" %)(% colspan="1" %)
436 436  (((
437 437  Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions>
433 +)))|(% colspan="1" %)(% colspan="1" %)
434 +(((
435 +
438 438  )))
439 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
437 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
440 440  (((
441 441  //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.//
442 442  )))
... ... @@ -449,8 +449,11 @@
449 449  )))|(% colspan="1" %)(% colspan="1" %)
450 450  (((
451 451  Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos**
450 +)))|(% colspan="1" %)(% colspan="1" %)
451 +(((
452 +
452 452  )))
453 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
454 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
454 454  (((
455 455  //Before the change, positions are relative to $dockingbay.parent.
456 456  After the change, positions are relative to $dockingbay as specified in the documentation.//
... ... @@ -464,8 +464,11 @@
464 464  )))|(% colspan="1" %)(% colspan="1" %)
465 465  (((
466 466  Support for entity flag "**skillsvisible**" dropped
468 +)))|(% colspan="1" %)(% colspan="1" %)
469 +(((
470 +
467 467  )))
468 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
472 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
469 469  (((
470 470  //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().//
471 471  )))
... ... @@ -475,8 +475,11 @@
475 475  3.0 Beta 2
476 476  )))|(((
477 477  Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**.
482 +)))|(% colspan="1" %)(% colspan="1" %)
483 +(((
484 +
478 478  )))
479 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
486 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
480 480  (((
481 481  //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.
482 482  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.
... ... @@ -492,8 +492,11 @@
492 492  )))|(% colspan="1" %)(% colspan="1" %)
493 493  (((
494 494  **MissionBoard** support dropped
502 +)))|(% colspan="1" %)(% colspan="1" %)
503 +(((
504 +
495 495  )))
496 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
506 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
497 497  (((
498 498  //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.//
499 499  )))
... ... @@ -503,8 +503,11 @@
503 503  3.0 Beta 1
504 504  )))|(((
505 505  By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined
516 +)))|(% colspan="1" %)(% colspan="1" %)
517 +(((
518 +
506 506  )))
507 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
520 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
508 508  (((
509 509  //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.//
510 510  )))
... ... @@ -517,8 +517,11 @@
517 517  )))|(% colspan="1" %)(% colspan="1" %)
518 518  (((
519 519  Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'**
533 +)))|(% colspan="1" %)(% colspan="1" %)
534 +(((
535 +
520 520  )))
521 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
537 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
522 522  (((
523 523  //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.//
524 524  )))
... ... @@ -531,8 +531,11 @@
531 531  )))|(% colspan="1" %)(% colspan="1" %)
532 532  (((
533 533  Script action **<set_doors_locked/>** attribute **'group'** changed
550 +)))|(% colspan="1" %)(% colspan="1" %)
551 +(((
552 +
534 534  )))
535 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
554 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
536 536  (((
537 537  //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.//
538 538  )))
... ... @@ -545,8 +545,11 @@
545 545  )))|(% colspan="1" %)(% colspan="1" %)
546 546  (((
547 547  Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed
567 +)))|(% colspan="1" %)(% colspan="1" %)
568 +(((
569 +
548 548  )))
549 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
571 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
550 550  (((
551 551  //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.//
552 552  )))
... ... @@ -559,8 +559,11 @@
559 559  )))|(% colspan="1" %)(% colspan="1" %)
560 560  (((
561 561  Script actions **<set_hack_target/>** and **<abort_hack/>** removed
584 +)))|(% colspan="1" %)(% colspan="1" %)
585 +(((
586 +
562 562  )))
563 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
588 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
564 564  (((
565 565  //These actions had no effect and were removed.//
566 566  )))
... ... @@ -573,8 +573,11 @@
573 573  )))|(% colspan="1" %)(% colspan="1" %)
574 574  (((
575 575  **<setup_conversation_minigame/>** script action removed
601 +)))|(% colspan="1" %)(% colspan="1" %)
602 +(((
603 +
576 576  )))
577 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
605 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
578 578  (((
579 579  //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.//
580 580  )))
... ... @@ -587,8 +587,11 @@
587 587  )))|(% colspan="1" %)(% colspan="1" %)
588 588  (((
589 589  <add_player_choice_*> **confidence** attribute removed
618 +)))|(% colspan="1" %)(% colspan="1" %)
619 +(((
620 +
590 590  )))
591 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
622 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
592 592  (((
593 593  //The default confidence of player options is another leftover from the XR era and had no effect in X4.//
594 594  )))
... ... @@ -601,8 +601,11 @@
601 601  )))|(% colspan="1" %)(% colspan="1" %)
602 602  (((
603 603  **<hack_via_control_panel/>** script action removed
635 +)))|(% colspan="1" %)(% colspan="1" %)
636 +(((
637 +
604 604  )))
605 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
639 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
606 606  (((
607 607  //Unused script action <hack_via_control_panel/> was removed.//
608 608  )))
... ... @@ -615,8 +615,11 @@
615 615  )))|(% colspan="1" %)(% colspan="1" %)
616 616  (((
617 617  **Lua: **GetMiniGameCursorPosition() removed
652 +)))|(% colspan="1" %)(% colspan="1" %)
653 +(((
654 +
618 618  )))
619 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
656 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
620 620  (((
621 621  //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.//
622 622  )))
... ... @@ -626,8 +626,11 @@
626 626  3.0 Beta 1
627 627  )))|(((
628 628  **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders
666 +)))|(% colspan="1" %)(% colspan="1" %)
667 +(((
668 +
629 629  )))
630 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
670 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
631 631  (((
632 632  //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.//
633 633  )))
... ... @@ -640,8 +640,11 @@
640 640  )))|(% colspan="1" %)(% colspan="1" %)
641 641  (((
642 642  **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor
683 +)))|(% colspan="1" %)(% colspan="1" %)
684 +(((
685 +
643 643  )))
644 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
687 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
645 645  (((
646 646  //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.//
647 647  )))
... ... @@ -654,8 +654,11 @@
654 654  )))|(% colspan="1" %)(% colspan="1" %)
655 655  (((
656 656  **$ware.illegal** updated
700 +)))|(% colspan="1" %)(% colspan="1" %)
701 +(((
702 +
657 657  )))
658 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
704 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
659 659  (((
660 660  //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.//
661 661  //It now returns true if $ware is illegal to any faction in the game.//
... ... @@ -669,8 +669,11 @@
669 669  )))|(% colspan="1" %)(% colspan="1" %)
670 670  (((
671 671  MD script **RML_Flight_Along_Path** removed
718 +)))|(% colspan="1" %)(% colspan="1" %)
719 +(((
720 +
672 672  )))
673 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
722 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
674 674  (((
675 675  //The MD script RML_Flight_Along_Path was not referened and was removed.//
676 676  )))
... ... @@ -683,8 +683,11 @@
683 683  )))|(% colspan="1" %)(% colspan="1" %)
684 684  (((
685 685  parameters of **<event_venture_mission_completed/>** changed
735 +)))|(% colspan="1" %)(% colspan="1" %)
736 +(((
737 +
686 686  )))
687 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
739 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
688 688  (((
689 689  //old params: param = venture details, param2 = ships involved, param3 = duration//
690 690  //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration//
... ... @@ -696,8 +696,11 @@
696 696  )))|(((
697 697  **<set_object_wing_name/>** removed,
698 698  **<set_object_fleet_name/>** added
751 +)))|(% colspan="1" %)(% colspan="1" %)
752 +(((
753 +
699 699  )))
700 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
755 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
701 701  (((
702 702  //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>//
703 703  )))
... ... @@ -708,12 +708,15 @@
708 708  )))|(((
709 709  **$controllable.wing.*** removed,
710 710  **$controllable.fleet.*** added
766 +)))|(% colspan="1" %)(% colspan="1" %)
767 +(((
768 +
711 711  )))
712 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
770 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
713 713  (((
714 714  $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander
715 715  )))
716 -|(% colspan="3" %)(% colspan="3" %)
774 +|(% colspan="4" %)(% colspan="4" %)
717 717  (((
718 718  == 2.60 ==
719 719  )))
... ... @@ -723,8 +723,11 @@
723 723  2.60 Beta 1
724 724  )))|(((
725 725  '**checkoperational**' filter behaviour changed
784 +)))|(% colspan="1" %)(% colspan="1" %)
785 +(((
786 +
726 726  )))
727 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
788 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
728 728  (((
729 729  //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.//
730 730  
... ... @@ -736,12 +736,15 @@
736 736  2.60 Beta 1
737 737  )))|(((
738 738  $container.**supplyresources** behavior changed
800 +)))|(% colspan="1" %)(% colspan="1" %)
801 +(((
802 +
739 739  )))
740 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
804 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
741 741  (((
742 742  //The script keyword $container.supplyresources now includes reserved wares.//
743 743  )))
744 -|(% colspan="3" %)(% colspan="3" %)
808 +|(% colspan="4" %)(% colspan="4" %)
745 745  (((
746 746  == 2.20 ==
747 747  )))
... ... @@ -754,8 +754,11 @@
754 754  )))|(% colspan="1" %)(% colspan="1" %)
755 755  (((
756 756  **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined.
821 +)))|(% colspan="1" %)(% colspan="1" %)
822 +(((
823 +
757 757  )))
758 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
825 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
759 759  (((
760 760  //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.
761 761  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.//
... ... @@ -772,12 +772,15 @@
772 772  )))|(% colspan="1" %)(% colspan="1" %)
773 773  (((
774 774  Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor'
842 +)))|(% colspan="1" %)(% colspan="1" %)
843 +(((
844 +
775 775  )))
776 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
846 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
777 777  (((
778 778  //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.//
779 779  )))
780 -|(% colspan="3" %)(% colspan="3" %)
850 +|(% colspan="4" %)(% colspan="4" %)
781 781  (((
782 782  == 2.00 ==
783 783  )))
... ... @@ -790,8 +790,11 @@
790 790  )))|(% colspan="1" %)(% colspan="1" %)
791 791  (((
792 792  **<event_build_finished/> **param2 now returns null instead of a construction sequence
863 +)))|(% colspan="1" %)(% colspan="1" %)
864 +(((
865 +
793 793  )))
794 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
867 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
795 795  (((
796 796  //The construction sequence which was finished should now be accessed via the buildtask provided via param3.//
797 797  )))
... ... @@ -804,8 +804,11 @@
804 804  )))|(% colspan="1" %)(% colspan="1" %)
805 805  (((
806 806  **param.boarding.{...}** strength parameters removed
880 +)))|(% colspan="1" %)(% colspan="1" %)
881 +(((
882 +
807 807  )))
808 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
884 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
809 809  (((
810 810  //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.//
811 811  )))
... ... @@ -818,8 +818,11 @@
818 818  )))|(% colspan="1" %)(% colspan="1" %)
819 819  (((
820 820  **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed
897 +)))|(% colspan="1" %)(% colspan="1" %)
898 +(((
899 +
821 821  )))
822 -|(% 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" %)
823 823  (((
824 824  //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.//
825 825  )))
... ... @@ -829,8 +829,11 @@
829 829  2.00 Beta 1
830 830  )))|(((
831 831  **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals
911 +)))|(% colspan="1" %)(% colspan="1" %)
912 +(((
913 +
832 832  )))
833 -|(% 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" %)
834 834  (((
835 835  //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.//
836 836  )))
... ... @@ -840,8 +840,11 @@
840 840  2.00 Beta 1
841 841  )))|(((
842 842  **FFI: SetFormationShape()** no longer indicates an error upon certain error cases
925 +)))|(% colspan="1" %)(% colspan="1" %)
926 +(((
927 +
843 843  )))
844 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
929 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
845 845  (((
846 846  //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.//
847 847  //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.//
... ... @@ -852,8 +852,11 @@
852 852  2.00 Beta 1
853 853  )))|(((
854 854  **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated.
940 +)))|(% colspan="1" %)(% colspan="1" %)
941 +(((
942 +
855 855  )))
856 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
944 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
857 857  (((
858 858  //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.//
859 859  )))
... ... @@ -863,8 +863,11 @@
863 863  2.00 Beta 1
864 864  )))|(((
865 865  **<event_player_changed_target/>** now fires and returns null if the player deselects a target.
954 +)))|(% colspan="1" %)(% colspan="1" %)
955 +(((
956 +
866 866  )))
867 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
958 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
868 868  (((
869 869  //For prior behavior, check for event.param being non-null.//
870 870  )))
... ... @@ -874,8 +874,11 @@
874 874  2.00 Beta 1
875 875  )))|(((
876 876  **<shoot/>/<shoot_at/>** attribute changes.
968 +)))|(% colspan="1" %)(% colspan="1" %)
969 +(((
970 +
877 877  )))
878 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
972 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
879 879  (((
880 880  //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.//
881 881  //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.//
... ... @@ -888,9 +888,12 @@
888 888  )))|(((
889 889  2.00 Beta 1
890 890  )))|(((
891 -**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.
985 +**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% class="confluenceTd" %)
986 +)))|(% colspan="1" %)(% colspan="1" %)
987 +(((
988 +
892 892  )))
893 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
990 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
894 894  (((
895 895  //Added possibility to query build tasks of a certain buildmodule.//
896 896  )))
... ... @@ -900,8 +900,11 @@
900 900  2.00 Beta 1
901 901  )))|(((
902 902  **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field.
1000 +)))|(% colspan="1" %)(% colspan="1" %)
1001 +(((
1002 +
903 903  )))
904 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1004 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
905 905  (((
906 906  //Added list of resources a buildmodule needs to build.//
907 907  )))
... ... @@ -911,8 +911,11 @@
911 911  2.00 Beta 1
912 912  )))|(((
913 913  (% 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);" %)
1014 +)))|(% colspan="1" %)(% colspan="1" %)
1015 +(((
1016 +
914 914  )))
915 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1018 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
916 916  (((
917 917  //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.//
918 918  )))
... ... @@ -921,13 +921,16 @@
921 921  )))|(((
922 922  2.00 Beta 1
923 923  )))|(((
924 -**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.
1027 +**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" %)
1028 +)))|(% colspan="1" %)(% colspan="1" %)
1029 +(((
1030 +
925 925  )))
926 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1032 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
927 927  (((
928 928  //Changed return value type to const char* to better identify failure reasons in Lua script.//
929 929  )))
930 -|(% colspan="3" %)(% colspan="3" %)
1036 +|(% colspan="4" %)(% colspan="4" %)
931 931  (((
932 932  == 1.50 ==
933 933  )))
... ... @@ -936,9 +936,12 @@
936 936  )))|(((
937 937  1.50 Beta 3
938 938  )))|(((
939 -**Lua: GetComponentData() **changed behavior of "docksizes" property.
1045 +**Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %)
1046 +)))|(% colspan="1" %)(% colspan="1" %)
1047 +(((
1048 +
940 940  )))
941 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1050 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
942 942  (((
943 943  //The "docksizes" property no longer includes internal ship storage docks.//
944 944  )))
... ... @@ -948,8 +948,11 @@
948 948  1.50 Beta 2
949 949  )))|(((
950 950  **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR).
1060 +)))|(% colspan="1" %)(% colspan="1" %)
1061 +(((
1062 +
951 951  )))
952 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1064 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
953 953  (((
954 954  //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".//
955 955  
... ... @@ -962,9 +962,12 @@
962 962  )))|(((
963 963  1.50 Beta 2
964 964  )))|(((
965 -**FFI: UpgradeGroupInfo **datatype was changed.
1077 +**FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %)
1078 +)))|(% colspan="1" %)(% colspan="1" %)
1079 +(((
1080 +
966 966  )))
967 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1082 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
968 968  (((
969 969  //Added new "operational" field to retrieve information about number of operational upgrades in a group.//
970 970  )))
... ... @@ -977,8 +977,11 @@
977 977  )))|(% colspan="1" %)(% colspan="1" %)
978 978  (((
979 979  **FFI: SetGuidance()** removed useinfopoint argument.
1095 +)))|(% colspan="1" %)(% colspan="1" %)
1096 +(((
1097 +
980 980  )))
981 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1099 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
982 982  (((
983 983  //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.
984 984  //
... ... @@ -990,13 +990,16 @@
990 990  )))|(((
991 991  1.50 Beta 1
992 992  )))|(((
993 -**FFI: CancelConstruction() **changed its return value.
1111 +**FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %)
1112 +)))|(% colspan="1" %)(% colspan="1" %)
1113 +(((
1114 +
994 994  )))
995 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1116 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
996 996  (((
997 997  (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. //
998 998  )))
999 -|(% colspan="3" %)(% colspan="3" %)
1120 +|(% colspan="4" %)(% colspan="4" %)
1000 1000  (((
1001 1001  == 1.32 ==
1002 1002  )))
... ... @@ -1006,12 +1006,15 @@
1006 1006  1.32
1007 1007  )))|(((
1008 1008  **Lua: GetComponentData() **removed the "nextdestname" property.
1130 +)))|(% colspan="1" %)(% colspan="1" %)
1131 +(((
1132 +
1009 1009  )))
1010 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1134 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1011 1011  (((
1012 1012  //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.//
1013 1013  )))
1014 -|(% colspan="3" %)(% colspan="3" %)
1138 +|(% colspan="4" %)(% colspan="4" %)
1015 1015  (((
1016 1016  == 1.20 ==
1017 1017  )))
... ... @@ -1020,9 +1020,12 @@
1020 1020  )))|(((
1021 1021  1.20
1022 1022  )))|(((
1023 -**FFI: GetAAOption()** got a new "useconfig" parameter.
1147 +**FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %)
1148 +)))|(% colspan="1" %)(% colspan="1" %)
1149 +(((
1150 +
1024 1024  )))
1025 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1152 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1026 1026  (((
1027 1027  //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.//
1028 1028  )))
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -135862012
1 +104923840
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/135862012/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/104923840/Breaking Changes