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.k laus1 +xwiki:XWiki.nick - Content
-
... ... @@ -25,10 +25,6 @@ 25 25 )))|=((( 26 26 Summary 27 27 ))) 28 -|(% colspan="3" %)(% colspan="3" %) 29 -((( 30 -== 3.00 == 31 -))) 32 32 |(% colspan="1" %)(% colspan="1" %) 33 33 ((( 34 34 Scripts ... ... @@ -164,11 +164,13 @@ 164 164 3.0 Beta 1 165 165 )))|(% colspan="1" %)(% colspan="1" %) 166 166 ((( 167 - MD script**RML_Flight_Along_Path** removed163 +'**checkoperational**' filter behaviour changed 168 168 ))) 169 169 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 170 170 ((( 171 -//The MD script RML_Flight_Along_Path was not referened and was removed.// 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.// 172 172 ))) 173 173 |(% colspan="1" %)(% colspan="1" %) 174 174 ((( ... ... @@ -178,45 +178,23 @@ 178 178 3.0 Beta 1 179 179 )))|(% colspan="1" %)(% colspan="1" %) 180 180 ((( 181 - parametersof**<event_venture_mission_completed/>**changed179 +MD script **RML_Flight_Along_Path** removed 182 182 ))) 183 183 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 184 184 ((( 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// 183 +//The MD script RML_Flight_Along_Path was not referened and was removed.// 187 187 ))) 188 -|(% colspan="3" %)(% colspan="3" %) 189 -((( 190 -== 2.60 == 191 -))) 192 192 |((( 193 193 Scripts 194 194 )))|((( 195 195 2.60 Beta 1 196 196 )))|((( 197 - '**checkoperational**' filter behaviour changed190 +$container.supplyresources behavior changed 198 198 ))) 199 199 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 200 200 ((( 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 -((( 214 214 //The script keyword $container.supplyresources now includes reserved wares.// 215 215 ))) 216 -|(% colspan="3" %)(% colspan="3" %) 217 -((( 218 -== 2.20 == 219 -))) 220 220 |(% colspan="1" %)(% colspan="1" %) 221 221 ((( 222 222 UI core ... ... @@ -249,10 +249,6 @@ 249 249 ((( 250 250 //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.// 251 251 ))) 252 -|(% colspan="3" %)(% colspan="3" %) 253 -((( 254 -== 2.00 == 255 -))) 256 256 |(% colspan="1" %)(% colspan="1" %) 257 257 ((( 258 258 Scripts ... ... @@ -399,10 +399,6 @@ 399 399 ((( 400 400 //Changed return value type to const char* to better identify failure reasons in Lua script.// 401 401 ))) 402 -|(% colspan="3" %)(% colspan="3" %) 403 -((( 404 -== 1.50 == 405 -))) 406 406 |((( 407 407 UI extensions 408 408 )))|((( ... ... @@ -468,10 +468,6 @@ 468 468 ((( 469 469 (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. // 470 470 ))) 471 -|(% colspan="3" %)(% colspan="3" %) 472 -((( 473 -== 1.32 == 474 -))) 475 475 |((( 476 476 UI extensions 477 477 )))|((( ... ... @@ -483,10 +483,6 @@ 483 483 ((( 484 484 //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.// 485 485 ))) 486 -|(% colspan="3" %)(% colspan="3" %) 487 -((( 488 -== 1.20 == 489 -))) 490 490 |((( 491 491 UI extensions 492 492 )))|(((
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 -8 60487721 +85132000 - url
-
... ... @@ -1,1 +1,1 @@ 1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/8 6048772/Breaking Changes1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/85132000/Breaking Changes