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.florian - Content
-
... ... @@ -30,69 +30,6 @@ 30 30 Scripts 31 31 )))|(% colspan="1" %)(% colspan="1" %) 32 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 96 2.20 Beta 3 97 97 )))|(% colspan="1" %)(% colspan="1" %) 98 98 (((
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 -8 34606751 +80052234 - url
-
... ... @@ -1,1 +1,1 @@ 1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/8 3460675/Breaking Changes1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/80052234/Breaking Changes