Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 100.1
edited by owen
on 2023/01/19 19:21
Change comment: There is no comment for this version
To version 92.1
edited by matthias
on 2021/06/30 12:44
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.matthias
Content
... ... @@ -18,7 +18,6 @@
18 18  
19 19  = Breaking Changes =
20 20  
21 -(% class="wrapped" %)
22 22  |=(((
23 23  Type
24 24  )))|=(((
... ... @@ -25,163 +25,54 @@
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 -Behaviour change for **<match_dock>** script component filter
33 +== 4.10 ==
42 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 -//<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes.
46 -This has introduced a new potential pitfall: If finding or counting contained components be wary that there may be multiple positive results, even if there is only one dockingbay. e.g. matching contents for a station will include the dockingbay but also its containing walkable module as that also contains the dockingbay. To only account for docking bays, also filter by dockingbay class.//
47 -)))
48 48  |(% colspan="1" %)(% colspan="1" %)
49 49  (((
50 -Scripts
37 +Parameters
51 51  )))|(% colspan="1" %)(% colspan="1" %)
52 52  (((
53 -6.00 Beta 1
40 +4.10 Beta 3
54 54  )))|(% colspan="1" %)(% colspan="1" %)
55 55  (((
56 -Changed result attribute location for **<get_attackstrength>**
57 -)))
58 -|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
59 -(((
60 -//The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.//
61 -)))
62 -|(((
63 -Assets
64 -)))|(((
65 -6.00 Beta 1
66 -)))|(((
67 -Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons
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 -//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.
72 -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.//
73 -)))
74 -|(% colspan="1" %)(% colspan="1" %)
75 -(((
76 -Scripts
43 +Renamed **<stationinfobox>** to **<infobox>**
77 77  )))|(% colspan="1" %)(% colspan="1" %)
78 78  (((
79 -6.00 Beta 1
80 -)))|(% colspan="1" %)(% colspan="1" %)
81 -(((
82 -Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects
46 +
83 83  )))
84 -|(% 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" %)
85 -(((
86 -//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.//
87 -)))
88 -|(((
89 -Scripts
90 -)))|(((
91 -6.00 Beta 1
92 -)))|(((
93 -**<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards.
94 -)))
95 -|(% 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" %)
96 -(((
97 -//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.//
98 -)))
99 -|(((
100 -Cutscenes
101 -)))|(((
102 -6.00 Beta 1
103 -)))|(((
104 -Changed behaviour of **<angles>** in cutscenes
105 -)))
106 -|(% colspan="3" %)(% colspan="3" %)
107 -(((
108 -The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.
109 -)))
110 -|(% colspan="3" %)(% colspan="3" %)
111 -(((
112 -== 5.00 ==
113 -)))
114 -|(((
115 -Parameters
116 -)))|(((
117 -5.00 Beta 1
118 -)))|(((
119 -**<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration
120 -)))
121 121  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
122 122  (((
123 -//'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.//
124 -)))
125 -|(% colspan="3" %)(% colspan="3" %)
126 -(((
127 -== 4.10 ==
128 -)))
129 -|(% colspan="1" %)(% colspan="1" %)
130 -(((
131 -UI extensions
50 +Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.
132 132  )))|(% colspan="1" %)(% colspan="1" %)
133 133  (((
134 -4.10 Beta 7
135 -)))|(% colspan="1" %)(% colspan="1" %)
136 -(((
137 -**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
53 +
138 138  )))
139 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
140 -(((
141 -//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.//
142 -)))
143 143  |(% colspan="1" %)(% colspan="1" %)
144 144  (((
145 145  UI extensions
146 146  )))|(% colspan="1" %)(% colspan="1" %)
147 147  (((
148 -4.10 Beta 6
60 +4.10 Beta 2
149 149  )))|(% colspan="1" %)(% colspan="1" %)
150 150  (((
151 -**FFI**: CustomGameStartPlayerProperty2 changed
152 -)))
153 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
154 -(((
155 -//This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.//
156 -)))
157 -|(% colspan="1" %)(% colspan="1" %)
158 -(((
159 -Parameters
63 +**FFI**: SetMacroMapPlayerSectorOffset() deprecated
160 160  )))|(% colspan="1" %)(% colspan="1" %)
161 161  (((
162 -4.10 Beta 3
163 -)))|(% colspan="1" %)(% colspan="1" %)
164 -(((
165 -Renamed **<stationinfobox>** to **<infobox>**
66 +
166 166  )))
167 167  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
168 168  (((
169 -//Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.//
170 -)))
171 -|(% colspan="1" %)(% colspan="1" %)
172 -(((
173 -UI extensions
70 +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.
174 174  )))|(% colspan="1" %)(% colspan="1" %)
175 175  (((
176 -4.10 Beta 2
177 -)))|(% colspan="1" %)(% colspan="1" %)
178 -(((
179 -**FFI**: SetMacroMapPlayerSectorOffset() deprecated
73 +
180 180  )))
181 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
182 -(((
183 -//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.//
184 -)))
185 185  |(((
186 186  UI extensions
187 187  )))|(((
... ... @@ -188,10 +188,16 @@
188 188  4.10 Beta 2
189 189  )))|(((
190 190  **FFI**: (% style="color: rgb(0,0,0);" %)FilterComponentForMapMode(%%)() and (% style="color: rgb(0,0,0);" %)SetMapObjectFilter() changed
81 +)))|(% colspan="1" %)(% colspan="1" %)
82 +(((
83 +
191 191  )))
192 192  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
193 193  (((
194 194  //These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.//
88 +)))|(% colspan="1" %)(% colspan="1" %)
89 +(((
90 +
195 195  )))
196 196  |(((
197 197  Scripts
... ... @@ -199,8 +199,10 @@
199 199  4.10 Beta 1
200 200  )))|(((
201 201  People related attributes of mission** <delivery> **node moved
98 +)))|(((
99 +
202 202  )))
203 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
101 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
204 204  (((
205 205  //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.//
206 206  )))
... ... @@ -213,10 +213,16 @@
213 213  )))|(% colspan="1" %)(% colspan="1" %)
214 214  (((
215 215  **$destructible.productions** replaced with $defensible.productions
114 +)))|(% colspan="1" %)(% colspan="1" %)
115 +(((
116 +
216 216  )))
217 217  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
218 218  (((
219 219  //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.//
121 +)))|(% colspan="1" %)(% colspan="1" %)
122 +(((
123 +
220 220  )))
221 221  |(((
222 222  Scripts
... ... @@ -224,12 +224,14 @@
224 224  4.10 Beta 1
225 225  )))|(((
226 226  Removed script property **$object.spawnsourceseed**
131 +)))|(((
132 +
227 227  )))
228 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
134 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
229 229  (((
230 230  //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.//
231 231  )))
232 -|(% colspan="3" %)(% colspan="3" %)
138 +|(% colspan="4" %)(% colspan="4" %)
233 233  (((
234 234  == 4.00 ==
235 235  )))
... ... @@ -242,6 +242,9 @@
242 242  )))|(% colspan="1" %)(% colspan="1" %)
243 243  (((
244 244  Controlled ship can change without a **gameplanchange-event** occurring.
151 +)))|(% colspan="1" %)(% colspan="1" %)
152 +(((
153 +
245 245  )))
246 246  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
247 247  (((
... ... @@ -248,6 +248,9 @@
248 248  //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).
249 249  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.
250 250  //
160 +)))|(% colspan="1" %)(% colspan="1" %)
161 +(((
162 +
251 251  )))
252 252  |(((
253 253  Scripts
... ... @@ -255,6 +255,8 @@
255 255  4.00 Beta 7
256 256  )))|(((
257 257  Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed
170 +)))|(((
171 +
258 258  )))
259 259  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
260 260  (((
... ... @@ -261,6 +261,9 @@
261 261  //Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects?
262 262  New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits
263 263  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//
178 +)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %)
179 +(((
180 +
264 264  )))
265 265  |(% colspan="1" %)(% colspan="1" %)
266 266  (((
... ... @@ -271,6 +271,9 @@
271 271  )))|(% colspan="1" %)(% colspan="1" %)
272 272  (((
273 273  **FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed
191 +)))|(% colspan="1" %)(% colspan="1" %)
192 +(((
193 +
274 274  )))
275 275  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
276 276  (((
... ... @@ -279,6 +279,9 @@
279 279  
280 280  //If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.
281 281  //
202 +)))|(% colspan="1" %)(% colspan="1" %)
203 +(((
204 +
282 282  )))
283 283  |(% colspan="1" %)(% colspan="1" %)
284 284  (((
... ... @@ -289,6 +289,9 @@
289 289  )))|(% colspan="1" %)(% colspan="1" %)
290 290  (((
291 291  **FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed
215 +)))|(% colspan="1" %)(% colspan="1" %)
216 +(((
217 +
292 292  )))
293 293  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
294 294  (((
... ... @@ -295,6 +295,9 @@
295 295  //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.//
296 296  
297 297  //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).
224 +)))|(% colspan="1" %)(% colspan="1" %)
225 +(((
226 +
298 298  )))
299 299  |(((
300 300  Parameters
... ... @@ -302,8 +302,10 @@
302 302  4.00 Beta 1
303 303  )))|(((
304 304  **requiresconstructionvessel** parameter moved
234 +)))|(((
235 +
305 305  )))
306 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
237 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
307 307  (((
308 308  //The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.//
309 309  )))
... ... @@ -313,12 +313,17 @@
313 313  4.00 Beta 1
314 314  )))|(((
315 315  Changed behaviour of **gatedistance** script property
247 +)))|(((
248 +
316 316  )))
317 317  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
318 318  (((
319 319  //The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.//
253 +)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %)
254 +(((
255 +
320 320  )))
321 -|(% colspan="3" %)(% colspan="3" %)
257 +|(% colspan="4" %)(% colspan="4" %)
322 322  (((
323 323  == 3.30 ==
324 324  )))
... ... @@ -328,12 +328,15 @@
328 328  3.30 Beta 3
329 329  )))|(((
330 330  **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()**
267 +)))|(% colspan="1" %)(% colspan="1" %)
268 +(((
269 +
331 331  )))
332 -|(% 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" %)
333 333  (((
334 334  //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()//
335 335  )))
336 -|(% colspan="3" %)(% colspan="3" %)
275 +|(% colspan="4" %)(% colspan="4" %)
337 337  (((
338 338  == 3.20 ==
339 339  )))
... ... @@ -343,8 +343,11 @@
343 343  3.20 Beta 1
344 344  )))|(((
345 345  Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed
285 +)))|(% colspan="1" %)(% colspan="1" %)
286 +(((
287 +
346 346  )))
347 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
289 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
348 348  (((
349 349  //Old params: param = attacked object, param2 = attack method, param3 = attacked component//
350 350  //New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon]
... ... @@ -359,8 +359,11 @@
359 359  )))|(% colspan="1" %)(% colspan="1" %)
360 360  (((
361 361  Removed script property $trade.**restriction.faction**
304 +)))|(% colspan="1" %)(% colspan="1" %)
305 +(((
306 +
362 362  )))
363 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
308 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
364 364  (((
365 365  //$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.//
366 366  )))
... ... @@ -370,12 +370,15 @@
370 370  3.20 Beta 1
371 371  )))|(((
372 372  **Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete!
318 +)))|(% colspan="1" %)(% colspan="1" %)
319 +(((
320 +
373 373  )))
374 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
322 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
375 375  (((
376 376  //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.//
377 377  )))
378 -|(% colspan="3" %)(% colspan="3" %)
326 +|(% colspan="4" %)(% colspan="4" %)
379 379  (((
380 380  == 3.10 ==
381 381  )))
... ... @@ -388,12 +388,15 @@
388 388  )))|(% colspan="1" %)(% colspan="1" %)
389 389  (((
390 390  Removed script action **<add_build/>**
339 +)))|(% colspan="1" %)(% colspan="1" %)
340 +(((
341 +
391 391  )))
392 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
343 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
393 393  (((
394 394  //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.//
395 395  )))
396 -|(% colspan="3" %)(% colspan="3" %)
347 +|(% colspan="4" %)(% colspan="4" %)
397 397  (((
398 398  == 3.00 ==
399 399  )))
... ... @@ -406,8 +406,11 @@
406 406  )))|(% colspan="1" %)(% colspan="1" %)
407 407  (((
408 408  Changed behaviour of script action **<get_suitable_job/>**
360 +)))|(% colspan="1" %)(% colspan="1" %)
361 +(((
362 +
409 409  )))
410 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
364 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
411 411  (((
412 412  //<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.//
413 413  )))
... ... @@ -420,8 +420,11 @@
420 420  )))|(% colspan="1" %)(% colspan="1" %)
421 421  (((
422 422  Changed behaviour of script action **<get_ware_definition/>**
377 +)))|(% colspan="1" %)(% colspan="1" %)
378 +(((
379 +
423 423  )))
424 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
381 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
425 425  (((
426 426  //<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.//
427 427  )))
... ... @@ -434,8 +434,11 @@
434 434  )))|(% colspan="1" %)(% colspan="1" %)
435 435  (((
436 436  Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case
394 +)))|(% colspan="1" %)(% colspan="1" %)
395 +(((
396 +
437 437  )))
438 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
398 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
439 439  (((
440 440  //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.)\\
441 441  
... ... @@ -450,8 +450,11 @@
450 450  )))|(% colspan="1" %)(% colspan="1" %)
451 451  (((
452 452  Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions>
413 +)))|(% colspan="1" %)(% colspan="1" %)
414 +(((
415 +
453 453  )))
454 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
417 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
455 455  (((
456 456  //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.//
457 457  )))
... ... @@ -464,8 +464,11 @@
464 464  )))|(% colspan="1" %)(% colspan="1" %)
465 465  (((
466 466  Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos**
430 +)))|(% colspan="1" %)(% colspan="1" %)
431 +(((
432 +
467 467  )))
468 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
434 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
469 469  (((
470 470  //Before the change, positions are relative to $dockingbay.parent.
471 471  After the change, positions are relative to $dockingbay as specified in the documentation.//
... ... @@ -479,8 +479,11 @@
479 479  )))|(% colspan="1" %)(% colspan="1" %)
480 480  (((
481 481  Support for entity flag "**skillsvisible**" dropped
448 +)))|(% colspan="1" %)(% colspan="1" %)
449 +(((
450 +
482 482  )))
483 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
452 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
484 484  (((
485 485  //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().//
486 486  )))
... ... @@ -490,8 +490,11 @@
490 490  3.0 Beta 2
491 491  )))|(((
492 492  Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**.
462 +)))|(% colspan="1" %)(% colspan="1" %)
463 +(((
464 +
493 493  )))
494 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
466 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
495 495  (((
496 496  //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.
497 497  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.
... ... @@ -507,8 +507,11 @@
507 507  )))|(% colspan="1" %)(% colspan="1" %)
508 508  (((
509 509  **MissionBoard** support dropped
482 +)))|(% colspan="1" %)(% colspan="1" %)
483 +(((
484 +
510 510  )))
511 -|(% 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" %)
512 512  (((
513 513  //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.//
514 514  )))
... ... @@ -518,8 +518,11 @@
518 518  3.0 Beta 1
519 519  )))|(((
520 520  By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined
496 +)))|(% colspan="1" %)(% colspan="1" %)
497 +(((
498 +
521 521  )))
522 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
500 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
523 523  (((
524 524  //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.//
525 525  )))
... ... @@ -532,8 +532,11 @@
532 532  )))|(% colspan="1" %)(% colspan="1" %)
533 533  (((
534 534  Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'**
513 +)))|(% colspan="1" %)(% colspan="1" %)
514 +(((
515 +
535 535  )))
536 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
517 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
537 537  (((
538 538  //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.//
539 539  )))
... ... @@ -546,8 +546,11 @@
546 546  )))|(% colspan="1" %)(% colspan="1" %)
547 547  (((
548 548  Script action **<set_doors_locked/>** attribute **'group'** changed
530 +)))|(% colspan="1" %)(% colspan="1" %)
531 +(((
532 +
549 549  )))
550 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
534 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
551 551  (((
552 552  //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.//
553 553  )))
... ... @@ -560,8 +560,11 @@
560 560  )))|(% colspan="1" %)(% colspan="1" %)
561 561  (((
562 562  Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed
547 +)))|(% colspan="1" %)(% colspan="1" %)
548 +(((
549 +
563 563  )))
564 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
551 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
565 565  (((
566 566  //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.//
567 567  )))
... ... @@ -574,8 +574,11 @@
574 574  )))|(% colspan="1" %)(% colspan="1" %)
575 575  (((
576 576  Script actions **<set_hack_target/>** and **<abort_hack/>** removed
564 +)))|(% colspan="1" %)(% colspan="1" %)
565 +(((
566 +
577 577  )))
578 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
568 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
579 579  (((
580 580  //These actions had no effect and were removed.//
581 581  )))
... ... @@ -588,8 +588,11 @@
588 588  )))|(% colspan="1" %)(% colspan="1" %)
589 589  (((
590 590  **<setup_conversation_minigame/>** script action removed
581 +)))|(% colspan="1" %)(% colspan="1" %)
582 +(((
583 +
591 591  )))
592 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
585 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
593 593  (((
594 594  //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.//
595 595  )))
... ... @@ -602,8 +602,11 @@
602 602  )))|(% colspan="1" %)(% colspan="1" %)
603 603  (((
604 604  <add_player_choice_*> **confidence** attribute removed
598 +)))|(% colspan="1" %)(% colspan="1" %)
599 +(((
600 +
605 605  )))
606 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
602 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
607 607  (((
608 608  //The default confidence of player options is another leftover from the XR era and had no effect in X4.//
609 609  )))
... ... @@ -616,8 +616,11 @@
616 616  )))|(% colspan="1" %)(% colspan="1" %)
617 617  (((
618 618  **<hack_via_control_panel/>** script action removed
615 +)))|(% colspan="1" %)(% colspan="1" %)
616 +(((
617 +
619 619  )))
620 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
619 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
621 621  (((
622 622  //Unused script action <hack_via_control_panel/> was removed.//
623 623  )))
... ... @@ -630,8 +630,11 @@
630 630  )))|(% colspan="1" %)(% colspan="1" %)
631 631  (((
632 632  **Lua: **GetMiniGameCursorPosition() removed
632 +)))|(% colspan="1" %)(% colspan="1" %)
633 +(((
634 +
633 633  )))
634 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
636 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
635 635  (((
636 636  //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.//
637 637  )))
... ... @@ -641,8 +641,11 @@
641 641  3.0 Beta 1
642 642  )))|(((
643 643  **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders
646 +)))|(% colspan="1" %)(% colspan="1" %)
647 +(((
648 +
644 644  )))
645 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
650 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
646 646  (((
647 647  //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.//
648 648  )))
... ... @@ -655,8 +655,11 @@
655 655  )))|(% colspan="1" %)(% colspan="1" %)
656 656  (((
657 657  **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor
663 +)))|(% colspan="1" %)(% colspan="1" %)
664 +(((
665 +
658 658  )))
659 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
667 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
660 660  (((
661 661  //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.//
662 662  )))
... ... @@ -669,8 +669,11 @@
669 669  )))|(% colspan="1" %)(% colspan="1" %)
670 670  (((
671 671  **$ware.illegal** updated
680 +)))|(% colspan="1" %)(% colspan="1" %)
681 +(((
682 +
672 672  )))
673 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
684 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
674 674  (((
675 675  //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.//
676 676  //It now returns true if $ware is illegal to any faction in the game.//
... ... @@ -684,8 +684,11 @@
684 684  )))|(% colspan="1" %)(% colspan="1" %)
685 685  (((
686 686  MD script **RML_Flight_Along_Path** removed
698 +)))|(% colspan="1" %)(% colspan="1" %)
699 +(((
700 +
687 687  )))
688 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
702 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
689 689  (((
690 690  //The MD script RML_Flight_Along_Path was not referened and was removed.//
691 691  )))
... ... @@ -698,8 +698,11 @@
698 698  )))|(% colspan="1" %)(% colspan="1" %)
699 699  (((
700 700  parameters of **<event_venture_mission_completed/>** changed
715 +)))|(% colspan="1" %)(% colspan="1" %)
716 +(((
717 +
701 701  )))
702 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
719 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
703 703  (((
704 704  //old params: param = venture details, param2 = ships involved, param3 = duration//
705 705  //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration//
... ... @@ -711,8 +711,11 @@
711 711  )))|(((
712 712  **<set_object_wing_name/>** removed,
713 713  **<set_object_fleet_name/>** added
731 +)))|(% colspan="1" %)(% colspan="1" %)
732 +(((
733 +
714 714  )))
715 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
735 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
716 716  (((
717 717  //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>//
718 718  )))
... ... @@ -723,12 +723,15 @@
723 723  )))|(((
724 724  **$controllable.wing.*** removed,
725 725  **$controllable.fleet.*** added
746 +)))|(% colspan="1" %)(% colspan="1" %)
747 +(((
748 +
726 726  )))
727 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
750 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
728 728  (((
729 729  $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander
730 730  )))
731 -|(% colspan="3" %)(% colspan="3" %)
754 +|(% colspan="4" %)(% colspan="4" %)
732 732  (((
733 733  == 2.60 ==
734 734  )))
... ... @@ -738,8 +738,11 @@
738 738  2.60 Beta 1
739 739  )))|(((
740 740  '**checkoperational**' filter behaviour changed
764 +)))|(% colspan="1" %)(% colspan="1" %)
765 +(((
766 +
741 741  )))
742 -|(% 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" %)
743 743  (((
744 744  //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.//
745 745  
... ... @@ -751,12 +751,15 @@
751 751  2.60 Beta 1
752 752  )))|(((
753 753  $container.**supplyresources** behavior changed
780 +)))|(% colspan="1" %)(% colspan="1" %)
781 +(((
782 +
754 754  )))
755 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
784 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
756 756  (((
757 757  //The script keyword $container.supplyresources now includes reserved wares.//
758 758  )))
759 -|(% colspan="3" %)(% colspan="3" %)
788 +|(% colspan="4" %)(% colspan="4" %)
760 760  (((
761 761  == 2.20 ==
762 762  )))
... ... @@ -769,8 +769,11 @@
769 769  )))|(% colspan="1" %)(% colspan="1" %)
770 770  (((
771 771  **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined.
801 +)))|(% colspan="1" %)(% colspan="1" %)
802 +(((
803 +
772 772  )))
773 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
805 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
774 774  (((
775 775  //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.
776 776  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.//
... ... @@ -787,12 +787,15 @@
787 787  )))|(% colspan="1" %)(% colspan="1" %)
788 788  (((
789 789  Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor'
822 +)))|(% colspan="1" %)(% colspan="1" %)
823 +(((
824 +
790 790  )))
791 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
826 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
792 792  (((
793 793  //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.//
794 794  )))
795 -|(% colspan="3" %)(% colspan="3" %)
830 +|(% colspan="4" %)(% colspan="4" %)
796 796  (((
797 797  == 2.00 ==
798 798  )))
... ... @@ -805,8 +805,11 @@
805 805  )))|(% colspan="1" %)(% colspan="1" %)
806 806  (((
807 807  **<event_build_finished/> **param2 now returns null instead of a construction sequence
843 +)))|(% colspan="1" %)(% colspan="1" %)
844 +(((
845 +
808 808  )))
809 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
847 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
810 810  (((
811 811  //The construction sequence which was finished should now be accessed via the buildtask provided via param3.//
812 812  )))
... ... @@ -819,8 +819,11 @@
819 819  )))|(% colspan="1" %)(% colspan="1" %)
820 820  (((
821 821  **param.boarding.{...}** strength parameters removed
860 +)))|(% colspan="1" %)(% colspan="1" %)
861 +(((
862 +
822 822  )))
823 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
864 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
824 824  (((
825 825  //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.//
826 826  )))
... ... @@ -833,8 +833,11 @@
833 833  )))|(% colspan="1" %)(% colspan="1" %)
834 834  (((
835 835  **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed
877 +)))|(% colspan="1" %)(% colspan="1" %)
878 +(((
879 +
836 836  )))
837 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
881 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
838 838  (((
839 839  //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.//
840 840  )))
... ... @@ -844,8 +844,11 @@
844 844  2.00 Beta 1
845 845  )))|(((
846 846  **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals
891 +)))|(% colspan="1" %)(% colspan="1" %)
892 +(((
893 +
847 847  )))
848 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
895 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
849 849  (((
850 850  //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.//
851 851  )))
... ... @@ -855,8 +855,11 @@
855 855  2.00 Beta 1
856 856  )))|(((
857 857  **FFI: SetFormationShape()** no longer indicates an error upon certain error cases
905 +)))|(% colspan="1" %)(% colspan="1" %)
906 +(((
907 +
858 858  )))
859 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
909 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
860 860  (((
861 861  //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.//
862 862  //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.//
... ... @@ -867,8 +867,11 @@
867 867  2.00 Beta 1
868 868  )))|(((
869 869  **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated.
920 +)))|(% colspan="1" %)(% colspan="1" %)
921 +(((
922 +
870 870  )))
871 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
924 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
872 872  (((
873 873  //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.//
874 874  )))
... ... @@ -878,8 +878,11 @@
878 878  2.00 Beta 1
879 879  )))|(((
880 880  **<event_player_changed_target/>** now fires and returns null if the player deselects a target.
934 +)))|(% colspan="1" %)(% colspan="1" %)
935 +(((
936 +
881 881  )))
882 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
938 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
883 883  (((
884 884  //For prior behavior, check for event.param being non-null.//
885 885  )))
... ... @@ -889,8 +889,11 @@
889 889  2.00 Beta 1
890 890  )))|(((
891 891  **<shoot/>/<shoot_at/>** attribute changes.
948 +)))|(% colspan="1" %)(% colspan="1" %)
949 +(((
950 +
892 892  )))
893 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
952 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
894 894  (((
895 895  //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.//
896 896  //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.//
... ... @@ -903,9 +903,12 @@
903 903  )))|(((
904 904  2.00 Beta 1
905 905  )))|(((
906 -**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.
965 +**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% class="confluenceTd" %)
966 +)))|(% colspan="1" %)(% colspan="1" %)
967 +(((
968 +
907 907  )))
908 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
970 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
909 909  (((
910 910  //Added possibility to query build tasks of a certain buildmodule.//
911 911  )))
... ... @@ -915,8 +915,11 @@
915 915  2.00 Beta 1
916 916  )))|(((
917 917  **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field.
980 +)))|(% colspan="1" %)(% colspan="1" %)
981 +(((
982 +
918 918  )))
919 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
984 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
920 920  (((
921 921  //Added list of resources a buildmodule needs to build.//
922 922  )))
... ... @@ -926,8 +926,11 @@
926 926  2.00 Beta 1
927 927  )))|(((
928 928  (% 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);" %)
994 +)))|(% colspan="1" %)(% colspan="1" %)
995 +(((
996 +
929 929  )))
930 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
998 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
931 931  (((
932 932  //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.//
933 933  )))
... ... @@ -936,13 +936,16 @@
936 936  )))|(((
937 937  2.00 Beta 1
938 938  )))|(((
939 -**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.
1007 +**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" %)
1008 +)))|(% colspan="1" %)(% colspan="1" %)
1009 +(((
1010 +
940 940  )))
941 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1012 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
942 942  (((
943 943  //Changed return value type to const char* to better identify failure reasons in Lua script.//
944 944  )))
945 -|(% colspan="3" %)(% colspan="3" %)
1016 +|(% colspan="4" %)(% colspan="4" %)
946 946  (((
947 947  == 1.50 ==
948 948  )))
... ... @@ -951,9 +951,12 @@
951 951  )))|(((
952 952  1.50 Beta 3
953 953  )))|(((
954 -**Lua: GetComponentData() **changed behavior of "docksizes" property.
1025 +**Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %)
1026 +)))|(% colspan="1" %)(% colspan="1" %)
1027 +(((
1028 +
955 955  )))
956 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1030 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
957 957  (((
958 958  //The "docksizes" property no longer includes internal ship storage docks.//
959 959  )))
... ... @@ -963,8 +963,11 @@
963 963  1.50 Beta 2
964 964  )))|(((
965 965  **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR).
1040 +)))|(% colspan="1" %)(% colspan="1" %)
1041 +(((
1042 +
966 966  )))
967 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1044 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
968 968  (((
969 969  //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".//
970 970  
... ... @@ -977,9 +977,12 @@
977 977  )))|(((
978 978  1.50 Beta 2
979 979  )))|(((
980 -**FFI: UpgradeGroupInfo **datatype was changed.
1057 +**FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %)
1058 +)))|(% colspan="1" %)(% colspan="1" %)
1059 +(((
1060 +
981 981  )))
982 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1062 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
983 983  (((
984 984  //Added new "operational" field to retrieve information about number of operational upgrades in a group.//
985 985  )))
... ... @@ -992,8 +992,11 @@
992 992  )))|(% colspan="1" %)(% colspan="1" %)
993 993  (((
994 994  **FFI: SetGuidance()** removed useinfopoint argument.
1075 +)))|(% colspan="1" %)(% colspan="1" %)
1076 +(((
1077 +
995 995  )))
996 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1079 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
997 997  (((
998 998  //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.
999 999  //
... ... @@ -1005,13 +1005,16 @@
1005 1005  )))|(((
1006 1006  1.50 Beta 1
1007 1007  )))|(((
1008 -**FFI: CancelConstruction() **changed its return value.
1091 +**FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %)
1092 +)))|(% colspan="1" %)(% colspan="1" %)
1093 +(((
1094 +
1009 1009  )))
1010 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1096 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1011 1011  (((
1012 1012  (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. //
1013 1013  )))
1014 -|(% colspan="3" %)(% colspan="3" %)
1100 +|(% colspan="4" %)(% colspan="4" %)
1015 1015  (((
1016 1016  == 1.32 ==
1017 1017  )))
... ... @@ -1021,12 +1021,15 @@
1021 1021  1.32
1022 1022  )))|(((
1023 1023  **Lua: GetComponentData() **removed the "nextdestname" property.
1110 +)))|(% colspan="1" %)(% colspan="1" %)
1111 +(((
1112 +
1024 1024  )))
1025 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1114 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1026 1026  (((
1027 1027  //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.//
1028 1028  )))
1029 -|(% colspan="3" %)(% colspan="3" %)
1118 +|(% colspan="4" %)(% colspan="4" %)
1030 1030  (((
1031 1031  == 1.20 ==
1032 1032  )))
... ... @@ -1035,9 +1035,12 @@
1035 1035  )))|(((
1036 1036  1.20
1037 1037  )))|(((
1038 -**FFI: GetAAOption()** got a new "useconfig" parameter.
1127 +**FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %)
1128 +)))|(% colspan="1" %)(% colspan="1" %)
1129 +(((
1130 +
1039 1039  )))
1040 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1132 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1041 1041  (((
1042 1042  //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.//
1043 1043  )))
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -135862105
1 +104596046
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/135862105/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/104596046/Breaking Changes