Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 23.1
edited by stefan
on 2019/02/08 12:15
Change comment: finished going through list
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.stefan
1 +xwiki:XWiki.owen
Content
... ... @@ -25,6 +25,110 @@
25 25  )))|=(((
26 26  Summary
27 27  )))
28 +|(% colspan="1" %)(% colspan="1" %)
29 +(((
30 +Scripts
31 +)))|(% colspan="1" %)(% colspan="1" %)
32 +(((
33 +3.0 Beta 1
34 +)))|(% colspan="1" %)(% colspan="1" %)
35 +(((
36 +'checkoperational' filter behaviour changed
37 +)))
38 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
39 +(((
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.//
43 +)))
44 +|(% colspan="1" %)(% colspan="1" %)
45 +(((
46 +Scripts
47 +)))|(% colspan="1" %)(% colspan="1" %)
48 +(((
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 +(((
81 +2.20 Beta 3
82 +)))|(% colspan="1" %)(% colspan="1" %)
83 +(((
84 +Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor'
85 +)))
86 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
87 +(((
88 +//The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.//
89 +)))
90 +|(% colspan="1" %)(% colspan="1" %)
91 +(((
92 +Scripts
93 +)))|(% colspan="1" %)(% colspan="1" %)
94 +(((
95 +2.00 Beta 1
96 +)))|(% colspan="1" %)(% colspan="1" %)
97 +(((
98 +**<event_build_finished/> **param2 now returns null instead of a construction sequence
99 +)))
100 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
101 +(((
102 +//The construction sequence which was finished should now be accessed via the buildtask provided via param3.//
103 +)))
104 +|(% colspan="1" %)(% colspan="1" %)
105 +(((
106 +Scripts
107 +)))|(% colspan="1" %)(% colspan="1" %)
108 +(((
109 +2.00 Beta 1
110 +)))|(% colspan="1" %)(% colspan="1" %)
111 +(((
112 +**param.boarding.{...}** strength parameters removed
113 +)))
114 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
115 +(((
116 +//The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.//
117 +)))
118 +|(% colspan="1" %)(% colspan="1" %)
119 +(((
120 +Scripts
121 +)))|(% colspan="1" %)(% colspan="1" %)
122 +(((
123 +2.00 Beta 1
124 +)))|(% colspan="1" %)(% colspan="1" %)
125 +(((
126 +**$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed
127 +)))
128 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
129 +(((
130 +//Due to changes to boarding in X4, the boarding connections accessed by these script properties and actions became redundent and thus, removed. Any connections set by these actions in a savegame will not survive loading.//
131 +)))
28 28  |(((
29 29  UI extensions
30 30  )))|(((
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -79265840
1 +83066959
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/79265840/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/83066959/Breaking Changes