Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 38.1
edited by nick
on 2019/09/09 13:13
Change comment: added parameters of event_venture_mission_completed changed
To version 44.1
edited by klaus
on 2019/11/18 16:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.nick
1 +xwiki:XWiki.klaus
Content
... ... @@ -25,8 +25,40 @@
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 +|(% colspan="1" %)(% colspan="1" %)
47 +(((
48 +Global
49 +)))|(% colspan="1" %)(% colspan="1" %)
50 +(((
51 +3.0 Beta 1
52 +)))|(% colspan="1" %)(% colspan="1" %)
53 +(((
54 +MissionBoard support dropped
55 +)))
56 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
57 +(((
58 +//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.//
59 +)))
60 +|(% colspan="1" %)(% colspan="1" %)
61 +(((
30 30  Scripts
31 31  )))|(% colspan="1" %)(% colspan="1" %)
32 32  (((
... ... @@ -37,7 +37,7 @@
37 37  )))
38 38  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
39 39  (((
40 -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.
72 +//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.//
41 41  )))
42 42  |(% colspan="1" %)(% colspan="1" %)
43 43  (((
... ... @@ -137,20 +137,30 @@
137 137  (((
138 138  //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.//
139 139  )))
172 +|(((
173 +UI core
174 +)))|(((
175 +3.0 Beta 1
176 +)))|(((
177 +**FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders
178 +)))
179 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
180 +(((
181 +//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.//
182 +)))
140 140  |(% colspan="1" %)(% colspan="1" %)
141 141  (((
142 -Scripts
185 +UI extensions
143 143  )))|(% colspan="1" %)(% colspan="1" %)
144 144  (((
145 145  3.0 Beta 1
146 146  )))|(% colspan="1" %)(% colspan="1" %)
147 147  (((
148 -**$ware.illegal** updated
191 +**FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor
149 149  )))
150 150  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
151 151  (((
152 -//$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.//
153 -\\//It now returns true if $ware is illegal to any faction in the game.//
195 +//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.//
154 154  )))
155 155  |(% colspan="1" %)(% colspan="1" %)
156 156  (((
... ... @@ -160,13 +160,12 @@
160 160  3.0 Beta 1
161 161  )))|(% colspan="1" %)(% colspan="1" %)
162 162  (((
163 -'**checkoperational**' filter behaviour changed
205 +**$ware.illegal** updated
164 164  )))
165 165  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
166 166  (((
167 -//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.//
168 -
169 -//Sub nodes such as match_child will have checkoperational default to false. Existing uses may find that results now include non-operational components.//
209 +//$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.//
210 +//It now returns true if $ware is illegal to any faction in the game.//
170 170  )))
171 171  |(% colspan="1" %)(% colspan="1" %)
172 172  (((
... ... @@ -190,24 +190,69 @@
190 190  3.0 Beta 1
191 191  )))|(% colspan="1" %)(% colspan="1" %)
192 192  (((
193 -parameters of event_venture_mission_completed changed
234 +parameters of **<event_venture_mission_completed/>** changed
194 194  )))
195 195  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
196 196  (((
197 -old params: param = venture details, param2 = ships involved, param3 = duration
198 -new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration
238 +//old params: param = venture details, param2 = ships involved, param3 = duration//
239 +//new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration//
199 199  )))
200 200  |(((
201 201  Scripts
202 202  )))|(((
244 +3.0 Beta 1
245 +)))|(((
246 +**<set_object_wing_name/>** removed,
247 +**<set_object_fleet_name/>** added
248 +)))
249 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
250 +(((
251 +//The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>//
252 +)))
253 +|(((
254 +Scripts
255 +)))|(((
256 +3.0 Beta 1
257 +)))|(((
258 +**$controllable.wing.*** removed,
259 +**$controllable.fleet.*** added
260 +)))
261 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
262 +(((
263 +$controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander
264 +)))
265 +|(% colspan="3" %)(% colspan="3" %)
266 +(((
267 +== 2.60 ==
268 +)))
269 +|(((
270 +Scripts
271 +)))|(((
203 203  2.60 Beta 1
204 204  )))|(((
205 -$container.supplyresources behavior changed
274 +'**checkoperational**' filter behaviour changed
206 206  )))
207 207  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
208 208  (((
278 +//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.//
279 +
280 +//Sub nodes such as match_child will have checkoperational default to false. Existing uses may find that results now include non-operational components.//
281 +)))
282 +|(((
283 +Scripts
284 +)))|(((
285 +2.60 Beta 1
286 +)))|(((
287 +$container.**supplyresources** behavior changed
288 +)))
289 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
290 +(((
209 209  //The script keyword $container.supplyresources now includes reserved wares.//
210 210  )))
293 +|(% colspan="3" %)(% colspan="3" %)
294 +(((
295 +== 2.20 ==
296 +)))
211 211  |(% colspan="1" %)(% colspan="1" %)
212 212  (((
213 213  UI core
... ... @@ -240,6 +240,10 @@
240 240  (((
241 241  //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.//
242 242  )))
329 +|(% colspan="3" %)(% colspan="3" %)
330 +(((
331 +== 2.00 ==
332 +)))
243 243  |(% colspan="1" %)(% colspan="1" %)
244 244  (((
245 245  Scripts
... ... @@ -386,6 +386,10 @@
386 386  (((
387 387  //Changed return value type to const char* to better identify failure reasons in Lua script.//
388 388  )))
479 +|(% colspan="3" %)(% colspan="3" %)
480 +(((
481 +== 1.50 ==
482 +)))
389 389  |(((
390 390  UI extensions
391 391  )))|(((
... ... @@ -451,6 +451,10 @@
451 451  (((
452 452  (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. //
453 453  )))
548 +|(% colspan="3" %)(% colspan="3" %)
549 +(((
550 +== 1.32 ==
551 +)))
454 454  |(((
455 455  UI extensions
456 456  )))|(((
... ... @@ -462,6 +462,10 @@
462 462  (((
463 463  //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.//
464 464  )))
563 +|(% colspan="3" %)(% colspan="3" %)
564 +(((
565 +== 1.20 ==
566 +)))
465 465  |(((
466 466  UI extensions
467 467  )))|(((
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -85622793
1 +88345805
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/85622793/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/88345805/Breaking Changes