Changes for page Breaking Changes
Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 107.1
edited by Daniel Turner
on 2023/09/05 15:49
on 2023/09/05 15:49
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -xwiki:XWiki. Daniel1 +xwiki:XWiki.Ketraar - Content
-
... ... @@ -18,26 +18,35 @@ 18 18 19 19 = Breaking Changes = 20 20 21 +=== 7.00 === 22 + 21 21 (% class="wrapped" %) 22 22 |=((( 23 23 Type 24 -)))|=((( 25 -Version 26 -)))|=((( 27 -Summary 28 28 ))) 29 -|(% colspan=" 3" %)(% colspan="3" %)27 +|(% colspan="1" %)(% colspan="1" %) 30 30 ((( 31 - ==6.00 ==29 +UI extensions 32 32 ))) 31 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 32 +((( 33 +// 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.// 34 +))) 35 + 36 +---- 37 + 38 +=== 6.00 === 39 + 40 + 41 +(% class="wrapped" %) 33 33 |((( 34 34 Libraries 35 35 )))|((( 36 36 6.00 Beta 7 37 -)))|((( 46 +)))|(% colspan="2" %)((( 38 38 Updated weights for ship groups in shipgroups.xml libraries of base game and all DLCs. 39 39 ))) 40 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)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 :" %) 41 41 ((( 42 42 //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.// 43 43 ... ... @@ -49,11 +49,11 @@ 49 49 )))|(% colspan="1" %)(% colspan="1" %) 50 50 ((( 51 51 6.00 Beta 4 52 -)))|(% colspan=" 1" %)(% colspan="1" %)61 +)))|(% colspan="2" %)(% colspan="1" %) 53 53 ((( 54 54 Changed conditions for **<event_player_travelmode_started> <event_player_travelmode_stopped> <event_player_travelmode_charge_started> <event_player_travelmode_charge_aborted>** to be raised. 55 55 ))) 56 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)65 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 57 57 ((( 58 58 //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. // 59 59 ... ... @@ -65,11 +65,11 @@ 65 65 )))|(% colspan="1" %)(% colspan="1" %) 66 66 ((( 67 67 6.00 Beta 3 68 -)))|(% colspan=" 1" %)(% colspan="1" %)77 +)))|(% colspan="2" %)(% colspan="1" %) 69 69 ((( 70 70 Changed result of **<find_object_surface>** action in the case of a failure 71 71 ))) 72 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)81 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 73 73 ((( 74 74 //The 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.// 75 75 ... ... @@ -83,11 +83,11 @@ 83 83 )))|(% colspan="1" %)(% colspan="1" %) 84 84 ((( 85 85 6.00 Beta 1 86 -)))|(% colspan=" 1" %)(% colspan="1" %)95 +)))|(% colspan="2" %)(% colspan="1" %) 87 87 ((( 88 88 Behaviour change for **<match_dock>** script component filter 89 89 ))) 90 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)99 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 91 91 ((( 92 92 //<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes. 93 93 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.// ... ... @@ -98,11 +98,11 @@ 98 98 )))|(% colspan="1" %)(% colspan="1" %) 99 99 ((( 100 100 6.00 Beta 1 101 -)))|(% colspan=" 1" %)(% colspan="1" %)110 +)))|(% colspan="2" %)(% colspan="1" %) 102 102 ((( 103 103 Changed result attribute location for **<get_attackstrength>** 104 104 ))) 105 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)114 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 106 106 ((( 107 107 //The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.// 108 108 ))) ... ... @@ -110,10 +110,10 @@ 110 110 Assets 111 111 )))|((( 112 112 6.00 Beta 1 113 -)))|((( 122 +)))|(% colspan="2" %)((( 114 114 Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons 115 115 ))) 116 -|(% class="highlight-grey" colspan=" 3" 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 +|(% 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%" %) 117 117 ((( 118 118 //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. 119 119 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.// ... ... @@ -124,11 +124,11 @@ 124 124 )))|(% colspan="1" %)(% colspan="1" %) 125 125 ((( 126 126 6.00 Beta 1 127 -)))|(% colspan=" 1" %)(% colspan="1" %)136 +)))|(% colspan="2" %)(% colspan="1" %) 128 128 ((( 129 129 Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects 130 130 ))) 131 -|(% class="highlight-grey" colspan=" 3" 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%" %)140 +|(% 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%" %) 132 132 ((( 133 133 //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.// 134 134 ))) ... ... @@ -136,10 +136,10 @@ 136 136 Scripts 137 137 )))|((( 138 138 6.00 Beta 1 139 -)))|((( 148 +)))|(% colspan="2" %)((( 140 140 **<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards. 141 141 ))) 142 -|(% class="highlight-grey" colspan=" 3" 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%" %)151 +|(% 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%" %) 143 143 ((( 144 144 //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.// 145 145 ))) ... ... @@ -147,32 +147,36 @@ 147 147 Cutscenes 148 148 )))|((( 149 149 6.00 Beta 1 150 -)))|((( 159 +)))|(% colspan="2" %)((( 151 151 Changed behaviour of **<angles>** in cutscenes 152 152 ))) 153 -|(% class="highlight-grey" colspan=" 3" 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%" %)162 +|(% 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%" %) 154 154 ((( 155 155 //The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.// 156 156 ))) 157 -|(% colspan="3" %)(% colspan="3" %) 158 -((( 159 -== 5.00 == 160 -))) 166 + 167 +---- 168 + 169 +=== 5.00 === 170 + 171 +(% class="wrapped" %) 161 161 |((( 162 162 Parameters 163 163 )))|((( 164 164 5.00 Beta 1 165 -)))|((( 176 +)))|(% colspan="2" %)((( 166 166 **<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration 167 167 ))) 168 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)179 +|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 169 169 ((( 170 170 //'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.// 171 171 ))) 172 -|(% colspan="3" %)(% colspan="3" %) 173 -((( 174 -== 4.10 == 175 -))) 183 + 184 +---- 185 + 186 +=== 4.10 === 187 + 188 +(% class="wrapped" %) 176 176 |(% colspan="1" %)(% colspan="1" %) 177 177 ((( 178 178 UI extensions ... ... @@ -179,13 +179,13 @@ 179 179 )))|(% colspan="1" %)(% colspan="1" %) 180 180 ((( 181 181 4.10 Beta 7 182 -)))|(% colspan=" 1" %)(% colspan="1" %)195 +)))|(% colspan="2" %)(% colspan="1" %) 183 183 ((( 184 -**FFI**: SetMapRenderCargoContents( %%)(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos()(%%)deprecated197 +**FFI**: SetMapRenderCargoContents(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos() deprecated 185 185 ))) 186 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)199 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 187 187 ((( 188 -//The functionality represented by SetMapRenderCargoContents( %%)(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos()(%%)has been removed and the function was therefore stubbed.//201 +//The functionality represented by SetMapRenderCargoContents(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos() has been removed and the function was therefore stubbed.// 189 189 ))) 190 190 |(% colspan="1" %)(% colspan="1" %) 191 191 ((( ... ... @@ -193,11 +193,11 @@ 193 193 )))|(% colspan="1" %)(% colspan="1" %) 194 194 ((( 195 195 4.10 Beta 6 196 -)))|(% colspan=" 1" %)(% colspan="1" %)209 +)))|(% colspan="2" %)(% colspan="1" %) 197 197 ((( 198 198 **FFI**: CustomGameStartPlayerProperty2 changed 199 199 ))) 200 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)213 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 201 201 ((( 202 202 //This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.// 203 203 ))) ... ... @@ -207,11 +207,11 @@ 207 207 )))|(% colspan="1" %)(% colspan="1" %) 208 208 ((( 209 209 4.10 Beta 3 210 -)))|(% colspan=" 1" %)(% colspan="1" %)223 +)))|(% colspan="2" %)(% colspan="1" %) 211 211 ((( 212 212 Renamed **<stationinfobox>** to **<infobox>** 213 213 ))) 214 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)227 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 215 215 ((( 216 216 //Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.// 217 217 ))) ... ... @@ -221,11 +221,11 @@ 221 221 )))|(% colspan="1" %)(% colspan="1" %) 222 222 ((( 223 223 4.10 Beta 2 224 -)))|(% colspan=" 1" %)(% colspan="1" %)237 +)))|(% colspan="2" %)(% colspan="1" %) 225 225 ((( 226 226 **FFI**: SetMacroMapPlayerSectorOffset() deprecated 227 227 ))) 228 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)241 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 229 229 ((( 230 230 //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.// 231 231 ))) ... ... @@ -233,10 +233,10 @@ 233 233 UI extensions 234 234 )))|((( 235 235 4.10 Beta 2 236 -)))|((( 237 -**FFI**: FilterComponentForMapMode( %%)()and SetMapObjectFilter() changed249 +)))|(% colspan="2" %)((( 250 +**FFI**: FilterComponentForMapMode() and SetMapObjectFilter() changed 238 238 ))) 239 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)252 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 240 240 ((( 241 241 //These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.// 242 242 ))) ... ... @@ -244,10 +244,10 @@ 244 244 Scripts 245 245 )))|((( 246 246 4.10 Beta 1 247 -)))|((( 260 +)))|(% colspan="2" %)((( 248 248 People related attributes of mission** <delivery> **node moved 249 249 ))) 250 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)263 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 251 251 ((( 252 252 //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.// 253 253 ))) ... ... @@ -257,11 +257,11 @@ 257 257 )))|(% colspan="1" %)(% colspan="1" %) 258 258 ((( 259 259 4.10 Beta 1 260 -)))|(% colspan=" 1" %)(% colspan="1" %)273 +)))|(% colspan="2" %)(% colspan="1" %) 261 261 ((( 262 262 **$destructible.productions** replaced with $defensible.productions 263 263 ))) 264 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)277 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 265 265 ((( 266 266 //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.// 267 267 ))) ... ... @@ -269,17 +269,19 @@ 269 269 Scripts 270 270 )))|((( 271 271 4.10 Beta 1 272 -)))|((( 285 +)))|(% colspan="2" %)((( 273 273 Removed script property **$object.spawnsourceseed** 274 274 ))) 275 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)288 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 276 276 ((( 277 277 //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.// 278 278 ))) 279 -|(% colspan="3" %)(% colspan="3" %) 280 -((( 281 -== 4.00 == 282 -))) 292 + 293 +---- 294 + 295 +=== 4.00 === 296 + 297 +(% class="wrapped" %) 283 283 |(% colspan="1" %)(% colspan="1" %) 284 284 ((( 285 285 UI core ... ... @@ -286,11 +286,11 @@ 286 286 )))|(% colspan="1" %)(% colspan="1" %) 287 287 ((( 288 288 4.00 Beta 10 289 -)))|(% colspan=" 1" %)(% colspan="1" %)304 +)))|(% colspan="2" %)(% colspan="1" %) 290 290 ((( 291 291 Controlled ship can change without a **gameplanchange-event** occurring. 292 292 ))) 293 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)308 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 294 294 ((( 295 295 //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). 296 296 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.// ... ... @@ -299,10 +299,10 @@ 299 299 Scripts 300 300 )))|((( 301 301 4.00 Beta 7 302 -)))|((( 317 +)))|(% colspan="2" %)((( 303 303 Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed 304 304 ))) 305 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)320 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 306 306 ((( 307 307 //Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects? 308 308 New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits ... ... @@ -314,11 +314,11 @@ 314 314 )))|(% colspan="1" %)(% colspan="1" %) 315 315 ((( 316 316 4.00 Beta 6 317 -)))|(% colspan=" 1" %)(% colspan="1" %)332 +)))|(% colspan="2" %)(% colspan="1" %) 318 318 ((( 319 319 **FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed 320 320 ))) 321 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)336 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 322 322 ((( 323 323 //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. 324 324 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).// ... ... @@ -331,11 +331,11 @@ 331 331 )))|(% colspan="1" %)(% colspan="1" %) 332 332 ((( 333 333 4.00 Beta 5 334 -)))|(% colspan=" 1" %)(% colspan="1" %)349 +)))|(% colspan="2" %)(% colspan="1" %) 335 335 ((( 336 336 **FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed 337 337 ))) 338 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)353 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 339 339 ((( 340 340 //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.// 341 341 ... ... @@ -345,10 +345,10 @@ 345 345 Parameters 346 346 )))|((( 347 347 4.00 Beta 1 348 -)))|((( 363 +)))|(% colspan="2" %)((( 349 349 **requiresconstructionvessel** parameter moved 350 350 ))) 351 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)366 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 352 352 ((( 353 353 //The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.// 354 354 ))) ... ... @@ -356,40 +356,44 @@ 356 356 Scripts 357 357 )))|((( 358 358 4.00 Beta 1 359 -)))|((( 374 +)))|(% colspan="2" %)((( 360 360 Changed behaviour of **gatedistance** script property 361 361 ))) 362 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)377 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 363 363 ((( 364 364 //The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.// 365 365 ))) 366 -|(% colspan="3" %)(% colspan="3" %) 367 -((( 368 -== 3.30 == 369 -))) 381 + 382 +---- 383 + 384 +=== 3.30 === 385 + 386 +(% class="wrapped" %) 370 370 |((( 371 371 UI extensions 372 372 )))|((( 373 373 3.30 Beta 3 374 -)))|((( 375 -**FFI: **Removed** (%%)**and** IsMissionLimit**(%%)**Enabled()**391 +)))|(% colspan="2" %)((( 392 +**FFI: **Removed** GetMissionLimit() **and** IsMissionLimitEnabled()** 376 376 ))) 377 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)394 +|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 378 378 ((( 379 -//These mission limit-related functions (added in 3.30 Beta 1 and 2) are replaced with FFI IsMissionLimit (%%)Reached()//396 +//These mission limit-related functions (added in 3.30 Beta 1 and 2) are replaced with FFI IsMissionLimitReached()// 380 380 ))) 381 -|(% colspan="3" %)(% colspan="3" %) 382 -((( 383 -== 3.20 == 384 -))) 398 + 399 +---- 400 + 401 +=== 3.20 === 402 + 403 +(% class="wrapped" %) 385 385 |((( 386 386 Scripts 387 387 )))|((( 388 388 3.20 Beta 1 389 -)))|((( 408 +)))|(% colspan="2" %)((( 390 390 Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed 391 391 ))) 392 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)411 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 393 393 ((( 394 394 //Old params: param = attacked object, param2 = attack method, param3 = attacked component// 395 395 //New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon] ... ... @@ -401,11 +401,11 @@ 401 401 )))|(% colspan="1" %)(% colspan="1" %) 402 402 ((( 403 403 3.20 Beta 1 404 -)))|(% colspan=" 1" %)(% colspan="1" %)423 +)))|(% colspan="2" %)(% colspan="1" %) 405 405 ((( 406 406 Removed script property $trade.**restriction.faction** 407 407 ))) 408 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)427 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 409 409 ((( 410 410 //$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.// 411 411 ))) ... ... @@ -413,17 +413,19 @@ 413 413 UI extensions 414 414 )))|((( 415 415 3.20 Beta 1 416 -)))|((( 435 +)))|(% colspan="2" %)((( 417 417 **Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete! 418 418 ))) 419 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)438 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 420 420 ((( 421 421 //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.// 422 422 ))) 423 -|(% colspan="3" %)(% colspan="3" %) 424 -((( 425 -== 3.10 == 426 -))) 442 + 443 +---- 444 + 445 +=== 3.10 === 446 + 447 +(% class="wrapped" %) 427 427 |(% colspan="1" %)(% colspan="1" %) 428 428 ((( 429 429 Scripts ... ... @@ -430,18 +430,20 @@ 430 430 )))|(% colspan="1" %)(% colspan="1" %) 431 431 ((( 432 432 3.10 Beta 1 433 -)))|(% colspan=" 1" %)(% colspan="1" %)454 +)))|(% colspan="2" %)(% colspan="1" %) 434 434 ((( 435 435 Removed script action **<add_build/>** 436 436 ))) 437 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)458 +|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 438 438 ((( 439 439 //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.// 440 440 ))) 441 -|(% colspan="3" %)(% colspan="3" %) 442 -((( 443 -== 3.00 == 444 -))) 462 + 463 +---- 464 + 465 +=== 3.00 === 466 + 467 +(% class="wrapped" %) 445 445 |(% colspan="1" %)(% colspan="1" %) 446 446 ((( 447 447 Scripts ... ... @@ -448,11 +448,11 @@ 448 448 )))|(% colspan="1" %)(% colspan="1" %) 449 449 ((( 450 450 3.0 Beta 6 451 -)))|(% colspan=" 1" %)(% colspan="1" %)474 +)))|(% colspan="2" %)(% colspan="1" %) 452 452 ((( 453 453 Changed behaviour of script action **<get_suitable_job/>** 454 454 ))) 455 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)478 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 456 456 ((( 457 457 //<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.// 458 458 ))) ... ... @@ -462,11 +462,11 @@ 462 462 )))|(% colspan="1" %)(% colspan="1" %) 463 463 ((( 464 464 3.0 Beta 6 465 -)))|(% colspan=" 1" %)(% colspan="1" %)488 +)))|(% colspan="2" %)(% colspan="1" %) 466 466 ((( 467 467 Changed behaviour of script action **<get_ware_definition/>** 468 468 ))) 469 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)492 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 470 470 ((( 471 471 //<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.// 472 472 ))) ... ... @@ -476,11 +476,11 @@ 476 476 )))|(% colspan="1" %)(% colspan="1" %) 477 477 ((( 478 478 3.0 Beta 5 479 -)))|(% colspan=" 1" %)(% colspan="1" %)502 +)))|(% colspan="2" %)(% colspan="1" %) 480 480 ((( 481 481 Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case 482 482 ))) 483 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)506 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 484 484 ((( 485 485 //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.) 486 486 ... ... @@ -492,11 +492,11 @@ 492 492 )))|(% colspan="1" %)(% colspan="1" %) 493 493 ((( 494 494 3.0 Beta 5 495 -)))|(% colspan=" 1" %)(% colspan="1" %)518 +)))|(% colspan="2" %)(% colspan="1" %) 496 496 ((( 497 497 Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions> 498 498 ))) 499 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)522 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 500 500 ((( 501 501 //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.// 502 502 ))) ... ... @@ -506,11 +506,11 @@ 506 506 )))|(% colspan="1" %)(% colspan="1" %) 507 507 ((( 508 508 3.0 Beta 5 509 -)))|(% colspan=" 1" %)(% colspan="1" %)532 +)))|(% colspan="2" %)(% colspan="1" %) 510 510 ((( 511 511 Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos** 512 512 ))) 513 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)536 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 514 514 ((( 515 515 //Before the change, positions are relative to $dockingbay.parent. 516 516 After the change, positions are relative to $dockingbay as specified in the documentation.// ... ... @@ -521,11 +521,11 @@ 521 521 )))|(% colspan="1" %)(% colspan="1" %) 522 522 ((( 523 523 3.0 Beta 2 524 -)))|(% colspan=" 1" %)(% colspan="1" %)547 +)))|(% colspan="2" %)(% colspan="1" %) 525 525 ((( 526 526 Support for entity flag "**skillsvisible**" dropped 527 527 ))) 528 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)551 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 529 529 ((( 530 530 //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().// 531 531 ))) ... ... @@ -533,10 +533,10 @@ 533 533 Scripts 534 534 )))|((( 535 535 3.0 Beta 2 536 -)))|((( 559 +)))|(% colspan="2" %)((( 537 537 Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**. 538 538 ))) 539 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)562 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 540 540 ((( 541 541 //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. 542 542 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. ... ... @@ -549,11 +549,11 @@ 549 549 )))|(% colspan="1" %)(% colspan="1" %) 550 550 ((( 551 551 3.0 Beta 1 552 -)))|(% colspan=" 1" %)(% colspan="1" %)575 +)))|(% colspan="2" %)(% colspan="1" %) 553 553 ((( 554 554 **MissionBoard** support dropped 555 555 ))) 556 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)579 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 557 557 ((( 558 558 //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.// 559 559 ))) ... ... @@ -561,10 +561,10 @@ 561 561 Job/God 562 562 )))|((( 563 563 3.0 Beta 1 564 -)))|((( 587 +)))|(% colspan="2" %)((( 565 565 By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined 566 566 ))) 567 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)590 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 568 568 ((( 569 569 //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.// 570 570 ))) ... ... @@ -574,11 +574,11 @@ 574 574 )))|(% colspan="1" %)(% colspan="1" %) 575 575 ((( 576 576 3.0 Beta 1 577 -)))|(% colspan=" 1" %)(% colspan="1" %)600 +)))|(% colspan="2" %)(% colspan="1" %) 578 578 ((( 579 579 Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'** 580 580 ))) 581 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)604 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 582 582 ((( 583 583 //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.// 584 584 ))) ... ... @@ -588,11 +588,11 @@ 588 588 )))|(% colspan="1" %)(% colspan="1" %) 589 589 ((( 590 590 3.0 Beta 1 591 -)))|(% colspan=" 1" %)(% colspan="1" %)614 +)))|(% colspan="2" %)(% colspan="1" %) 592 592 ((( 593 593 Script action **<set_doors_locked/>** attribute **'group'** changed 594 594 ))) 595 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)618 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 596 596 ((( 597 597 //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.// 598 598 ))) ... ... @@ -602,11 +602,11 @@ 602 602 )))|(% colspan="1" %)(% colspan="1" %) 603 603 ((( 604 604 3.0 Beta 1 605 -)))|(% colspan=" 1" %)(% colspan="1" %)628 +)))|(% colspan="2" %)(% colspan="1" %) 606 606 ((( 607 607 Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed 608 608 ))) 609 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)632 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 610 610 ((( 611 611 //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.// 612 612 ))) ... ... @@ -616,11 +616,11 @@ 616 616 )))|(% colspan="1" %)(% colspan="1" %) 617 617 ((( 618 618 3.0 Beta 1 619 -)))|(% colspan=" 1" %)(% colspan="1" %)642 +)))|(% colspan="2" %)(% colspan="1" %) 620 620 ((( 621 621 Script actions **<set_hack_target/>** and **<abort_hack/>** removed 622 622 ))) 623 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)646 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 624 624 ((( 625 625 //These actions had no effect and were removed.// 626 626 ))) ... ... @@ -630,11 +630,11 @@ 630 630 )))|(% colspan="1" %)(% colspan="1" %) 631 631 ((( 632 632 3.0 Beta 1 633 -)))|(% colspan=" 1" %)(% colspan="1" %)656 +)))|(% colspan="2" %)(% colspan="1" %) 634 634 ((( 635 635 **<setup_conversation_minigame/>** script action removed 636 636 ))) 637 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)660 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 638 638 ((( 639 639 //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.// 640 640 ))) ... ... @@ -644,11 +644,11 @@ 644 644 )))|(% colspan="1" %)(% colspan="1" %) 645 645 ((( 646 646 3.0 Beta 1 647 -)))|(% colspan=" 1" %)(% colspan="1" %)670 +)))|(% colspan="2" %)(% colspan="1" %) 648 648 ((( 649 649 <add_player_choice_*> **confidence** attribute removed 650 650 ))) 651 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)674 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 652 652 ((( 653 653 //The default confidence of player options is another leftover from the XR era and had no effect in X4.// 654 654 ))) ... ... @@ -658,11 +658,11 @@ 658 658 )))|(% colspan="1" %)(% colspan="1" %) 659 659 ((( 660 660 3.0 Beta 1 661 -)))|(% colspan=" 1" %)(% colspan="1" %)684 +)))|(% colspan="2" %)(% colspan="1" %) 662 662 ((( 663 663 **<hack_via_control_panel/>** script action removed 664 664 ))) 665 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)688 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 666 666 ((( 667 667 //Unused script action <hack_via_control_panel/> was removed.// 668 668 ))) ... ... @@ -672,11 +672,11 @@ 672 672 )))|(% colspan="1" %)(% colspan="1" %) 673 673 ((( 674 674 3.0 Beta 1 675 -)))|(% colspan=" 1" %)(% colspan="1" %)698 +)))|(% colspan="2" %)(% colspan="1" %) 676 676 ((( 677 677 **Lua: **GetMiniGameCursorPosition() removed 678 678 ))) 679 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)702 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 680 680 ((( 681 681 //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.// 682 682 ))) ... ... @@ -684,10 +684,10 @@ 684 684 UI core 685 685 )))|((( 686 686 3.0 Beta 1 687 -)))|((( 710 +)))|(% colspan="2" %)((( 688 688 **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders 689 689 ))) 690 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)713 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 691 691 ((( 692 692 //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.// 693 693 ))) ... ... @@ -697,11 +697,11 @@ 697 697 )))|(% colspan="1" %)(% colspan="1" %) 698 698 ((( 699 699 3.0 Beta 1 700 -)))|(% colspan=" 1" %)(% colspan="1" %)723 +)))|(% colspan="2" %)(% colspan="1" %) 701 701 ((( 702 702 **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor 703 703 ))) 704 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)727 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 705 705 ((( 706 706 //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.// 707 707 ))) ... ... @@ -711,11 +711,11 @@ 711 711 )))|(% colspan="1" %)(% colspan="1" %) 712 712 ((( 713 713 3.0 Beta 1 714 -)))|(% colspan=" 1" %)(% colspan="1" %)737 +)))|(% colspan="2" %)(% colspan="1" %) 715 715 ((( 716 716 **$ware.illegal** updated 717 717 ))) 718 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)741 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 719 719 ((( 720 720 //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.// 721 721 //It now returns true if $ware is illegal to any faction in the game.// ... ... @@ -726,11 +726,11 @@ 726 726 )))|(% colspan="1" %)(% colspan="1" %) 727 727 ((( 728 728 3.0 Beta 1 729 -)))|(% colspan=" 1" %)(% colspan="1" %)752 +)))|(% colspan="2" %)(% colspan="1" %) 730 730 ((( 731 731 MD script **RML_Flight_Along_Path** removed 732 732 ))) 733 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)756 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 734 734 ((( 735 735 //The MD script RML_Flight_Along_Path was not referened and was removed.// 736 736 ))) ... ... @@ -740,11 +740,11 @@ 740 740 )))|(% colspan="1" %)(% colspan="1" %) 741 741 ((( 742 742 3.0 Beta 1 743 -)))|(% colspan=" 1" %)(% colspan="1" %)766 +)))|(% colspan="2" %)(% colspan="1" %) 744 744 ((( 745 745 parameters of **<event_venture_mission_completed/>** changed 746 746 ))) 747 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)770 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 748 748 ((( 749 749 //old params: param = venture details, param2 = ships involved, param3 = duration// 750 750 //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration// ... ... @@ -753,11 +753,11 @@ 753 753 Scripts 754 754 )))|((( 755 755 3.0 Beta 1 756 -)))|((( 779 +)))|(% colspan="2" %)((( 757 757 **<set_object_wing_name/>** removed, 758 758 **<set_object_fleet_name/>** added 759 759 ))) 760 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)783 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 761 761 ((( 762 762 //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>// 763 763 ))) ... ... @@ -765,26 +765,28 @@ 765 765 Scripts 766 766 )))|((( 767 767 3.0 Beta 1 768 -)))|((( 791 +)))|(% colspan="2" %)((( 769 769 **$controllable.wing.*** removed, 770 770 **$controllable.fleet.*** added 771 771 ))) 772 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)795 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 773 773 ((( 774 774 $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander 775 775 ))) 776 -|(% colspan="3" %)(% colspan="3" %) 777 -((( 778 -== 2.60 == 779 -))) 799 + 800 +---- 801 + 802 +=== 2.60 === 803 + 804 +(% class="wrapped" %) 780 780 |((( 781 781 Scripts 782 782 )))|((( 783 783 2.60 Beta 1 784 -)))|((( 809 +)))|(% colspan="2" %)((( 785 785 '**checkoperational**' filter behaviour changed 786 786 ))) 787 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)812 +|(% class="highlight-grey" colspan="10" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 788 788 ((( 789 789 //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.// 790 790 ... ... @@ -794,14 +794,20 @@ 794 794 Scripts 795 795 )))|((( 796 796 2.60 Beta 1 797 -)))|((( 822 +)))|(% colspan="2" %)((( 798 798 $container.**supplyresources** behavior changed 799 -))) 800 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)824 +)))| | | 825 +|(% class="highlight-grey" colspan="10" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 801 801 ((( 802 802 //The script keyword $container.supplyresources now includes reserved wares.// 803 803 ))) 804 -|(% colspan="3" %)(% colspan="3" %) 829 + 830 +---- 831 + 832 +=== 2.20 === 833 + 834 +(% class="wrapped" %) 835 +|(% colspan="4" %)(% colspan="3" %) 805 805 ((( 806 806 == 2.20 == 807 807 ))) ... ... @@ -811,11 +811,11 @@ 811 811 )))|(% colspan="1" %)(% colspan="1" %) 812 812 ((( 813 813 2.20 Beta 3/4 814 -)))|(% colspan=" 1" %)(% colspan="1" %)845 +)))|(% colspan="2" %)(% colspan="1" %) 815 815 ((( 816 816 **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined. 817 817 ))) 818 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)849 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 819 819 ((( 820 820 //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. 821 821 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.// ... ... @@ -828,18 +828,20 @@ 828 828 )))|(% colspan="1" %)(% colspan="1" %) 829 829 ((( 830 830 2.20 Beta 3 831 -)))|(% colspan=" 1" %)(% colspan="1" %)862 +)))|(% colspan="2" %)(% colspan="1" %) 832 832 ((( 833 833 Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor' 834 834 ))) 835 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)866 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 836 836 ((( 837 837 //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.// 838 838 ))) 839 -|(% colspan="3" %)(% colspan="3" %) 840 -((( 841 -== 2.00 == 842 -))) 870 + 871 +---- 872 + 873 +=== 2.00 === 874 + 875 +(% class="wrapped" %) 843 843 |(% colspan="1" %)(% colspan="1" %) 844 844 ((( 845 845 Scripts ... ... @@ -846,11 +846,11 @@ 846 846 )))|(% colspan="1" %)(% colspan="1" %) 847 847 ((( 848 848 2.00 Beta 1 849 -)))|(% colspan=" 1" %)(% colspan="1" %)882 +)))|(% colspan="2" %)(% colspan="1" %) 850 850 ((( 851 851 **<event_build_finished/> **param2 now returns null instead of a construction sequence 852 852 ))) 853 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)886 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 854 854 ((( 855 855 //The construction sequence which was finished should now be accessed via the buildtask provided via param3.// 856 856 ))) ... ... @@ -860,11 +860,11 @@ 860 860 )))|(% colspan="1" %)(% colspan="1" %) 861 861 ((( 862 862 2.00 Beta 1 863 -)))|(% colspan=" 1" %)(% colspan="1" %)896 +)))|(% colspan="2" %)(% colspan="1" %) 864 864 ((( 865 865 **param.boarding.{...}** strength parameters removed 866 866 ))) 867 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)900 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 868 868 ((( 869 869 //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.// 870 870 ))) ... ... @@ -874,11 +874,11 @@ 874 874 )))|(% colspan="1" %)(% colspan="1" %) 875 875 ((( 876 876 2.00 Beta 1 877 -)))|(% colspan=" 1" %)(% colspan="1" %)910 +)))|(% colspan="2" %)(% colspan="1" %) 878 878 ((( 879 879 **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed 880 880 ))) 881 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)914 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 882 882 ((( 883 883 //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.// 884 884 ))) ... ... @@ -886,10 +886,10 @@ 886 886 UI extensions 887 887 )))|((( 888 888 2.00 Beta 1 889 -)))|((( 922 +)))|(% colspan="2" %)((( 890 890 **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals 891 891 ))) 892 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)925 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 893 893 ((( 894 894 //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.// 895 895 ))) ... ... @@ -897,10 +897,10 @@ 897 897 UI extensions 898 898 )))|((( 899 899 2.00 Beta 1 900 -)))|((( 933 +)))|(% colspan="2" %)((( 901 901 **FFI: SetFormationShape()** no longer indicates an error upon certain error cases 902 902 ))) 903 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)936 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 904 904 ((( 905 905 //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.// 906 906 //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.// ... ... @@ -909,10 +909,10 @@ 909 909 Scripts 910 910 )))|((( 911 911 2.00 Beta 1 912 -)))|((( 945 +)))|(% colspan="2" %)((( 913 913 **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated. 914 914 ))) 915 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)948 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 916 916 ((( 917 917 //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.// 918 918 ))) ... ... @@ -920,10 +920,10 @@ 920 920 Scripts 921 921 )))|((( 922 922 2.00 Beta 1 923 -)))|((( 956 +)))|(% colspan="2" %)((( 924 924 **<event_player_changed_target/>** now fires and returns null if the player deselects a target. 925 925 ))) 926 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)959 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 927 927 ((( 928 928 //For prior behavior, check for event.param being non-null.// 929 929 ))) ... ... @@ -931,10 +931,10 @@ 931 931 AI Scripts 932 932 )))|((( 933 933 2.00 Beta 1 934 -)))|((( 967 +)))|(% colspan="2" %)((( 935 935 **<shoot/>/<shoot_at/>** attribute changes. 936 936 ))) 937 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)970 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 938 938 ((( 939 939 //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.// 940 940 //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.// ... ... @@ -946,10 +946,10 @@ 946 946 UI extensions 947 947 )))|((( 948 948 2.00 Beta 1 949 -)))|((( 982 +)))|(% colspan="2" %)((( 950 950 **FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter. 951 951 ))) 952 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)985 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 953 953 ((( 954 954 //Added possibility to query build tasks of a certain buildmodule.// 955 955 ))) ... ... @@ -957,10 +957,10 @@ 957 957 UI extensions 958 958 )))|((( 959 959 2.00 Beta 1 960 -)))|((( 993 +)))|(% colspan="2" %)((( 961 961 **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field. 962 962 ))) 963 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)996 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 964 964 ((( 965 965 //Added list of resources a buildmodule needs to build.// 966 966 ))) ... ... @@ -968,10 +968,10 @@ 968 968 UI extensions 969 969 )))|((( 970 970 2.00 Beta 1 971 -)))|((( 972 -**Lua: CalculateTotalHullFraction() ** (%%)was removed.1004 +)))|(% colspan="2" %)((( 1005 +**Lua: CalculateTotalHullFraction() **was removed. 973 973 ))) 974 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1007 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 975 975 ((( 976 976 //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.// 977 977 ))) ... ... @@ -979,25 +979,27 @@ 979 979 UI extensions 980 980 )))|((( 981 981 2.00 Beta 1 982 -)))|((( 983 -**FFI: RequestDockAtReason()/UndockPlayerShip() (%%)**changed their return values.1015 +)))|(% colspan="2" %)((( 1016 +**FFI: RequestDockAtReason()/UndockPlayerShip() **changed their return values. 984 984 ))) 985 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1018 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 986 986 ((( 987 987 //Changed return value type to const char* to better identify failure reasons in Lua script.// 988 988 ))) 989 -|(% colspan="3" %)(% colspan="3" %) 990 -((( 991 -== 1.50 == 992 -))) 1022 + 1023 +---- 1024 + 1025 +=== 1.50 === 1026 + 1027 +(% class="wrapped" %) 993 993 |((( 994 994 UI extensions 995 995 )))|((( 996 996 1.50 Beta 3 997 -)))|((( 1032 +)))|(% colspan="2" %)((( 998 998 **Lua: GetComponentData() **changed behavior of "docksizes" property. 999 999 ))) 1000 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1035 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1001 1001 ((( 1002 1002 //The "docksizes" property no longer includes internal ship storage docks.// 1003 1003 ))) ... ... @@ -1005,10 +1005,10 @@ 1005 1005 All 1006 1006 )))|((( 1007 1007 1.50 Beta 2 1008 -)))|((( 1043 +)))|(% colspan="2" %)((( 1009 1009 **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR). 1010 1010 ))) 1011 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1046 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1012 1012 ((( 1013 1013 //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".// 1014 1014 ... ... @@ -1020,10 +1020,10 @@ 1020 1020 UI extensions 1021 1021 )))|((( 1022 1022 1.50 Beta 2 1023 -)))|((( 1058 +)))|(% colspan="2" %)((( 1024 1024 **FFI: UpgradeGroupInfo **datatype was changed. 1025 1025 ))) 1026 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1061 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1027 1027 ((( 1028 1028 //Added new "operational" field to retrieve information about number of operational upgrades in a group.// 1029 1029 ))) ... ... @@ -1033,11 +1033,11 @@ 1033 1033 )))|(% colspan="1" %)(% colspan="1" %) 1034 1034 ((( 1035 1035 1.50 Beta 1 1036 -)))|(% colspan=" 1" %)(% colspan="1" %)1071 +)))|(% colspan="2" %)(% colspan="1" %) 1037 1037 ((( 1038 1038 **FFI: SetGuidance()** removed useinfopoint argument. 1039 1039 ))) 1040 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1075 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1041 1041 ((( 1042 1042 //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.// 1043 1043 ... ... @@ -1047,40 +1047,46 @@ 1047 1047 UI extensions 1048 1048 )))|((( 1049 1049 1.50 Beta 1 1050 -)))|((( 1085 +)))|(% colspan="2" %)((( 1051 1051 **FFI: CancelConstruction() **changed its return value. 1052 1052 ))) 1053 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1088 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1054 1054 ((( 1055 1055 //CancelConstruction() now returns if the cancellation was successful. // 1056 1056 ))) 1057 -|(% colspan="3" %)(% colspan="3" %) 1058 -((( 1059 -== 1.32 == 1060 -))) 1092 + 1093 +---- 1094 + 1095 +=== 1.32 === 1096 + 1097 +(% class="wrapped" %) 1061 1061 |((( 1062 1062 UI extensions 1063 1063 )))|((( 1064 1064 1.32 1065 -)))|((( 1102 +)))|(% colspan="2" %)((( 1066 1066 **Lua: GetComponentData() **removed the "nextdestname" property. 1067 1067 ))) 1068 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1105 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1069 1069 ((( 1070 1070 //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.// 1071 1071 ))) 1072 -|(% colspan="3" %)(% colspan="3" %) 1073 -((( 1074 -== 1.20 == 1075 -))) 1109 + 1110 +---- 1111 + 1112 +=== 1.20 === 1113 + 1114 +(% class="wrapped" %) 1076 1076 |((( 1077 1077 UI extensions 1078 1078 )))|((( 1079 1079 1.20 1080 -)))|((( 1119 +)))|(% colspan="2" %)((( 1081 1081 **FFI: GetAAOption()** got a new "useconfig" parameter. 1082 1082 ))) 1083 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1122 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1084 1084 ((( 1085 1085 //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.// 1086 1086 ))) 1126 + 1127 +