Changes for page Breaking Changes
Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 102.1
edited by owen
on 2023/02/07 12:57
on 2023/02/07 12:57
Change comment:
Added documentation for <find_object_surface> changes
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.o wen1 +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,24 +23,70 @@ 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 ))) 50 +|((( 51 +Libraries 52 +)))|((( 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 +))) 33 33 |(% colspan="1" %)(% colspan="1" %) 34 34 ((( 35 35 Scripts 36 36 )))|(% colspan="1" %)(% colspan="1" %) 37 37 ((( 38 -6.00 Beta 3 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 39 39 )))|(% colspan="1" %)(% colspan="1" %) 40 40 ((( 84 +6.00 Beta 3 85 +)))|(% colspan="2" %)(% colspan="1" %) 86 +((( 41 41 Changed result of **<find_object_surface>** action in the case of a failure 42 42 ))) 43 -|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey"%)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)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 :" %) 44 44 ((( 45 45 //The 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.// 46 46 ... ... @@ -54,11 +54,11 @@ 54 54 )))|(% colspan="1" %)(% colspan="1" %) 55 55 ((( 56 56 6.00 Beta 1 57 -)))|(% colspan=" 1" %)(% colspan="1" %)103 +)))|(% colspan="2" %)(% colspan="1" %) 58 58 ((( 59 59 Behaviour change for **<match_dock>** script component filter 60 60 ))) 61 -|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey"%)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)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 :" %) 62 62 ((( 63 63 //<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes. 64 64 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.// ... ... @@ -69,11 +69,11 @@ 69 69 )))|(% colspan="1" %)(% colspan="1" %) 70 70 ((( 71 71 6.00 Beta 1 72 -)))|(% colspan=" 1" %)(% colspan="1" %)118 +)))|(% colspan="2" %)(% colspan="1" %) 73 73 ((( 74 74 Changed result attribute location for **<get_attackstrength>** 75 75 ))) 76 -|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey"%)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)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 :" %) 77 77 ((( 78 78 //The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.// 79 79 ))) ... ... @@ -81,10 +81,10 @@ 81 81 Assets 82 82 )))|((( 83 83 6.00 Beta 1 84 -)))|((( 130 +)))|(% colspan="2" %)((( 85 85 Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons 86 86 ))) 87 -|(% 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%" %) 88 88 ((( 89 89 //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. 90 90 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.// ... ... @@ -95,11 +95,11 @@ 95 95 )))|(% colspan="1" %)(% colspan="1" %) 96 96 ((( 97 97 6.00 Beta 1 98 -)))|(% colspan=" 1" %)(% colspan="1" %)144 +)))|(% colspan="2" %)(% colspan="1" %) 99 99 ((( 100 100 Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects 101 101 ))) 102 -|(% 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%" %) 103 103 ((( 104 104 //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.// 105 105 ))) ... ... @@ -107,10 +107,10 @@ 107 107 Scripts 108 108 )))|((( 109 109 6.00 Beta 1 110 -)))|((( 156 +)))|(% colspan="2" %)((( 111 111 **<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards. 112 112 ))) 113 -|(% 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%" %) 114 114 ((( 115 115 //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.// 116 116 ))) ... ... @@ -118,14 +118,14 @@ 118 118 Cutscenes 119 119 )))|((( 120 120 6.00 Beta 1 121 -)))|((( 167 +)))|(% colspan="2" %)((( 122 122 Changed behaviour of **<angles>** in cutscenes 123 123 ))) 124 -|(% 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"%)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%" %) 125 125 ((( 126 126 //The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.// 127 127 ))) 128 -|(% colspan=" 3" %)(% colspan="3" %)174 +|(% colspan="4" %)(% colspan="3" %) 129 129 ((( 130 130 == 5.00 == 131 131 ))) ... ... @@ -133,14 +133,14 @@ 133 133 Parameters 134 134 )))|((( 135 135 5.00 Beta 1 136 -)))|((( 182 +)))|(% colspan="2" %)((( 137 137 **<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration 138 138 ))) 139 -|(% 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" %) 140 140 ((( 141 141 //'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.// 142 142 ))) 143 -|(% colspan=" 3" %)(% colspan="3" %)189 +|(% colspan="4" %)(% colspan="3" %) 144 144 ((( 145 145 == 4.10 == 146 146 ))) ... ... @@ -150,13 +150,13 @@ 150 150 )))|(% colspan="1" %)(% colspan="1" %) 151 151 ((( 152 152 4.10 Beta 7 153 -)))|(% colspan=" 1" %)(% colspan="1" %)199 +)))|(% colspan="2" %)(% colspan="1" %) 154 154 ((( 155 -**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 156 156 ))) 157 -|(% 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" %) 158 158 ((( 159 -//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.// 160 160 ))) 161 161 |(% colspan="1" %)(% colspan="1" %) 162 162 ((( ... ... @@ -164,11 +164,11 @@ 164 164 )))|(% colspan="1" %)(% colspan="1" %) 165 165 ((( 166 166 4.10 Beta 6 167 -)))|(% colspan=" 1" %)(% colspan="1" %)213 +)))|(% colspan="2" %)(% colspan="1" %) 168 168 ((( 169 169 **FFI**: CustomGameStartPlayerProperty2 changed 170 170 ))) 171 -|(% 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" %) 172 172 ((( 173 173 //This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.// 174 174 ))) ... ... @@ -178,11 +178,11 @@ 178 178 )))|(% colspan="1" %)(% colspan="1" %) 179 179 ((( 180 180 4.10 Beta 3 181 -)))|(% colspan=" 1" %)(% colspan="1" %)227 +)))|(% colspan="2" %)(% colspan="1" %) 182 182 ((( 183 183 Renamed **<stationinfobox>** to **<infobox>** 184 184 ))) 185 -|(% 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" %) 186 186 ((( 187 187 //Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.// 188 188 ))) ... ... @@ -192,11 +192,11 @@ 192 192 )))|(% colspan="1" %)(% colspan="1" %) 193 193 ((( 194 194 4.10 Beta 2 195 -)))|(% colspan=" 1" %)(% colspan="1" %)241 +)))|(% colspan="2" %)(% colspan="1" %) 196 196 ((( 197 197 **FFI**: SetMacroMapPlayerSectorOffset() deprecated 198 198 ))) 199 -|(% 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" %) 200 200 ((( 201 201 //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.// 202 202 ))) ... ... @@ -204,10 +204,10 @@ 204 204 UI extensions 205 205 )))|((( 206 206 4.10 Beta 2 207 -)))|((( 208 -**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 209 209 ))) 210 -|(% 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" %) 211 211 ((( 212 212 //These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.// 213 213 ))) ... ... @@ -215,10 +215,10 @@ 215 215 Scripts 216 216 )))|((( 217 217 4.10 Beta 1 218 -)))|((( 219 -People related attributes of mission** 264 +)))|(% colspan="2" %)((( 265 +People related attributes of mission** <delivery> **node moved 220 220 ))) 221 -|(% 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" %) 222 222 ((( 223 223 //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.// 224 224 ))) ... ... @@ -228,11 +228,11 @@ 228 228 )))|(% colspan="1" %)(% colspan="1" %) 229 229 ((( 230 230 4.10 Beta 1 231 -)))|(% colspan=" 1" %)(% colspan="1" %)277 +)))|(% colspan="2" %)(% colspan="1" %) 232 232 ((( 233 233 **$destructible.productions** replaced with $defensible.productions 234 234 ))) 235 -|(% 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" %) 236 236 ((( 237 237 //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.// 238 238 ))) ... ... @@ -240,14 +240,14 @@ 240 240 Scripts 241 241 )))|((( 242 242 4.10 Beta 1 243 -)))|((( 289 +)))|(% colspan="2" %)((( 244 244 Removed script property **$object.spawnsourceseed** 245 245 ))) 246 -|(% 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" %) 247 247 ((( 248 248 //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.// 249 249 ))) 250 -|(% colspan=" 3" %)(% colspan="3" %)296 +|(% colspan="4" %)(% colspan="3" %) 251 251 ((( 252 252 == 4.00 == 253 253 ))) ... ... @@ -257,24 +257,23 @@ 257 257 )))|(% colspan="1" %)(% colspan="1" %) 258 258 ((( 259 259 4.00 Beta 10 260 -)))|(% colspan=" 1" %)(% colspan="1" %)306 +)))|(% colspan="2" %)(% colspan="1" %) 261 261 ((( 262 262 Controlled ship can change without a **gameplanchange-event** occurring. 263 263 ))) 264 -|(% 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" %) 265 265 ((( 266 266 //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). 267 -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. 268 -// 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.// 269 269 ))) 270 270 |((( 271 271 Scripts 272 272 )))|((( 273 273 4.00 Beta 7 274 -)))|((( 319 +)))|(% colspan="2" %)((( 275 275 Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed 276 276 ))) 277 -|(% 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" %) 278 278 ((( 279 279 //Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects? 280 280 New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits ... ... @@ -286,17 +286,16 @@ 286 286 )))|(% colspan="1" %)(% colspan="1" %) 287 287 ((( 288 288 4.00 Beta 6 289 -)))|(% colspan=" 1" %)(% colspan="1" %)334 +)))|(% colspan="2" %)(% colspan="1" %) 290 290 ((( 291 291 **FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed 292 292 ))) 293 -|(% 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" %) 294 294 ((( 295 295 //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. 296 296 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).// 297 297 298 -//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead. 299 -// 343 +//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.// 300 300 ))) 301 301 |(% colspan="1" %)(% colspan="1" %) 302 302 ((( ... ... @@ -304,11 +304,11 @@ 304 304 )))|(% colspan="1" %)(% colspan="1" %) 305 305 ((( 306 306 4.00 Beta 5 307 -)))|(% colspan=" 1" %)(% colspan="1" %)351 +)))|(% colspan="2" %)(% colspan="1" %) 308 308 ((( 309 309 **FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed 310 310 ))) 311 -|(% 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" %) 312 312 ((( 313 313 //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.// 314 314 ... ... @@ -318,10 +318,10 @@ 318 318 Parameters 319 319 )))|((( 320 320 4.00 Beta 1 321 -)))|((( 365 +)))|(% colspan="2" %)((( 322 322 **requiresconstructionvessel** parameter moved 323 323 ))) 324 -|(% 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" %) 325 325 ((( 326 326 //The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.// 327 327 ))) ... ... @@ -329,14 +329,14 @@ 329 329 Scripts 330 330 )))|((( 331 331 4.00 Beta 1 332 -)))|((( 376 +)))|(% colspan="2" %)((( 333 333 Changed behaviour of **gatedistance** script property 334 334 ))) 335 -|(% 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" %) 336 336 ((( 337 337 //The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.// 338 338 ))) 339 -|(% colspan=" 3" %)(% colspan="3" %)383 +|(% colspan="4" %)(% colspan="3" %) 340 340 ((( 341 341 == 3.30 == 342 342 ))) ... ... @@ -344,14 +344,14 @@ 344 344 UI extensions 345 345 )))|((( 346 346 3.30 Beta 3 347 -)))|((( 348 -**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()** 349 349 ))) 350 -|(% 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" %) 351 351 ((( 352 -//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()// 353 353 ))) 354 -|(% colspan=" 3" %)(% colspan="3" %)398 +|(% colspan="4" %)(% colspan="3" %) 355 355 ((( 356 356 == 3.20 == 357 357 ))) ... ... @@ -359,10 +359,10 @@ 359 359 Scripts 360 360 )))|((( 361 361 3.20 Beta 1 362 -)))|((( 406 +)))|(% colspan="2" %)((( 363 363 Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed 364 364 ))) 365 -|(% 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" %) 366 366 ((( 367 367 //Old params: param = attacked object, param2 = attack method, param3 = attacked component// 368 368 //New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon] ... ... @@ -374,11 +374,11 @@ 374 374 )))|(% colspan="1" %)(% colspan="1" %) 375 375 ((( 376 376 3.20 Beta 1 377 -)))|(% colspan=" 1" %)(% colspan="1" %)421 +)))|(% colspan="2" %)(% colspan="1" %) 378 378 ((( 379 379 Removed script property $trade.**restriction.faction** 380 380 ))) 381 -|(% 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" %) 382 382 ((( 383 383 //$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.// 384 384 ))) ... ... @@ -386,14 +386,14 @@ 386 386 UI extensions 387 387 )))|((( 388 388 3.20 Beta 1 389 -)))|((( 433 +)))|(% colspan="2" %)((( 390 390 **Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete! 391 391 ))) 392 -|(% 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" %) 393 393 ((( 394 394 //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.// 395 395 ))) 396 -|(% colspan=" 3" %)(% colspan="3" %)440 +|(% colspan="4" %)(% colspan="3" %) 397 397 ((( 398 398 == 3.10 == 399 399 ))) ... ... @@ -403,15 +403,15 @@ 403 403 )))|(% colspan="1" %)(% colspan="1" %) 404 404 ((( 405 405 3.10 Beta 1 406 -)))|(% colspan=" 1" %)(% colspan="1" %)450 +)))|(% colspan="2" %)(% colspan="1" %) 407 407 ((( 408 408 Removed script action **<add_build/>** 409 409 ))) 410 -|(% 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" %) 411 411 ((( 412 412 //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.// 413 413 ))) 414 -|(% colspan=" 3" %)(% colspan="3" %)458 +|(% colspan="4" %)(% colspan="3" %) 415 415 ((( 416 416 == 3.00 == 417 417 ))) ... ... @@ -421,11 +421,11 @@ 421 421 )))|(% colspan="1" %)(% colspan="1" %) 422 422 ((( 423 423 3.0 Beta 6 424 -)))|(% colspan=" 1" %)(% colspan="1" %)468 +)))|(% colspan="2" %)(% colspan="1" %) 425 425 ((( 426 426 Changed behaviour of script action **<get_suitable_job/>** 427 427 ))) 428 -|(% 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" %) 429 429 ((( 430 430 //<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.// 431 431 ))) ... ... @@ -435,11 +435,11 @@ 435 435 )))|(% colspan="1" %)(% colspan="1" %) 436 436 ((( 437 437 3.0 Beta 6 438 -)))|(% colspan=" 1" %)(% colspan="1" %)482 +)))|(% colspan="2" %)(% colspan="1" %) 439 439 ((( 440 440 Changed behaviour of script action **<get_ware_definition/>** 441 441 ))) 442 -|(% 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" %) 443 443 ((( 444 444 //<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.// 445 445 ))) ... ... @@ -449,13 +449,13 @@ 449 449 )))|(% colspan="1" %)(% colspan="1" %) 450 450 ((( 451 451 3.0 Beta 5 452 -)))|(% colspan=" 1" %)(% colspan="1" %)496 +)))|(% colspan="2" %)(% colspan="1" %) 453 453 ((( 454 454 Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case 455 455 ))) 456 -|(% 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" %) 457 457 ((( 458 -//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.) 459 459 460 460 //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).// 461 461 ))) ... ... @@ -465,11 +465,11 @@ 465 465 )))|(% colspan="1" %)(% colspan="1" %) 466 466 ((( 467 467 3.0 Beta 5 468 -)))|(% colspan=" 1" %)(% colspan="1" %)512 +)))|(% colspan="2" %)(% colspan="1" %) 469 469 ((( 470 470 Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions> 471 471 ))) 472 -|(% 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" %) 473 473 ((( 474 474 //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.// 475 475 ))) ... ... @@ -479,11 +479,11 @@ 479 479 )))|(% colspan="1" %)(% colspan="1" %) 480 480 ((( 481 481 3.0 Beta 5 482 -)))|(% colspan=" 1" %)(% colspan="1" %)526 +)))|(% colspan="2" %)(% colspan="1" %) 483 483 ((( 484 484 Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos** 485 485 ))) 486 -|(% 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" %) 487 487 ((( 488 488 //Before the change, positions are relative to $dockingbay.parent. 489 489 After the change, positions are relative to $dockingbay as specified in the documentation.// ... ... @@ -494,11 +494,11 @@ 494 494 )))|(% colspan="1" %)(% colspan="1" %) 495 495 ((( 496 496 3.0 Beta 2 497 -)))|(% colspan=" 1" %)(% colspan="1" %)541 +)))|(% colspan="2" %)(% colspan="1" %) 498 498 ((( 499 499 Support for entity flag "**skillsvisible**" dropped 500 500 ))) 501 -|(% 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" %) 502 502 ((( 503 503 //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().// 504 504 ))) ... ... @@ -506,10 +506,10 @@ 506 506 Scripts 507 507 )))|((( 508 508 3.0 Beta 2 509 -)))|((( 553 +)))|(% colspan="2" %)((( 510 510 Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**. 511 511 ))) 512 -|(% 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" %) 513 513 ((( 514 514 //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. 515 515 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. ... ... @@ -522,11 +522,11 @@ 522 522 )))|(% colspan="1" %)(% colspan="1" %) 523 523 ((( 524 524 3.0 Beta 1 525 -)))|(% colspan=" 1" %)(% colspan="1" %)569 +)))|(% colspan="2" %)(% colspan="1" %) 526 526 ((( 527 527 **MissionBoard** support dropped 528 528 ))) 529 -|(% 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" %) 530 530 ((( 531 531 //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.// 532 532 ))) ... ... @@ -534,10 +534,10 @@ 534 534 Job/God 535 535 )))|((( 536 536 3.0 Beta 1 537 -)))|((( 581 +)))|(% colspan="2" %)((( 538 538 By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined 539 539 ))) 540 -|(% 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" %) 541 541 ((( 542 542 //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.// 543 543 ))) ... ... @@ -547,11 +547,11 @@ 547 547 )))|(% colspan="1" %)(% colspan="1" %) 548 548 ((( 549 549 3.0 Beta 1 550 -)))|(% colspan=" 1" %)(% colspan="1" %)594 +)))|(% colspan="2" %)(% colspan="1" %) 551 551 ((( 552 552 Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'** 553 553 ))) 554 -|(% 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" %) 555 555 ((( 556 556 //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.// 557 557 ))) ... ... @@ -561,11 +561,11 @@ 561 561 )))|(% colspan="1" %)(% colspan="1" %) 562 562 ((( 563 563 3.0 Beta 1 564 -)))|(% colspan=" 1" %)(% colspan="1" %)608 +)))|(% colspan="2" %)(% colspan="1" %) 565 565 ((( 566 566 Script action **<set_doors_locked/>** attribute **'group'** changed 567 567 ))) 568 -|(% 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" %) 569 569 ((( 570 570 //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.// 571 571 ))) ... ... @@ -575,11 +575,11 @@ 575 575 )))|(% colspan="1" %)(% colspan="1" %) 576 576 ((( 577 577 3.0 Beta 1 578 -)))|(% colspan=" 1" %)(% colspan="1" %)622 +)))|(% colspan="2" %)(% colspan="1" %) 579 579 ((( 580 580 Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed 581 581 ))) 582 -|(% 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" %) 583 583 ((( 584 584 //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.// 585 585 ))) ... ... @@ -589,11 +589,11 @@ 589 589 )))|(% colspan="1" %)(% colspan="1" %) 590 590 ((( 591 591 3.0 Beta 1 592 -)))|(% colspan=" 1" %)(% colspan="1" %)636 +)))|(% colspan="2" %)(% colspan="1" %) 593 593 ((( 594 594 Script actions **<set_hack_target/>** and **<abort_hack/>** removed 595 595 ))) 596 -|(% 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" %) 597 597 ((( 598 598 //These actions had no effect and were removed.// 599 599 ))) ... ... @@ -603,11 +603,11 @@ 603 603 )))|(% colspan="1" %)(% colspan="1" %) 604 604 ((( 605 605 3.0 Beta 1 606 -)))|(% colspan=" 1" %)(% colspan="1" %)650 +)))|(% colspan="2" %)(% colspan="1" %) 607 607 ((( 608 608 **<setup_conversation_minigame/>** script action removed 609 609 ))) 610 -|(% 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" %) 611 611 ((( 612 612 //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.// 613 613 ))) ... ... @@ -617,11 +617,11 @@ 617 617 )))|(% colspan="1" %)(% colspan="1" %) 618 618 ((( 619 619 3.0 Beta 1 620 -)))|(% colspan=" 1" %)(% colspan="1" %)664 +)))|(% colspan="2" %)(% colspan="1" %) 621 621 ((( 622 622 <add_player_choice_*> **confidence** attribute removed 623 623 ))) 624 -|(% 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" %) 625 625 ((( 626 626 //The default confidence of player options is another leftover from the XR era and had no effect in X4.// 627 627 ))) ... ... @@ -631,11 +631,11 @@ 631 631 )))|(% colspan="1" %)(% colspan="1" %) 632 632 ((( 633 633 3.0 Beta 1 634 -)))|(% colspan=" 1" %)(% colspan="1" %)678 +)))|(% colspan="2" %)(% colspan="1" %) 635 635 ((( 636 636 **<hack_via_control_panel/>** script action removed 637 637 ))) 638 -|(% 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" %) 639 639 ((( 640 640 //Unused script action <hack_via_control_panel/> was removed.// 641 641 ))) ... ... @@ -645,11 +645,11 @@ 645 645 )))|(% colspan="1" %)(% colspan="1" %) 646 646 ((( 647 647 3.0 Beta 1 648 -)))|(% colspan=" 1" %)(% colspan="1" %)692 +)))|(% colspan="2" %)(% colspan="1" %) 649 649 ((( 650 650 **Lua: **GetMiniGameCursorPosition() removed 651 651 ))) 652 -|(% 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" %) 653 653 ((( 654 654 //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.// 655 655 ))) ... ... @@ -657,10 +657,10 @@ 657 657 UI core 658 658 )))|((( 659 659 3.0 Beta 1 660 -)))|((( 704 +)))|(% colspan="2" %)((( 661 661 **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders 662 662 ))) 663 -|(% 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" %) 664 664 ((( 665 665 //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.// 666 666 ))) ... ... @@ -670,11 +670,11 @@ 670 670 )))|(% colspan="1" %)(% colspan="1" %) 671 671 ((( 672 672 3.0 Beta 1 673 -)))|(% colspan=" 1" %)(% colspan="1" %)717 +)))|(% colspan="2" %)(% colspan="1" %) 674 674 ((( 675 675 **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor 676 676 ))) 677 -|(% 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" %) 678 678 ((( 679 679 //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.// 680 680 ))) ... ... @@ -684,11 +684,11 @@ 684 684 )))|(% colspan="1" %)(% colspan="1" %) 685 685 ((( 686 686 3.0 Beta 1 687 -)))|(% colspan=" 1" %)(% colspan="1" %)731 +)))|(% colspan="2" %)(% colspan="1" %) 688 688 ((( 689 689 **$ware.illegal** updated 690 690 ))) 691 -|(% 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" %) 692 692 ((( 693 693 //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.// 694 694 //It now returns true if $ware is illegal to any faction in the game.// ... ... @@ -699,11 +699,11 @@ 699 699 )))|(% colspan="1" %)(% colspan="1" %) 700 700 ((( 701 701 3.0 Beta 1 702 -)))|(% colspan=" 1" %)(% colspan="1" %)746 +)))|(% colspan="2" %)(% colspan="1" %) 703 703 ((( 704 704 MD script **RML_Flight_Along_Path** removed 705 705 ))) 706 -|(% 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" %) 707 707 ((( 708 708 //The MD script RML_Flight_Along_Path was not referened and was removed.// 709 709 ))) ... ... @@ -713,11 +713,11 @@ 713 713 )))|(% colspan="1" %)(% colspan="1" %) 714 714 ((( 715 715 3.0 Beta 1 716 -)))|(% colspan=" 1" %)(% colspan="1" %)760 +)))|(% colspan="2" %)(% colspan="1" %) 717 717 ((( 718 718 parameters of **<event_venture_mission_completed/>** changed 719 719 ))) 720 -|(% 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" %) 721 721 ((( 722 722 //old params: param = venture details, param2 = ships involved, param3 = duration// 723 723 //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration// ... ... @@ -726,11 +726,11 @@ 726 726 Scripts 727 727 )))|((( 728 728 3.0 Beta 1 729 -)))|((( 773 +)))|(% colspan="2" %)((( 730 730 **<set_object_wing_name/>** removed, 731 731 **<set_object_fleet_name/>** added 732 732 ))) 733 -|(% 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" %) 734 734 ((( 735 735 //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>// 736 736 ))) ... ... @@ -738,15 +738,15 @@ 738 738 Scripts 739 739 )))|((( 740 740 3.0 Beta 1 741 -)))|((( 785 +)))|(% colspan="2" %)((( 742 742 **$controllable.wing.*** removed, 743 743 **$controllable.fleet.*** added 744 744 ))) 745 -|(% 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" %) 746 746 ((( 747 747 $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander 748 748 ))) 749 -|(% colspan=" 3" %)(% colspan="3" %)793 +|(% colspan="4" %)(% colspan="3" %) 750 750 ((( 751 751 == 2.60 == 752 752 ))) ... ... @@ -754,10 +754,10 @@ 754 754 Scripts 755 755 )))|((( 756 756 2.60 Beta 1 757 -)))|((( 801 +)))|(% colspan="2" %)((( 758 758 '**checkoperational**' filter behaviour changed 759 759 ))) 760 -|(% 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" %) 761 761 ((( 762 762 //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.// 763 763 ... ... @@ -767,14 +767,14 @@ 767 767 Scripts 768 768 )))|((( 769 769 2.60 Beta 1 770 -)))|((( 814 +)))|(% colspan="2" %)((( 771 771 $container.**supplyresources** behavior changed 772 772 ))) 773 -|(% 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" %) 774 774 ((( 775 775 //The script keyword $container.supplyresources now includes reserved wares.// 776 776 ))) 777 -|(% colspan=" 3" %)(% colspan="3" %)821 +|(% colspan="4" %)(% colspan="3" %) 778 778 ((( 779 779 == 2.20 == 780 780 ))) ... ... @@ -784,17 +784,16 @@ 784 784 )))|(% colspan="1" %)(% colspan="1" %) 785 785 ((( 786 786 2.20 Beta 3/4 787 -)))|(% colspan=" 1" %)(% colspan="1" %)831 +)))|(% colspan="2" %)(% colspan="1" %) 788 788 ((( 789 789 **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined. 790 790 ))) 791 -|(% 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" %) 792 792 ((( 793 793 //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. 794 794 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.// 795 795 796 -//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. 797 -// 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.// 798 798 ))) 799 799 |(% colspan="1" %)(% colspan="1" %) 800 800 ((( ... ... @@ -802,15 +802,15 @@ 802 802 )))|(% colspan="1" %)(% colspan="1" %) 803 803 ((( 804 804 2.20 Beta 3 805 -)))|(% colspan=" 1" %)(% colspan="1" %)848 +)))|(% colspan="2" %)(% colspan="1" %) 806 806 ((( 807 807 Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor' 808 808 ))) 809 -|(% 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" %) 810 810 ((( 811 811 //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.// 812 812 ))) 813 -|(% colspan=" 3" %)(% colspan="3" %)856 +|(% colspan="4" %)(% colspan="3" %) 814 814 ((( 815 815 == 2.00 == 816 816 ))) ... ... @@ -820,11 +820,11 @@ 820 820 )))|(% colspan="1" %)(% colspan="1" %) 821 821 ((( 822 822 2.00 Beta 1 823 -)))|(% colspan=" 1" %)(% colspan="1" %)866 +)))|(% colspan="2" %)(% colspan="1" %) 824 824 ((( 825 825 **<event_build_finished/> **param2 now returns null instead of a construction sequence 826 826 ))) 827 -|(% 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" %) 828 828 ((( 829 829 //The construction sequence which was finished should now be accessed via the buildtask provided via param3.// 830 830 ))) ... ... @@ -834,11 +834,11 @@ 834 834 )))|(% colspan="1" %)(% colspan="1" %) 835 835 ((( 836 836 2.00 Beta 1 837 -)))|(% colspan=" 1" %)(% colspan="1" %)880 +)))|(% colspan="2" %)(% colspan="1" %) 838 838 ((( 839 839 **param.boarding.{...}** strength parameters removed 840 840 ))) 841 -|(% 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" %) 842 842 ((( 843 843 //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.// 844 844 ))) ... ... @@ -848,11 +848,11 @@ 848 848 )))|(% colspan="1" %)(% colspan="1" %) 849 849 ((( 850 850 2.00 Beta 1 851 -)))|(% colspan=" 1" %)(% colspan="1" %)894 +)))|(% colspan="2" %)(% colspan="1" %) 852 852 ((( 853 853 **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed 854 854 ))) 855 -|(% 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" %) 856 856 ((( 857 857 //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.// 858 858 ))) ... ... @@ -860,10 +860,10 @@ 860 860 UI extensions 861 861 )))|((( 862 862 2.00 Beta 1 863 -)))|((( 906 +)))|(% colspan="2" %)((( 864 864 **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals 865 865 ))) 866 -|(% 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" %) 867 867 ((( 868 868 //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.// 869 869 ))) ... ... @@ -871,10 +871,10 @@ 871 871 UI extensions 872 872 )))|((( 873 873 2.00 Beta 1 874 -)))|((( 917 +)))|(% colspan="2" %)((( 875 875 **FFI: SetFormationShape()** no longer indicates an error upon certain error cases 876 876 ))) 877 -|(% 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" %) 878 878 ((( 879 879 //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.// 880 880 //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.// ... ... @@ -883,10 +883,10 @@ 883 883 Scripts 884 884 )))|((( 885 885 2.00 Beta 1 886 -)))|((( 929 +)))|(% colspan="2" %)((( 887 887 **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated. 888 888 ))) 889 -|(% 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" %) 890 890 ((( 891 891 //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.// 892 892 ))) ... ... @@ -894,10 +894,10 @@ 894 894 Scripts 895 895 )))|((( 896 896 2.00 Beta 1 897 -)))|((( 940 +)))|(% colspan="2" %)((( 898 898 **<event_player_changed_target/>** now fires and returns null if the player deselects a target. 899 899 ))) 900 -|(% 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" %) 901 901 ((( 902 902 //For prior behavior, check for event.param being non-null.// 903 903 ))) ... ... @@ -905,10 +905,10 @@ 905 905 AI Scripts 906 906 )))|((( 907 907 2.00 Beta 1 908 -)))|((( 951 +)))|(% colspan="2" %)((( 909 909 **<shoot/>/<shoot_at/>** attribute changes. 910 910 ))) 911 -|(% 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" %) 912 912 ((( 913 913 //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.// 914 914 //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.// ... ... @@ -920,10 +920,10 @@ 920 920 UI extensions 921 921 )))|((( 922 922 2.00 Beta 1 923 -)))|((( 966 +)))|(% colspan="2" %)((( 924 924 **FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter. 925 925 ))) 926 -|(% 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" %) 927 927 ((( 928 928 //Added possibility to query build tasks of a certain buildmodule.// 929 929 ))) ... ... @@ -931,10 +931,10 @@ 931 931 UI extensions 932 932 )))|((( 933 933 2.00 Beta 1 934 -)))|((( 977 +)))|(% colspan="2" %)((( 935 935 **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field. 936 936 ))) 937 -|(% 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" %) 938 938 ((( 939 939 //Added list of resources a buildmodule needs to build.// 940 940 ))) ... ... @@ -942,10 +942,10 @@ 942 942 UI extensions 943 943 )))|((( 944 944 2.00 Beta 1 945 -)))|((( 946 - (% 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. 947 947 ))) 948 -|(% 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" %) 949 949 ((( 950 950 //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.// 951 951 ))) ... ... @@ -953,14 +953,14 @@ 953 953 UI extensions 954 954 )))|((( 955 955 2.00 Beta 1 956 -)))|((( 957 -**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. 958 958 ))) 959 -|(% 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" %) 960 960 ((( 961 961 //Changed return value type to const char* to better identify failure reasons in Lua script.// 962 962 ))) 963 -|(% colspan=" 3" %)(% colspan="3" %)1006 +|(% colspan="4" %)(% colspan="3" %) 964 964 ((( 965 965 == 1.50 == 966 966 ))) ... ... @@ -968,10 +968,10 @@ 968 968 UI extensions 969 969 )))|((( 970 970 1.50 Beta 3 971 -)))|((( 1014 +)))|(% colspan="2" %)((( 972 972 **Lua: GetComponentData() **changed behavior of "docksizes" property. 973 973 ))) 974 -|(% 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" %) 975 975 ((( 976 976 //The "docksizes" property no longer includes internal ship storage docks.// 977 977 ))) ... ... @@ -979,10 +979,10 @@ 979 979 All 980 980 )))|((( 981 981 1.50 Beta 2 982 -)))|((( 1025 +)))|(% colspan="2" %)((( 983 983 **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR). 984 984 ))) 985 -|(% 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" %) 986 986 ((( 987 987 //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".// 988 988 ... ... @@ -994,10 +994,10 @@ 994 994 UI extensions 995 995 )))|((( 996 996 1.50 Beta 2 997 -)))|((( 1040 +)))|(% colspan="2" %)((( 998 998 **FFI: UpgradeGroupInfo **datatype was changed. 999 999 ))) 1000 -|(% 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" %) 1001 1001 ((( 1002 1002 //Added new "operational" field to retrieve information about number of operational upgrades in a group.// 1003 1003 ))) ... ... @@ -1007,14 +1007,13 @@ 1007 1007 )))|(% colspan="1" %)(% colspan="1" %) 1008 1008 ((( 1009 1009 1.50 Beta 1 1010 -)))|(% colspan=" 1" %)(% colspan="1" %)1053 +)))|(% colspan="2" %)(% colspan="1" %) 1011 1011 ((( 1012 1012 **FFI: SetGuidance()** removed useinfopoint argument. 1013 1013 ))) 1014 -|(% 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" %) 1015 1015 ((( 1016 -//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. 1017 -// 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.// 1018 1018 1019 1019 //The new function declaration is: void SetGuidance(UniverseID componentid, UIPosRot offset)// 1020 1020 ))) ... ... @@ -1022,14 +1022,14 @@ 1022 1022 UI extensions 1023 1023 )))|((( 1024 1024 1.50 Beta 1 1025 -)))|((( 1067 +)))|(% colspan="2" %)((( 1026 1026 **FFI: CancelConstruction() **changed its return value. 1027 1027 ))) 1028 -|(% 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" %) 1029 1029 ((( 1030 - (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. //1072 +//CancelConstruction() now returns if the cancellation was successful. // 1031 1031 ))) 1032 -|(% colspan=" 3" %)(% colspan="3" %)1074 +|(% colspan="4" %)(% colspan="3" %) 1033 1033 ((( 1034 1034 == 1.32 == 1035 1035 ))) ... ... @@ -1037,14 +1037,14 @@ 1037 1037 UI extensions 1038 1038 )))|((( 1039 1039 1.32 1040 -)))|((( 1082 +)))|(% colspan="2" %)((( 1041 1041 **Lua: GetComponentData() **removed the "nextdestname" property. 1042 1042 ))) 1043 -|(% 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" %) 1044 1044 ((( 1045 1045 //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.// 1046 1046 ))) 1047 -|(% colspan=" 3" %)(% colspan="3" %)1089 +|(% colspan="4" %)(% colspan="3" %) 1048 1048 ((( 1049 1049 == 1.20 == 1050 1050 ))) ... ... @@ -1052,10 +1052,10 @@ 1052 1052 UI extensions 1053 1053 )))|((( 1054 1054 1.20 1055 -)))|((( 1097 +)))|(% colspan="2" %)((( 1056 1056 **FFI: GetAAOption()** got a new "useconfig" parameter. 1057 1057 ))) 1058 -|(% 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" %) 1059 1059 ((( 1060 -//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.// 1061 1061 )))
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 - 1388725281 +78577854 - url
-
... ... @@ -1,1 +1,1 @@ 1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/ 138872528/Breaking Changes1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/78577854/Breaking Changes