Changes for page Breaking Changes
Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 114.4
edited by Volodymyr Boichuk
on 2024/04/10 12:49
on 2024/04/10 12:49
Change comment:
There is no comment for this version
To 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
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Parent
-
... ... @@ -1,1 +1,0 @@ 1 -X4 Foundations Wiki.Modding Support.WebHome - Author
-
... ... @@ -1,1 +1,1 @@ 1 -xwiki:XWiki. Volodymyr1 +xwiki:XWiki.klaus - 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 -{{ info}}8 - ⚠The list of breaking changes does7 +{{note}} 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 -{{/ info}}13 +{{/note}} 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. ... ... @@ -18,140 +18,26 @@ 18 18 19 19 = Breaking Changes = 20 20 21 -{{toc scope="LOCAL" start="3"/}} 22 - 23 -=== Version 7.00 === 24 - 25 - 26 26 (% class="wrapped" %) 27 -|(% colspan="1" style="width:117px" %) |(% colspan="1" style="width:119px" %) |(% colspan="2" style="width:1625px" %) 28 -|(% colspan="1" style="width:117px" %) |(% colspan="1" style="width:119px" %) |(% colspan="2" style="width:1625px" %) 29 -|(% colspan="1" style="width:117px" %)(% colspan="1" %) 30 -((( 31 -Scripts 32 -)))|(% colspan="1" style="width:119px" %)((( 33 -7.00 Beta 1 34 -)))|(% colspan="2" style="width:1625px" %)((( 35 -MD action **<set_presentation_cluster_persistence/>** now requires the cluster to be a presentation cluster. 22 +|=((( 23 +Type 24 +)))|=((( 25 +Version 26 +)))|=((( 27 +Summary 36 36 ))) 37 -|(% c lass="highlight-grey" colspan="4"data-highlight-colour="grey" title="Background colour :"%)(% class="highlight-grey" colspan="3"data-highlight-colour="grey" title="Background colour :"%)29 +|(% colspan="3" %)(% colspan="3" %) 38 38 ((( 39 - //Previously it was possible to set normal clusters to be persistent presentation clusters which was an invalid state.//31 +== 6.00 == 40 40 ))) 41 -|(% colspan="1" style="width:117px" %)(% colspan="1" %) 42 -((( 43 -UI extensions 44 -)))|(% colspan="1" style="width:119px" %)((( 45 -7.00 Beta 1 46 -)))|(% colspan="2" style="width:1625px" %)((( 47 -**FFI**: RemoveBuildPlot() changed 48 -))) 49 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 50 -((( 51 -// 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.// 52 -))) 53 -|(% colspan="1" style="width:117px" %)(% colspan="1" %) 54 -((( 55 -Assets 56 -)))|(% colspan="1" style="width:119px" %)((( 57 -7.00 Beta 1 58 -)))|(% colspan="2" style="width:1625px" %)((( 59 -**Some Split DLC materials moved to base game** 60 -))) 61 -|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 62 -((( 63 -// //"spl_p1_fx" AND "split_p1_hulltexture_01" were moved from Split DLC to base game 64 -))) 65 - 66 ----- 67 - 68 -=== Version 6.00 === 69 - 70 -(% class="wrapped" %) 71 71 |((( 72 -Libraries 73 -)))|((( 74 -6.00 Beta 7 75 -)))|(% colspan="2" %)((( 76 -Updated weights for ship groups in shipgroups.xml libraries of base game and all DLCs. 77 -))) 78 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 79 -((( 80 -//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.// 81 - 82 -//All groups should now have "weight" parameter added and old "weights" were updated to not have single-digit numbers.// 83 -))) 84 -|(% colspan="1" %)(% colspan="1" %) 85 -((( 86 -Scripts 87 -)))|(% colspan="1" %)(% colspan="1" %) 88 -((( 89 -6.00 Beta 4 90 -)))|(% colspan="2" %)(% colspan="1" %) 91 -((( 92 -Changed conditions for **<event_player_travelmode_started> <event_player_travelmode_stopped> <event_player_travelmode_charge_started> <event_player_travelmode_charge_aborted>** to be raised. 93 -))) 94 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 95 -((( 96 -//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. // 97 - 98 -//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.// 99 -))) 100 -|(% colspan="1" %)(% colspan="1" %) 101 -((( 102 -Scripts 103 -)))|(% colspan="1" %)(% colspan="1" %) 104 -((( 105 -6.00 Beta 3 106 -)))|(% colspan="2" %)(% colspan="1" %) 107 -((( 108 -Changed result of **<find_object_surface>** action in the case of a failure 109 -))) 110 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 111 -((( 112 -//The 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.// 113 - 114 -//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.// 115 - 116 -//The action itself has been improved to increase the chance of finding suitable surface positions.// 117 -))) 118 -|(% colspan="1" %)(% colspan="1" %) 119 -((( 120 -Scripts 121 -)))|(% colspan="1" %)(% colspan="1" %) 122 -((( 123 -6.00 Beta 1 124 -)))|(% colspan="2" %)(% colspan="1" %) 125 -((( 126 -Behaviour change for **<match_dock>** script component filter 127 -))) 128 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 129 -((( 130 -//<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes. 131 -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.// 132 -))) 133 -|(% colspan="1" %)(% colspan="1" %) 134 -((( 135 -Scripts 136 -)))|(% colspan="1" %)(% colspan="1" %) 137 -((( 138 -6.00 Beta 1 139 -)))|(% colspan="2" %)(% colspan="1" %) 140 -((( 141 -Changed result attribute location for **<get_attackstrength>** 142 -))) 143 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 144 -((( 145 -//The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.// 146 -))) 147 -|((( 148 148 Assets 149 149 )))|((( 150 150 6.00 Beta 1 151 -)))|( % colspan="2" %)(((37 +)))|((( 152 152 Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons 153 153 ))) 154 -|(% 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%" %)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" %) 155 155 ((( 156 156 //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. 157 157 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.// ... ... @@ -162,11 +162,11 @@ 162 162 )))|(% colspan="1" %)(% colspan="1" %) 163 163 ((( 164 164 6.00 Beta 1 165 -)))|(% colspan=" 2" %)(% colspan="1" %)51 +)))|(% colspan="1" %)(% colspan="1" %) 166 166 ((( 167 167 Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects 168 168 ))) 169 -|(% 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%" %)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" %) 170 170 ((( 171 171 //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.// 172 172 ))) ... ... @@ -174,10 +174,10 @@ 174 174 Scripts 175 175 )))|((( 176 176 6.00 Beta 1 177 -)))|( % colspan="2" %)(((63 +)))|((( 178 178 **<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards. 179 179 ))) 180 -|(% 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%" %)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" %) 181 181 ((( 182 182 //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.// 183 183 ))) ... ... @@ -185,36 +185,32 @@ 185 185 Cutscenes 186 186 )))|((( 187 187 6.00 Beta 1 188 -)))|( % colspan="2" %)(((74 +)))|((( 189 189 Changed behaviour of **<angles>** in cutscenes 190 190 ))) 191 -|(% c lass="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%" %)77 +|(% colspan="3" %)(% colspan="3" %) 192 192 ((( 193 - //The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.//79 +The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees. 194 194 ))) 195 - 196 ----- 197 - 198 -=== Version 5.00 === 199 - 200 -(% class="wrapped" %) 81 +|(% colspan="3" %)(% colspan="3" %) 82 +((( 83 +== 5.00 == 84 +))) 201 201 |((( 202 202 Parameters 203 203 )))|((( 204 204 5.00 Beta 1 205 -)))|( % colspan="2" %)(((89 +)))|((( 206 206 **<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration 207 207 ))) 208 -|(% class="highlight-grey" colspan=" 7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)92 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 209 209 ((( 210 210 //'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.// 211 211 ))) 212 - 213 ----- 214 - 215 -=== Version 4.10 === 216 - 217 -(% class="wrapped" %) 96 +|(% colspan="3" %)(% colspan="3" %) 97 +((( 98 +== 4.10 == 99 +))) 218 218 |(% colspan="1" %)(% colspan="1" %) 219 219 ((( 220 220 UI extensions ... ... @@ -221,13 +221,13 @@ 221 221 )))|(% colspan="1" %)(% colspan="1" %) 222 222 ((( 223 223 4.10 Beta 7 224 -)))|(% colspan=" 2" %)(% colspan="1" %)106 +)))|(% colspan="1" %)(% colspan="1" %) 225 225 ((( 226 -**FFI**: SetMapRenderCargoContents(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos() deprecated 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()(%%) deprecated 227 227 ))) 228 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)110 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 229 229 ((( 230 -//The functionality represented by SetMapRenderCargoContents(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos() has been removed and the function was therefore stubbed.// 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.// 231 231 ))) 232 232 |(% colspan="1" %)(% colspan="1" %) 233 233 ((( ... ... @@ -235,11 +235,11 @@ 235 235 )))|(% colspan="1" %)(% colspan="1" %) 236 236 ((( 237 237 4.10 Beta 6 238 -)))|(% colspan=" 2" %)(% colspan="1" %)120 +)))|(% colspan="1" %)(% colspan="1" %) 239 239 ((( 240 240 **FFI**: CustomGameStartPlayerProperty2 changed 241 241 ))) 242 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)124 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 243 243 ((( 244 244 //This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.// 245 245 ))) ... ... @@ -249,11 +249,11 @@ 249 249 )))|(% colspan="1" %)(% colspan="1" %) 250 250 ((( 251 251 4.10 Beta 3 252 -)))|(% colspan=" 2" %)(% colspan="1" %)134 +)))|(% colspan="1" %)(% colspan="1" %) 253 253 ((( 254 254 Renamed **<stationinfobox>** to **<infobox>** 255 255 ))) 256 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)138 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 257 257 ((( 258 258 //Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.// 259 259 ))) ... ... @@ -263,11 +263,11 @@ 263 263 )))|(% colspan="1" %)(% colspan="1" %) 264 264 ((( 265 265 4.10 Beta 2 266 -)))|(% colspan=" 2" %)(% colspan="1" %)148 +)))|(% colspan="1" %)(% colspan="1" %) 267 267 ((( 268 268 **FFI**: SetMacroMapPlayerSectorOffset() deprecated 269 269 ))) 270 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)152 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 271 271 ((( 272 272 //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.// 273 273 ))) ... ... @@ -275,10 +275,10 @@ 275 275 UI extensions 276 276 )))|((( 277 277 4.10 Beta 2 278 -)))|( % colspan="2" %)(((279 -**FFI**: FilterComponentForMapMode() and SetMapObjectFilter() changed 160 +)))|((( 161 +**FFI**: (% style="color: rgb(0,0,0);" %)FilterComponentForMapMode(%%)() and (% style="color: rgb(0,0,0);" %)SetMapObjectFilter() changed 280 280 ))) 281 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)163 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 282 282 ((( 283 283 //These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.// 284 284 ))) ... ... @@ -286,10 +286,10 @@ 286 286 Scripts 287 287 )))|((( 288 288 4.10 Beta 1 289 -)))|( % colspan="2" %)(((290 -People related attributes of mission** 171 +)))|((( 172 +People related attributes of mission** <delivery> **node moved 291 291 ))) 292 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)174 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 293 293 ((( 294 294 //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.// 295 295 ))) ... ... @@ -299,11 +299,11 @@ 299 299 )))|(% colspan="1" %)(% colspan="1" %) 300 300 ((( 301 301 4.10 Beta 1 302 -)))|(% colspan=" 2" %)(% colspan="1" %)184 +)))|(% colspan="1" %)(% colspan="1" %) 303 303 ((( 304 304 **$destructible.productions** replaced with $defensible.productions 305 305 ))) 306 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)188 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 307 307 ((( 308 308 //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.// 309 309 ))) ... ... @@ -311,19 +311,17 @@ 311 311 Scripts 312 312 )))|((( 313 313 4.10 Beta 1 314 -)))|( % colspan="2" %)(((196 +)))|((( 315 315 Removed script property **$object.spawnsourceseed** 316 316 ))) 317 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)199 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 318 318 ((( 319 319 //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.// 320 320 ))) 321 - 322 ----- 323 - 324 -=== Version 4.00 === 325 - 326 -(% class="wrapped" %) 203 +|(% colspan="3" %)(% colspan="3" %) 204 +((( 205 +== 4.00 == 206 +))) 327 327 |(% colspan="1" %)(% colspan="1" %) 328 328 ((( 329 329 UI core ... ... @@ -330,23 +330,24 @@ 330 330 )))|(% colspan="1" %)(% colspan="1" %) 331 331 ((( 332 332 4.00 Beta 10 333 -)))|(% colspan=" 2" %)(% colspan="1" %)213 +)))|(% colspan="1" %)(% colspan="1" %) 334 334 ((( 335 335 Controlled ship can change without a **gameplanchange-event** occurring. 336 336 ))) 337 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)217 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 338 338 ((( 339 339 //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). 340 -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.// 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 +// 341 341 ))) 342 342 |((( 343 343 Scripts 344 344 )))|((( 345 345 4.00 Beta 7 346 -)))|( % colspan="2" %)(((227 +)))|((( 347 347 Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed 348 348 ))) 349 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)230 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 350 350 ((( 351 351 //Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects? 352 352 New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits ... ... @@ -358,16 +358,17 @@ 358 358 )))|(% colspan="1" %)(% colspan="1" %) 359 359 ((( 360 360 4.00 Beta 6 361 -)))|(% colspan=" 2" %)(% colspan="1" %)242 +)))|(% colspan="1" %)(% colspan="1" %) 362 362 ((( 363 363 **FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed 364 364 ))) 365 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)246 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 366 366 ((( 367 367 //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. 368 368 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).// 369 369 370 -//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.// 251 +//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead. 252 +// 371 371 ))) 372 372 |(% colspan="1" %)(% colspan="1" %) 373 373 ((( ... ... @@ -375,11 +375,11 @@ 375 375 )))|(% colspan="1" %)(% colspan="1" %) 376 376 ((( 377 377 4.00 Beta 5 378 -)))|(% colspan=" 2" %)(% colspan="1" %)260 +)))|(% colspan="1" %)(% colspan="1" %) 379 379 ((( 380 380 **FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed 381 381 ))) 382 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)264 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 383 383 ((( 384 384 //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.// 385 385 ... ... @@ -389,10 +389,10 @@ 389 389 Parameters 390 390 )))|((( 391 391 4.00 Beta 1 392 -)))|( % colspan="2" %)(((274 +)))|((( 393 393 **requiresconstructionvessel** parameter moved 394 394 ))) 395 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)277 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 396 396 ((( 397 397 //The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.// 398 398 ))) ... ... @@ -400,44 +400,40 @@ 400 400 Scripts 401 401 )))|((( 402 402 4.00 Beta 1 403 -)))|( % colspan="2" %)(((285 +)))|((( 404 404 Changed behaviour of **gatedistance** script property 405 405 ))) 406 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)288 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 407 407 ((( 408 408 //The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.// 409 409 ))) 410 - 411 ----- 412 - 413 -=== Version 3.30 === 414 - 415 -(% class="wrapped" %) 292 +|(% colspan="3" %)(% colspan="3" %) 293 +((( 294 +== 3.30 == 295 +))) 416 416 |((( 417 417 UI extensions 418 418 )))|((( 419 419 3.30 Beta 3 420 -)))|( % colspan="2" %)(((421 -**FFI: **Removed** 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()** 422 422 ))) 423 -|(% class="highlight-grey" colspan=" 7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)303 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 424 424 ((( 425 -//These mission limit-related functions (added in 3.30 Beta 1 and 2) are replaced with FFI IsMissionLimitReached()// 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()// 426 426 ))) 427 - 428 ----- 429 - 430 -=== Version 3.20 === 431 - 432 -(% class="wrapped" %) 307 +|(% colspan="3" %)(% colspan="3" %) 308 +((( 309 +== 3.20 == 310 +))) 433 433 |((( 434 434 Scripts 435 435 )))|((( 436 436 3.20 Beta 1 437 -)))|( % colspan="2" %)(((315 +)))|((( 438 438 Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed 439 439 ))) 440 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)318 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 441 441 ((( 442 442 //Old params: param = attacked object, param2 = attack method, param3 = attacked component// 443 443 //New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon] ... ... @@ -449,11 +449,11 @@ 449 449 )))|(% colspan="1" %)(% colspan="1" %) 450 450 ((( 451 451 3.20 Beta 1 452 -)))|(% colspan=" 2" %)(% colspan="1" %)330 +)))|(% colspan="1" %)(% colspan="1" %) 453 453 ((( 454 454 Removed script property $trade.**restriction.faction** 455 455 ))) 456 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)334 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 457 457 ((( 458 458 //$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.// 459 459 ))) ... ... @@ -461,19 +461,17 @@ 461 461 UI extensions 462 462 )))|((( 463 463 3.20 Beta 1 464 -)))|( % colspan="2" %)(((342 +)))|((( 465 465 **Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete! 466 466 ))) 467 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)345 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 468 468 ((( 469 469 //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.// 470 470 ))) 471 - 472 ----- 473 - 474 -=== Version 3.10 === 475 - 476 -(% class="wrapped" %) 349 +|(% colspan="3" %)(% colspan="3" %) 350 +((( 351 +== 3.10 == 352 +))) 477 477 |(% colspan="1" %)(% colspan="1" %) 478 478 ((( 479 479 Scripts ... ... @@ -480,20 +480,18 @@ 480 480 )))|(% colspan="1" %)(% colspan="1" %) 481 481 ((( 482 482 3.10 Beta 1 483 -)))|(% colspan=" 2" %)(% colspan="1" %)359 +)))|(% colspan="1" %)(% colspan="1" %) 484 484 ((( 485 485 Removed script action **<add_build/>** 486 486 ))) 487 -|(% class="highlight-grey" colspan=" 7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)363 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 488 488 ((( 489 489 //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.// 490 490 ))) 491 - 492 ----- 493 - 494 -=== Version 3.00 === 495 - 496 -(% class="wrapped" %) 367 +|(% colspan="3" %)(% colspan="3" %) 368 +((( 369 +== 3.00 == 370 +))) 497 497 |(% colspan="1" %)(% colspan="1" %) 498 498 ((( 499 499 Scripts ... ... @@ -500,11 +500,11 @@ 500 500 )))|(% colspan="1" %)(% colspan="1" %) 501 501 ((( 502 502 3.0 Beta 6 503 -)))|(% colspan=" 2" %)(% colspan="1" %)377 +)))|(% colspan="1" %)(% colspan="1" %) 504 504 ((( 505 505 Changed behaviour of script action **<get_suitable_job/>** 506 506 ))) 507 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)381 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 508 508 ((( 509 509 //<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.// 510 510 ))) ... ... @@ -514,11 +514,11 @@ 514 514 )))|(% colspan="1" %)(% colspan="1" %) 515 515 ((( 516 516 3.0 Beta 6 517 -)))|(% colspan=" 2" %)(% colspan="1" %)391 +)))|(% colspan="1" %)(% colspan="1" %) 518 518 ((( 519 519 Changed behaviour of script action **<get_ware_definition/>** 520 520 ))) 521 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)395 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 522 522 ((( 523 523 //<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.// 524 524 ))) ... ... @@ -528,13 +528,13 @@ 528 528 )))|(% colspan="1" %)(% colspan="1" %) 529 529 ((( 530 530 3.0 Beta 5 531 -)))|(% colspan=" 2" %)(% colspan="1" %)405 +)))|(% colspan="1" %)(% colspan="1" %) 532 532 ((( 533 533 Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case 534 534 ))) 535 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)409 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 536 536 ((( 537 -//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.) 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.)\\ 538 538 539 539 //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).// 540 540 ))) ... ... @@ -544,11 +544,11 @@ 544 544 )))|(% colspan="1" %)(% colspan="1" %) 545 545 ((( 546 546 3.0 Beta 5 547 -)))|(% colspan=" 2" %)(% colspan="1" %)421 +)))|(% colspan="1" %)(% colspan="1" %) 548 548 ((( 549 549 Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions> 550 550 ))) 551 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)425 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 552 552 ((( 553 553 //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.// 554 554 ))) ... ... @@ -558,11 +558,11 @@ 558 558 )))|(% colspan="1" %)(% colspan="1" %) 559 559 ((( 560 560 3.0 Beta 5 561 -)))|(% colspan=" 2" %)(% colspan="1" %)435 +)))|(% colspan="1" %)(% colspan="1" %) 562 562 ((( 563 563 Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos** 564 564 ))) 565 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)439 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 566 566 ((( 567 567 //Before the change, positions are relative to $dockingbay.parent. 568 568 After the change, positions are relative to $dockingbay as specified in the documentation.// ... ... @@ -573,11 +573,11 @@ 573 573 )))|(% colspan="1" %)(% colspan="1" %) 574 574 ((( 575 575 3.0 Beta 2 576 -)))|(% colspan=" 2" %)(% colspan="1" %)450 +)))|(% colspan="1" %)(% colspan="1" %) 577 577 ((( 578 578 Support for entity flag "**skillsvisible**" dropped 579 579 ))) 580 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)454 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 581 581 ((( 582 582 //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().// 583 583 ))) ... ... @@ -585,10 +585,10 @@ 585 585 Scripts 586 586 )))|((( 587 587 3.0 Beta 2 588 -)))|( % colspan="2" %)(((462 +)))|((( 589 589 Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**. 590 590 ))) 591 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)465 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 592 592 ((( 593 593 //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. 594 594 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. ... ... @@ -601,11 +601,11 @@ 601 601 )))|(% colspan="1" %)(% colspan="1" %) 602 602 ((( 603 603 3.0 Beta 1 604 -)))|(% colspan=" 2" %)(% colspan="1" %)478 +)))|(% colspan="1" %)(% colspan="1" %) 605 605 ((( 606 606 **MissionBoard** support dropped 607 607 ))) 608 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)482 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 609 609 ((( 610 610 //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.// 611 611 ))) ... ... @@ -613,10 +613,10 @@ 613 613 Job/God 614 614 )))|((( 615 615 3.0 Beta 1 616 -)))|( % colspan="2" %)(((490 +)))|((( 617 617 By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined 618 618 ))) 619 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)493 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 620 620 ((( 621 621 //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.// 622 622 ))) ... ... @@ -626,11 +626,11 @@ 626 626 )))|(% colspan="1" %)(% colspan="1" %) 627 627 ((( 628 628 3.0 Beta 1 629 -)))|(% colspan=" 2" %)(% colspan="1" %)503 +)))|(% colspan="1" %)(% colspan="1" %) 630 630 ((( 631 631 Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'** 632 632 ))) 633 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)507 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 634 634 ((( 635 635 //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.// 636 636 ))) ... ... @@ -640,11 +640,11 @@ 640 640 )))|(% colspan="1" %)(% colspan="1" %) 641 641 ((( 642 642 3.0 Beta 1 643 -)))|(% colspan=" 2" %)(% colspan="1" %)517 +)))|(% colspan="1" %)(% colspan="1" %) 644 644 ((( 645 645 Script action **<set_doors_locked/>** attribute **'group'** changed 646 646 ))) 647 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)521 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 648 648 ((( 649 649 //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.// 650 650 ))) ... ... @@ -654,11 +654,11 @@ 654 654 )))|(% colspan="1" %)(% colspan="1" %) 655 655 ((( 656 656 3.0 Beta 1 657 -)))|(% colspan=" 2" %)(% colspan="1" %)531 +)))|(% colspan="1" %)(% colspan="1" %) 658 658 ((( 659 659 Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed 660 660 ))) 661 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)535 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 662 662 ((( 663 663 //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.// 664 664 ))) ... ... @@ -668,11 +668,11 @@ 668 668 )))|(% colspan="1" %)(% colspan="1" %) 669 669 ((( 670 670 3.0 Beta 1 671 -)))|(% colspan=" 2" %)(% colspan="1" %)545 +)))|(% colspan="1" %)(% colspan="1" %) 672 672 ((( 673 673 Script actions **<set_hack_target/>** and **<abort_hack/>** removed 674 674 ))) 675 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)549 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 676 676 ((( 677 677 //These actions had no effect and were removed.// 678 678 ))) ... ... @@ -682,11 +682,11 @@ 682 682 )))|(% colspan="1" %)(% colspan="1" %) 683 683 ((( 684 684 3.0 Beta 1 685 -)))|(% colspan=" 2" %)(% colspan="1" %)559 +)))|(% colspan="1" %)(% colspan="1" %) 686 686 ((( 687 687 **<setup_conversation_minigame/>** script action removed 688 688 ))) 689 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)563 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 690 690 ((( 691 691 //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.// 692 692 ))) ... ... @@ -696,11 +696,11 @@ 696 696 )))|(% colspan="1" %)(% colspan="1" %) 697 697 ((( 698 698 3.0 Beta 1 699 -)))|(% colspan=" 2" %)(% colspan="1" %)573 +)))|(% colspan="1" %)(% colspan="1" %) 700 700 ((( 701 701 <add_player_choice_*> **confidence** attribute removed 702 702 ))) 703 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)577 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 704 704 ((( 705 705 //The default confidence of player options is another leftover from the XR era and had no effect in X4.// 706 706 ))) ... ... @@ -710,11 +710,11 @@ 710 710 )))|(% colspan="1" %)(% colspan="1" %) 711 711 ((( 712 712 3.0 Beta 1 713 -)))|(% colspan=" 2" %)(% colspan="1" %)587 +)))|(% colspan="1" %)(% colspan="1" %) 714 714 ((( 715 715 **<hack_via_control_panel/>** script action removed 716 716 ))) 717 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)591 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 718 718 ((( 719 719 //Unused script action <hack_via_control_panel/> was removed.// 720 720 ))) ... ... @@ -724,11 +724,11 @@ 724 724 )))|(% colspan="1" %)(% colspan="1" %) 725 725 ((( 726 726 3.0 Beta 1 727 -)))|(% colspan=" 2" %)(% colspan="1" %)601 +)))|(% colspan="1" %)(% colspan="1" %) 728 728 ((( 729 729 **Lua: **GetMiniGameCursorPosition() removed 730 730 ))) 731 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)605 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 732 732 ((( 733 733 //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.// 734 734 ))) ... ... @@ -736,10 +736,10 @@ 736 736 UI core 737 737 )))|((( 738 738 3.0 Beta 1 739 -)))|( % colspan="2" %)(((613 +)))|((( 740 740 **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders 741 741 ))) 742 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)616 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 743 743 ((( 744 744 //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.// 745 745 ))) ... ... @@ -749,11 +749,11 @@ 749 749 )))|(% colspan="1" %)(% colspan="1" %) 750 750 ((( 751 751 3.0 Beta 1 752 -)))|(% colspan=" 2" %)(% colspan="1" %)626 +)))|(% colspan="1" %)(% colspan="1" %) 753 753 ((( 754 754 **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor 755 755 ))) 756 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)630 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 757 757 ((( 758 758 //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.// 759 759 ))) ... ... @@ -763,11 +763,11 @@ 763 763 )))|(% colspan="1" %)(% colspan="1" %) 764 764 ((( 765 765 3.0 Beta 1 766 -)))|(% colspan=" 2" %)(% colspan="1" %)640 +)))|(% colspan="1" %)(% colspan="1" %) 767 767 ((( 768 768 **$ware.illegal** updated 769 769 ))) 770 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)644 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 771 771 ((( 772 772 //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.// 773 773 //It now returns true if $ware is illegal to any faction in the game.// ... ... @@ -778,11 +778,11 @@ 778 778 )))|(% colspan="1" %)(% colspan="1" %) 779 779 ((( 780 780 3.0 Beta 1 781 -)))|(% colspan=" 2" %)(% colspan="1" %)655 +)))|(% colspan="1" %)(% colspan="1" %) 782 782 ((( 783 783 MD script **RML_Flight_Along_Path** removed 784 784 ))) 785 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)659 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 786 786 ((( 787 787 //The MD script RML_Flight_Along_Path was not referened and was removed.// 788 788 ))) ... ... @@ -792,11 +792,11 @@ 792 792 )))|(% colspan="1" %)(% colspan="1" %) 793 793 ((( 794 794 3.0 Beta 1 795 -)))|(% colspan=" 2" %)(% colspan="1" %)669 +)))|(% colspan="1" %)(% colspan="1" %) 796 796 ((( 797 797 parameters of **<event_venture_mission_completed/>** changed 798 798 ))) 799 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)673 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 800 800 ((( 801 801 //old params: param = venture details, param2 = ships involved, param3 = duration// 802 802 //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration// ... ... @@ -805,11 +805,11 @@ 805 805 Scripts 806 806 )))|((( 807 807 3.0 Beta 1 808 -)))|( % colspan="2" %)(((682 +)))|((( 809 809 **<set_object_wing_name/>** removed, 810 810 **<set_object_fleet_name/>** added 811 811 ))) 812 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)686 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 813 813 ((( 814 814 //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>// 815 815 ))) ... ... @@ -817,28 +817,26 @@ 817 817 Scripts 818 818 )))|((( 819 819 3.0 Beta 1 820 -)))|( % colspan="2" %)(((694 +)))|((( 821 821 **$controllable.wing.*** removed, 822 822 **$controllable.fleet.*** added 823 823 ))) 824 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)698 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 825 825 ((( 826 826 $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander 827 827 ))) 828 - 829 ----- 830 - 831 -=== Version 2.60 === 832 - 833 -(% class="wrapped" %) 702 +|(% colspan="3" %)(% colspan="3" %) 703 +((( 704 +== 2.60 == 705 +))) 834 834 |((( 835 835 Scripts 836 836 )))|((( 837 837 2.60 Beta 1 838 -)))|( % colspan="2" %)(((710 +)))|((( 839 839 '**checkoperational**' filter behaviour changed 840 840 ))) 841 -|(% class="highlight-grey" colspan=" 10" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)713 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 842 842 ((( 843 843 //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.// 844 844 ... ... @@ -848,19 +848,17 @@ 848 848 Scripts 849 849 )))|((( 850 850 2.60 Beta 1 851 -)))|( % colspan="2" %)(((723 +)))|((( 852 852 $container.**supplyresources** behavior changed 853 -))) | | |854 -|(% class="highlight-grey" colspan=" 10" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)725 +))) 726 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 855 855 ((( 856 856 //The script keyword $container.supplyresources now includes reserved wares.// 857 857 ))) 858 - 859 ----- 860 - 861 -=== Version 2.20 === 862 - 863 -(% class="wrapped" %) 730 +|(% colspan="3" %)(% colspan="3" %) 731 +((( 732 +== 2.20 == 733 +))) 864 864 |(% colspan="1" %)(% colspan="1" %) 865 865 ((( 866 866 UI core ... ... @@ -867,16 +867,17 @@ 867 867 )))|(% colspan="1" %)(% colspan="1" %) 868 868 ((( 869 869 2.20 Beta 3/4 870 -)))|(% colspan=" 2" %)(% colspan="1" %)740 +)))|(% colspan="1" %)(% colspan="1" %) 871 871 ((( 872 872 **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined. 873 873 ))) 874 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)744 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 875 875 ((( 876 876 //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. 877 877 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.// 878 878 879 -//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.// 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 +// 880 880 ))) 881 881 |(% colspan="1" %)(% colspan="1" %) 882 882 ((( ... ... @@ -884,20 +884,18 @@ 884 884 )))|(% colspan="1" %)(% colspan="1" %) 885 885 ((( 886 886 2.20 Beta 3 887 -)))|(% colspan=" 2" %)(% colspan="1" %)758 +)))|(% colspan="1" %)(% colspan="1" %) 888 888 ((( 889 889 Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor' 890 890 ))) 891 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)762 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 892 892 ((( 893 893 //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.// 894 894 ))) 895 - 896 ----- 897 - 898 -=== Version 2.00 === 899 - 900 -(% class="wrapped" %) 766 +|(% colspan="3" %)(% colspan="3" %) 767 +((( 768 +== 2.00 == 769 +))) 901 901 |(% colspan="1" %)(% colspan="1" %) 902 902 ((( 903 903 Scripts ... ... @@ -904,11 +904,11 @@ 904 904 )))|(% colspan="1" %)(% colspan="1" %) 905 905 ((( 906 906 2.00 Beta 1 907 -)))|(% colspan=" 2" %)(% colspan="1" %)776 +)))|(% colspan="1" %)(% colspan="1" %) 908 908 ((( 909 909 **<event_build_finished/> **param2 now returns null instead of a construction sequence 910 910 ))) 911 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)780 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 912 912 ((( 913 913 //The construction sequence which was finished should now be accessed via the buildtask provided via param3.// 914 914 ))) ... ... @@ -918,11 +918,11 @@ 918 918 )))|(% colspan="1" %)(% colspan="1" %) 919 919 ((( 920 920 2.00 Beta 1 921 -)))|(% colspan=" 2" %)(% colspan="1" %)790 +)))|(% colspan="1" %)(% colspan="1" %) 922 922 ((( 923 923 **param.boarding.{...}** strength parameters removed 924 924 ))) 925 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)794 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 926 926 ((( 927 927 //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.// 928 928 ))) ... ... @@ -932,11 +932,11 @@ 932 932 )))|(% colspan="1" %)(% colspan="1" %) 933 933 ((( 934 934 2.00 Beta 1 935 -)))|(% colspan=" 2" %)(% colspan="1" %)804 +)))|(% colspan="1" %)(% colspan="1" %) 936 936 ((( 937 937 **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed 938 938 ))) 939 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)808 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 940 940 ((( 941 941 //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.// 942 942 ))) ... ... @@ -944,10 +944,10 @@ 944 944 UI extensions 945 945 )))|((( 946 946 2.00 Beta 1 947 -)))|( % colspan="2" %)(((816 +)))|((( 948 948 **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals 949 949 ))) 950 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)819 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 951 951 ((( 952 952 //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.// 953 953 ))) ... ... @@ -955,10 +955,10 @@ 955 955 UI extensions 956 956 )))|((( 957 957 2.00 Beta 1 958 -)))|( % colspan="2" %)(((827 +)))|((( 959 959 **FFI: SetFormationShape()** no longer indicates an error upon certain error cases 960 960 ))) 961 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)830 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 962 962 ((( 963 963 //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.// 964 964 //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.// ... ... @@ -967,10 +967,10 @@ 967 967 Scripts 968 968 )))|((( 969 969 2.00 Beta 1 970 -)))|( % colspan="2" %)(((839 +)))|((( 971 971 **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated. 972 972 ))) 973 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)842 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 974 974 ((( 975 975 //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.// 976 976 ))) ... ... @@ -978,10 +978,10 @@ 978 978 Scripts 979 979 )))|((( 980 980 2.00 Beta 1 981 -)))|( % colspan="2" %)(((850 +)))|((( 982 982 **<event_player_changed_target/>** now fires and returns null if the player deselects a target. 983 983 ))) 984 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)853 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 985 985 ((( 986 986 //For prior behavior, check for event.param being non-null.// 987 987 ))) ... ... @@ -989,10 +989,10 @@ 989 989 AI Scripts 990 990 )))|((( 991 991 2.00 Beta 1 992 -)))|( % colspan="2" %)(((861 +)))|((( 993 993 **<shoot/>/<shoot_at/>** attribute changes. 994 994 ))) 995 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)864 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 996 996 ((( 997 997 //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.// 998 998 //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.// ... ... @@ -1004,10 +1004,10 @@ 1004 1004 UI extensions 1005 1005 )))|((( 1006 1006 2.00 Beta 1 1007 -)))|( % colspan="2" %)(((876 +)))|((( 1008 1008 **FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter. 1009 1009 ))) 1010 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)879 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1011 1011 ((( 1012 1012 //Added possibility to query build tasks of a certain buildmodule.// 1013 1013 ))) ... ... @@ -1015,10 +1015,10 @@ 1015 1015 UI extensions 1016 1016 )))|((( 1017 1017 2.00 Beta 1 1018 -)))|( % colspan="2" %)(((887 +)))|((( 1019 1019 **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field. 1020 1020 ))) 1021 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)890 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1022 1022 ((( 1023 1023 //Added list of resources a buildmodule needs to build.// 1024 1024 ))) ... ... @@ -1026,10 +1026,10 @@ 1026 1026 UI extensions 1027 1027 )))|((( 1028 1028 2.00 Beta 1 1029 -)))|( % colspan="2" %)(((1030 -**Lua: 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);" %) 1031 1031 ))) 1032 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)901 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1033 1033 ((( 1034 1034 //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.// 1035 1035 ))) ... ... @@ -1037,27 +1037,25 @@ 1037 1037 UI extensions 1038 1038 )))|((( 1039 1039 2.00 Beta 1 1040 -)))|( % colspan="2" %)(((1041 -**FFI: RequestDockAtReason()/UndockPlayerShip() **changed their return values. 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. 1042 1042 ))) 1043 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)912 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1044 1044 ((( 1045 1045 //Changed return value type to const char* to better identify failure reasons in Lua script.// 1046 1046 ))) 1047 - 1048 ----- 1049 - 1050 -=== Version 1.50 === 1051 - 1052 -(% class="wrapped" %) 916 +|(% colspan="3" %)(% colspan="3" %) 917 +((( 918 +== 1.50 == 919 +))) 1053 1053 |((( 1054 1054 UI extensions 1055 1055 )))|((( 1056 1056 1.50 Beta 3 1057 -)))|( % colspan="2" %)(((924 +)))|((( 1058 1058 **Lua: GetComponentData() **changed behavior of "docksizes" property. 1059 1059 ))) 1060 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)927 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1061 1061 ((( 1062 1062 //The "docksizes" property no longer includes internal ship storage docks.// 1063 1063 ))) ... ... @@ -1065,10 +1065,10 @@ 1065 1065 All 1066 1066 )))|((( 1067 1067 1.50 Beta 2 1068 -)))|( % colspan="2" %)(((935 +)))|((( 1069 1069 **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR). 1070 1070 ))) 1071 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)938 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1072 1072 ((( 1073 1073 //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".// 1074 1074 ... ... @@ -1080,10 +1080,10 @@ 1080 1080 UI extensions 1081 1081 )))|((( 1082 1082 1.50 Beta 2 1083 -)))|( % colspan="2" %)(((950 +)))|((( 1084 1084 **FFI: UpgradeGroupInfo **datatype was changed. 1085 1085 ))) 1086 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)953 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1087 1087 ((( 1088 1088 //Added new "operational" field to retrieve information about number of operational upgrades in a group.// 1089 1089 ))) ... ... @@ -1093,13 +1093,14 @@ 1093 1093 )))|(% colspan="1" %)(% colspan="1" %) 1094 1094 ((( 1095 1095 1.50 Beta 1 1096 -)))|(% colspan=" 2" %)(% colspan="1" %)963 +)))|(% colspan="1" %)(% colspan="1" %) 1097 1097 ((( 1098 1098 **FFI: SetGuidance()** removed useinfopoint argument. 1099 1099 ))) 1100 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)967 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1101 1101 ((( 1102 -//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.// 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 +// 1103 1103 1104 1104 //The new function declaration is: void SetGuidance(UniverseID componentid, UIPosRot offset)// 1105 1105 ))) ... ... @@ -1107,44 +1107,40 @@ 1107 1107 UI extensions 1108 1108 )))|((( 1109 1109 1.50 Beta 1 1110 -)))|( % colspan="2" %)(((978 +)))|((( 1111 1111 **FFI: CancelConstruction() **changed its return value. 1112 1112 ))) 1113 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)981 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1114 1114 ((( 1115 -//CancelConstruction() now returns if the cancellation was successful. // 983 +(% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. // 1116 1116 ))) 1117 - 1118 ----- 1119 - 1120 -=== Version 1.32 === 1121 - 1122 -(% class="wrapped" %) 985 +|(% colspan="3" %)(% colspan="3" %) 986 +((( 987 +== 1.32 == 988 +))) 1123 1123 |((( 1124 1124 UI extensions 1125 1125 )))|((( 1126 1126 1.32 1127 -)))|( % colspan="2" %)(((993 +)))|((( 1128 1128 **Lua: GetComponentData() **removed the "nextdestname" property. 1129 1129 ))) 1130 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)996 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1131 1131 ((( 1132 1132 //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.// 1133 1133 ))) 1134 - 1135 ----- 1136 - 1137 -=== Version 1.20 === 1138 - 1139 -(% class="wrapped" %) 1000 +|(% colspan="3" %)(% colspan="3" %) 1001 +((( 1002 +== 1.20 == 1003 +))) 1140 1140 |((( 1141 1141 UI extensions 1142 1142 )))|((( 1143 1143 1.20 1144 -)))|( % colspan="2" %)(((1008 +)))|((( 1145 1145 **FFI: GetAAOption()** got a new "useconfig" parameter. 1146 1146 ))) 1147 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1011 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1148 1148 ((( 1149 -//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.// 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.// 1150 1150 )))
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 - 785778541 +135862009 - url
-
... ... @@ -1,1 +1,1 @@ 1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/ 78577854/Breaking Changes1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/135862009/Breaking Changes