Skip to Content

Changes for page Breaking Changes

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

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.stefan
1 +xwiki:XWiki.owen
Content
... ... @@ -25,26 +25,8 @@
25 25  )))|=(((
26 26  Summary
27 27  )))
28 -|(% colspan="3" %)(% colspan="3" %)
29 -(((
30 -== 3.00 ==
31 -)))
32 32  |(% colspan="1" %)(% colspan="1" %)
33 33  (((
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 -(((
48 48  Scripts
49 49  )))|(% colspan="1" %)(% colspan="1" %)
50 50  (((
... ... @@ -51,25 +51,11 @@
51 51  3.0 Beta 1
52 52  )))|(% colspan="1" %)(% colspan="1" %)
53 53  (((
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 -(((
68 68  Script action **<set_doors_locked/>** attribute **'group'** changed
69 69  )))
70 70  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
71 71  (((
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.//
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.
73 73  )))
74 74  |(% colspan="1" %)(% colspan="1" %)
75 75  (((
... ... @@ -155,17 +155,6 @@
155 155  (((
156 156  //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.//
157 157  )))
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 -)))
169 169  |(% colspan="1" %)(% colspan="1" %)
170 170  (((
171 171  Scripts
... ... @@ -179,7 +179,7 @@
179 179  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
180 180  (((
181 181  //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.//
182 -//It now returns true if $ware is illegal to any faction in the game.//
139 +\\//It now returns true if $ware is illegal to any faction in the game.//
183 183  )))
184 184  |(% colspan="1" %)(% colspan="1" %)
185 185  (((
... ... @@ -189,11 +189,13 @@
189 189  3.0 Beta 1
190 190  )))|(% colspan="1" %)(% colspan="1" %)
191 191  (((
192 -MD script **RML_Flight_Along_Path** removed
149 +'**checkoperational**' filter behaviour changed
193 193  )))
194 194  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
195 195  (((
196 -//The MD script RML_Flight_Along_Path was not referened and was removed.//
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.//
197 197  )))
198 198  |(% colspan="1" %)(% colspan="1" %)
199 199  (((
... ... @@ -203,45 +203,12 @@
203 203  3.0 Beta 1
204 204  )))|(% colspan="1" %)(% colspan="1" %)
205 205  (((
206 -parameters of **<event_venture_mission_completed/>** changed
165 +MD script **RML_Flight_Along_Path** removed
207 207  )))
208 208  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
209 209  (((
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//
169 +//The MD script RML_Flight_Along_Path was not referened and was removed.//
212 212  )))
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 -)))
245 245  |(% colspan="1" %)(% colspan="1" %)
246 246  (((
247 247  UI core
... ... @@ -274,10 +274,6 @@
274 274  (((
275 275  //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.//
276 276  )))
277 -|(% colspan="3" %)(% colspan="3" %)
278 -(((
279 -== 2.00 ==
280 -)))
281 281  |(% colspan="1" %)(% colspan="1" %)
282 282  (((
283 283  Scripts
... ... @@ -424,10 +424,6 @@
424 424  (((
425 425  //Changed return value type to const char* to better identify failure reasons in Lua script.//
426 426  )))
427 -|(% colspan="3" %)(% colspan="3" %)
428 -(((
429 -== 1.50 ==
430 -)))
431 431  |(((
432 432  UI extensions
433 433  )))|(((
... ... @@ -493,10 +493,6 @@
493 493  (((
494 494  (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. //
495 495  )))
496 -|(% colspan="3" %)(% colspan="3" %)
497 -(((
498 -== 1.32 ==
499 -)))
500 500  |(((
501 501  UI extensions
502 502  )))|(((
... ... @@ -508,10 +508,6 @@
508 508  (((
509 509  //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.//
510 510  )))
511 -|(% colspan="3" %)(% colspan="3" %)
512 -(((
513 -== 1.20 ==
514 -)))
515 515  |(((
516 516  UI extensions
517 517  )))|(((
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -87916742
1 +85131714
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/87916742/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/85131714/Breaking Changes