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