Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 103.1
edited by cbj
on 2023/02/20 14:12
Change comment: There is no comment for this version
To version 77.1
edited by stefan
on 2021/02/01 12:01
Change comment: 0 <-> 1 mismatch

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.cbj
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,246 +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 4
39 -)))|(% colspan="1" %)(% colspan="1" %)
40 -(((
41 -Changed conditions for **<event_player_travelmode_started> <event_player_travelmode_stopped> <event_player_travelmode_charge_started> <event_player_travelmode_charge_aborted>** to be raised.
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 <event_player_travelmode_started>, <event_player_travelmode_stopped>, <event_player_travelmode_charge_started> and <event_player_travelmode_charge_aborted> events will no longer be raised if the player is a passenger on board a ship which enters or leaves travel mode. Previously these events would be raised whether the player was the pilot or a passenger. //
46 -
47 -//Scripts that need to check whether the player exits travel mode may also need to consider checking whether the player leaves the control seat using <event_player_stopped_control> since this will also result in travel mode stopping.//
48 -)))
49 -|(% colspan="1" %)(% colspan="1" %)
50 -(((
51 -Scripts
52 -)))|(% colspan="1" %)(% colspan="1" %)
53 -(((
54 -6.00 Beta 3
55 -)))|(% colspan="1" %)(% colspan="1" %)
56 -(((
57 -Changed result of **<find_object_surface>** action in the case of a failure
58 -)))
59 -|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
60 -(((
61 -//The 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.//
62 -
63 -//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.//
64 -
65 -//The action itself has been improved to increase the chance of finding suitable surface positions.//
66 -)))
67 -|(% colspan="1" %)(% colspan="1" %)
68 -(((
69 -Scripts
70 -)))|(% colspan="1" %)(% colspan="1" %)
71 -(((
72 -6.00 Beta 1
73 -)))|(% colspan="1" %)(% colspan="1" %)
74 -(((
75 -Behaviour change for **<match_dock>** script component filter
76 -)))
77 -|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
78 -(((
79 -//<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes.
80 -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.//
81 -)))
82 -|(% colspan="1" %)(% colspan="1" %)
83 -(((
84 -Scripts
85 -)))|(% colspan="1" %)(% colspan="1" %)
86 -(((
87 -6.00 Beta 1
88 -)))|(% colspan="1" %)(% colspan="1" %)
89 -(((
90 -Changed result attribute location for **<get_attackstrength>**
91 -)))
92 -|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
93 -(((
94 -//The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.//
95 -)))
96 -|(((
97 -Assets
98 -)))|(((
99 -6.00 Beta 1
100 -)))|(((
101 -Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons
102 -)))
103 -|(% 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" %)
104 -(((
105 -//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.
106 -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.//
107 -)))
108 -|(% colspan="1" %)(% colspan="1" %)
109 -(((
110 -Scripts
111 -)))|(% colspan="1" %)(% colspan="1" %)
112 -(((
113 -6.00 Beta 1
114 -)))|(% colspan="1" %)(% colspan="1" %)
115 -(((
116 -Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects
117 -)))
118 -|(% 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" %)
119 -(((
120 -//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.//
121 -)))
122 -|(((
123 -Scripts
124 -)))|(((
125 -6.00 Beta 1
126 -)))|(((
127 -**<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards.
128 -)))
129 -|(% 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" %)
130 -(((
131 -//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.//
132 -)))
133 -|(((
134 -Cutscenes
135 -)))|(((
136 -6.00 Beta 1
137 -)))|(((
138 -Changed behaviour of **<angles>** in cutscenes
139 -)))
140 -|(% 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" %)
141 -(((
142 -//The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.//
143 -)))
144 -|(% colspan="3" %)(% colspan="3" %)
145 -(((
146 -== 5.00 ==
147 -)))
148 -|(((
149 -Parameters
150 -)))|(((
151 -5.00 Beta 1
152 -)))|(((
153 -**<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration
154 -)))
155 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
156 -(((
157 -//'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.//
158 -)))
159 -|(% colspan="3" %)(% colspan="3" %)
160 -(((
161 -== 4.10 ==
162 -)))
163 -|(% colspan="1" %)(% colspan="1" %)
164 -(((
165 -UI extensions
166 -)))|(% colspan="1" %)(% colspan="1" %)
167 -(((
168 -4.10 Beta 7
169 -)))|(% colspan="1" %)(% colspan="1" %)
170 -(((
171 -**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
172 -)))
173 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
174 -(((
175 -//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.//
176 -)))
177 -|(% colspan="1" %)(% colspan="1" %)
178 -(((
179 -UI extensions
180 -)))|(% colspan="1" %)(% colspan="1" %)
181 -(((
182 -4.10 Beta 6
183 -)))|(% colspan="1" %)(% colspan="1" %)
184 -(((
185 -**FFI**: CustomGameStartPlayerProperty2 changed
186 -)))
187 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
188 -(((
189 -//This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.//
190 -)))
191 -|(% colspan="1" %)(% colspan="1" %)
192 -(((
193 -Parameters
194 -)))|(% colspan="1" %)(% colspan="1" %)
195 -(((
196 -4.10 Beta 3
197 -)))|(% colspan="1" %)(% colspan="1" %)
198 -(((
199 -Renamed **<stationinfobox>** to **<infobox>**
200 -)))
201 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
202 -(((
203 -//Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.//
204 -)))
205 -|(% colspan="1" %)(% colspan="1" %)
206 -(((
207 -UI extensions
208 -)))|(% colspan="1" %)(% colspan="1" %)
209 -(((
210 -4.10 Beta 2
211 -)))|(% colspan="1" %)(% colspan="1" %)
212 -(((
213 -**FFI**: SetMacroMapPlayerSectorOffset() deprecated
214 -)))
215 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
216 -(((
217 -//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.//
218 -)))
219 -|(((
220 -UI extensions
221 -)))|(((
222 -4.10 Beta 2
223 -)))|(((
224 -**FFI**: (% style="color: rgb(0,0,0);" %)FilterComponentForMapMode(%%)() and (% style="color: rgb(0,0,0);" %)SetMapObjectFilter() changed
225 -)))
226 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
227 -(((
228 -//These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.//
229 -)))
230 -|(((
231 -Scripts
232 -)))|(((
233 -4.10 Beta 1
234 -)))|(((
235 -People related attributes of mission** <delivery> **node moved
236 -)))
237 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
238 -(((
239 -//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.//
240 -)))
241 -|(% colspan="1" %)(% colspan="1" %)
242 -(((
243 -Scripts
244 -)))|(% colspan="1" %)(% colspan="1" %)
245 -(((
246 -4.10 Beta 1
247 -)))|(% colspan="1" %)(% colspan="1" %)
248 -(((
249 -**$destructible.productions** replaced with $defensible.productions
250 -)))
251 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
252 -(((
253 -//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.//
254 -)))
255 -|(((
256 -Scripts
257 -)))|(((
258 -4.10 Beta 1
259 -)))|(((
260 -Removed script property **$object.spawnsourceseed**
261 -)))
262 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
263 -(((
264 -//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.//
265 -)))
266 -|(% colspan="3" %)(% colspan="3" %)
267 -(((
268 268  == 4.00 ==
269 269  )))
270 270  |(% colspan="1" %)(% colspan="1" %)
... ... @@ -272,39 +272,13 @@
272 272  UI core
273 273  )))|(% colspan="1" %)(% colspan="1" %)
274 274  (((
275 -4.00 Beta 10
276 -)))|(% colspan="1" %)(% colspan="1" %)
277 -(((
278 -Controlled ship can change without a **gameplanchange-event** occurring.
279 -)))
280 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
281 -(((
282 -//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).
283 -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.
284 -//
285 -)))
286 -|(((
287 -Scripts
288 -)))|(((
289 -4.00 Beta 7
290 -)))|(((
291 -Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed
292 -)))
293 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
294 -(((
295 -//Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects?
296 -New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits
297 -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//
298 -)))
299 -|(% colspan="1" %)(% colspan="1" %)
300 -(((
301 -UI core
302 -)))|(% colspan="1" %)(% colspan="1" %)
303 -(((
304 304  4.00 Beta 6
305 305  )))|(% colspan="1" %)(% colspan="1" %)
306 306  (((
307 307  **FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed
44 +)))|(% colspan="1" %)(% colspan="1" %)
45 +(((
46 +
308 308  )))
309 309  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
310 310  (((
... ... @@ -313,6 +313,9 @@
313 313  
314 314  //If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.
315 315  //
55 +)))|(% colspan="1" %)(% colspan="1" %)
56 +(((
57 +
316 316  )))
317 317  |(% colspan="1" %)(% colspan="1" %)
318 318  (((
... ... @@ -323,6 +323,9 @@
323 323  )))|(% colspan="1" %)(% colspan="1" %)
324 324  (((
325 325  **FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed
68 +)))|(% colspan="1" %)(% colspan="1" %)
69 +(((
70 +
326 326  )))
327 327  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
328 328  (((
... ... @@ -329,6 +329,9 @@
329 329  //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.//
330 330  
331 331  //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).
77 +)))|(% colspan="1" %)(% colspan="1" %)
78 +(((
79 +
332 332  )))
333 333  |(((
334 334  Parameters
... ... @@ -336,8 +336,10 @@
336 336  4.00 Beta 1
337 337  )))|(((
338 338  **requiresconstructionvessel** parameter moved
87 +)))|(((
88 +
339 339  )))
340 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
90 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
341 341  (((
342 342  //The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.//
343 343  )))
... ... @@ -347,12 +347,17 @@
347 347  4.00 Beta 1
348 348  )))|(((
349 349  Changed behaviour of **gatedistance** script property
100 +)))|(((
101 +
350 350  )))
351 351  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
352 352  (((
353 353  //The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.//
106 +)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %)
107 +(((
108 +
354 354  )))
355 -|(% colspan="3" %)(% colspan="3" %)
110 +|(% colspan="4" %)(% colspan="4" %)
356 356  (((
357 357  == 3.30 ==
358 358  )))
... ... @@ -362,12 +362,15 @@
362 362  3.30 Beta 3
363 363  )))|(((
364 364  **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()**
120 +)))|(% colspan="1" %)(% colspan="1" %)
121 +(((
122 +
365 365  )))
366 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
124 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
367 367  (((
368 368  //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()//
369 369  )))
370 -|(% colspan="3" %)(% colspan="3" %)
128 +|(% colspan="4" %)(% colspan="4" %)
371 371  (((
372 372  == 3.20 ==
373 373  )))
... ... @@ -377,8 +377,11 @@
377 377  3.20 Beta 1
378 378  )))|(((
379 379  Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed
138 +)))|(% colspan="1" %)(% colspan="1" %)
139 +(((
140 +
380 380  )))
381 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
142 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
382 382  (((
383 383  //Old params: param = attacked object, param2 = attack method, param3 = attacked component//
384 384  //New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon]
... ... @@ -393,8 +393,11 @@
393 393  )))|(% colspan="1" %)(% colspan="1" %)
394 394  (((
395 395  Removed script property $trade.**restriction.faction**
157 +)))|(% colspan="1" %)(% colspan="1" %)
158 +(((
159 +
396 396  )))
397 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
161 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
398 398  (((
399 399  //$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.//
400 400  )))
... ... @@ -404,12 +404,15 @@
404 404  3.20 Beta 1
405 405  )))|(((
406 406  **Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete!
171 +)))|(% colspan="1" %)(% colspan="1" %)
172 +(((
173 +
407 407  )))
408 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
175 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
409 409  (((
410 410  //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.//
411 411  )))
412 -|(% colspan="3" %)(% colspan="3" %)
179 +|(% colspan="4" %)(% colspan="4" %)
413 413  (((
414 414  == 3.10 ==
415 415  )))
... ... @@ -422,12 +422,15 @@
422 422  )))|(% colspan="1" %)(% colspan="1" %)
423 423  (((
424 424  Removed script action **<add_build/>**
192 +)))|(% colspan="1" %)(% colspan="1" %)
193 +(((
194 +
425 425  )))
426 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
196 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
427 427  (((
428 428  //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.//
429 429  )))
430 -|(% colspan="3" %)(% colspan="3" %)
200 +|(% colspan="4" %)(% colspan="4" %)
431 431  (((
432 432  == 3.00 ==
433 433  )))
... ... @@ -440,8 +440,11 @@
440 440  )))|(% colspan="1" %)(% colspan="1" %)
441 441  (((
442 442  Changed behaviour of script action **<get_suitable_job/>**
213 +)))|(% colspan="1" %)(% colspan="1" %)
214 +(((
215 +
443 443  )))
444 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
217 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
445 445  (((
446 446  //<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.//
447 447  )))
... ... @@ -454,8 +454,11 @@
454 454  )))|(% colspan="1" %)(% colspan="1" %)
455 455  (((
456 456  Changed behaviour of script action **<get_ware_definition/>**
230 +)))|(% colspan="1" %)(% colspan="1" %)
231 +(((
232 +
457 457  )))
458 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
234 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
459 459  (((
460 460  //<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.//
461 461  )))
... ... @@ -468,8 +468,11 @@
468 468  )))|(% colspan="1" %)(% colspan="1" %)
469 469  (((
470 470  Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case
247 +)))|(% colspan="1" %)(% colspan="1" %)
248 +(((
249 +
471 471  )))
472 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
251 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
473 473  (((
474 474  //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.)\\
475 475  
... ... @@ -484,8 +484,11 @@
484 484  )))|(% colspan="1" %)(% colspan="1" %)
485 485  (((
486 486  Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions>
266 +)))|(% colspan="1" %)(% colspan="1" %)
267 +(((
268 +
487 487  )))
488 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
270 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
489 489  (((
490 490  //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.//
491 491  )))
... ... @@ -498,8 +498,11 @@
498 498  )))|(% colspan="1" %)(% colspan="1" %)
499 499  (((
500 500  Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos**
283 +)))|(% colspan="1" %)(% colspan="1" %)
284 +(((
285 +
501 501  )))
502 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
287 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
503 503  (((
504 504  //Before the change, positions are relative to $dockingbay.parent.
505 505  After the change, positions are relative to $dockingbay as specified in the documentation.//
... ... @@ -513,8 +513,11 @@
513 513  )))|(% colspan="1" %)(% colspan="1" %)
514 514  (((
515 515  Support for entity flag "**skillsvisible**" dropped
301 +)))|(% colspan="1" %)(% colspan="1" %)
302 +(((
303 +
516 516  )))
517 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
305 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
518 518  (((
519 519  //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().//
520 520  )))
... ... @@ -524,8 +524,11 @@
524 524  3.0 Beta 2
525 525  )))|(((
526 526  Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**.
315 +)))|(% colspan="1" %)(% colspan="1" %)
316 +(((
317 +
527 527  )))
528 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
319 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
529 529  (((
530 530  //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.
531 531  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.
... ... @@ -541,8 +541,11 @@
541 541  )))|(% colspan="1" %)(% colspan="1" %)
542 542  (((
543 543  **MissionBoard** support dropped
335 +)))|(% colspan="1" %)(% colspan="1" %)
336 +(((
337 +
544 544  )))
545 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
339 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
546 546  (((
547 547  //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.//
548 548  )))
... ... @@ -552,8 +552,11 @@
552 552  3.0 Beta 1
553 553  )))|(((
554 554  By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined
349 +)))|(% colspan="1" %)(% colspan="1" %)
350 +(((
351 +
555 555  )))
556 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
353 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
557 557  (((
558 558  //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.//
559 559  )))
... ... @@ -566,8 +566,11 @@
566 566  )))|(% colspan="1" %)(% colspan="1" %)
567 567  (((
568 568  Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'**
366 +)))|(% colspan="1" %)(% colspan="1" %)
367 +(((
368 +
569 569  )))
570 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
370 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
571 571  (((
572 572  //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.//
573 573  )))
... ... @@ -580,8 +580,11 @@
580 580  )))|(% colspan="1" %)(% colspan="1" %)
581 581  (((
582 582  Script action **<set_doors_locked/>** attribute **'group'** changed
383 +)))|(% colspan="1" %)(% colspan="1" %)
384 +(((
385 +
583 583  )))
584 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
387 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
585 585  (((
586 586  //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.//
587 587  )))
... ... @@ -594,8 +594,11 @@
594 594  )))|(% colspan="1" %)(% colspan="1" %)
595 595  (((
596 596  Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed
400 +)))|(% colspan="1" %)(% colspan="1" %)
401 +(((
402 +
597 597  )))
598 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
404 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
599 599  (((
600 600  //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.//
601 601  )))
... ... @@ -608,8 +608,11 @@
608 608  )))|(% colspan="1" %)(% colspan="1" %)
609 609  (((
610 610  Script actions **<set_hack_target/>** and **<abort_hack/>** removed
417 +)))|(% colspan="1" %)(% colspan="1" %)
418 +(((
419 +
611 611  )))
612 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
421 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
613 613  (((
614 614  //These actions had no effect and were removed.//
615 615  )))
... ... @@ -622,8 +622,11 @@
622 622  )))|(% colspan="1" %)(% colspan="1" %)
623 623  (((
624 624  **<setup_conversation_minigame/>** script action removed
434 +)))|(% colspan="1" %)(% colspan="1" %)
435 +(((
436 +
625 625  )))
626 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
438 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
627 627  (((
628 628  //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.//
629 629  )))
... ... @@ -636,8 +636,11 @@
636 636  )))|(% colspan="1" %)(% colspan="1" %)
637 637  (((
638 638  <add_player_choice_*> **confidence** attribute removed
451 +)))|(% colspan="1" %)(% colspan="1" %)
452 +(((
453 +
639 639  )))
640 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
455 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
641 641  (((
642 642  //The default confidence of player options is another leftover from the XR era and had no effect in X4.//
643 643  )))
... ... @@ -650,8 +650,11 @@
650 650  )))|(% colspan="1" %)(% colspan="1" %)
651 651  (((
652 652  **<hack_via_control_panel/>** script action removed
468 +)))|(% colspan="1" %)(% colspan="1" %)
469 +(((
470 +
653 653  )))
654 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
472 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
655 655  (((
656 656  //Unused script action <hack_via_control_panel/> was removed.//
657 657  )))
... ... @@ -664,8 +664,11 @@
664 664  )))|(% colspan="1" %)(% colspan="1" %)
665 665  (((
666 666  **Lua: **GetMiniGameCursorPosition() removed
485 +)))|(% colspan="1" %)(% colspan="1" %)
486 +(((
487 +
667 667  )))
668 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
489 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
669 669  (((
670 670  //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.//
671 671  )))
... ... @@ -675,8 +675,11 @@
675 675  3.0 Beta 1
676 676  )))|(((
677 677  **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders
499 +)))|(% colspan="1" %)(% colspan="1" %)
500 +(((
501 +
678 678  )))
679 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
503 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
680 680  (((
681 681  //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.//
682 682  )))
... ... @@ -689,8 +689,11 @@
689 689  )))|(% colspan="1" %)(% colspan="1" %)
690 690  (((
691 691  **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor
516 +)))|(% colspan="1" %)(% colspan="1" %)
517 +(((
518 +
692 692  )))
693 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
520 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
694 694  (((
695 695  //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.//
696 696  )))
... ... @@ -703,8 +703,11 @@
703 703  )))|(% colspan="1" %)(% colspan="1" %)
704 704  (((
705 705  **$ware.illegal** updated
533 +)))|(% colspan="1" %)(% colspan="1" %)
534 +(((
535 +
706 706  )))
707 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
537 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
708 708  (((
709 709  //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.//
710 710  //It now returns true if $ware is illegal to any faction in the game.//
... ... @@ -718,8 +718,11 @@
718 718  )))|(% colspan="1" %)(% colspan="1" %)
719 719  (((
720 720  MD script **RML_Flight_Along_Path** removed
551 +)))|(% colspan="1" %)(% colspan="1" %)
552 +(((
553 +
721 721  )))
722 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
555 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
723 723  (((
724 724  //The MD script RML_Flight_Along_Path was not referened and was removed.//
725 725  )))
... ... @@ -732,8 +732,11 @@
732 732  )))|(% colspan="1" %)(% colspan="1" %)
733 733  (((
734 734  parameters of **<event_venture_mission_completed/>** changed
568 +)))|(% colspan="1" %)(% colspan="1" %)
569 +(((
570 +
735 735  )))
736 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
572 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
737 737  (((
738 738  //old params: param = venture details, param2 = ships involved, param3 = duration//
739 739  //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration//
... ... @@ -745,8 +745,11 @@
745 745  )))|(((
746 746  **<set_object_wing_name/>** removed,
747 747  **<set_object_fleet_name/>** added
584 +)))|(% colspan="1" %)(% colspan="1" %)
585 +(((
586 +
748 748  )))
749 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
588 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
750 750  (((
751 751  //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>//
752 752  )))
... ... @@ -757,12 +757,15 @@
757 757  )))|(((
758 758  **$controllable.wing.*** removed,
759 759  **$controllable.fleet.*** added
599 +)))|(% colspan="1" %)(% colspan="1" %)
600 +(((
601 +
760 760  )))
761 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
603 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
762 762  (((
763 763  $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander
764 764  )))
765 -|(% colspan="3" %)(% colspan="3" %)
607 +|(% colspan="4" %)(% colspan="4" %)
766 766  (((
767 767  == 2.60 ==
768 768  )))
... ... @@ -772,8 +772,11 @@
772 772  2.60 Beta 1
773 773  )))|(((
774 774  '**checkoperational**' filter behaviour changed
617 +)))|(% colspan="1" %)(% colspan="1" %)
618 +(((
619 +
775 775  )))
776 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
621 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
777 777  (((
778 778  //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.//
779 779  
... ... @@ -785,12 +785,15 @@
785 785  2.60 Beta 1
786 786  )))|(((
787 787  $container.**supplyresources** behavior changed
633 +)))|(% colspan="1" %)(% colspan="1" %)
634 +(((
635 +
788 788  )))
789 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
637 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
790 790  (((
791 791  //The script keyword $container.supplyresources now includes reserved wares.//
792 792  )))
793 -|(% colspan="3" %)(% colspan="3" %)
641 +|(% colspan="4" %)(% colspan="4" %)
794 794  (((
795 795  == 2.20 ==
796 796  )))
... ... @@ -803,8 +803,11 @@
803 803  )))|(% colspan="1" %)(% colspan="1" %)
804 804  (((
805 805  **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined.
654 +)))|(% colspan="1" %)(% colspan="1" %)
655 +(((
656 +
806 806  )))
807 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
658 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
808 808  (((
809 809  //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.
810 810  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.//
... ... @@ -821,12 +821,15 @@
821 821  )))|(% colspan="1" %)(% colspan="1" %)
822 822  (((
823 823  Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor'
675 +)))|(% colspan="1" %)(% colspan="1" %)
676 +(((
677 +
824 824  )))
825 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
679 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
826 826  (((
827 827  //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.//
828 828  )))
829 -|(% colspan="3" %)(% colspan="3" %)
683 +|(% colspan="4" %)(% colspan="4" %)
830 830  (((
831 831  == 2.00 ==
832 832  )))
... ... @@ -839,8 +839,11 @@
839 839  )))|(% colspan="1" %)(% colspan="1" %)
840 840  (((
841 841  **<event_build_finished/> **param2 now returns null instead of a construction sequence
696 +)))|(% colspan="1" %)(% colspan="1" %)
697 +(((
698 +
842 842  )))
843 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
700 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
844 844  (((
845 845  //The construction sequence which was finished should now be accessed via the buildtask provided via param3.//
846 846  )))
... ... @@ -853,8 +853,11 @@
853 853  )))|(% colspan="1" %)(% colspan="1" %)
854 854  (((
855 855  **param.boarding.{...}** strength parameters removed
713 +)))|(% colspan="1" %)(% colspan="1" %)
714 +(((
715 +
856 856  )))
857 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
717 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
858 858  (((
859 859  //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.//
860 860  )))
... ... @@ -867,8 +867,11 @@
867 867  )))|(% colspan="1" %)(% colspan="1" %)
868 868  (((
869 869  **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed
730 +)))|(% colspan="1" %)(% colspan="1" %)
731 +(((
732 +
870 870  )))
871 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
734 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
872 872  (((
873 873  //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.//
874 874  )))
... ... @@ -878,8 +878,11 @@
878 878  2.00 Beta 1
879 879  )))|(((
880 880  **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals
744 +)))|(% colspan="1" %)(% colspan="1" %)
745 +(((
746 +
881 881  )))
882 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
748 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
883 883  (((
884 884  //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.//
885 885  )))
... ... @@ -889,8 +889,11 @@
889 889  2.00 Beta 1
890 890  )))|(((
891 891  **FFI: SetFormationShape()** no longer indicates an error upon certain error cases
758 +)))|(% colspan="1" %)(% colspan="1" %)
759 +(((
760 +
892 892  )))
893 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
762 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
894 894  (((
895 895  //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.//
896 896  //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.//
... ... @@ -901,8 +901,11 @@
901 901  2.00 Beta 1
902 902  )))|(((
903 903  **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated.
773 +)))|(% colspan="1" %)(% colspan="1" %)
774 +(((
775 +
904 904  )))
905 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
777 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
906 906  (((
907 907  //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.//
908 908  )))
... ... @@ -912,8 +912,11 @@
912 912  2.00 Beta 1
913 913  )))|(((
914 914  **<event_player_changed_target/>** now fires and returns null if the player deselects a target.
787 +)))|(% colspan="1" %)(% colspan="1" %)
788 +(((
789 +
915 915  )))
916 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
791 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
917 917  (((
918 918  //For prior behavior, check for event.param being non-null.//
919 919  )))
... ... @@ -923,8 +923,11 @@
923 923  2.00 Beta 1
924 924  )))|(((
925 925  **<shoot/>/<shoot_at/>** attribute changes.
801 +)))|(% colspan="1" %)(% colspan="1" %)
802 +(((
803 +
926 926  )))
927 -|(% 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" %)
928 928  (((
929 929  //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.//
930 930  //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.//
... ... @@ -937,9 +937,12 @@
937 937  )))|(((
938 938  2.00 Beta 1
939 939  )))|(((
940 -**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.
818 +**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% class="confluenceTd" %)
819 +)))|(% colspan="1" %)(% colspan="1" %)
820 +(((
821 +
941 941  )))
942 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
823 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
943 943  (((
944 944  //Added possibility to query build tasks of a certain buildmodule.//
945 945  )))
... ... @@ -949,8 +949,11 @@
949 949  2.00 Beta 1
950 950  )))|(((
951 951  **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field.
833 +)))|(% colspan="1" %)(% colspan="1" %)
834 +(((
835 +
952 952  )))
953 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
837 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
954 954  (((
955 955  //Added list of resources a buildmodule needs to build.//
956 956  )))
... ... @@ -960,8 +960,11 @@
960 960  2.00 Beta 1
961 961  )))|(((
962 962  (% 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);" %)
847 +)))|(% colspan="1" %)(% colspan="1" %)
848 +(((
849 +
963 963  )))
964 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
851 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
965 965  (((
966 966  //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.//
967 967  )))
... ... @@ -970,13 +970,16 @@
970 970  )))|(((
971 971  2.00 Beta 1
972 972  )))|(((
973 -**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.
860 +**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" %)
861 +)))|(% colspan="1" %)(% colspan="1" %)
862 +(((
863 +
974 974  )))
975 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
865 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
976 976  (((
977 977  //Changed return value type to const char* to better identify failure reasons in Lua script.//
978 978  )))
979 -|(% colspan="3" %)(% colspan="3" %)
869 +|(% colspan="4" %)(% colspan="4" %)
980 980  (((
981 981  == 1.50 ==
982 982  )))
... ... @@ -985,9 +985,12 @@
985 985  )))|(((
986 986  1.50 Beta 3
987 987  )))|(((
988 -**Lua: GetComponentData() **changed behavior of "docksizes" property.
878 +**Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %)
879 +)))|(% colspan="1" %)(% colspan="1" %)
880 +(((
881 +
989 989  )))
990 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
883 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
991 991  (((
992 992  //The "docksizes" property no longer includes internal ship storage docks.//
993 993  )))
... ... @@ -997,8 +997,11 @@
997 997  1.50 Beta 2
998 998  )))|(((
999 999  **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR).
893 +)))|(% colspan="1" %)(% colspan="1" %)
894 +(((
895 +
1000 1000  )))
1001 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
897 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1002 1002  (((
1003 1003  //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".//
1004 1004  
... ... @@ -1011,9 +1011,12 @@
1011 1011  )))|(((
1012 1012  1.50 Beta 2
1013 1013  )))|(((
1014 -**FFI: UpgradeGroupInfo **datatype was changed.
910 +**FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %)
911 +)))|(% colspan="1" %)(% colspan="1" %)
912 +(((
913 +
1015 1015  )))
1016 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
915 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1017 1017  (((
1018 1018  //Added new "operational" field to retrieve information about number of operational upgrades in a group.//
1019 1019  )))
... ... @@ -1026,8 +1026,11 @@
1026 1026  )))|(% colspan="1" %)(% colspan="1" %)
1027 1027  (((
1028 1028  **FFI: SetGuidance()** removed useinfopoint argument.
928 +)))|(% colspan="1" %)(% colspan="1" %)
929 +(((
930 +
1029 1029  )))
1030 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
932 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1031 1031  (((
1032 1032  //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.
1033 1033  //
... ... @@ -1039,13 +1039,16 @@
1039 1039  )))|(((
1040 1040  1.50 Beta 1
1041 1041  )))|(((
1042 -**FFI: CancelConstruction() **changed its return value.
944 +**FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %)
945 +)))|(% colspan="1" %)(% colspan="1" %)
946 +(((
947 +
1043 1043  )))
1044 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
949 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1045 1045  (((
1046 1046  (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. //
1047 1047  )))
1048 -|(% colspan="3" %)(% colspan="3" %)
953 +|(% colspan="4" %)(% colspan="4" %)
1049 1049  (((
1050 1050  == 1.32 ==
1051 1051  )))
... ... @@ -1055,12 +1055,15 @@
1055 1055  1.32
1056 1056  )))|(((
1057 1057  **Lua: GetComponentData() **removed the "nextdestname" property.
963 +)))|(% colspan="1" %)(% colspan="1" %)
964 +(((
965 +
1058 1058  )))
1059 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
967 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1060 1060  (((
1061 1061  //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.//
1062 1062  )))
1063 -|(% colspan="3" %)(% colspan="3" %)
971 +|(% colspan="4" %)(% colspan="4" %)
1064 1064  (((
1065 1065  == 1.20 ==
1066 1066  )))
... ... @@ -1069,9 +1069,12 @@
1069 1069  )))|(((
1070 1070  1.20
1071 1071  )))|(((
1072 -**FFI: GetAAOption()** got a new "useconfig" parameter.
980 +**FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %)
981 +)))|(% colspan="1" %)(% colspan="1" %)
982 +(((
983 +
1073 1073  )))
1074 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
985 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1075 1075  (((
1076 1076  //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.//
1077 1077  )))
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -141329146
1 +101548190
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/141329146/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/101548190/Breaking Changes