Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 70.1
edited by matthias
on 2020/10/20 08:43
Change comment: Added changed script property
To version 23.1
edited by stefan
on 2019/02/08 12:15
Change comment: finished going through list

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.matthias
1 +xwiki:XWiki.stefan
Content
... ... @@ -24,682 +24,15 @@
24 24  Version
25 25  )))|=(((
26 26  Summary
27 -)))|=(% colspan="1" %)(% colspan="1" %)
28 -(((
29 -
30 30  )))
31 -|(% colspan="4" %)(% colspan="4" %)
32 -(((
33 -== 4.00 ==
34 -)))
35 35  |(((
36 -Parameters
37 -)))|(((
38 -4.00 Beta 1
39 -)))|(((
40 -**requiresconstructionvessel** parameter moved
41 -)))|(((
42 -
43 -)))
44 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
45 -(((
46 -//The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.//
47 -)))
48 -|(((
49 -Scripts
50 -)))|(((
51 -4.00 Beta 1
52 -)))|(((
53 -Changed behaviour of **gatedistance** script property
54 -)))|(((
55 -
56 -)))
57 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
58 -(((
59 -//The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.//
60 -)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %)
61 -(((
62 -
63 -)))
64 -|(% colspan="4" %)(% colspan="4" %)
65 -(((
66 -== 3.30 ==
67 -)))
68 -|(((
69 69  UI extensions
70 70  )))|(((
71 -3.30 Beta 3
72 -)))|(((
73 -**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()**
74 -)))|(% colspan="1" %)(% colspan="1" %)
75 -(((
76 -
77 -)))
78 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
79 -(((
80 -//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()//
81 -)))
82 -|(% colspan="4" %)(% colspan="4" %)
83 -(((
84 -== 3.20 ==
85 -)))
86 -|(((
87 -Scripts
88 -)))|(((
89 -3.20 Beta 1
90 -)))|(((
91 -Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed
92 -)))|(% colspan="1" %)(% colspan="1" %)
93 -(((
94 -
95 -)))
96 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
97 -(((
98 -//Old params: param = attacked object, param2 = attack method, param3 = attacked component//
99 -//New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon]
100 -Note that this also means the component attribute to the events is no longer available, so scripts checking the attacked component need to use event.param3.{1} instead//
101 -)))
102 -|(% colspan="1" %)(% colspan="1" %)
103 -(((
104 -Scripts
105 -)))|(% colspan="1" %)(% colspan="1" %)
106 -(((
107 -3.20 Beta 1
108 -)))|(% colspan="1" %)(% colspan="1" %)
109 -(((
110 -Removed script property $trade.**restriction.faction**
111 -)))|(% colspan="1" %)(% colspan="1" %)
112 -(((
113 -
114 -)))
115 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
116 -(((
117 -//$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.//
118 -)))
119 -|(((
120 -UI extensions
121 -)))|(((
122 -3.20 Beta 1
123 -)))|(((
124 -**Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete!
125 -)))|(% colspan="1" %)(% colspan="1" %)
126 -(((
127 -
128 -)))
129 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
130 -(((
131 -//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.//
132 -)))
133 -|(% colspan="4" %)(% colspan="4" %)
134 -(((
135 -== 3.10 ==
136 -)))
137 -|(% colspan="1" %)(% colspan="1" %)
138 -(((
139 -Scripts
140 -)))|(% colspan="1" %)(% colspan="1" %)
141 -(((
142 -3.10 Beta 1
143 -)))|(% colspan="1" %)(% colspan="1" %)
144 -(((
145 -Removed script action **<add_build/>**
146 -)))|(% colspan="1" %)(% colspan="1" %)
147 -(((
148 -
149 -)))
150 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
151 -(((
152 -//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.//
153 -)))
154 -|(% colspan="4" %)(% colspan="4" %)
155 -(((
156 -== 3.00 ==
157 -)))
158 -|(% colspan="1" %)(% colspan="1" %)
159 -(((
160 -Scripts
161 -)))|(% colspan="1" %)(% colspan="1" %)
162 -(((
163 -3.0 Beta 6
164 -)))|(% colspan="1" %)(% colspan="1" %)
165 -(((
166 -Changed behaviour of script action **<get_suitable_job/>**
167 -)))|(% colspan="1" %)(% colspan="1" %)
168 -(((
169 -
170 -)))
171 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
172 -(((
173 -//<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.//
174 -)))
175 -|(% colspan="1" %)(% colspan="1" %)
176 -(((
177 -Scripts
178 -)))|(% colspan="1" %)(% colspan="1" %)
179 -(((
180 -3.0 Beta 6
181 -)))|(% colspan="1" %)(% colspan="1" %)
182 -(((
183 -Changed behaviour of script action **<get_ware_definition/>**
184 -)))|(% colspan="1" %)(% colspan="1" %)
185 -(((
186 -
187 -)))
188 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
189 -(((
190 -//<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.//
191 -)))
192 -|(% colspan="1" %)(% colspan="1" %)
193 -(((
194 -Global
195 -)))|(% colspan="1" %)(% colspan="1" %)
196 -(((
197 -3.0 Beta 5
198 -)))|(% colspan="1" %)(% colspan="1" %)
199 -(((
200 -Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case
201 -)))|(% colspan="1" %)(% colspan="1" %)
202 -(((
203 -
204 -)))
205 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
206 -(((
207 -//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.)\\
208 -
209 -//Note that this change has no effect on the actual content of scripts or cutscenes. The MD script/cutscene names are stored in the files, regardless of the filenames, so that references to them remain unchanged (e.g., "md.Setup.Start" references a cue in setup.xml).//
210 -)))
211 -|(% colspan="1" %)(% colspan="1" %)
212 -(((
213 -Scripts
214 -)))|(% colspan="1" %)(% colspan="1" %)
215 -(((
216 -3.0 Beta 5
217 -)))|(% colspan="1" %)(% colspan="1" %)
218 -(((
219 -Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions>
220 -)))|(% colspan="1" %)(% colspan="1" %)
221 -(((
222 -
223 -)))
224 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
225 -(((
226 -//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.//
227 -)))
228 -|(% colspan="1" %)(% colspan="1" %)
229 -(((
230 -Scripts
231 -)))|(% colspan="1" %)(% colspan="1" %)
232 -(((
233 -3.0 Beta 5
234 -)))|(% colspan="1" %)(% colspan="1" %)
235 -(((
236 -Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos**
237 -)))|(% colspan="1" %)(% colspan="1" %)
238 -(((
239 -
240 -)))
241 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
242 -(((
243 -//Before the change, positions are relative to $dockingbay.parent.
244 -After the change, positions are relative to $dockingbay as specified in the documentation.//
245 -)))
246 -|(% colspan="1" %)(% colspan="1" %)
247 -(((
248 -Global
249 -)))|(% colspan="1" %)(% colspan="1" %)
250 -(((
251 -3.0 Beta 2
252 -)))|(% colspan="1" %)(% colspan="1" %)
253 -(((
254 -Support for entity flag "**skillsvisible**" dropped
255 -)))|(% colspan="1" %)(% colspan="1" %)
256 -(((
257 -
258 -)))
259 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
260 -(((
261 -//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().//
262 -)))
263 -|(((
264 -Scripts
265 -)))|(((
266 -3.0 Beta 2
267 -)))|(((
268 -Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**.
269 -)))|(% colspan="1" %)(% colspan="1" %)
270 -(((
271 -
272 -)))
273 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
274 -(((
275 -//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.
276 -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.
277 -If in your scripts you make use of the <event_object_changed_owner> condition you need to verify that you indeed want to work with the "effective" component owner or whether your script code actually should work with the true owner of an object and update your code accordingly.
278 -On top of that the 3rd parameter of <event_object_changed_owner> (trueprevious) was dropped as the event is no longer triggered upon a change of the true owner alone (i.e. only if the change of the true owner has also an effect on the "effective" component owner).
279 -)))
280 -|(% colspan="1" %)(% colspan="1" %)
281 -(((
282 -Global
283 -)))|(% colspan="1" %)(% colspan="1" %)
284 -(((
285 -3.0 Beta 1
286 -)))|(% colspan="1" %)(% colspan="1" %)
287 -(((
288 -**MissionBoard** support dropped
289 -)))|(% colspan="1" %)(% colspan="1" %)
290 -(((
291 -
292 -)))
293 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
294 -(((
295 -//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.//
296 -)))
297 -|(((
298 -Job/God
299 -)))|(((
300 -3.0 Beta 1
301 -)))|(((
302 -By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined
303 -)))|(% colspan="1" %)(% colspan="1" %)
304 -(((
305 -
306 -)))
307 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
308 -(((
309 -//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.//
310 -)))
311 -|(% colspan="1" %)(% colspan="1" %)
312 -(((
313 -Scripts
314 -)))|(% colspan="1" %)(% colspan="1" %)
315 -(((
316 -3.0 Beta 1
317 -)))|(% colspan="1" %)(% colspan="1" %)
318 -(((
319 -Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'**
320 -)))|(% colspan="1" %)(% colspan="1" %)
321 -(((
322 -
323 -)))
324 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
325 -(((
326 -//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.//
327 -)))
328 -|(% colspan="1" %)(% colspan="1" %)
329 -(((
330 -Scripts
331 -)))|(% colspan="1" %)(% colspan="1" %)
332 -(((
333 -3.0 Beta 1
334 -)))|(% colspan="1" %)(% colspan="1" %)
335 -(((
336 -Script action **<set_doors_locked/>** attribute **'group'** changed
337 -)))|(% colspan="1" %)(% colspan="1" %)
338 -(((
339 -
340 -)))
341 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
342 -(((
343 -//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.//
344 -)))
345 -|(% colspan="1" %)(% colspan="1" %)
346 -(((
347 -Scripts
348 -)))|(% colspan="1" %)(% colspan="1" %)
349 -(((
350 -3.0 Beta 1
351 -)))|(% colspan="1" %)(% colspan="1" %)
352 -(((
353 -Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed
354 -)))|(% colspan="1" %)(% colspan="1" %)
355 -(((
356 -
357 -)))
358 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
359 -(((
360 -//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.//
361 -)))
362 -|(% colspan="1" %)(% colspan="1" %)
363 -(((
364 -Scripts
365 -)))|(% colspan="1" %)(% colspan="1" %)
366 -(((
367 -3.0 Beta 1
368 -)))|(% colspan="1" %)(% colspan="1" %)
369 -(((
370 -Script actions **<set_hack_target/>** and **<abort_hack/>** removed
371 -)))|(% colspan="1" %)(% colspan="1" %)
372 -(((
373 -
374 -)))
375 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
376 -(((
377 -//These actions had no effect and were removed.//
378 -)))
379 -|(% colspan="1" %)(% colspan="1" %)
380 -(((
381 -Scripts
382 -)))|(% colspan="1" %)(% colspan="1" %)
383 -(((
384 -3.0 Beta 1
385 -)))|(% colspan="1" %)(% colspan="1" %)
386 -(((
387 -**<setup_conversation_minigame/>** script action removed
388 -)))|(% colspan="1" %)(% colspan="1" %)
389 -(((
390 -
391 -)))
392 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
393 -(((
394 -//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.//
395 -)))
396 -|(% colspan="1" %)(% colspan="1" %)
397 -(((
398 -Scripts
399 -)))|(% colspan="1" %)(% colspan="1" %)
400 -(((
401 -3.0 Beta 1
402 -)))|(% colspan="1" %)(% colspan="1" %)
403 -(((
404 -<add_player_choice_*> **confidence** attribute removed
405 -)))|(% colspan="1" %)(% colspan="1" %)
406 -(((
407 -
408 -)))
409 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
410 -(((
411 -//The default confidence of player options is another leftover from the XR era and had no effect in X4.//
412 -)))
413 -|(% colspan="1" %)(% colspan="1" %)
414 -(((
415 -Scripts
416 -)))|(% colspan="1" %)(% colspan="1" %)
417 -(((
418 -3.0 Beta 1
419 -)))|(% colspan="1" %)(% colspan="1" %)
420 -(((
421 -**<hack_via_control_panel/>** script action removed
422 -)))|(% colspan="1" %)(% colspan="1" %)
423 -(((
424 -
425 -)))
426 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
427 -(((
428 -//Unused script action <hack_via_control_panel/> was removed.//
429 -)))
430 -|(% colspan="1" %)(% colspan="1" %)
431 -(((
432 -UI core
433 -)))|(% colspan="1" %)(% colspan="1" %)
434 -(((
435 -3.0 Beta 1
436 -)))|(% colspan="1" %)(% colspan="1" %)
437 -(((
438 -**Lua: **GetMiniGameCursorPosition() removed
439 -)))|(% colspan="1" %)(% colspan="1" %)
440 -(((
441 -
442 -)))
443 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
444 -(((
445 -//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.//
446 -)))
447 -|(((
448 -UI core
449 -)))|(((
450 -3.0 Beta 1
451 -)))|(((
452 -**FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders
453 -)))|(% colspan="1" %)(% colspan="1" %)
454 -(((
455 -
456 -)))
457 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
458 -(((
459 -//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.//
460 -)))
461 -|(% colspan="1" %)(% colspan="1" %)
462 -(((
463 -UI extensions
464 -)))|(% colspan="1" %)(% colspan="1" %)
465 -(((
466 -3.0 Beta 1
467 -)))|(% colspan="1" %)(% colspan="1" %)
468 -(((
469 -**FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor
470 -)))|(% colspan="1" %)(% colspan="1" %)
471 -(((
472 -
473 -)))
474 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
475 -(((
476 -//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.//
477 -)))
478 -|(% colspan="1" %)(% colspan="1" %)
479 -(((
480 -Scripts
481 -)))|(% colspan="1" %)(% colspan="1" %)
482 -(((
483 -3.0 Beta 1
484 -)))|(% colspan="1" %)(% colspan="1" %)
485 -(((
486 -**$ware.illegal** updated
487 -)))|(% colspan="1" %)(% colspan="1" %)
488 -(((
489 -
490 -)))
491 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
492 -(((
493 -//$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.//
494 -//It now returns true if $ware is illegal to any faction in the game.//
495 -)))
496 -|(% colspan="1" %)(% colspan="1" %)
497 -(((
498 -Scripts
499 -)))|(% colspan="1" %)(% colspan="1" %)
500 -(((
501 -3.0 Beta 1
502 -)))|(% colspan="1" %)(% colspan="1" %)
503 -(((
504 -MD script **RML_Flight_Along_Path** removed
505 -)))|(% colspan="1" %)(% colspan="1" %)
506 -(((
507 -
508 -)))
509 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
510 -(((
511 -//The MD script RML_Flight_Along_Path was not referened and was removed.//
512 -)))
513 -|(% colspan="1" %)(% colspan="1" %)
514 -(((
515 -Scripts
516 -)))|(% colspan="1" %)(% colspan="1" %)
517 -(((
518 -3.0 Beta 1
519 -)))|(% colspan="1" %)(% colspan="1" %)
520 -(((
521 -parameters of **<event_venture_mission_completed/>** changed
522 -)))|(% colspan="1" %)(% colspan="1" %)
523 -(((
524 -
525 -)))
526 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
527 -(((
528 -//old params: param = venture details, param2 = ships involved, param3 = duration//
529 -//new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration//
530 -)))
531 -|(((
532 -Scripts
533 -)))|(((
534 -3.0 Beta 1
535 -)))|(((
536 -**<set_object_wing_name/>** removed,
537 -**<set_object_fleet_name/>** added
538 -)))|(% colspan="1" %)(% colspan="1" %)
539 -(((
540 -
541 -)))
542 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
543 -(((
544 -//The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>//
545 -)))
546 -|(((
547 -Scripts
548 -)))|(((
549 -3.0 Beta 1
550 -)))|(((
551 -**$controllable.wing.*** removed,
552 -**$controllable.fleet.*** added
553 -)))|(% colspan="1" %)(% colspan="1" %)
554 -(((
555 -
556 -)))
557 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
558 -(((
559 -$controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander
560 -)))
561 -|(% colspan="4" %)(% colspan="4" %)
562 -(((
563 -== 2.60 ==
564 -)))
565 -|(((
566 -Scripts
567 -)))|(((
568 -2.60 Beta 1
569 -)))|(((
570 -'**checkoperational**' filter behaviour changed
571 -)))|(% colspan="1" %)(% colspan="1" %)
572 -(((
573 -
574 -)))
575 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
576 -(((
577 -//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.//
578 -
579 -//Sub nodes such as match_child will have checkoperational default to false. Existing uses may find that results now include non-operational components.//
580 -)))
581 -|(((
582 -Scripts
583 -)))|(((
584 -2.60 Beta 1
585 -)))|(((
586 -$container.**supplyresources** behavior changed
587 -)))|(% colspan="1" %)(% colspan="1" %)
588 -(((
589 -
590 -)))
591 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
592 -(((
593 -//The script keyword $container.supplyresources now includes reserved wares.//
594 -)))
595 -|(% colspan="4" %)(% colspan="4" %)
596 -(((
597 -== 2.20 ==
598 -)))
599 -|(% colspan="1" %)(% colspan="1" %)
600 -(((
601 -UI core
602 -)))|(% colspan="1" %)(% colspan="1" %)
603 -(((
604 -2.20 Beta 3/4
605 -)))|(% colspan="1" %)(% colspan="1" %)
606 -(((
607 -**Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined.
608 -)))|(% colspan="1" %)(% colspan="1" %)
609 -(((
610 -
611 -)))
612 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
613 -(((
614 -//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.
615 -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.//
616 -
617 -//It's a pending change to ensure that the returned mode is more reasonable in an upcoming patch. So be aware that another breaking change might be introduced at some point.
618 -//
619 -)))
620 -|(% colspan="1" %)(% colspan="1" %)
621 -(((
622 -Scripts
623 -)))|(% colspan="1" %)(% colspan="1" %)
624 -(((
625 -2.20 Beta 3
626 -)))|(% colspan="1" %)(% colspan="1" %)
627 -(((
628 -Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor'
629 -)))|(% colspan="1" %)(% colspan="1" %)
630 -(((
631 -
632 -)))
633 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
634 -(((
635 -//The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.//
636 -)))
637 -|(% colspan="4" %)(% colspan="4" %)
638 -(((
639 -== 2.00 ==
640 -)))
641 -|(% colspan="1" %)(% colspan="1" %)
642 -(((
643 -Scripts
644 -)))|(% colspan="1" %)(% colspan="1" %)
645 -(((
646 646  2.00 Beta 1
647 -)))|(% colspan="1" %)(% colspan="1" %)
648 -(((
649 -**<event_build_finished/> **param2 now returns null instead of a construction sequence
650 -)))|(% colspan="1" %)(% colspan="1" %)
651 -(((
652 -
653 -)))
654 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
655 -(((
656 -//The construction sequence which was finished should now be accessed via the buildtask provided via param3.//
657 -)))
658 -|(% colspan="1" %)(% colspan="1" %)
659 -(((
660 -Scripts
661 -)))|(% colspan="1" %)(% colspan="1" %)
662 -(((
663 -2.00 Beta 1
664 -)))|(% colspan="1" %)(% colspan="1" %)
665 -(((
666 -**param.boarding.{...}** strength parameters removed
667 -)))|(% colspan="1" %)(% colspan="1" %)
668 -(((
669 -
670 -)))
671 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
672 -(((
673 -//The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.//
674 -)))
675 -|(% colspan="1" %)(% colspan="1" %)
676 -(((
677 -Scripts
678 -)))|(% colspan="1" %)(% colspan="1" %)
679 -(((
680 -2.00 Beta 1
681 -)))|(% colspan="1" %)(% colspan="1" %)
682 -(((
683 -**$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed
684 -)))|(% colspan="1" %)(% colspan="1" %)
685 -(((
686 -
687 -)))
688 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
689 -(((
690 -//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.//
691 -)))
692 -|(((
693 -UI extensions
694 694  )))|(((
695 -2.00 Beta 1
696 -)))|(((
697 697  **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals
698 -)))|(% colspan="1" %)(% colspan="1" %)
699 -(((
700 -
701 701  )))
702 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
35 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
703 703  (((
704 704  //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.//
705 705  )))
... ... @@ -709,11 +709,8 @@
709 709  2.00 Beta 1
710 710  )))|(((
711 711  **FFI: SetFormationShape()** no longer indicates an error upon certain error cases
712 -)))|(% colspan="1" %)(% colspan="1" %)
713 -(((
714 -
715 715  )))
716 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
46 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
717 717  (((
718 718  //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.//
719 719  //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.//
... ... @@ -724,11 +724,8 @@
724 724  2.00 Beta 1
725 725  )))|(((
726 726  **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated.
727 -)))|(% colspan="1" %)(% colspan="1" %)
728 -(((
729 -
730 730  )))
731 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
58 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
732 732  (((
733 733  //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.//
734 734  )))
... ... @@ -738,11 +738,8 @@
738 738  2.00 Beta 1
739 739  )))|(((
740 740  **<event_player_changed_target/>** now fires and returns null if the player deselects a target.
741 -)))|(% colspan="1" %)(% colspan="1" %)
742 -(((
743 -
744 744  )))
745 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
69 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
746 746  (((
747 747  //For prior behavior, check for event.param being non-null.//
748 748  )))
... ... @@ -752,11 +752,8 @@
752 752  2.00 Beta 1
753 753  )))|(((
754 754  **<shoot/>/<shoot_at/>** attribute changes.
755 -)))|(% colspan="1" %)(% colspan="1" %)
756 -(((
757 -
758 758  )))
759 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
80 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
760 760  (((
761 761  //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.//
762 762  //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.//
... ... @@ -770,11 +770,8 @@
770 770  2.00 Beta 1
771 771  )))|(((
772 772  **FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% class="confluenceTd" %)
773 -)))|(% colspan="1" %)(% colspan="1" %)
774 -(((
775 -
776 776  )))
777 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
95 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
778 778  (((
779 779  //Added possibility to query build tasks of a certain buildmodule.//
780 780  )))
... ... @@ -784,11 +784,8 @@
784 784  2.00 Beta 1
785 785  )))|(((
786 786  **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field.
787 -)))|(% colspan="1" %)(% colspan="1" %)
788 -(((
789 -
790 790  )))
791 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
106 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
792 792  (((
793 793  //Added list of resources a buildmodule needs to build.//
794 794  )))
... ... @@ -798,11 +798,8 @@
798 798  2.00 Beta 1
799 799  )))|(((
800 800  (% 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);" %)
801 -)))|(% colspan="1" %)(% colspan="1" %)
802 -(((
803 -
804 804  )))
805 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
117 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
806 806  (((
807 807  //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.//
808 808  )))
... ... @@ -812,18 +812,11 @@
812 812  2.00 Beta 1
813 813  )))|(((
814 814  **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" %)
815 -)))|(% colspan="1" %)(% colspan="1" %)
816 -(((
817 -
818 818  )))
819 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
128 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
820 820  (((
821 821  //Changed return value type to const char* to better identify failure reasons in Lua script.//
822 822  )))
823 -|(% colspan="4" %)(% colspan="4" %)
824 -(((
825 -== 1.50 ==
826 -)))
827 827  |(((
828 828  UI extensions
829 829  )))|(((
... ... @@ -830,11 +830,8 @@
830 830  1.50 Beta 3
831 831  )))|(((
832 832  **Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %)
833 -)))|(% colspan="1" %)(% colspan="1" %)
834 -(((
835 -
836 836  )))
837 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
139 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
838 838  (((
839 839  //The "docksizes" property no longer includes internal ship storage docks.//
840 840  )))
... ... @@ -844,11 +844,8 @@
844 844  1.50 Beta 2
845 845  )))|(((
846 846  **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR).
847 -)))|(% colspan="1" %)(% colspan="1" %)
848 -(((
849 -
850 850  )))
851 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
150 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
852 852  (((
853 853  //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".//
854 854  
... ... @@ -862,11 +862,8 @@
862 862  1.50 Beta 2
863 863  )))|(((
864 864  **FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %)
865 -)))|(% colspan="1" %)(% colspan="1" %)
866 -(((
867 -
868 868  )))
869 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
165 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
870 870  (((
871 871  //Added new "operational" field to retrieve information about number of operational upgrades in a group.//
872 872  )))
... ... @@ -879,11 +879,8 @@
879 879  )))|(% colspan="1" %)(% colspan="1" %)
880 880  (((
881 881  **FFI: SetGuidance()** removed useinfopoint argument.
882 -)))|(% colspan="1" %)(% colspan="1" %)
883 -(((
884 -
885 885  )))
886 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
179 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
887 887  (((
888 888  //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.
889 889  //
... ... @@ -896,18 +896,11 @@
896 896  1.50 Beta 1
897 897  )))|(((
898 898  **FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %)
899 -)))|(% colspan="1" %)(% colspan="1" %)
900 -(((
901 -
902 902  )))
903 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
193 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
904 904  (((
905 905  (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. //
906 906  )))
907 -|(% colspan="4" %)(% colspan="4" %)
908 -(((
909 -== 1.32 ==
910 -)))
911 911  |(((
912 912  UI extensions
913 913  )))|(((
... ... @@ -914,18 +914,11 @@
914 914  1.32
915 915  )))|(((
916 916  **Lua: GetComponentData() **removed the "nextdestname" property.
917 -)))|(% colspan="1" %)(% colspan="1" %)
918 -(((
919 -
920 920  )))
921 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
204 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
922 922  (((
923 923  //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.//
924 924  )))
925 -|(% colspan="4" %)(% colspan="4" %)
926 -(((
927 -== 1.20 ==
928 -)))
929 929  |(((
930 930  UI extensions
931 931  )))|(((
... ... @@ -932,11 +932,8 @@
932 932  1.20
933 933  )))|(((
934 934  **FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %)
935 -)))|(% colspan="1" %)(% colspan="1" %)
936 -(((
937 -
938 938  )))
939 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
215 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
940 940  (((
941 941  //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.//
942 942  )))
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -100860788
1 +79265840
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/100860788/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/79265840/Breaking Changes