Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 36.1
edited by owen
on 2019/08/26 00:28
Change comment: There is no comment for this version
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.owen
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,8 +137,33 @@
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  (((
185 +UI extensions
186 +)))|(% colspan="1" %)(% colspan="1" %)
187 +(((
188 +3.0 Beta 1
189 +)))|(% colspan="1" %)(% colspan="1" %)
190 +(((
191 +**FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor
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 for a new weapon mod property "SurfaceElementFactor" to allow weapons to deal increased damage to surface elements such as Shield Generators, Turrets or Engines.//
196 +)))
197 +|(% colspan="1" %)(% colspan="1" %)
198 +(((
142 142  Scripts
143 143  )))|(% colspan="1" %)(% colspan="1" %)
144 144  (((
... ... @@ -150,7 +150,7 @@
150 150  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
151 151  (((
152 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.//
210 +//It now returns true if $ware is illegal to any faction in the game.//
154 154  )))
155 155  |(% colspan="1" %)(% colspan="1" %)
156 156  (((
... ... @@ -160,13 +160,11 @@
160 160  3.0 Beta 1
161 161  )))|(% colspan="1" %)(% colspan="1" %)
162 162  (((
163 -'**checkoperational**' filter behaviour changed
220 +MD script **RML_Flight_Along_Path** removed
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.//
224 +//The MD script RML_Flight_Along_Path was not referened and was removed.//
170 170  )))
171 171  |(% colspan="1" %)(% colspan="1" %)
172 172  (((
... ... @@ -176,12 +176,69 @@
176 176  3.0 Beta 1
177 177  )))|(% colspan="1" %)(% colspan="1" %)
178 178  (((
179 -MD script **RML_Flight_Along_Path** removed
234 +parameters of **<event_venture_mission_completed/>** changed
180 180  )))
181 181  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
182 182  (((
183 -//The MD script RML_Flight_Along_Path was not referened and was removed.//
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//
184 184  )))
241 +|(((
242 +Scripts
243 +)))|(((
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 +)))|(((
272 +2.60 Beta 1
273 +)))|(((
274 +'**checkoperational**' filter behaviour changed
275 +)))
276 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
277 +(((
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 +(((
291 +//The script keyword $container.supplyresources now includes reserved wares.//
292 +)))
293 +|(% colspan="3" %)(% colspan="3" %)
294 +(((
295 +== 2.20 ==
296 +)))
185 185  |(% colspan="1" %)(% colspan="1" %)
186 186  (((
187 187  UI core
... ... @@ -214,6 +214,10 @@
214 214  (((
215 215  //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.//
216 216  )))
329 +|(% colspan="3" %)(% colspan="3" %)
330 +(((
331 +== 2.00 ==
332 +)))
217 217  |(% colspan="1" %)(% colspan="1" %)
218 218  (((
219 219  Scripts
... ... @@ -360,6 +360,10 @@
360 360  (((
361 361  //Changed return value type to const char* to better identify failure reasons in Lua script.//
362 362  )))
479 +|(% colspan="3" %)(% colspan="3" %)
480 +(((
481 +== 1.50 ==
482 +)))
363 363  |(((
364 364  UI extensions
365 365  )))|(((
... ... @@ -425,6 +425,10 @@
425 425  (((
426 426  (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. //
427 427  )))
548 +|(% colspan="3" %)(% colspan="3" %)
549 +(((
550 +== 1.32 ==
551 +)))
428 428  |(((
429 429  UI extensions
430 430  )))|(((
... ... @@ -436,6 +436,10 @@
436 436  (((
437 437  //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.//
438 438  )))
563 +|(% colspan="3" %)(% colspan="3" %)
564 +(((
565 +== 1.20 ==
566 +)))
439 439  |(((
440 440  UI extensions
441 441  )))|(((
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -85131856
1 +88345805
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/85131856/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/88345805/Breaking Changes