Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 30.1
edited by nick
on 2019/06/12 12:45
Change comment: documented $ware.illegal change
To version 22.1
edited by stefan
on 2019/02/08 12:09
Change comment: multiple corrections/layout tweaks

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.nick
1 +xwiki:XWiki.stefan
Content
... ... @@ -25,125 +25,6 @@
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 -$ware.illegal updated
37 -)))
38 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
39 -(((
40 -$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.
41 -\\It now returns true if $ware is illegal to any faction in the game.
42 -)))
43 -|(% colspan="1" %)(% colspan="1" %)
44 -(((
45 -Scripts
46 -)))|(% colspan="1" %)(% colspan="1" %)
47 -(((
48 -3.0 Beta 1
49 -)))|(% colspan="1" %)(% colspan="1" %)
50 -(((
51 -'checkoperational' filter behaviour changed
52 -)))
53 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
54 -(((
55 -//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.//
56 -
57 -//Sub nodes such as match_child will have checkoperational default to false. Existing uses may find that results now include non-operational components.//
58 -)))
59 -|(% colspan="1" %)(% colspan="1" %)
60 -(((
61 -Scripts
62 -)))|(% colspan="1" %)(% colspan="1" %)
63 -(((
64 -3.0 Beta 1
65 -)))|(% colspan="1" %)(% colspan="1" %)
66 -(((
67 -MD script **RML_Flight_Along_Path** removed
68 -)))
69 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
70 -(((
71 -//The MD script RML_Flight_Along_Path was not referened and was removed.//
72 -)))
73 -|(% colspan="1" %)(% colspan="1" %)
74 -(((
75 -UI core
76 -)))|(% colspan="1" %)(% colspan="1" %)
77 -(((
78 -2.20 Beta 3/4
79 -)))|(% colspan="1" %)(% colspan="1" %)
80 -(((
81 -**Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined.
82 -)))
83 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
84 -(((
85 -//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.
86 -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.//
87 -
88 -//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.
89 -//
90 -)))
91 -|(% colspan="1" %)(% colspan="1" %)
92 -(((
93 -Scripts
94 -)))|(% colspan="1" %)(% colspan="1" %)
95 -(((
96 -2.20 Beta 3
97 -)))|(% colspan="1" %)(% colspan="1" %)
98 -(((
99 -Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor'
100 -)))
101 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
102 -(((
103 -//The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.//
104 -)))
105 -|(% colspan="1" %)(% colspan="1" %)
106 -(((
107 -Scripts
108 -)))|(% colspan="1" %)(% colspan="1" %)
109 -(((
110 -2.00 Beta 1
111 -)))|(% colspan="1" %)(% colspan="1" %)
112 -(((
113 -**<event_build_finished/> **param2 now returns null instead of a construction sequence
114 -)))
115 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
116 -(((
117 -//The construction sequence which was finished should now be accessed via the buildtask provided via param3.//
118 -)))
119 -|(% colspan="1" %)(% colspan="1" %)
120 -(((
121 -Scripts
122 -)))|(% colspan="1" %)(% colspan="1" %)
123 -(((
124 -2.00 Beta 1
125 -)))|(% colspan="1" %)(% colspan="1" %)
126 -(((
127 -**param.boarding.{...}** strength parameters removed
128 -)))
129 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
130 -(((
131 -//The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.//
132 -)))
133 -|(% colspan="1" %)(% colspan="1" %)
134 -(((
135 -Scripts
136 -)))|(% colspan="1" %)(% colspan="1" %)
137 -(((
138 -2.00 Beta 1
139 -)))|(% colspan="1" %)(% colspan="1" %)
140 -(((
141 -**$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed
142 -)))
143 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
144 -(((
145 -//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.//
146 -)))
147 147  |(((
148 148  UI extensions
149 149  )))|(((
... ... @@ -279,11 +279,11 @@
279 279  )))|(((
280 280  1.50 Beta 2
281 281  )))|(((
282 -**FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %)
163 +**FFI**: Added "**operational**" field to (% style="color: rgb(0,0,0);" %)**UpgradeGroupInfo **struct.
283 283  )))
284 284  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
285 285  (((
286 -//Added new "operational" field to retrieve information about number of operational upgrades in a group.//
167 +//Added information about number of operational upgrades in a group, affected functions: (% style="color: rgb(0,0,0);" %)GetUpgradeGroupInfo().//
287 287  )))
288 288  |(% colspan="1" %)(% colspan="1" %)
289 289  (((
... ... @@ -293,7 +293,7 @@
293 293  1.50 Beta 1
294 294  )))|(% colspan="1" %)(% colspan="1" %)
295 295  (((
296 -**FFI: SetGuidance()** removed useinfopoint argument.
177 +**FFI:** Removed **SetGuidance()** argument useinfopoint.
297 297  )))
298 298  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
299 299  (((
... ... @@ -307,11 +307,11 @@
307 307  )))|(((
308 308  1.50 Beta 1
309 309  )))|(((
310 -**FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %)
191 +**FFI:** Changed return value for (% style="color: rgb(0,0,0);" %)**CancelConstruction()**.
311 311  )))
312 312  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
313 313  (((
314 -(% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. //
195 +(% style="color: rgb(0,0,0);" %)CancelConstruction() now returns if the cancellation was successful.
315 315  )))
316 316  |(((
317 317  UI extensions
... ... @@ -318,11 +318,11 @@
318 318  )))|(((
319 319  1.32
320 320  )))|(((
321 -**Lua: GetComponentData() **removed the "nextdestname" property.
202 +**Lua:** Removed **GetComponentData()** property "**nextdestname**".
322 322  )))
323 323  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
324 324  (((
325 -//Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.//
206 +//Instead of "nextdestname", use the GetComponentData() properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.//
326 326  )))
327 327  |(((
328 328  UI extensions
... ... @@ -329,9 +329,9 @@
329 329  )))|(((
330 330  1.20
331 331  )))|(((
332 -**FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %)
213 +**FFI**: Added "**useconfig**" parameter to (% style="color: rgb(0,0,0);" %)**GetAAOption()**.
333 333  )))
334 334  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
335 335  (((
336 -//The AA setting was changed to check the new setting with the user. In order to restore the old setting (% style="color: rgb(0,0,0);" %)GetAAOption() gets the option to retrieve the config settings.//
217 +//The AA setting was changed to check the new setting with the user. In order to restore the old setting (% style="color: rgb(0,0,0);" %)**GetAAOption() **gets the option to retrieve the config settings.//
337 337  )))
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -83460675
1 +78578533
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/83460675/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/78578533/Breaking Changes