Changes for page Breaking Changes
Last modified by Michael Baumgardt on 2026/04/17 12:03
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -xwiki:XWiki. nick1 +xwiki:XWiki.klaus - Content
-
... ... @@ -25,6 +25,10 @@ 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 ((( 30 30 Scripts ... ... @@ -160,13 +160,11 @@ 160 160 3.0 Beta 1 161 161 )))|(% colspan="1" %)(% colspan="1" %) 162 162 ((( 163 - '**checkoperational**'filterbehaviour changed167 +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.// 171 +//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,45 @@ 176 176 3.0 Beta 1 177 177 )))|(% colspan="1" %)(% colspan="1" %) 178 178 ((( 179 - MD script **RML_Flight_Along_Path**removed181 +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.// 185 +//old params: param = venture details, param2 = ships involved, param3 = duration// 186 +//new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration// 184 184 ))) 188 +|(% colspan="3" %)(% colspan="3" %) 189 +((( 190 +== 2.60 == 191 +))) 185 185 |((( 186 186 Scripts 187 187 )))|((( 188 188 2.60 Beta 1 189 189 )))|((( 190 - $container.supplyresourcesbehavior changed197 +'**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 ((( 201 +//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.// 202 + 203 +//Sub nodes such as match_child will have checkoperational default to false. Existing uses may find that results now include non-operational components.// 204 +))) 205 +|((( 206 +Scripts 207 +)))|((( 208 +2.60 Beta 1 209 +)))|((( 210 +$container.**supplyresources** behavior changed 211 +))) 212 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 213 +((( 194 194 //The script keyword $container.supplyresources now includes reserved wares.// 195 195 ))) 216 +|(% colspan="3" %)(% colspan="3" %) 217 +((( 218 +== 2.20 == 219 +))) 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 ))) 252 +|(% colspan="3" %)(% colspan="3" %) 253 +((( 254 +== 2.00 == 255 +))) 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 ))) 402 +|(% colspan="3" %)(% colspan="3" %) 403 +((( 404 +== 1.50 == 405 +))) 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 ))) 471 +|(% colspan="3" %)(% colspan="3" %) 472 +((( 473 +== 1.32 == 474 +))) 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 ))) 486 +|(% colspan="3" %)(% colspan="3" %) 487 +((( 488 +== 1.20 == 489 +))) 450 450 |((( 451 451 UI extensions 452 452 )))|(((
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 -8 51320001 +86048772 - url
-
... ... @@ -1,1 +1,1 @@ 1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/8 5132000/Breaking Changes1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/86048772/Breaking Changes