Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 26.1
edited by florian
on 2019/03/14 11:12
Change comment: There is no comment for this version
To version 29.1
edited by owen
on 2019/05/24 17:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.florian
1 +xwiki:XWiki.owen
Content
... ... @@ -27,17 +27,19 @@
27 27  )))
28 28  |(% colspan="1" %)(% colspan="1" %)
29 29  (((
30 -UI extensions
30 +Scripts
31 31  )))|(% colspan="1" %)(% colspan="1" %)
32 32  (((
33 -2.50 Beta 1
33 +3.0 Beta 1
34 34  )))|(% colspan="1" %)(% colspan="1" %)
35 35  (((
36 -**FFI: GetNumMissingBuildResources() and GetNumMissingLoadoutResources()** got a new "playercase" parameter
36 +'checkoperational' filter behaviour 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 -Added possibility to query only the resources that are missing then queueing new player builds.
40 +//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.//
41 +
42 +//Sub nodes such as match_child will have checkoperational default to false. Existing uses may find that results now include non-operational components.//
41 41  )))
42 42  |(% colspan="1" %)(% colspan="1" %)
43 43  (((
... ... @@ -44,6 +44,38 @@
44 44  Scripts
45 45  )))|(% colspan="1" %)(% colspan="1" %)
46 46  (((
49 +3.0 Beta 1
50 +)))|(% colspan="1" %)(% colspan="1" %)
51 +(((
52 +MD script **RML_Flight_Along_Path** removed
53 +)))
54 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
55 +(((
56 +//The MD script RML_Flight_Along_Path was not referened and was removed.//
57 +)))
58 +|(% colspan="1" %)(% colspan="1" %)
59 +(((
60 +UI core
61 +)))|(% colspan="1" %)(% colspan="1" %)
62 +(((
63 +2.20 Beta 3/4
64 +)))|(% colspan="1" %)(% colspan="1" %)
65 +(((
66 +**Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined.
67 +)))
68 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
69 +(((
70 +//2.20 Beta 3 introduced the new direct mouse steering mode. The mode was however not integrated as a first level mode and hence GetControllerInfo() returned the "gamepad" mode while direct mouse steering was active.
71 +In 2.20 Beta 4 we improved the situation slightly so that a call to GetControllerInfo() will return either "mouseCursor" or "mouseSteering" in any of the 3 mouse modes.//
72 +
73 +//It's a pending change to ensure that the returned mode is more reasonable in an upcoming patch. So be aware that another breaking change might be introduced at some point.
74 +//
75 +)))
76 +|(% colspan="1" %)(% colspan="1" %)
77 +(((
78 +Scripts
79 +)))|(% colspan="1" %)(% colspan="1" %)
80 +(((
47 47  2.20 Beta 3
48 48  )))|(% colspan="1" %)(% colspan="1" %)
49 49  (((
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -80052232
1 +83066959
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/80052232/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/83066959/Breaking Changes