Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03

From version 35.1
edited by owen
on 2019/08/15 17:14
Change comment: There is no comment for this version
To version 41.1
edited by stefan
on 2019/10/07 18:29
Change comment: added mission board case

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.owen
1 +xwiki:XWiki.stefan
Content
... ... @@ -25,8 +25,26 @@
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 1
38 +)))|(% colspan="1" %)(% colspan="1" %)
39 +(((
40 +MissionBoard support dropped.
41 +)))
42 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
43 +(((
44 +//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.//
45 +)))
46 +|(% colspan="1" %)(% colspan="1" %)
47 +(((
30 30  Scripts
31 31  )))|(% colspan="1" %)(% colspan="1" %)
32 32  (((
... ... @@ -33,11 +33,25 @@
33 33  3.0 Beta 1
34 34  )))|(% colspan="1" %)(% colspan="1" %)
35 35  (((
54 +Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'**
55 +)))
56 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
57 +(((
58 +//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.//
59 +)))
60 +|(% colspan="1" %)(% colspan="1" %)
61 +(((
62 +Scripts
63 +)))|(% colspan="1" %)(% colspan="1" %)
64 +(((
65 +3.0 Beta 1
66 +)))|(% colspan="1" %)(% colspan="1" %)
67 +(((
36 36  Script action **<set_doors_locked/>** attribute **'group'** changed
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 -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.
72 +//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.//
41 41  )))
42 42  |(% colspan="1" %)(% colspan="1" %)
43 43  (((
... ... @@ -123,6 +123,17 @@
123 123  (((
124 124  //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.//
125 125  )))
158 +|(((
159 +UI core
160 +)))|(((
161 +3.0 Beta 1
162 +)))|(((
163 +**FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders
164 +)))
165 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
166 +(((
167 +//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.//
168 +)))
126 126  |(% colspan="1" %)(% colspan="1" %)
127 127  (((
128 128  Scripts
... ... @@ -136,7 +136,7 @@
136 136  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
137 137  (((
138 138  //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.//
139 -\\//It now returns true if $ware is illegal to any faction in the game.//
182 +//It now returns true if $ware is illegal to any faction in the game.//
140 140  )))
141 141  |(% colspan="1" %)(% colspan="1" %)
142 142  (((
... ... @@ -146,13 +146,11 @@
146 146  3.0 Beta 1
147 147  )))|(% colspan="1" %)(% colspan="1" %)
148 148  (((
149 -'**checkoperational**' filter behaviour changed
192 +MD script **RML_Flight_Along_Path** removed
150 150  )))
151 151  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
152 152  (((
153 -//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.//
154 -
155 -//Sub nodes such as match_child will have checkoperational default to false. Existing uses may find that results now include non-operational components.//
196 +//The MD script RML_Flight_Along_Path was not referened and was removed.//
156 156  )))
157 157  |(% colspan="1" %)(% colspan="1" %)
158 158  (((
... ... @@ -162,12 +162,45 @@
162 162  3.0 Beta 1
163 163  )))|(% colspan="1" %)(% colspan="1" %)
164 164  (((
165 -MD script **RML_Flight_Along_Path** removed
206 +parameters of **<event_venture_mission_completed/>** changed
166 166  )))
167 167  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
168 168  (((
169 -//The MD script RML_Flight_Along_Path was not referened and was removed.//
210 +//old params: param = venture details, param2 = ships involved, param3 = duration//
211 +//new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration//
170 170  )))
213 +|(% colspan="3" %)(% colspan="3" %)
214 +(((
215 +== 2.60 ==
216 +)))
217 +|(((
218 +Scripts
219 +)))|(((
220 +2.60 Beta 1
221 +)))|(((
222 +'**checkoperational**' filter behaviour changed
223 +)))
224 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
225 +(((
226 +//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.//
227 +
228 +//Sub nodes such as match_child will have checkoperational default to false. Existing uses may find that results now include non-operational components.//
229 +)))
230 +|(((
231 +Scripts
232 +)))|(((
233 +2.60 Beta 1
234 +)))|(((
235 +$container.**supplyresources** behavior changed
236 +)))
237 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
238 +(((
239 +//The script keyword $container.supplyresources now includes reserved wares.//
240 +)))
241 +|(% colspan="3" %)(% colspan="3" %)
242 +(((
243 +== 2.20 ==
244 +)))
171 171  |(% colspan="1" %)(% colspan="1" %)
172 172  (((
173 173  UI core
... ... @@ -200,6 +200,10 @@
200 200  (((
201 201  //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.//
202 202  )))
277 +|(% colspan="3" %)(% colspan="3" %)
278 +(((
279 +== 2.00 ==
280 +)))
203 203  |(% colspan="1" %)(% colspan="1" %)
204 204  (((
205 205  Scripts
... ... @@ -346,6 +346,10 @@
346 346  (((
347 347  //Changed return value type to const char* to better identify failure reasons in Lua script.//
348 348  )))
427 +|(% colspan="3" %)(% colspan="3" %)
428 +(((
429 +== 1.50 ==
430 +)))
349 349  |(((
350 350  UI extensions
351 351  )))|(((
... ... @@ -411,6 +411,10 @@
411 411  (((
412 412  (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. //
413 413  )))
496 +|(% colspan="3" %)(% colspan="3" %)
497 +(((
498 +== 1.32 ==
499 +)))
414 414  |(((
415 415  UI extensions
416 416  )))|(((
... ... @@ -422,6 +422,10 @@
422 422  (((
423 423  //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.//
424 424  )))
511 +|(% colspan="3" %)(% colspan="3" %)
512 +(((
513 +== 1.20 ==
514 +)))
425 425  |(((
426 426  UI extensions
427 427  )))|(((
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -85131714
1 +87916742
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/85131714/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/87916742/Breaking Changes