Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 34.1
edited by klaus
on 2019/06/28 12:10
Change comment: Removed script features related to minigame and hacking
To version 45.1
edited by stefan
on 2019/11/19 20:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.klaus
1 +xwiki:XWiki.stefan
Content
... ... @@ -25,14 +25,88 @@
25 25  )))|=(((
26 26  Summary
27 27  )))
28 +|(% colspan="3" %)(% colspan="3" %)
29 +(((
30 +== 3.00 ==
31 +)))
28 28  |(% colspan="1" %)(% colspan="1" %)
29 29  (((
34 +Global
35 +)))|(% colspan="1" %)(% colspan="1" %)
36 +(((
37 +3.0 Beta 2
38 +)))|(% colspan="1" %)(% colspan="1" %)
39 +(((
40 +Support for entity flag "**skillsvisible**" dropped
41 +)))
42 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
43 +(((
44 +//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().//
45 +)))
46 +|(((
30 30  Scripts
48 +)))|(((
49 +3.0 Beta 2
50 +)))|(((
51 +Changes to **<event_changed_owner>** and added **<event_changed_true_owner>**.
52 +)))
53 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
54 +(((
55 +//Before 3.0 Beta 2 there was just a single event_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.
56 +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_changed_true_owner was introduced.
57 +If in your scripts you make use of the event_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.
58 +On top of that the 3rd-parameter of the event_changed_owner (oldtrueowner) 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).//
59 +)))
60 +|(% colspan="1" %)(% colspan="1" %)
61 +(((
62 +Global
31 31  )))|(% colspan="1" %)(% colspan="1" %)
32 32  (((
33 33  3.0 Beta 1
34 34  )))|(% colspan="1" %)(% colspan="1" %)
35 35  (((
68 +MissionBoard support dropped
69 +)))
70 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
71 +(((
72 +//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 behavior would occur. Therefore we cleaned things up in 3.0 Beta 1 including deprecating/removing any related UI/script function.//
73 +)))
74 +|(% colspan="1" %)(% colspan="1" %)
75 +(((
76 +Scripts
77 +)))|(% colspan="1" %)(% colspan="1" %)
78 +(((
79 +3.0 Beta 1
80 +)))|(% colspan="1" %)(% colspan="1" %)
81 +(((
82 +Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'**
83 +)))
84 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
85 +(((
86 +//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.//
87 +)))
88 +|(% colspan="1" %)(% colspan="1" %)
89 +(((
90 +Scripts
91 +)))|(% colspan="1" %)(% colspan="1" %)
92 +(((
93 +3.0 Beta 1
94 +)))|(% colspan="1" %)(% colspan="1" %)
95 +(((
96 +Script action **<set_doors_locked/>** attribute **'group'** changed
97 +)))
98 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
99 +(((
100 +//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.//
101 +)))
102 +|(% colspan="1" %)(% colspan="1" %)
103 +(((
104 +Scripts
105 +)))|(% colspan="1" %)(% colspan="1" %)
106 +(((
107 +3.0 Beta 1
108 +)))|(% colspan="1" %)(% colspan="1" %)
109 +(((
36 36  Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed
37 37  )))
38 38  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
... ... @@ -109,8 +109,33 @@
109 109  (((
110 110  //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.//
111 111  )))
186 +|(((
187 +UI core
188 +)))|(((
189 +3.0 Beta 1
190 +)))|(((
191 +**FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders
192 +)))
193 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
194 +(((
195 +//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.//
196 +)))
112 112  |(% colspan="1" %)(% colspan="1" %)
113 113  (((
199 +UI extensions
200 +)))|(% colspan="1" %)(% colspan="1" %)
201 +(((
202 +3.0 Beta 1
203 +)))|(% colspan="1" %)(% colspan="1" %)
204 +(((
205 +**FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor
206 +)))
207 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
208 +(((
209 +//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.//
210 +)))
211 +|(% colspan="1" %)(% colspan="1" %)
212 +(((
114 114  Scripts
115 115  )))|(% colspan="1" %)(% colspan="1" %)
116 116  (((
... ... @@ -122,7 +122,7 @@
122 122  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
123 123  (((
124 124  //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.//
125 -\\//It now returns true if $ware is illegal to any faction in the game.//
224 +//It now returns true if $ware is illegal to any faction in the game.//
126 126  )))
127 127  |(% colspan="1" %)(% colspan="1" %)
128 128  (((
... ... @@ -132,13 +132,11 @@
132 132  3.0 Beta 1
133 133  )))|(% colspan="1" %)(% colspan="1" %)
134 134  (((
135 -'**checkoperational**' filter behaviour changed
234 +MD script **RML_Flight_Along_Path** removed
136 136  )))
137 137  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
138 138  (((
139 -//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.//
140 -
141 -//Sub nodes such as match_child will have checkoperational default to false. Existing uses may find that results now include non-operational components.//
238 +//The MD script RML_Flight_Along_Path was not referened and was removed.//
142 142  )))
143 143  |(% colspan="1" %)(% colspan="1" %)
144 144  (((
... ... @@ -148,12 +148,69 @@
148 148  3.0 Beta 1
149 149  )))|(% colspan="1" %)(% colspan="1" %)
150 150  (((
151 -MD script **RML_Flight_Along_Path** removed
248 +parameters of **<event_venture_mission_completed/>** changed
152 152  )))
153 153  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
154 154  (((
155 -//The MD script RML_Flight_Along_Path was not referened and was removed.//
252 +//old params: param = venture details, param2 = ships involved, param3 = duration//
253 +//new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration//
156 156  )))
255 +|(((
256 +Scripts
257 +)))|(((
258 +3.0 Beta 1
259 +)))|(((
260 +**<set_object_wing_name/>** removed,
261 +**<set_object_fleet_name/>** added
262 +)))
263 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
264 +(((
265 +//The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>//
266 +)))
267 +|(((
268 +Scripts
269 +)))|(((
270 +3.0 Beta 1
271 +)))|(((
272 +**$controllable.wing.*** removed,
273 +**$controllable.fleet.*** added
274 +)))
275 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
276 +(((
277 +$controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander
278 +)))
279 +|(% colspan="3" %)(% colspan="3" %)
280 +(((
281 +== 2.60 ==
282 +)))
283 +|(((
284 +Scripts
285 +)))|(((
286 +2.60 Beta 1
287 +)))|(((
288 +'**checkoperational**' filter behaviour changed
289 +)))
290 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
291 +(((
292 +//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.//
293 +
294 +//Sub nodes such as match_child will have checkoperational default to false. Existing uses may find that results now include non-operational components.//
295 +)))
296 +|(((
297 +Scripts
298 +)))|(((
299 +2.60 Beta 1
300 +)))|(((
301 +$container.**supplyresources** behavior changed
302 +)))
303 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
304 +(((
305 +//The script keyword $container.supplyresources now includes reserved wares.//
306 +)))
307 +|(% colspan="3" %)(% colspan="3" %)
308 +(((
309 +== 2.20 ==
310 +)))
157 157  |(% colspan="1" %)(% colspan="1" %)
158 158  (((
159 159  UI core
... ... @@ -186,6 +186,10 @@
186 186  (((
187 187  //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.//
188 188  )))
343 +|(% colspan="3" %)(% colspan="3" %)
344 +(((
345 +== 2.00 ==
346 +)))
189 189  |(% colspan="1" %)(% colspan="1" %)
190 190  (((
191 191  Scripts
... ... @@ -332,6 +332,10 @@
332 332  (((
333 333  //Changed return value type to const char* to better identify failure reasons in Lua script.//
334 334  )))
493 +|(% colspan="3" %)(% colspan="3" %)
494 +(((
495 +== 1.50 ==
496 +)))
335 335  |(((
336 336  UI extensions
337 337  )))|(((
... ... @@ -397,6 +397,10 @@
397 397  (((
398 398  (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. //
399 399  )))
562 +|(% colspan="3" %)(% colspan="3" %)
563 +(((
564 +== 1.32 ==
565 +)))
400 400  |(((
401 401  UI extensions
402 402  )))|(((
... ... @@ -408,6 +408,10 @@
408 408  (((
409 409  //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.//
410 410  )))
577 +|(% colspan="3" %)(% colspan="3" %)
578 +(((
579 +== 1.20 ==
580 +)))
411 411  |(((
412 412  UI extensions
413 413  )))|(((
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -85131350
1 +88346129
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/85131350/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/88346129/Breaking Changes