Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 102.1
edited by owen
on 2023/02/07 12:57
Change comment: Added documentation for <find_object_surface> changes
To version 75.1
edited by stefan
on 2021/02/01 04:38
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.stefan
Content
... ... @@ -18,7 +18,6 @@
18 18  
19 19  = Breaking Changes =
20 20  
21 -(% class="wrapped" %)
22 22  |=(((
23 23  Type
24 24  )))|=(((
... ... @@ -25,230 +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 3
39 -)))|(% colspan="1" %)(% colspan="1" %)
40 -(((
41 -Changed result of **<find_object_surface>** action in the case of a failure
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 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.//
46 -
47 -//Previously, it returned null only if there was a physics error. It however returned a valid, somewhat-random, position if physics were fine but it was still unable to find a suitable surface position. This position was often unsuitable to use for gameplay purposes so it is now null so the caller can handle the situation.//
48 -
49 -//The action itself has been improved to increase the chance of finding suitable surface positions.//
50 -)))
51 -|(% colspan="1" %)(% colspan="1" %)
52 -(((
53 -Scripts
54 -)))|(% colspan="1" %)(% colspan="1" %)
55 -(((
56 -6.00 Beta 1
57 -)))|(% colspan="1" %)(% colspan="1" %)
58 -(((
59 -Behaviour change for **<match_dock>** script component filter
60 -)))
61 -|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
62 -(((
63 -//<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes.
64 -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.//
65 -)))
66 -|(% colspan="1" %)(% colspan="1" %)
67 -(((
68 -Scripts
69 -)))|(% colspan="1" %)(% colspan="1" %)
70 -(((
71 -6.00 Beta 1
72 -)))|(% colspan="1" %)(% colspan="1" %)
73 -(((
74 -Changed result attribute location for **<get_attackstrength>**
75 -)))
76 -|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
77 -(((
78 -//The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.//
79 -)))
80 -|(((
81 -Assets
82 -)))|(((
83 -6.00 Beta 1
84 -)))|(((
85 -Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons
86 -)))
87 -|(% 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" %)
88 -(((
89 -//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.
90 -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.//
91 -)))
92 -|(% colspan="1" %)(% colspan="1" %)
93 -(((
94 -Scripts
95 -)))|(% colspan="1" %)(% colspan="1" %)
96 -(((
97 -6.00 Beta 1
98 -)))|(% colspan="1" %)(% colspan="1" %)
99 -(((
100 -Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects
101 -)))
102 -|(% 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" %)
103 -(((
104 -//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.//
105 -)))
106 -|(((
107 -Scripts
108 -)))|(((
109 -6.00 Beta 1
110 -)))|(((
111 -**<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards.
112 -)))
113 -|(% 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" %)
114 -(((
115 -//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.//
116 -)))
117 -|(((
118 -Cutscenes
119 -)))|(((
120 -6.00 Beta 1
121 -)))|(((
122 -Changed behaviour of **<angles>** in cutscenes
123 -)))
124 -|(% 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" %)
125 -(((
126 -//The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.//
127 -)))
128 -|(% colspan="3" %)(% colspan="3" %)
129 -(((
130 -== 5.00 ==
131 -)))
132 -|(((
133 -Parameters
134 -)))|(((
135 -5.00 Beta 1
136 -)))|(((
137 -**<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration
138 -)))
139 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
140 -(((
141 -//'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.//
142 -)))
143 -|(% colspan="3" %)(% colspan="3" %)
144 -(((
145 -== 4.10 ==
146 -)))
147 -|(% colspan="1" %)(% colspan="1" %)
148 -(((
149 -UI extensions
150 -)))|(% colspan="1" %)(% colspan="1" %)
151 -(((
152 -4.10 Beta 7
153 -)))|(% colspan="1" %)(% colspan="1" %)
154 -(((
155 -**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
156 -)))
157 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
158 -(((
159 -//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.//
160 -)))
161 -|(% colspan="1" %)(% colspan="1" %)
162 -(((
163 -UI extensions
164 -)))|(% colspan="1" %)(% colspan="1" %)
165 -(((
166 -4.10 Beta 6
167 -)))|(% colspan="1" %)(% colspan="1" %)
168 -(((
169 -**FFI**: CustomGameStartPlayerProperty2 changed
170 -)))
171 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
172 -(((
173 -//This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.//
174 -)))
175 -|(% colspan="1" %)(% colspan="1" %)
176 -(((
177 -Parameters
178 -)))|(% colspan="1" %)(% colspan="1" %)
179 -(((
180 -4.10 Beta 3
181 -)))|(% colspan="1" %)(% colspan="1" %)
182 -(((
183 -Renamed **<stationinfobox>** to **<infobox>**
184 -)))
185 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
186 -(((
187 -//Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.//
188 -)))
189 -|(% colspan="1" %)(% colspan="1" %)
190 -(((
191 -UI extensions
192 -)))|(% colspan="1" %)(% colspan="1" %)
193 -(((
194 -4.10 Beta 2
195 -)))|(% colspan="1" %)(% colspan="1" %)
196 -(((
197 -**FFI**: SetMacroMapPlayerSectorOffset() deprecated
198 -)))
199 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
200 -(((
201 -//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.//
202 -)))
203 -|(((
204 -UI extensions
205 -)))|(((
206 -4.10 Beta 2
207 -)))|(((
208 -**FFI**: (% style="color: rgb(0,0,0);" %)FilterComponentForMapMode(%%)() and (% style="color: rgb(0,0,0);" %)SetMapObjectFilter() changed
209 -)))
210 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
211 -(((
212 -//These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.//
213 -)))
214 -|(((
215 -Scripts
216 -)))|(((
217 -4.10 Beta 1
218 -)))|(((
219 -People related attributes of mission** <delivery> **node moved
220 -)))
221 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
222 -(((
223 -//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.//
224 -)))
225 -|(% colspan="1" %)(% colspan="1" %)
226 -(((
227 -Scripts
228 -)))|(% colspan="1" %)(% colspan="1" %)
229 -(((
230 -4.10 Beta 1
231 -)))|(% colspan="1" %)(% colspan="1" %)
232 -(((
233 -**$destructible.productions** replaced with $defensible.productions
234 -)))
235 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
236 -(((
237 -//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.//
238 -)))
239 -|(((
240 -Scripts
241 -)))|(((
242 -4.10 Beta 1
243 -)))|(((
244 -Removed script property **$object.spawnsourceseed**
245 -)))
246 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
247 -(((
248 -//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.//
249 -)))
250 -|(% colspan="3" %)(% colspan="3" %)
251 -(((
252 252  == 4.00 ==
253 253  )))
254 254  |(% colspan="1" %)(% colspan="1" %)
... ... @@ -256,64 +256,22 @@
256 256  UI core
257 257  )))|(% colspan="1" %)(% colspan="1" %)
258 258  (((
259 -4.00 Beta 10
40 +4.00 Beta 5
260 260  )))|(% colspan="1" %)(% colspan="1" %)
261 261  (((
262 -Controlled ship can change without a **gameplanchange-event** occurring.
263 -)))
264 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
265 -(((
266 -//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).
267 -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.
268 -//
269 -)))
270 -|(((
271 -Scripts
272 -)))|(((
273 -4.00 Beta 7
274 -)))|(((
275 -Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed
276 -)))
277 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
278 -(((
279 -//Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects?
280 -New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits
281 -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//
282 -)))
283 -|(% colspan="1" %)(% colspan="1" %)
284 -(((
285 -UI core
43 +**FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed
286 286  )))|(% colspan="1" %)(% colspan="1" %)
287 287  (((
288 -4.00 Beta 6
289 -)))|(% colspan="1" %)(% colspan="1" %)
290 -(((
291 -**FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed
46 +
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 -//In order to keep consistency with regards to the new behvior 'hostile' relation state and the older (deprecated) UI functions, the behavior of the deprecated GetFactionRelationStatus() function was changed according to the behavior of the GetRelationStatus()/GetRelationStatus2() functions which was done in the previous beta.
296 -Factions with a relation rating between -20 and -10 will now report a relation status of 'neutral' (aka: 1) instead of 'hostile'/'enemy' (aka: 0).//
297 -
298 -//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.
299 -//
300 -)))
301 -|(% colspan="1" %)(% colspan="1" %)
302 -(((
303 -UI core
50 +//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.
51 +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).
304 304  )))|(% colspan="1" %)(% colspan="1" %)
305 305  (((
306 -4.00 Beta 5
307 -)))|(% colspan="1" %)(% colspan="1" %)
308 -(((
309 -**FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed
54 +
310 310  )))
311 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
312 -(((
313 -//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.//
314 -
315 -//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).
316 -)))
317 317  |(((
318 318  Parameters
319 319  )))|(((
... ... @@ -320,8 +320,10 @@
320 320  4.00 Beta 1
321 321  )))|(((
322 322  **requiresconstructionvessel** parameter moved
62 +)))|(((
63 +
323 323  )))
324 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
65 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
325 325  (((
326 326  //The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.//
327 327  )))
... ... @@ -331,12 +331,17 @@
331 331  4.00 Beta 1
332 332  )))|(((
333 333  Changed behaviour of **gatedistance** script property
75 +)))|(((
76 +
334 334  )))
335 335  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
336 336  (((
337 337  //The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.//
81 +)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %)
82 +(((
83 +
338 338  )))
339 -|(% colspan="3" %)(% colspan="3" %)
85 +|(% colspan="4" %)(% colspan="4" %)
340 340  (((
341 341  == 3.30 ==
342 342  )))
... ... @@ -346,12 +346,15 @@
346 346  3.30 Beta 3
347 347  )))|(((
348 348  **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()**
95 +)))|(% colspan="1" %)(% colspan="1" %)
96 +(((
97 +
349 349  )))
350 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
99 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
351 351  (((
352 352  //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()//
353 353  )))
354 -|(% colspan="3" %)(% colspan="3" %)
103 +|(% colspan="4" %)(% colspan="4" %)
355 355  (((
356 356  == 3.20 ==
357 357  )))
... ... @@ -361,8 +361,11 @@
361 361  3.20 Beta 1
362 362  )))|(((
363 363  Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed
113 +)))|(% colspan="1" %)(% colspan="1" %)
114 +(((
115 +
364 364  )))
365 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
117 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
366 366  (((
367 367  //Old params: param = attacked object, param2 = attack method, param3 = attacked component//
368 368  //New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon]
... ... @@ -377,8 +377,11 @@
377 377  )))|(% colspan="1" %)(% colspan="1" %)
378 378  (((
379 379  Removed script property $trade.**restriction.faction**
132 +)))|(% colspan="1" %)(% colspan="1" %)
133 +(((
134 +
380 380  )))
381 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
136 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
382 382  (((
383 383  //$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.//
384 384  )))
... ... @@ -388,12 +388,15 @@
388 388  3.20 Beta 1
389 389  )))|(((
390 390  **Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete!
146 +)))|(% colspan="1" %)(% colspan="1" %)
147 +(((
148 +
391 391  )))
392 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
150 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
393 393  (((
394 394  //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.//
395 395  )))
396 -|(% colspan="3" %)(% colspan="3" %)
154 +|(% colspan="4" %)(% colspan="4" %)
397 397  (((
398 398  == 3.10 ==
399 399  )))
... ... @@ -406,12 +406,15 @@
406 406  )))|(% colspan="1" %)(% colspan="1" %)
407 407  (((
408 408  Removed script action **<add_build/>**
167 +)))|(% colspan="1" %)(% colspan="1" %)
168 +(((
169 +
409 409  )))
410 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
171 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
411 411  (((
412 412  //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.//
413 413  )))
414 -|(% colspan="3" %)(% colspan="3" %)
175 +|(% colspan="4" %)(% colspan="4" %)
415 415  (((
416 416  == 3.00 ==
417 417  )))
... ... @@ -424,8 +424,11 @@
424 424  )))|(% colspan="1" %)(% colspan="1" %)
425 425  (((
426 426  Changed behaviour of script action **<get_suitable_job/>**
188 +)))|(% colspan="1" %)(% colspan="1" %)
189 +(((
190 +
427 427  )))
428 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
192 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
429 429  (((
430 430  //<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.//
431 431  )))
... ... @@ -438,8 +438,11 @@
438 438  )))|(% colspan="1" %)(% colspan="1" %)
439 439  (((
440 440  Changed behaviour of script action **<get_ware_definition/>**
205 +)))|(% colspan="1" %)(% colspan="1" %)
206 +(((
207 +
441 441  )))
442 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
209 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
443 443  (((
444 444  //<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.//
445 445  )))
... ... @@ -452,8 +452,11 @@
452 452  )))|(% colspan="1" %)(% colspan="1" %)
453 453  (((
454 454  Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case
222 +)))|(% colspan="1" %)(% colspan="1" %)
223 +(((
224 +
455 455  )))
456 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
226 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
457 457  (((
458 458  //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.)\\
459 459  
... ... @@ -468,8 +468,11 @@
468 468  )))|(% colspan="1" %)(% colspan="1" %)
469 469  (((
470 470  Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions>
241 +)))|(% colspan="1" %)(% colspan="1" %)
242 +(((
243 +
471 471  )))
472 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
245 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
473 473  (((
474 474  //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.//
475 475  )))
... ... @@ -482,8 +482,11 @@
482 482  )))|(% colspan="1" %)(% colspan="1" %)
483 483  (((
484 484  Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos**
258 +)))|(% colspan="1" %)(% colspan="1" %)
259 +(((
260 +
485 485  )))
486 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
262 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
487 487  (((
488 488  //Before the change, positions are relative to $dockingbay.parent.
489 489  After the change, positions are relative to $dockingbay as specified in the documentation.//
... ... @@ -497,8 +497,11 @@
497 497  )))|(% colspan="1" %)(% colspan="1" %)
498 498  (((
499 499  Support for entity flag "**skillsvisible**" dropped
276 +)))|(% colspan="1" %)(% colspan="1" %)
277 +(((
278 +
500 500  )))
501 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
280 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
502 502  (((
503 503  //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().//
504 504  )))
... ... @@ -508,8 +508,11 @@
508 508  3.0 Beta 2
509 509  )))|(((
510 510  Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**.
290 +)))|(% colspan="1" %)(% colspan="1" %)
291 +(((
292 +
511 511  )))
512 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
294 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
513 513  (((
514 514  //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.
515 515  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.
... ... @@ -525,8 +525,11 @@
525 525  )))|(% colspan="1" %)(% colspan="1" %)
526 526  (((
527 527  **MissionBoard** support dropped
310 +)))|(% colspan="1" %)(% colspan="1" %)
311 +(((
312 +
528 528  )))
529 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
314 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
530 530  (((
531 531  //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.//
532 532  )))
... ... @@ -536,8 +536,11 @@
536 536  3.0 Beta 1
537 537  )))|(((
538 538  By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined
324 +)))|(% colspan="1" %)(% colspan="1" %)
325 +(((
326 +
539 539  )))
540 -|(% 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" %)
541 541  (((
542 542  //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.//
543 543  )))
... ... @@ -550,8 +550,11 @@
550 550  )))|(% colspan="1" %)(% colspan="1" %)
551 551  (((
552 552  Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'**
341 +)))|(% colspan="1" %)(% colspan="1" %)
342 +(((
343 +
553 553  )))
554 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
345 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
555 555  (((
556 556  //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.//
557 557  )))
... ... @@ -564,8 +564,11 @@
564 564  )))|(% colspan="1" %)(% colspan="1" %)
565 565  (((
566 566  Script action **<set_doors_locked/>** attribute **'group'** changed
358 +)))|(% colspan="1" %)(% colspan="1" %)
359 +(((
360 +
567 567  )))
568 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
362 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
569 569  (((
570 570  //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.//
571 571  )))
... ... @@ -578,8 +578,11 @@
578 578  )))|(% colspan="1" %)(% colspan="1" %)
579 579  (((
580 580  Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed
375 +)))|(% colspan="1" %)(% colspan="1" %)
376 +(((
377 +
581 581  )))
582 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
379 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
583 583  (((
584 584  //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.//
585 585  )))
... ... @@ -592,8 +592,11 @@
592 592  )))|(% colspan="1" %)(% colspan="1" %)
593 593  (((
594 594  Script actions **<set_hack_target/>** and **<abort_hack/>** removed
392 +)))|(% colspan="1" %)(% colspan="1" %)
393 +(((
394 +
595 595  )))
596 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
396 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
597 597  (((
598 598  //These actions had no effect and were removed.//
599 599  )))
... ... @@ -606,8 +606,11 @@
606 606  )))|(% colspan="1" %)(% colspan="1" %)
607 607  (((
608 608  **<setup_conversation_minigame/>** script action removed
409 +)))|(% colspan="1" %)(% colspan="1" %)
410 +(((
411 +
609 609  )))
610 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
413 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
611 611  (((
612 612  //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.//
613 613  )))
... ... @@ -620,8 +620,11 @@
620 620  )))|(% colspan="1" %)(% colspan="1" %)
621 621  (((
622 622  <add_player_choice_*> **confidence** attribute removed
426 +)))|(% colspan="1" %)(% colspan="1" %)
427 +(((
428 +
623 623  )))
624 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
430 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
625 625  (((
626 626  //The default confidence of player options is another leftover from the XR era and had no effect in X4.//
627 627  )))
... ... @@ -634,8 +634,11 @@
634 634  )))|(% colspan="1" %)(% colspan="1" %)
635 635  (((
636 636  **<hack_via_control_panel/>** script action removed
443 +)))|(% colspan="1" %)(% colspan="1" %)
444 +(((
445 +
637 637  )))
638 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
447 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
639 639  (((
640 640  //Unused script action <hack_via_control_panel/> was removed.//
641 641  )))
... ... @@ -648,8 +648,11 @@
648 648  )))|(% colspan="1" %)(% colspan="1" %)
649 649  (((
650 650  **Lua: **GetMiniGameCursorPosition() removed
460 +)))|(% colspan="1" %)(% colspan="1" %)
461 +(((
462 +
651 651  )))
652 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
464 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
653 653  (((
654 654  //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.//
655 655  )))
... ... @@ -659,8 +659,11 @@
659 659  3.0 Beta 1
660 660  )))|(((
661 661  **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders
474 +)))|(% colspan="1" %)(% colspan="1" %)
475 +(((
476 +
662 662  )))
663 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
478 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
664 664  (((
665 665  //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.//
666 666  )))
... ... @@ -673,8 +673,11 @@
673 673  )))|(% colspan="1" %)(% colspan="1" %)
674 674  (((
675 675  **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor
491 +)))|(% colspan="1" %)(% colspan="1" %)
492 +(((
493 +
676 676  )))
677 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
495 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
678 678  (((
679 679  //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.//
680 680  )))
... ... @@ -687,8 +687,11 @@
687 687  )))|(% colspan="1" %)(% colspan="1" %)
688 688  (((
689 689  **$ware.illegal** updated
508 +)))|(% colspan="1" %)(% colspan="1" %)
509 +(((
510 +
690 690  )))
691 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
512 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
692 692  (((
693 693  //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.//
694 694  //It now returns true if $ware is illegal to any faction in the game.//
... ... @@ -702,8 +702,11 @@
702 702  )))|(% colspan="1" %)(% colspan="1" %)
703 703  (((
704 704  MD script **RML_Flight_Along_Path** removed
526 +)))|(% colspan="1" %)(% colspan="1" %)
527 +(((
528 +
705 705  )))
706 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
530 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
707 707  (((
708 708  //The MD script RML_Flight_Along_Path was not referened and was removed.//
709 709  )))
... ... @@ -716,8 +716,11 @@
716 716  )))|(% colspan="1" %)(% colspan="1" %)
717 717  (((
718 718  parameters of **<event_venture_mission_completed/>** changed
543 +)))|(% colspan="1" %)(% colspan="1" %)
544 +(((
545 +
719 719  )))
720 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
547 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
721 721  (((
722 722  //old params: param = venture details, param2 = ships involved, param3 = duration//
723 723  //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration//
... ... @@ -729,8 +729,11 @@
729 729  )))|(((
730 730  **<set_object_wing_name/>** removed,
731 731  **<set_object_fleet_name/>** added
559 +)))|(% colspan="1" %)(% colspan="1" %)
560 +(((
561 +
732 732  )))
733 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
563 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
734 734  (((
735 735  //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>//
736 736  )))
... ... @@ -741,12 +741,15 @@
741 741  )))|(((
742 742  **$controllable.wing.*** removed,
743 743  **$controllable.fleet.*** added
574 +)))|(% colspan="1" %)(% colspan="1" %)
575 +(((
576 +
744 744  )))
745 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
578 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
746 746  (((
747 747  $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander
748 748  )))
749 -|(% colspan="3" %)(% colspan="3" %)
582 +|(% colspan="4" %)(% colspan="4" %)
750 750  (((
751 751  == 2.60 ==
752 752  )))
... ... @@ -756,8 +756,11 @@
756 756  2.60 Beta 1
757 757  )))|(((
758 758  '**checkoperational**' filter behaviour changed
592 +)))|(% colspan="1" %)(% colspan="1" %)
593 +(((
594 +
759 759  )))
760 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
596 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
761 761  (((
762 762  //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.//
763 763  
... ... @@ -769,12 +769,15 @@
769 769  2.60 Beta 1
770 770  )))|(((
771 771  $container.**supplyresources** behavior changed
608 +)))|(% colspan="1" %)(% colspan="1" %)
609 +(((
610 +
772 772  )))
773 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
612 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
774 774  (((
775 775  //The script keyword $container.supplyresources now includes reserved wares.//
776 776  )))
777 -|(% colspan="3" %)(% colspan="3" %)
616 +|(% colspan="4" %)(% colspan="4" %)
778 778  (((
779 779  == 2.20 ==
780 780  )))
... ... @@ -787,8 +787,11 @@
787 787  )))|(% colspan="1" %)(% colspan="1" %)
788 788  (((
789 789  **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined.
629 +)))|(% colspan="1" %)(% colspan="1" %)
630 +(((
631 +
790 790  )))
791 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
633 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
792 792  (((
793 793  //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.
794 794  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.//
... ... @@ -805,12 +805,15 @@
805 805  )))|(% colspan="1" %)(% colspan="1" %)
806 806  (((
807 807  Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor'
650 +)))|(% colspan="1" %)(% colspan="1" %)
651 +(((
652 +
808 808  )))
809 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
654 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
810 810  (((
811 811  //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.//
812 812  )))
813 -|(% colspan="3" %)(% colspan="3" %)
658 +|(% colspan="4" %)(% colspan="4" %)
814 814  (((
815 815  == 2.00 ==
816 816  )))
... ... @@ -823,8 +823,11 @@
823 823  )))|(% colspan="1" %)(% colspan="1" %)
824 824  (((
825 825  **<event_build_finished/> **param2 now returns null instead of a construction sequence
671 +)))|(% colspan="1" %)(% colspan="1" %)
672 +(((
673 +
826 826  )))
827 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
675 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
828 828  (((
829 829  //The construction sequence which was finished should now be accessed via the buildtask provided via param3.//
830 830  )))
... ... @@ -837,8 +837,11 @@
837 837  )))|(% colspan="1" %)(% colspan="1" %)
838 838  (((
839 839  **param.boarding.{...}** strength parameters removed
688 +)))|(% colspan="1" %)(% colspan="1" %)
689 +(((
690 +
840 840  )))
841 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
692 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
842 842  (((
843 843  //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.//
844 844  )))
... ... @@ -851,8 +851,11 @@
851 851  )))|(% colspan="1" %)(% colspan="1" %)
852 852  (((
853 853  **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed
705 +)))|(% colspan="1" %)(% colspan="1" %)
706 +(((
707 +
854 854  )))
855 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
709 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
856 856  (((
857 857  //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.//
858 858  )))
... ... @@ -862,8 +862,11 @@
862 862  2.00 Beta 1
863 863  )))|(((
864 864  **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals
719 +)))|(% colspan="1" %)(% colspan="1" %)
720 +(((
721 +
865 865  )))
866 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
723 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
867 867  (((
868 868  //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.//
869 869  )))
... ... @@ -873,8 +873,11 @@
873 873  2.00 Beta 1
874 874  )))|(((
875 875  **FFI: SetFormationShape()** no longer indicates an error upon certain error cases
733 +)))|(% colspan="1" %)(% colspan="1" %)
734 +(((
735 +
876 876  )))
877 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
737 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
878 878  (((
879 879  //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.//
880 880  //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.//
... ... @@ -885,8 +885,11 @@
885 885  2.00 Beta 1
886 886  )))|(((
887 887  **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated.
748 +)))|(% colspan="1" %)(% colspan="1" %)
749 +(((
750 +
888 888  )))
889 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
752 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
890 890  (((
891 891  //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.//
892 892  )))
... ... @@ -896,8 +896,11 @@
896 896  2.00 Beta 1
897 897  )))|(((
898 898  **<event_player_changed_target/>** now fires and returns null if the player deselects a target.
762 +)))|(% colspan="1" %)(% colspan="1" %)
763 +(((
764 +
899 899  )))
900 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
766 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
901 901  (((
902 902  //For prior behavior, check for event.param being non-null.//
903 903  )))
... ... @@ -907,8 +907,11 @@
907 907  2.00 Beta 1
908 908  )))|(((
909 909  **<shoot/>/<shoot_at/>** attribute changes.
776 +)))|(% colspan="1" %)(% colspan="1" %)
777 +(((
778 +
910 910  )))
911 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
780 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
912 912  (((
913 913  //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.//
914 914  //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.//
... ... @@ -921,9 +921,12 @@
921 921  )))|(((
922 922  2.00 Beta 1
923 923  )))|(((
924 -**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.
793 +**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% class="confluenceTd" %)
794 +)))|(% colspan="1" %)(% colspan="1" %)
795 +(((
796 +
925 925  )))
926 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
798 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
927 927  (((
928 928  //Added possibility to query build tasks of a certain buildmodule.//
929 929  )))
... ... @@ -933,8 +933,11 @@
933 933  2.00 Beta 1
934 934  )))|(((
935 935  **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field.
808 +)))|(% colspan="1" %)(% colspan="1" %)
809 +(((
810 +
936 936  )))
937 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
812 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
938 938  (((
939 939  //Added list of resources a buildmodule needs to build.//
940 940  )))
... ... @@ -944,8 +944,11 @@
944 944  2.00 Beta 1
945 945  )))|(((
946 946  (% 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);" %)
822 +)))|(% colspan="1" %)(% colspan="1" %)
823 +(((
824 +
947 947  )))
948 -|(% 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" %)
949 949  (((
950 950  //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.//
951 951  )))
... ... @@ -954,13 +954,16 @@
954 954  )))|(((
955 955  2.00 Beta 1
956 956  )))|(((
957 -**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.
835 +**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" %)
836 +)))|(% colspan="1" %)(% colspan="1" %)
837 +(((
838 +
958 958  )))
959 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
840 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
960 960  (((
961 961  //Changed return value type to const char* to better identify failure reasons in Lua script.//
962 962  )))
963 -|(% colspan="3" %)(% colspan="3" %)
844 +|(% colspan="4" %)(% colspan="4" %)
964 964  (((
965 965  == 1.50 ==
966 966  )))
... ... @@ -969,9 +969,12 @@
969 969  )))|(((
970 970  1.50 Beta 3
971 971  )))|(((
972 -**Lua: GetComponentData() **changed behavior of "docksizes" property.
853 +**Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %)
854 +)))|(% colspan="1" %)(% colspan="1" %)
855 +(((
856 +
973 973  )))
974 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
858 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
975 975  (((
976 976  //The "docksizes" property no longer includes internal ship storage docks.//
977 977  )))
... ... @@ -981,8 +981,11 @@
981 981  1.50 Beta 2
982 982  )))|(((
983 983  **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR).
868 +)))|(% colspan="1" %)(% colspan="1" %)
869 +(((
870 +
984 984  )))
985 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
872 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
986 986  (((
987 987  //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".//
988 988  
... ... @@ -995,9 +995,12 @@
995 995  )))|(((
996 996  1.50 Beta 2
997 997  )))|(((
998 -**FFI: UpgradeGroupInfo **datatype was changed.
885 +**FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %)
886 +)))|(% colspan="1" %)(% colspan="1" %)
887 +(((
888 +
999 999  )))
1000 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
890 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1001 1001  (((
1002 1002  //Added new "operational" field to retrieve information about number of operational upgrades in a group.//
1003 1003  )))
... ... @@ -1010,8 +1010,11 @@
1010 1010  )))|(% colspan="1" %)(% colspan="1" %)
1011 1011  (((
1012 1012  **FFI: SetGuidance()** removed useinfopoint argument.
903 +)))|(% colspan="1" %)(% colspan="1" %)
904 +(((
905 +
1013 1013  )))
1014 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
907 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1015 1015  (((
1016 1016  //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.
1017 1017  //
... ... @@ -1023,13 +1023,16 @@
1023 1023  )))|(((
1024 1024  1.50 Beta 1
1025 1025  )))|(((
1026 -**FFI: CancelConstruction() **changed its return value.
919 +**FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %)
920 +)))|(% colspan="1" %)(% colspan="1" %)
921 +(((
922 +
1027 1027  )))
1028 -|(% 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" %)
1029 1029  (((
1030 1030  (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. //
1031 1031  )))
1032 -|(% colspan="3" %)(% colspan="3" %)
928 +|(% colspan="4" %)(% colspan="4" %)
1033 1033  (((
1034 1034  == 1.32 ==
1035 1035  )))
... ... @@ -1039,12 +1039,15 @@
1039 1039  1.32
1040 1040  )))|(((
1041 1041  **Lua: GetComponentData() **removed the "nextdestname" property.
938 +)))|(% colspan="1" %)(% colspan="1" %)
939 +(((
940 +
1042 1042  )))
1043 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
942 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1044 1044  (((
1045 1045  //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.//
1046 1046  )))
1047 -|(% colspan="3" %)(% colspan="3" %)
946 +|(% colspan="4" %)(% colspan="4" %)
1048 1048  (((
1049 1049  == 1.20 ==
1050 1050  )))
... ... @@ -1053,9 +1053,12 @@
1053 1053  )))|(((
1054 1054  1.20
1055 1055  )))|(((
1056 -**FFI: GetAAOption()** got a new "useconfig" parameter.
955 +**FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %)
956 +)))|(% colspan="1" %)(% colspan="1" %)
957 +(((
958 +
1057 1057  )))
1058 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
960 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1059 1059  (((
1060 1060  //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.//
1061 1061  )))
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -138872528
1 +101548080
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/138872528/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/101548080/Breaking Changes