Changes for page Breaking Changes

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

From version 37.1
edited by nick
on 2019/09/02 12:03
Change comment: There is no comment for this version
To version 42.1
edited by nick
on 2019/11/05 12:12
Change comment: There is no comment for this version

Summary

Details

Page properties
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  (((
... ... @@ -37,7 +37,7 @@
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 -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.
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.//
41 41  )))
42 42  |(% colspan="1" %)(% colspan="1" %)
43 43  (((
... ... @@ -137,6 +137,17 @@
137 137  (((
138 138  //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.//
139 139  )))
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 +)))
140 140  |(% colspan="1" %)(% colspan="1" %)
141 141  (((
142 142  Scripts
... ... @@ -150,7 +150,7 @@
150 150  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
151 151  (((
152 152  //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.//
153 -\\//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.//
154 154  )))
155 155  |(% colspan="1" %)(% colspan="1" %)
156 156  (((
... ... @@ -160,13 +160,11 @@
160 160  3.0 Beta 1
161 161  )))|(% colspan="1" %)(% colspan="1" %)
162 162  (((
163 -'**checkoperational**' filter behaviour changed
192 +MD script **RML_Flight_Along_Path** removed
164 164  )))
165 165  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
166 166  (((
167 -//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.//
168 -
169 -//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.//
170 170  )))
171 171  |(% colspan="1" %)(% colspan="1" %)
172 172  (((
... ... @@ -176,23 +176,69 @@
176 176  3.0 Beta 1
177 177  )))|(% colspan="1" %)(% colspan="1" %)
178 178  (((
179 -MD script **RML_Flight_Along_Path** removed
206 +parameters of **<event_venture_mission_completed/>** changed
180 180  )))
181 181  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
182 182  (((
183 -//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//
184 184  )))
185 185  |(((
186 186  Scripts
187 187  )))|(((
216 +3.0 Beta 1
217 +)))|(((
218 +**<set_object_wing_name/>** removed,
219 +**<set_object_fleet_name/>** added
220 +)))
221 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
222 +(((
223 +//The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>//
224 +)))
225 +|(((
226 +Scripts
227 +)))|(((
228 +3.0 Beta 1
229 +)))|(((
230 +**$controllable.wing.*** removed,
231 +**$controllable.fleet.*** added
232 +)))
233 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
234 +(((
235 +$controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander
236 +)))
237 +|(% colspan="3" %)(% colspan="3" %)
238 +(((
239 +== 2.60 ==
240 +)))
241 +|(((
242 +Scripts
243 +)))|(((
188 188  2.60 Beta 1
189 189  )))|(((
190 -$container.supplyresources behavior changed
246 +'**checkoperational**' filter behaviour changed
191 191  )))
192 192  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
193 193  (((
250 +//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.//
251 +
252 +//Sub nodes such as match_child will have checkoperational default to false. Existing uses may find that results now include non-operational components.//
253 +)))
254 +|(((
255 +Scripts
256 +)))|(((
257 +2.60 Beta 1
258 +)))|(((
259 +$container.**supplyresources** behavior changed
260 +)))
261 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
262 +(((
194 194  //The script keyword $container.supplyresources now includes reserved wares.//
195 195  )))
265 +|(% colspan="3" %)(% colspan="3" %)
266 +(((
267 +== 2.20 ==
268 +)))
196 196  |(% colspan="1" %)(% colspan="1" %)
197 197  (((
198 198  UI core
... ... @@ -225,6 +225,10 @@
225 225  (((
226 226  //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.//
227 227  )))
301 +|(% colspan="3" %)(% colspan="3" %)
302 +(((
303 +== 2.00 ==
304 +)))
228 228  |(% colspan="1" %)(% colspan="1" %)
229 229  (((
230 230  Scripts
... ... @@ -371,6 +371,10 @@
371 371  (((
372 372  //Changed return value type to const char* to better identify failure reasons in Lua script.//
373 373  )))
451 +|(% colspan="3" %)(% colspan="3" %)
452 +(((
453 +== 1.50 ==
454 +)))
374 374  |(((
375 375  UI extensions
376 376  )))|(((
... ... @@ -436,6 +436,10 @@
436 436  (((
437 437  (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. //
438 438  )))
520 +|(% colspan="3" %)(% colspan="3" %)
521 +(((
522 +== 1.32 ==
523 +)))
439 439  |(((
440 440  UI extensions
441 441  )))|(((
... ... @@ -447,6 +447,10 @@
447 447  (((
448 448  //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.//
449 449  )))
535 +|(% colspan="3" %)(% colspan="3" %)
536 +(((
537 +== 1.20 ==
538 +)))
450 450  |(((
451 451  UI extensions
452 452  )))|(((
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -85132000
1 +87917725
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/85132000/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/87917725/Breaking Changes