Changes for page Breaking Changes
Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 98.1
edited by klaus
on 2023/01/06 16:59
on 2023/01/06 16:59
Change comment:
There is no comment for this version
To version 108.1
edited by Florian Lütkecosmann
on 2023/11/22 13:55
on 2023/11/22 13:55
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Parent
-
... ... @@ -1,0 +1,1 @@ 1 +X4 Foundations Wiki.Modding Support.WebHome - Author
-
... ... @@ -1,1 +1,1 @@ 1 -xwiki:XWiki. klaus1 +xwiki:XWiki.Florian - Content
-
... ... @@ -4,13 +4,13 @@ 4 4 The following table provides an overview about all breaking changes. This should help you to make any necessary changes to restore compatibility of older mods with new versions of X4. 5 5 Feel free to drop a note if a certain breaking change is breaking your mod and you have difficulties finding a way to work around the issue. 6 6 7 -{{no te}}8 -The list of breaking changes does 7 +{{info}} 8 +⚠ The list of breaking changes does **NOT** cover changes in the provided/shipped scripts (for instance UI scripts like the ones located under ui/addons/XXX or ui/core/Lua). These scripts can change anytime without explicit notice. If you hook into one of these scripts or provide replacements for these, please check the script for possible breaking changes yourself. 9 9 10 10 Further note that the list provides information about breaking changes which are in the pipeline of being released. This is meant merely as an informational heads up. Neither do mistake this as an announcement of that version becoming available soon nor take it for granted that such a change will go live. Any information provided for not yet released versions can change (and even be removed) prior to such version having seen the light of day. 11 11 12 12 As a final note, please be aware that issues introduced during the beta phase might not be explicitly mentioned in the list below, if things would only be broken in-between two beta versions. While we still aim to document any (potential) breaking change here, there might be circumstances for which we divert from that procedure (especially in case of only minor issues which are considered merely bugfixes rather than an intended behavior change). 13 -{{/no te}}13 +{{/info}} 14 14 15 15 {{warning title="UI modding considered unstable until further notice..."}} 16 16 Please note that UI modding must be considered **unstable** in the current version. While we are working hard to get the UI modding integration into a stable state, we might have to introduce larger backwards incompatibilities in the following patches. This means that you might have to modify any mod using UI modding capabilities to a larger extend to keep it compatible with certain patches. Still, we are doing our best not to unnecessarily break things for modders and certainly will announce such changes on this page here. ... ... @@ -23,21 +23,114 @@ 23 23 Type 24 24 )))|=((( 25 25 Version 26 -)))|=((( 26 +)))|=(% colspan="2" %)((( 27 27 Summary 28 28 ))) 29 -|(% colspan="3" %)(% colspan="3" %) 29 +|(% colspan="4" %)((( 30 +== 7.00 == 31 +))) 32 +|(% colspan="1" %)(% colspan="1" %) 30 30 ((( 34 +UI extensions 35 +)))|(% colspan="1" %)(% colspan="1" %) 36 +((( 37 +7.00 Beta 1 38 +)))|(% colspan="2" %)(% colspan="1" %) 39 +((( 40 +**FFI**: RemoveBuildPlot() changed 41 +))) 42 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 43 +((( 44 +// The build plot's buildstorage is no longer removed implicitly. The buildstorage will instead be cleaned-up once it is empty and no ships are docked. 45 +))) 46 +|(% colspan="4" %)(% colspan="3" %) 47 +((( 31 31 == 6.00 == 32 32 ))) 33 33 |((( 34 - Assets51 +Libraries 35 35 )))|((( 53 +6.00 Beta 7 54 +)))|(% colspan="2" %)((( 55 +Updated weights for ship groups in shipgroups.xml libraries of base game and all DLCs. 56 +))) 57 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 58 +((( 59 +//Previously some entries were lacking "weight" parameter, causing it to default to "1", which prevent adding new ships to the group with appropriate/configurable granularity.// 60 + 61 +//All groups should now have "weight" parameter added and old "weights" were updated to not have single-digit numbers.// 62 +))) 63 +|(% colspan="1" %)(% colspan="1" %) 64 +((( 65 +Scripts 66 +)))|(% colspan="1" %)(% colspan="1" %) 67 +((( 68 +6.00 Beta 4 69 +)))|(% colspan="2" %)(% colspan="1" %) 70 +((( 71 +Changed conditions for **<event_player_travelmode_started> <event_player_travelmode_stopped> <event_player_travelmode_charge_started> <event_player_travelmode_charge_aborted>** to be raised. 72 +))) 73 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 74 +((( 75 +//The <event_player_travelmode_started>, <event_player_travelmode_stopped>, <event_player_travelmode_charge_started> and <event_player_travelmode_charge_aborted> events will no longer be raised if the player is a passenger on board a ship which enters or leaves travel mode. Previously these events would be raised whether the player was the pilot or a passenger. // 76 + 77 +//Scripts that need to check whether the player exits travel mode may also need to consider checking whether the player leaves the control seat using <event_player_stopped_control> since this will also result in travel mode stopping.// 78 +))) 79 +|(% colspan="1" %)(% colspan="1" %) 80 +((( 81 +Scripts 82 +)))|(% colspan="1" %)(% colspan="1" %) 83 +((( 84 +6.00 Beta 3 85 +)))|(% colspan="2" %)(% colspan="1" %) 86 +((( 87 +Changed result of **<find_object_surface>** action in the case of a failure 88 +))) 89 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 90 +((( 91 +//The 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.// 92 + 93 +//Previously, it returned null only if there was a physics error. It however returned a valid, somewhat-random, position if physics were fine but it was still unable to find a suitable surface position. This position was often unsuitable to use for gameplay purposes so it is now null so the caller can handle the situation.// 94 + 95 +//The action itself has been improved to increase the chance of finding suitable surface positions.// 96 +))) 97 +|(% colspan="1" %)(% colspan="1" %) 98 +((( 99 +Scripts 100 +)))|(% colspan="1" %)(% colspan="1" %) 101 +((( 36 36 6.00 Beta 1 103 +)))|(% colspan="2" %)(% colspan="1" %) 104 +((( 105 +Behaviour change for **<match_dock>** script component filter 106 +))) 107 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 108 +((( 109 +//<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes. 110 +This has introduced a new potential pitfall: If finding or counting contained components be wary that there may be multiple positive results, even if there is only one dockingbay. e.g. matching contents for a station will include the dockingbay but also its containing walkable module as that also contains the dockingbay. To only account for docking bays, also filter by dockingbay class.// 111 +))) 112 +|(% colspan="1" %)(% colspan="1" %) 113 +((( 114 +Scripts 115 +)))|(% colspan="1" %)(% colspan="1" %) 116 +((( 117 +6.00 Beta 1 118 +)))|(% colspan="2" %)(% colspan="1" %) 119 +((( 120 +Changed result attribute location for **<get_attackstrength>** 121 +))) 122 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 123 +((( 124 +//The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.// 125 +))) 126 +|((( 127 +Assets 37 37 )))|((( 129 +6.00 Beta 1 130 +)))|(% colspan="2" %)((( 38 38 Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons 39 39 ))) 40 -|(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)(% class="highlight-#f4f5f7" title="Background color : Light grey 100%"colspan="3" data-highlight-colour="#f4f5f7"%)133 +|(% class="highlight-grey" colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% class="highlight-grey" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %) 41 41 ((( 42 42 //Connection tags used to specify compatibilities in component templates between a ship or station module and engines or shields now additionally require the use of the "standard" tag matching weapon or turret logic. For weapons that are neither Missile Launcher nor Mining Laser, the tag "combat" is also required. 43 43 Exception: special equipment that is deliberately not compatible with the majority of slots may use another tag instead of "standard", e.g. "highpower" for certain Terran weapons.// ... ... @@ -48,11 +48,11 @@ 48 48 )))|(% colspan="1" %)(% colspan="1" %) 49 49 ((( 50 50 6.00 Beta 1 51 -)))|(% colspan=" 1" %)(% colspan="1" %)144 +)))|(% colspan="2" %)(% colspan="1" %) 52 52 ((( 53 53 Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects 54 54 ))) 55 -|(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)(% class="highlight-#f4f5f7" title="Background color : Light grey 100%"colspan="3" data-highlight-colour="#f4f5f7"%)148 +|(% class="highlight-grey" colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% class="highlight-grey" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %) 56 56 ((( 57 57 //When finding components with attribute "sortbygatedistanceto", e.g. in <find_object>, any objects with a negative gatedistance (i.e. unreachable objects) are automatically excluded from the result.// 58 58 ))) ... ... @@ -60,10 +60,10 @@ 60 60 Scripts 61 61 )))|((( 62 62 6.00 Beta 1 63 -)))|((( 156 +)))|(% colspan="2" %)((( 64 64 **<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards. 65 65 ))) 66 -|(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)(% class="highlight-#f4f5f7" title="Background color : Light grey 100%"colspan="3" data-highlight-colour="#f4f5f7"%)159 +|(% class="highlight-grey" colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% class="highlight-grey" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %) 67 67 ((( 68 68 //The order of events was adjusted, allowing handlers of <event_player_owned_killed_object> and <event_player_owned_destroyed> to access commander/subordinate relationship of the destroyed object.// 69 69 ))) ... ... @@ -71,14 +71,14 @@ 71 71 Cutscenes 72 72 )))|((( 73 73 6.00 Beta 1 74 -)))|((( 167 +)))|(% colspan="2" %)((( 75 75 Changed behaviour of **<angles>** in cutscenes 76 76 ))) 77 -|(% colspan=" 3" %)(% colspan="3" %)170 +|(% class="highlight-grey" colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% class="highlight-grey" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %) 78 78 ((( 79 -The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees. 172 +//The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.// 80 80 ))) 81 -|(% colspan=" 3" %)(% colspan="3" %)174 +|(% colspan="4" %)(% colspan="3" %) 82 82 ((( 83 83 == 5.00 == 84 84 ))) ... ... @@ -86,14 +86,14 @@ 86 86 Parameters 87 87 )))|((( 88 88 5.00 Beta 1 89 -)))|((( 182 +)))|(% colspan="2" %)((( 90 90 **<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration 91 91 ))) 92 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)185 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 93 93 ((( 94 94 //'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.// 95 95 ))) 96 -|(% colspan=" 3" %)(% colspan="3" %)189 +|(% colspan="4" %)(% colspan="3" %) 97 97 ((( 98 98 == 4.10 == 99 99 ))) ... ... @@ -103,13 +103,13 @@ 103 103 )))|(% colspan="1" %)(% colspan="1" %) 104 104 ((( 105 105 4.10 Beta 7 106 -)))|(% colspan=" 1" %)(% colspan="1" %)199 +)))|(% colspan="2" %)(% colspan="1" %) 107 107 ((( 108 -**FFI**: (% style="color: rgb(0,0,0);" %)SetMapRenderCargoContents(%%)(),(% style="color: rgb(0,0,0);" %)SetMapRenderWorkForceInfo(),(% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)SetMapRenderCrewInfo() and(% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)SetMapRenderDockedShipInfos()(%%)deprecated201 +**FFI**: SetMapRenderCargoContents(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos() deprecated 109 109 ))) 110 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)203 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 111 111 ((( 112 -//The functionality represented by (% style="color: rgb(0,0,0);" %)SetMapRenderCargoContents(%%)(),(% style="color: rgb(0,0,0);" %)SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos()(%%)has been removed and the function was therefore stubbed.//205 +//The functionality represented by SetMapRenderCargoContents(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos() has been removed and the function was therefore stubbed.// 113 113 ))) 114 114 |(% colspan="1" %)(% colspan="1" %) 115 115 ((( ... ... @@ -117,11 +117,11 @@ 117 117 )))|(% colspan="1" %)(% colspan="1" %) 118 118 ((( 119 119 4.10 Beta 6 120 -)))|(% colspan=" 1" %)(% colspan="1" %)213 +)))|(% colspan="2" %)(% colspan="1" %) 121 121 ((( 122 122 **FFI**: CustomGameStartPlayerProperty2 changed 123 123 ))) 124 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)217 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 125 125 ((( 126 126 //This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.// 127 127 ))) ... ... @@ -131,11 +131,11 @@ 131 131 )))|(% colspan="1" %)(% colspan="1" %) 132 132 ((( 133 133 4.10 Beta 3 134 -)))|(% colspan=" 1" %)(% colspan="1" %)227 +)))|(% colspan="2" %)(% colspan="1" %) 135 135 ((( 136 136 Renamed **<stationinfobox>** to **<infobox>** 137 137 ))) 138 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)231 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 139 139 ((( 140 140 //Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.// 141 141 ))) ... ... @@ -145,11 +145,11 @@ 145 145 )))|(% colspan="1" %)(% colspan="1" %) 146 146 ((( 147 147 4.10 Beta 2 148 -)))|(% colspan=" 1" %)(% colspan="1" %)241 +)))|(% colspan="2" %)(% colspan="1" %) 149 149 ((( 150 150 **FFI**: SetMacroMapPlayerSectorOffset() deprecated 151 151 ))) 152 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)245 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 153 153 ((( 154 154 //The functionality represented by SetMacroMapPlayerSectorOffset() has been removed and the function was therefore stubbed. Setting the gamestart properties "sector" and "offset" will affect the universe macro map instead directly.// 155 155 ))) ... ... @@ -157,10 +157,10 @@ 157 157 UI extensions 158 158 )))|((( 159 159 4.10 Beta 2 160 -)))|((( 161 -**FFI**: (% style="color: rgb(0,0,0);" %)FilterComponentForMapMode(%%)()and(% style="color: rgb(0,0,0);" %)SetMapObjectFilter() changed253 +)))|(% colspan="2" %)((( 254 +**FFI**: FilterComponentForMapMode() and SetMapObjectFilter() changed 162 162 ))) 163 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)256 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 164 164 ((( 165 165 //These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.// 166 166 ))) ... ... @@ -168,10 +168,10 @@ 168 168 Scripts 169 169 )))|((( 170 170 4.10 Beta 1 171 -)))|((( 172 -People related attributes of mission** 264 +)))|(% colspan="2" %)((( 265 +People related attributes of mission** <delivery> **node moved 173 173 ))) 174 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)267 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 175 175 ((( 176 176 //The <delivery> node of <create_mission> and <update_mission> has been changed to support a new <wares> subnode. The people related attributes: 'people' and 'skills' have been moved from the <delivery> node itself to a <people> subnode.// 177 177 ))) ... ... @@ -181,11 +181,11 @@ 181 181 )))|(% colspan="1" %)(% colspan="1" %) 182 182 ((( 183 183 4.10 Beta 1 184 -)))|(% colspan=" 1" %)(% colspan="1" %)277 +)))|(% colspan="2" %)(% colspan="1" %) 185 185 ((( 186 186 **$destructible.productions** replaced with $defensible.productions 187 187 ))) 188 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)281 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 189 189 ((( 190 190 //The $destructible.productions script property was removed and reimplemented as $defensible.productions meaning some old uses may no longer work unless the destructible is also a defensible. The old implementation functioned by finding the containing object of the destructible (including itself) to query for the production modules.// 191 191 ))) ... ... @@ -193,14 +193,14 @@ 193 193 Scripts 194 194 )))|((( 195 195 4.10 Beta 1 196 -)))|((( 289 +)))|(% colspan="2" %)((( 197 197 Removed script property **$object.spawnsourceseed** 198 198 ))) 199 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)292 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 200 200 ((( 201 201 //The spawnsource seed is no longer directly accessible by scripts. Use $component.seed, which will internally use the spawnsource seed if able. Note: An improvement is that .seed on objects without a spawnsource seed will now result in a value that differs between objects of the same macro, meaning it can now reliably be used for player property or job ships.// 202 202 ))) 203 -|(% colspan=" 3" %)(% colspan="3" %)296 +|(% colspan="4" %)(% colspan="3" %) 204 204 ((( 205 205 == 4.00 == 206 206 ))) ... ... @@ -210,24 +210,23 @@ 210 210 )))|(% colspan="1" %)(% colspan="1" %) 211 211 ((( 212 212 4.00 Beta 10 213 -)))|(% colspan=" 1" %)(% colspan="1" %)306 +)))|(% colspan="2" %)(% colspan="1" %) 214 214 ((( 215 215 Controlled ship can change without a **gameplanchange-event** occurring. 216 216 ))) 217 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)310 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 218 218 ((( 219 219 //Before 4.00 Beta 10 it was ensured that there is no direct transition between the 'cockpit ui mode' of one ship to another. Instead, it was always ensured that the UI first transitions into the firstperson mode and then back into the cockpit mode (controlling then the other ship). 220 -In order to support the new emergency eject feature which was added in 4.00 Beta 7, this assurance was dropped. As of 4.00 Beta 10 it is now possible that the ship the player controls can swap without the gameplanchange-event being risen which one could rely upon in previous versions. If your addon relied on the fact that the ship would not change without first going into first person mode, you will have to adjust your addon accordingly. 221 -// 313 +In order to support the new emergency eject feature which was added in 4.00 Beta 7, this assurance was dropped. As of 4.00 Beta 10 it is now possible that the ship the player controls can swap without the gameplanchange-event being risen which one could rely upon in previous versions. If your addon relied on the fact that the ship would not change without first going into first person mode, you will have to adjust your addon accordingly.// 222 222 ))) 223 223 |((( 224 224 Scripts 225 225 )))|((( 226 226 4.00 Beta 7 227 -)))|((( 319 +)))|(% colspan="2" %)((( 228 228 Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed 229 229 ))) 230 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)322 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 231 231 ((( 232 232 //Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects? 233 233 New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits ... ... @@ -239,17 +239,16 @@ 239 239 )))|(% colspan="1" %)(% colspan="1" %) 240 240 ((( 241 241 4.00 Beta 6 242 -)))|(% colspan=" 1" %)(% colspan="1" %)334 +)))|(% colspan="2" %)(% colspan="1" %) 243 243 ((( 244 244 **FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed 245 245 ))) 246 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)338 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 247 247 ((( 248 248 //In order to keep consistency with regards to the new behvior 'hostile' relation state and the older (deprecated) UI functions, the behavior of the deprecated GetFactionRelationStatus() function was changed according to the behavior of the GetRelationStatus()/GetRelationStatus2() functions which was done in the previous beta. 249 249 Factions with a relation rating between -20 and -10 will now report a relation status of 'neutral' (aka: 1) instead of 'hostile'/'enemy' (aka: 0).// 250 250 251 -//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead. 252 -// 343 +//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.// 253 253 ))) 254 254 |(% colspan="1" %)(% colspan="1" %) 255 255 ((( ... ... @@ -257,11 +257,11 @@ 257 257 )))|(% colspan="1" %)(% colspan="1" %) 258 258 ((( 259 259 4.00 Beta 5 260 -)))|(% colspan=" 1" %)(% colspan="1" %)351 +)))|(% colspan="2" %)(% colspan="1" %) 261 261 ((( 262 262 **FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed 263 263 ))) 264 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)355 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 265 265 ((( 266 266 //4.00 Beta 5// //introduces a new 'hostile' relation status and the game now distinguishes between hostile and enemy relation states. Objects not yet 'hostile' with the player are now visualized differently and therefore distinguishable from real hostile ones. Because of that, several related changes were made for these objects to bring them more in line with how 'neutral' objects behave (f.e. no automatic attacking of these objects by the player property anymore, no target selection when targeting the closest enemy, etc.). To reflect this, these objects are now returning 1 (neutral) as the relation status by the GetRelationStatus()/GetRelationStatus2() functions.// 267 267 ... ... @@ -271,10 +271,10 @@ 271 271 Parameters 272 272 )))|((( 273 273 4.00 Beta 1 274 -)))|((( 365 +)))|(% colspan="2" %)((( 275 275 **requiresconstructionvessel** parameter moved 276 276 ))) 277 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)368 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 278 278 ((( 279 279 //The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.// 280 280 ))) ... ... @@ -282,14 +282,14 @@ 282 282 Scripts 283 283 )))|((( 284 284 4.00 Beta 1 285 -)))|((( 376 +)))|(% colspan="2" %)((( 286 286 Changed behaviour of **gatedistance** script property 287 287 ))) 288 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)379 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 289 289 ((( 290 290 //The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.// 291 291 ))) 292 -|(% colspan=" 3" %)(% colspan="3" %)383 +|(% colspan="4" %)(% colspan="3" %) 293 293 ((( 294 294 == 3.30 == 295 295 ))) ... ... @@ -297,14 +297,14 @@ 297 297 UI extensions 298 298 )))|((( 299 299 3.30 Beta 3 300 -)))|((( 301 -**FFI: **Removed** (% style="color: rgb(0,0,0);" %)GetMissionLimit()(%%)**(% style="color: rgb(0,0,0);" %)and****(% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)**IsMissionLimit**(%%)**Enabled()**391 +)))|(% colspan="2" %)((( 392 +**FFI: **Removed** GetMissionLimit() **and** IsMissionLimitEnabled()** 302 302 ))) 303 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)394 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 304 304 ((( 305 -//These mission limit-related functions (added in 3.30 Beta 1 and 2) are replaced with FFI (% style="color: rgb(0,0,0);" %)IsMissionLimit(%%)Reach(% style="color: rgb(0,0,0);" %)ed()//396 +//These mission limit-related functions (added in 3.30 Beta 1 and 2) are replaced with FFI IsMissionLimitReached()// 306 306 ))) 307 -|(% colspan=" 3" %)(% colspan="3" %)398 +|(% colspan="4" %)(% colspan="3" %) 308 308 ((( 309 309 == 3.20 == 310 310 ))) ... ... @@ -312,10 +312,10 @@ 312 312 Scripts 313 313 )))|((( 314 314 3.20 Beta 1 315 -)))|((( 406 +)))|(% colspan="2" %)((( 316 316 Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed 317 317 ))) 318 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)409 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 319 319 ((( 320 320 //Old params: param = attacked object, param2 = attack method, param3 = attacked component// 321 321 //New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon] ... ... @@ -327,11 +327,11 @@ 327 327 )))|(% colspan="1" %)(% colspan="1" %) 328 328 ((( 329 329 3.20 Beta 1 330 -)))|(% colspan=" 1" %)(% colspan="1" %)421 +)))|(% colspan="2" %)(% colspan="1" %) 331 331 ((( 332 332 Removed script property $trade.**restriction.faction** 333 333 ))) 334 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)425 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 335 335 ((( 336 336 //$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.// 337 337 ))) ... ... @@ -339,14 +339,14 @@ 339 339 UI extensions 340 340 )))|((( 341 341 3.20 Beta 1 342 -)))|((( 433 +)))|(% colspan="2" %)((( 343 343 **Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete! 344 344 ))) 345 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)436 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 346 346 ((( 347 347 //With the addition of the Trade Rule feature the given functions are obsolete and do not function anymore. This set of functions will return dummy values to avoid breaking scripts. Use GetAllTradeRules(), GetContainerTradeRuleID(), SetContainerTradeRule() and similar trade rule functions as replacement.// 348 348 ))) 349 -|(% colspan=" 3" %)(% colspan="3" %)440 +|(% colspan="4" %)(% colspan="3" %) 350 350 ((( 351 351 == 3.10 == 352 352 ))) ... ... @@ -356,15 +356,15 @@ 356 356 )))|(% colspan="1" %)(% colspan="1" %) 357 357 ((( 358 358 3.10 Beta 1 359 -)))|(% colspan=" 1" %)(% colspan="1" %)450 +)))|(% colspan="2" %)(% colspan="1" %) 360 360 ((( 361 361 Removed script action **<add_build/>** 362 362 ))) 363 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)454 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 364 364 ((( 365 365 //Removed <add_build/> action which was no longer needed and would result in builds being added in unsupported ways. Use other <add_build_xxx/> actions.// 366 366 ))) 367 -|(% colspan=" 3" %)(% colspan="3" %)458 +|(% colspan="4" %)(% colspan="3" %) 368 368 ((( 369 369 == 3.00 == 370 370 ))) ... ... @@ -374,11 +374,11 @@ 374 374 )))|(% colspan="1" %)(% colspan="1" %) 375 375 ((( 376 376 3.0 Beta 6 377 -)))|(% colspan=" 1" %)(% colspan="1" %)468 +)))|(% colspan="2" %)(% colspan="1" %) 378 378 ((( 379 379 Changed behaviour of script action **<get_suitable_job/>** 380 380 ))) 381 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)472 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 382 382 ((( 383 383 //<get_suitable_job/> previously did not respect job quotas or the current number of job ships. It now does, only returning job IDs which are not exceeding the maxgalaxy quota. Using 'exceedquota' allows the action to behave as before.// 384 384 ))) ... ... @@ -388,11 +388,11 @@ 388 388 )))|(% colspan="1" %)(% colspan="1" %) 389 389 ((( 390 390 3.0 Beta 6 391 -)))|(% colspan=" 1" %)(% colspan="1" %)482 +)))|(% colspan="2" %)(% colspan="1" %) 392 392 ((( 393 393 Changed behaviour of script action **<get_ware_definition/>** 394 394 ))) 395 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)486 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 396 396 ((( 397 397 //<get_ware_definition/> previously filtered for equipment wares by default. This is now not the case and existing cases now use flags="equipment". Additional filter attributes for group and tags has also been added.// 398 398 ))) ... ... @@ -402,13 +402,13 @@ 402 402 )))|(% colspan="1" %)(% colspan="1" %) 403 403 ((( 404 404 3.0 Beta 5 405 -)))|(% colspan=" 1" %)(% colspan="1" %)496 +)))|(% colspan="2" %)(% colspan="1" %) 406 406 ((( 407 407 Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case 408 408 ))) 409 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)500 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 410 410 ((( 411 -//All MD, UI, and cutscene files have been renamed as lower-case. For most users this should have no effect since files packed in catalogs are essentially case-insensitive. However, this change can affect users on Linux systems when running a mod that contains single files instead of a catalog, and/or when playing with unpacked base game files//. If your mod has XML patch files that are not packed in a catalog, the filenames must be lower-case to match the filenames in the base game. (For info on using mod catalogs, see the Readme of the X Catalog Tool.) \\502 +//All MD, UI, and cutscene files have been renamed as lower-case. For most users this should have no effect since files packed in catalogs are essentially case-insensitive. However, this change can affect users on Linux systems when running a mod that contains single files instead of a catalog, and/or when playing with unpacked base game files//. If your mod has XML patch files that are not packed in a catalog, the filenames must be lower-case to match the filenames in the base game. (For info on using mod catalogs, see the Readme of the X Catalog Tool.) 412 412 413 413 //Note that this change has no effect on the actual content of scripts or cutscenes. The MD script/cutscene names are stored in the files, regardless of the filenames, so that references to them remain unchanged (e.g., "md.Setup.Start" references a cue in setup.xml).// 414 414 ))) ... ... @@ -418,11 +418,11 @@ 418 418 )))|(% colspan="1" %)(% colspan="1" %) 419 419 ((( 420 420 3.0 Beta 5 421 -)))|(% colspan=" 1" %)(% colspan="1" %)512 +)))|(% colspan="2" %)(% colspan="1" %) 422 422 ((( 423 423 Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions> 424 424 ))) 425 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)516 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 426 426 ((( 427 427 //Some MD library cues in the base game that were previously used with <include_actions> have been adjusted, so they must now be used with the new MD action <run_actions> instead. Mods that use such a library with <include_actions> will have to switch to <run_actions> as well. A list of affected libraries is not provided here. Note: Additional library cues may be adjusted in future builds without further warning.// 428 428 ))) ... ... @@ -432,11 +432,11 @@ 432 432 )))|(% colspan="1" %)(% colspan="1" %) 433 433 ((( 434 434 3.0 Beta 5 435 -)))|(% colspan=" 1" %)(% colspan="1" %)526 +)))|(% colspan="2" %)(% colspan="1" %) 436 436 ((( 437 437 Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos** 438 438 ))) 439 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)530 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 440 440 ((( 441 441 //Before the change, positions are relative to $dockingbay.parent. 442 442 After the change, positions are relative to $dockingbay as specified in the documentation.// ... ... @@ -447,11 +447,11 @@ 447 447 )))|(% colspan="1" %)(% colspan="1" %) 448 448 ((( 449 449 3.0 Beta 2 450 -)))|(% colspan=" 1" %)(% colspan="1" %)541 +)))|(% colspan="2" %)(% colspan="1" %) 451 451 ((( 452 452 Support for entity flag "**skillsvisible**" dropped 453 453 ))) 454 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)545 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 455 455 ((( 456 456 //Entity skills are always visible; that flag was a leftover from XR. We removed support for the script property .skillsvisible, the attribute "skillsvisible" of <set_entity_traits> and <set_npc_template_traits>, and the parameter "skillsvisible" of Lua function GetComponentData().// 457 457 ))) ... ... @@ -459,10 +459,10 @@ 459 459 Scripts 460 460 )))|((( 461 461 3.0 Beta 2 462 -)))|((( 553 +)))|(% colspan="2" %)((( 463 463 Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**. 464 464 ))) 465 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)556 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 466 466 ((( 467 467 //Before 3.0 Beta 2 there was just a single <event_object//_changed_owner> condition. This condition was triggered in multiple cases when an owner change occurred. However, the exact cases were inconsistent and also the event could have been triggered w/o an effective owner change having been applied. 468 468 3.0 Beta 2 fixes these inconsistencies and ensures that the event is only fired, if the "effective" component owner of the object changed. To handle cases where the script actually needs to be informed if the "true" owner of a component was changed (i.e. not taking the cover faction into account) a new <event_object_changed_true_owner> was introduced. ... ... @@ -475,11 +475,11 @@ 475 475 )))|(% colspan="1" %)(% colspan="1" %) 476 476 ((( 477 477 3.0 Beta 1 478 -)))|(% colspan=" 1" %)(% colspan="1" %)569 +)))|(% colspan="2" %)(% colspan="1" %) 479 479 ((( 480 480 **MissionBoard** support dropped 481 481 ))) 482 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)573 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 483 483 ((( 484 484 //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 behaviour would occur. Therefore we cleaned things up in 3.0 Beta 1 including deprecating/removing any related UI/script function.// 485 485 ))) ... ... @@ -487,10 +487,10 @@ 487 487 Job/God 488 488 )))|((( 489 489 3.0 Beta 1 490 -)))|((( 581 +)))|(% colspan="2" %)((( 491 491 By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined 492 492 ))) 493 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)584 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 494 494 ((( 495 495 //To better support extensions which add to the base game map, a job/god entry now defaults to only spawning objects in areas of the map that are added by the extension in which that entry is defined. You can override this behaviour by adding a matchextension="false" attribute to the job/god entry definition. This allows the entry to spawn objects anywhere that matches the entry's other criteria.// 496 496 ))) ... ... @@ -500,11 +500,11 @@ 500 500 )))|(% colspan="1" %)(% colspan="1" %) 501 501 ((( 502 502 3.0 Beta 1 503 -)))|(% colspan=" 1" %)(% colspan="1" %)594 +)))|(% colspan="2" %)(% colspan="1" %) 504 504 ((( 505 505 Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'** 506 506 ))) 507 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)598 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 508 508 ((( 509 509 //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.// 510 510 ))) ... ... @@ -514,11 +514,11 @@ 514 514 )))|(% colspan="1" %)(% colspan="1" %) 515 515 ((( 516 516 3.0 Beta 1 517 -)))|(% colspan=" 1" %)(% colspan="1" %)608 +)))|(% colspan="2" %)(% colspan="1" %) 518 518 ((( 519 519 Script action **<set_doors_locked/>** attribute **'group'** changed 520 520 ))) 521 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)612 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 522 522 ((( 523 523 //The 'group' attribute of <set_doors_locked/> can no longer be a list. It must be a single tag value. Previously, a list containing one tag was accepted, which was redundant.// 524 524 ))) ... ... @@ -528,11 +528,11 @@ 528 528 )))|(% colspan="1" %)(% colspan="1" %) 529 529 ((( 530 530 3.0 Beta 1 531 -)))|(% colspan=" 1" %)(% colspan="1" %)622 +)))|(% colspan="2" %)(% colspan="1" %) 532 532 ((( 533 533 Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed 534 534 ))) 535 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)626 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 536 536 ((( 537 537 //These events were never triggered, with the exception of <event_hack_started/> on the player entity for instant control panel hacks. Use <event_player_hacked_object> instead.// 538 538 ))) ... ... @@ -542,11 +542,11 @@ 542 542 )))|(% colspan="1" %)(% colspan="1" %) 543 543 ((( 544 544 3.0 Beta 1 545 -)))|(% colspan=" 1" %)(% colspan="1" %)636 +)))|(% colspan="2" %)(% colspan="1" %) 546 546 ((( 547 547 Script actions **<set_hack_target/>** and **<abort_hack/>** removed 548 548 ))) 549 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)640 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 550 550 ((( 551 551 //These actions had no effect and were removed.// 552 552 ))) ... ... @@ -556,11 +556,11 @@ 556 556 )))|(% colspan="1" %)(% colspan="1" %) 557 557 ((( 558 558 3.0 Beta 1 559 -)))|(% colspan=" 1" %)(% colspan="1" %)650 +)))|(% colspan="2" %)(% colspan="1" %) 560 560 ((( 561 561 **<setup_conversation_minigame/>** script action removed 562 562 ))) 563 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)654 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 564 564 ((( 565 565 //The script action was a leftover from the XR era and was never supported in X4 and couldn't be used in a meaningful way. It was therefore decided to better drop it altogether as it's not expected having been used by any mods.// 566 566 ))) ... ... @@ -570,11 +570,11 @@ 570 570 )))|(% colspan="1" %)(% colspan="1" %) 571 571 ((( 572 572 3.0 Beta 1 573 -)))|(% colspan=" 1" %)(% colspan="1" %)664 +)))|(% colspan="2" %)(% colspan="1" %) 574 574 ((( 575 575 <add_player_choice_*> **confidence** attribute removed 576 576 ))) 577 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)668 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 578 578 ((( 579 579 //The default confidence of player options is another leftover from the XR era and had no effect in X4.// 580 580 ))) ... ... @@ -584,11 +584,11 @@ 584 584 )))|(% colspan="1" %)(% colspan="1" %) 585 585 ((( 586 586 3.0 Beta 1 587 -)))|(% colspan=" 1" %)(% colspan="1" %)678 +)))|(% colspan="2" %)(% colspan="1" %) 588 588 ((( 589 589 **<hack_via_control_panel/>** script action removed 590 590 ))) 591 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)682 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 592 592 ((( 593 593 //Unused script action <hack_via_control_panel/> was removed.// 594 594 ))) ... ... @@ -598,11 +598,11 @@ 598 598 )))|(% colspan="1" %)(% colspan="1" %) 599 599 ((( 600 600 3.0 Beta 1 601 -)))|(% colspan=" 1" %)(% colspan="1" %)692 +)))|(% colspan="2" %)(% colspan="1" %) 602 602 ((( 603 603 **Lua: **GetMiniGameCursorPosition() removed 604 604 ))) 605 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)696 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 606 606 ((( 607 607 //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.// 608 608 ))) ... ... @@ -610,10 +610,10 @@ 610 610 UI core 611 611 )))|((( 612 612 3.0 Beta 1 613 -)))|((( 704 +)))|(% colspan="2" %)((( 614 614 **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders 615 615 ))) 616 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)707 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 617 617 ((( 618 618 //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.// 619 619 ))) ... ... @@ -623,11 +623,11 @@ 623 623 )))|(% colspan="1" %)(% colspan="1" %) 624 624 ((( 625 625 3.0 Beta 1 626 -)))|(% colspan=" 1" %)(% colspan="1" %)717 +)))|(% colspan="2" %)(% colspan="1" %) 627 627 ((( 628 628 **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor 629 629 ))) 630 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)721 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 631 631 ((( 632 632 //In 3.0 Beta 1 we added support for a new weapon mod property "SurfaceElementFactor" to allow weapons to deal increased damage to surface elements such as Shield Generators, Turrets or Engines.// 633 633 ))) ... ... @@ -637,11 +637,11 @@ 637 637 )))|(% colspan="1" %)(% colspan="1" %) 638 638 ((( 639 639 3.0 Beta 1 640 -)))|(% colspan=" 1" %)(% colspan="1" %)731 +)))|(% colspan="2" %)(% colspan="1" %) 641 641 ((( 642 642 **$ware.illegal** updated 643 643 ))) 644 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)735 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 645 645 ((( 646 646 //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.// 647 647 //It now returns true if $ware is illegal to any faction in the game.// ... ... @@ -652,11 +652,11 @@ 652 652 )))|(% colspan="1" %)(% colspan="1" %) 653 653 ((( 654 654 3.0 Beta 1 655 -)))|(% colspan=" 1" %)(% colspan="1" %)746 +)))|(% colspan="2" %)(% colspan="1" %) 656 656 ((( 657 657 MD script **RML_Flight_Along_Path** removed 658 658 ))) 659 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)750 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 660 660 ((( 661 661 //The MD script RML_Flight_Along_Path was not referened and was removed.// 662 662 ))) ... ... @@ -666,11 +666,11 @@ 666 666 )))|(% colspan="1" %)(% colspan="1" %) 667 667 ((( 668 668 3.0 Beta 1 669 -)))|(% colspan=" 1" %)(% colspan="1" %)760 +)))|(% colspan="2" %)(% colspan="1" %) 670 670 ((( 671 671 parameters of **<event_venture_mission_completed/>** changed 672 672 ))) 673 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)764 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 674 674 ((( 675 675 //old params: param = venture details, param2 = ships involved, param3 = duration// 676 676 //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration// ... ... @@ -679,11 +679,11 @@ 679 679 Scripts 680 680 )))|((( 681 681 3.0 Beta 1 682 -)))|((( 773 +)))|(% colspan="2" %)((( 683 683 **<set_object_wing_name/>** removed, 684 684 **<set_object_fleet_name/>** added 685 685 ))) 686 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)777 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 687 687 ((( 688 688 //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>// 689 689 ))) ... ... @@ -691,15 +691,15 @@ 691 691 Scripts 692 692 )))|((( 693 693 3.0 Beta 1 694 -)))|((( 785 +)))|(% colspan="2" %)((( 695 695 **$controllable.wing.*** removed, 696 696 **$controllable.fleet.*** added 697 697 ))) 698 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)789 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 699 699 ((( 700 700 $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander 701 701 ))) 702 -|(% colspan=" 3" %)(% colspan="3" %)793 +|(% colspan="4" %)(% colspan="3" %) 703 703 ((( 704 704 == 2.60 == 705 705 ))) ... ... @@ -707,10 +707,10 @@ 707 707 Scripts 708 708 )))|((( 709 709 2.60 Beta 1 710 -)))|((( 801 +)))|(% colspan="2" %)((( 711 711 '**checkoperational**' filter behaviour changed 712 712 ))) 713 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)804 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 714 714 ((( 715 715 //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.// 716 716 ... ... @@ -720,14 +720,14 @@ 720 720 Scripts 721 721 )))|((( 722 722 2.60 Beta 1 723 -)))|((( 814 +)))|(% colspan="2" %)((( 724 724 $container.**supplyresources** behavior changed 725 725 ))) 726 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)817 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 727 727 ((( 728 728 //The script keyword $container.supplyresources now includes reserved wares.// 729 729 ))) 730 -|(% colspan=" 3" %)(% colspan="3" %)821 +|(% colspan="4" %)(% colspan="3" %) 731 731 ((( 732 732 == 2.20 == 733 733 ))) ... ... @@ -737,17 +737,16 @@ 737 737 )))|(% colspan="1" %)(% colspan="1" %) 738 738 ((( 739 739 2.20 Beta 3/4 740 -)))|(% colspan=" 1" %)(% colspan="1" %)831 +)))|(% colspan="2" %)(% colspan="1" %) 741 741 ((( 742 742 **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined. 743 743 ))) 744 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)835 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 745 745 ((( 746 746 //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. 747 747 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.// 748 748 749 -//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. 750 -// 840 +//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.// 751 751 ))) 752 752 |(% colspan="1" %)(% colspan="1" %) 753 753 ((( ... ... @@ -755,15 +755,15 @@ 755 755 )))|(% colspan="1" %)(% colspan="1" %) 756 756 ((( 757 757 2.20 Beta 3 758 -)))|(% colspan=" 1" %)(% colspan="1" %)848 +)))|(% colspan="2" %)(% colspan="1" %) 759 759 ((( 760 760 Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor' 761 761 ))) 762 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)852 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 763 763 ((( 764 764 //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.// 765 765 ))) 766 -|(% colspan=" 3" %)(% colspan="3" %)856 +|(% colspan="4" %)(% colspan="3" %) 767 767 ((( 768 768 == 2.00 == 769 769 ))) ... ... @@ -773,11 +773,11 @@ 773 773 )))|(% colspan="1" %)(% colspan="1" %) 774 774 ((( 775 775 2.00 Beta 1 776 -)))|(% colspan=" 1" %)(% colspan="1" %)866 +)))|(% colspan="2" %)(% colspan="1" %) 777 777 ((( 778 778 **<event_build_finished/> **param2 now returns null instead of a construction sequence 779 779 ))) 780 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)870 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 781 781 ((( 782 782 //The construction sequence which was finished should now be accessed via the buildtask provided via param3.// 783 783 ))) ... ... @@ -787,11 +787,11 @@ 787 787 )))|(% colspan="1" %)(% colspan="1" %) 788 788 ((( 789 789 2.00 Beta 1 790 -)))|(% colspan=" 1" %)(% colspan="1" %)880 +)))|(% colspan="2" %)(% colspan="1" %) 791 791 ((( 792 792 **param.boarding.{...}** strength parameters removed 793 793 ))) 794 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)884 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 795 795 ((( 796 796 //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.// 797 797 ))) ... ... @@ -801,11 +801,11 @@ 801 801 )))|(% colspan="1" %)(% colspan="1" %) 802 802 ((( 803 803 2.00 Beta 1 804 -)))|(% colspan=" 1" %)(% colspan="1" %)894 +)))|(% colspan="2" %)(% colspan="1" %) 805 805 ((( 806 806 **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed 807 807 ))) 808 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)898 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 809 809 ((( 810 810 //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.// 811 811 ))) ... ... @@ -813,10 +813,10 @@ 813 813 UI extensions 814 814 )))|((( 815 815 2.00 Beta 1 816 -)))|((( 906 +)))|(% colspan="2" %)((( 817 817 **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals 818 818 ))) 819 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)909 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 820 820 ((( 821 821 //Before 2.0 Beta 1 using GetUpgradeSlotCurrentComponent() or GetUpgradeSlotGroup() only performed on operational objects (i.e. not wrecked objects or objects under construction). Since this is inconsistent with the rest of the UI functions, this was considered a bug and fixed in 2.0 Beta 1. If you require the old behavior, use the FFI function: IsComponentOperational() to check the passed object's state before making the call.// 822 822 ))) ... ... @@ -824,10 +824,10 @@ 824 824 UI extensions 825 825 )))|((( 826 826 2.00 Beta 1 827 -)))|((( 917 +)))|(% colspan="2" %)((( 828 828 **FFI: SetFormationShape()** no longer indicates an error upon certain error cases 829 829 ))) 830 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)920 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 831 831 ((( 832 832 //Before 2.0 Beta 1 a call to SetFormationShape() indicated an error state to the caller in certain cases where setting a formation shape (potentially) failed. Due to a design flaw in the handling of formations, this however doesn't do any good, since the function by itself doesn't really set the formation shape in all cases. On top of that the call can fail at random. Hence, at the moment an indication of an error case that setting a formation potentially fails is no good to the caller and he has no means to distinguish that case from a real error case.// 833 833 //Therefore, in 2.0 Beta 1 we drop the error indication in case of an attempt to set the formation fails. We are currently working on a better solution to the underlying problem and hope to have it ready as part of a following beta.// ... ... @@ -836,10 +836,10 @@ 836 836 Scripts 837 837 )))|((( 838 838 2.00 Beta 1 839 -)))|((( 929 +)))|(% colspan="2" %)((( 840 840 **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated. 841 841 ))) 842 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)932 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 843 843 ((( 844 844 //This now enforces a leader and at least one follower in order to create or change a formation. Former implementation made it possible to create formations without any followers which led to issues.// 845 845 ))) ... ... @@ -847,10 +847,10 @@ 847 847 Scripts 848 848 )))|((( 849 849 2.00 Beta 1 850 -)))|((( 940 +)))|(% colspan="2" %)((( 851 851 **<event_player_changed_target/>** now fires and returns null if the player deselects a target. 852 852 ))) 853 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)943 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 854 854 ((( 855 855 //For prior behavior, check for event.param being non-null.// 856 856 ))) ... ... @@ -858,10 +858,10 @@ 858 858 AI Scripts 859 859 )))|((( 860 860 2.00 Beta 1 861 -)))|((( 951 +)))|(% colspan="2" %)((( 862 862 **<shoot/>/<shoot_at/>** attribute changes. 863 863 ))) 864 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)954 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 865 865 ((( 866 866 //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.// 867 867 //New attribute: "secondary" is an optional attribute that defines whether weapons from the ship's active secondary weapon group will be fired. Defaults to true.// ... ... @@ -873,10 +873,10 @@ 873 873 UI extensions 874 874 )))|((( 875 875 2.00 Beta 1 876 -)))|((( 966 +)))|(% colspan="2" %)((( 877 877 **FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter. 878 878 ))) 879 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)969 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 880 880 ((( 881 881 //Added possibility to query build tasks of a certain buildmodule.// 882 882 ))) ... ... @@ -884,10 +884,10 @@ 884 884 UI extensions 885 885 )))|((( 886 886 2.00 Beta 1 887 -)))|((( 977 +)))|(% colspan="2" %)((( 888 888 **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field. 889 889 ))) 890 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)980 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 891 891 ((( 892 892 //Added list of resources a buildmodule needs to build.// 893 893 ))) ... ... @@ -895,10 +895,10 @@ 895 895 UI extensions 896 896 )))|((( 897 897 2.00 Beta 1 898 -)))|((( 899 - (% style="color: rgb(0,0,0);" %)**Lua:**(% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)**CalculateTotalHullFraction()**(%style="color: rgb(0,0,0);" %)****(%%)was removed.(%style="color: rgb(0,0,0);" %)988 +)))|(% colspan="2" %)((( 989 +**Lua: CalculateTotalHullFraction() **was removed. 900 900 ))) 901 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)991 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 902 902 ((( 903 903 //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.// 904 904 ))) ... ... @@ -906,14 +906,14 @@ 906 906 UI extensions 907 907 )))|((( 908 908 2.00 Beta 1 909 -)))|((( 910 -**FFI: (% style="color: rgb(0,0,0);" %)RequestDockAtReason()/(% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)UndockPlayerShip()(%%)**changed their return values.999 +)))|(% colspan="2" %)((( 1000 +**FFI: RequestDockAtReason()/UndockPlayerShip() **changed their return values. 911 911 ))) 912 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1002 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 913 913 ((( 914 914 //Changed return value type to const char* to better identify failure reasons in Lua script.// 915 915 ))) 916 -|(% colspan=" 3" %)(% colspan="3" %)1006 +|(% colspan="4" %)(% colspan="3" %) 917 917 ((( 918 918 == 1.50 == 919 919 ))) ... ... @@ -921,10 +921,10 @@ 921 921 UI extensions 922 922 )))|((( 923 923 1.50 Beta 3 924 -)))|((( 1014 +)))|(% colspan="2" %)((( 925 925 **Lua: GetComponentData() **changed behavior of "docksizes" property. 926 926 ))) 927 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1017 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 928 928 ((( 929 929 //The "docksizes" property no longer includes internal ship storage docks.// 930 930 ))) ... ... @@ -932,10 +932,10 @@ 932 932 All 933 933 )))|((( 934 934 1.50 Beta 2 935 -)))|((( 1025 +)))|(% colspan="2" %)((( 936 936 **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR). 937 937 ))) 938 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1028 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 939 939 ((( 940 940 //Shipyards (formerly also known as Capital Shipyards) can build capital ships, while Wharfs only build non-capital ships. To check whether a station is a Shipyard or a Wharf, check whether the station "can build ships".// 941 941 ... ... @@ -947,10 +947,10 @@ 947 947 UI extensions 948 948 )))|((( 949 949 1.50 Beta 2 950 -)))|((( 1040 +)))|(% colspan="2" %)((( 951 951 **FFI: UpgradeGroupInfo **datatype was changed. 952 952 ))) 953 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1043 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 954 954 ((( 955 955 //Added new "operational" field to retrieve information about number of operational upgrades in a group.// 956 956 ))) ... ... @@ -960,14 +960,13 @@ 960 960 )))|(% colspan="1" %)(% colspan="1" %) 961 961 ((( 962 962 1.50 Beta 1 963 -)))|(% colspan=" 1" %)(% colspan="1" %)1053 +)))|(% colspan="2" %)(% colspan="1" %) 964 964 ((( 965 965 **FFI: SetGuidance()** removed useinfopoint argument. 966 966 ))) 967 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1057 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 968 968 ((( 969 -//In X Rebirth "info points" existed (which were mainly used as interaction points to scan stations/access information about modules). These were removed in X4 but this left-over property here was missed to be removed in-time for release. It was therefore removed now in order to move towards a stable/clean UI API. 970 -// 1059 +//In X Rebirth "info points" existed (which were mainly used as interaction points to scan stations/access information about modules). These were removed in X4 but this left-over property here was missed to be removed in-time for release. It was therefore removed now in order to move towards a stable/clean UI API.// 971 971 972 972 //The new function declaration is: void SetGuidance(UniverseID componentid, UIPosRot offset)// 973 973 ))) ... ... @@ -975,14 +975,14 @@ 975 975 UI extensions 976 976 )))|((( 977 977 1.50 Beta 1 978 -)))|((( 1067 +)))|(% colspan="2" %)((( 979 979 **FFI: CancelConstruction() **changed its return value. 980 980 ))) 981 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1070 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 982 982 ((( 983 - (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. //1072 +//CancelConstruction() now returns if the cancellation was successful. // 984 984 ))) 985 -|(% colspan=" 3" %)(% colspan="3" %)1074 +|(% colspan="4" %)(% colspan="3" %) 986 986 ((( 987 987 == 1.32 == 988 988 ))) ... ... @@ -990,14 +990,14 @@ 990 990 UI extensions 991 991 )))|((( 992 992 1.32 993 -)))|((( 1082 +)))|(% colspan="2" %)((( 994 994 **Lua: GetComponentData() **removed the "nextdestname" property. 995 995 ))) 996 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1085 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 997 997 ((( 998 998 //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.// 999 999 ))) 1000 -|(% colspan=" 3" %)(% colspan="3" %)1089 +|(% colspan="4" %)(% colspan="3" %) 1001 1001 ((( 1002 1002 == 1.20 == 1003 1003 ))) ... ... @@ -1005,10 +1005,10 @@ 1005 1005 UI extensions 1006 1006 )))|((( 1007 1007 1.20 1008 -)))|((( 1097 +)))|(% colspan="2" %)((( 1009 1009 **FFI: GetAAOption()** got a new "useconfig" parameter. 1010 1010 ))) 1011 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1100 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1012 1012 ((( 1013 -//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.//1102 +//The AA setting was changed to check the new setting with the user. In order to restore the old setting GetAAOption() gets the option to retrieve the config settings.// 1014 1014 )))
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 - 1358620091 +78577854 - url
-
... ... @@ -1,1 +1,1 @@ 1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/ 135862009/Breaking Changes1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/78577854/Breaking Changes