Changes for page Breaking Changes
Last modified by Michael Baumgardt on 2026/04/17 12:03
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -xwiki:XWiki. stefan1 +xwiki:XWiki.florian - Content
-
... ... @@ -24,109 +24,9 @@ 24 24 Version 25 25 )))|=((( 26 26 Summary 27 -)))|=(% colspan="1" %)(% colspan="1" %) 28 -((( 29 - 30 30 ))) 31 -|(% colspan=" 4" %)(% colspan="4" %)28 +|(% colspan="3" %)(% colspan="3" %) 32 32 ((( 33 -== 4.00 == 34 -))) 35 -|(% colspan="1" %)(% colspan="1" %) 36 -((( 37 -UI core 38 -)))|(% colspan="1" %)(% colspan="1" %) 39 -((( 40 -4.00 Beta 6 41 -)))|(% colspan="1" %)(% colspan="1" %) 42 -((( 43 -**FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed 44 -)))|(% colspan="1" %)(% colspan="1" %) 45 -((( 46 - 47 -))) 48 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 49 -((( 50 -//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. 51 -Factions with a relation rating between -20 and -10 will now report a relation status of 'neutral' (aka: 0) instead of 'hostile'/'enemy' (aka: 1).// 52 - 53 -//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead. 54 -// 55 -)))|(% colspan="1" %)(% colspan="1" %) 56 -((( 57 - 58 -))) 59 -|(% colspan="1" %)(% colspan="1" %) 60 -((( 61 -UI core 62 -)))|(% colspan="1" %)(% colspan="1" %) 63 -((( 64 -4.00 Beta 5 65 -)))|(% colspan="1" %)(% colspan="1" %) 66 -((( 67 -**FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed 68 -)))|(% colspan="1" %)(% colspan="1" %) 69 -((( 70 - 71 -))) 72 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 73 -((( 74 -//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.// 75 - 76 -//If you rely on a handling where they are treated like enemies, please use the new GetRelationStatus3() //function which returns the new range for these objects: 1 (meaning 'enemy' (aka: not yet hostile) here with following relations having been shifted up). 77 -)))|(% colspan="1" %)(% colspan="1" %) 78 -((( 79 - 80 -))) 81 -|((( 82 -Parameters 83 -)))|((( 84 -4.00 Beta 1 85 -)))|((( 86 -**requiresconstructionvessel** parameter moved 87 -)))|((( 88 - 89 -))) 90 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 91 -((( 92 -//The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.// 93 -))) 94 -|((( 95 -Scripts 96 -)))|((( 97 -4.00 Beta 1 98 -)))|((( 99 -Changed behaviour of **gatedistance** script property 100 -)))|((( 101 - 102 -))) 103 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 104 -((( 105 -//The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.// 106 -)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %) 107 -((( 108 - 109 -))) 110 -|(% colspan="4" %)(% colspan="4" %) 111 -((( 112 -== 3.30 == 113 -))) 114 -|((( 115 -UI extensions 116 -)))|((( 117 -3.30 Beta 3 118 -)))|((( 119 -**FFI: **Removed** (% style="color: rgb(0,0,0);" %)GetMissionLimit() (%%)**(% style="color: rgb(0,0,0);" %)and** **(% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)**IsMissionLimit**(%%)**Enabled()** 120 -)))|(% colspan="1" %)(% colspan="1" %) 121 -((( 122 - 123 -))) 124 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 125 -((( 126 -//These mission limit-related functions (added in 3.30 Beta 1 and 2) are replaced with FFI (% style="color: rgb(0,0,0);" %)IsMissionLimit(%%)Reach(% style="color: rgb(0,0,0);" %)ed()// 127 -))) 128 -|(% colspan="4" %)(% colspan="4" %) 129 -((( 130 130 == 3.20 == 131 131 ))) 132 132 |((( ... ... @@ -135,32 +135,23 @@ 135 135 3.20 Beta 1 136 136 )))|((( 137 137 Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed 138 -)))|(% colspan="1" %)(% colspan="1" %) 139 -((( 140 - 141 141 ))) 142 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)39 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 143 143 ((( 144 144 //Old params: param = attacked object, param2 = attack method, param3 = attacked component// 145 145 //New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon] 146 146 Note that this also means the component attribute to the events is no longer available, so scripts checking the attacked component need to use event.param3.{1} instead// 147 147 ))) 148 -|(% colspan="1" %)(% colspan="1" %) 149 -((( 150 -Scripts 151 -)))|(% colspan="1" %)(% colspan="1" %) 152 -((( 45 +|((( 46 +UI extensions 47 +)))|((( 153 153 3.20 Beta 1 154 -)))|(% colspan="1" %)(% colspan="1" %) 155 -((( 156 -Removed script property $trade.**restriction.faction** 157 -)))|(% colspan="1" %)(% colspan="1" %) 158 -((( 159 - 49 +)))|((( 50 +**FFI**: Deprecated the following functions: **GetContainerAllowedBuildFactions()**, **GetNumContainerAllowedBuildFactions()**, **IsContainerFactionBuildRescricted()**, **IsContainerFactionTradeRescricted()**, **SetContainerBuildAllowedFactions()**, **SetContainerFactionBuildRescricted()** 160 160 ))) 161 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)52 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 162 162 ((( 163 - //$trade.restriction.factionhasbeenreplacedwith$trade.restriction.factions,whichreturns a listoffactions.//54 +With the addition of the Trade Rule feature the given functions are considered deprecated and should not be used anymore. Consider GetAllTradeRules(), GetContainerTradeRuleID(), SetContainerTradeRule() and similar trade rule functions for replacement. 164 164 ))) 165 165 |((( 166 166 UI extensions ... ... @@ -168,15 +168,12 @@ 168 168 3.20 Beta 1 169 169 )))|((( 170 170 **Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete! 171 -)))|(% colspan="1" %)(% colspan="1" %) 172 -((( 173 - 174 174 ))) 175 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)63 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 176 176 ((( 177 - //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.//65 +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. 178 178 ))) 179 -|(% colspan=" 4" %)(% colspan="4" %)67 +|(% colspan="3" %)(% colspan="3" %) 180 180 ((( 181 181 == 3.10 == 182 182 ))) ... ... @@ -189,15 +189,12 @@ 189 189 )))|(% colspan="1" %)(% colspan="1" %) 190 190 ((( 191 191 Removed script action **<add_build/>** 192 -)))|(% colspan="1" %)(% colspan="1" %) 193 -((( 194 - 195 195 ))) 196 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)81 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 197 197 ((( 198 - //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.//83 +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. 199 199 ))) 200 -|(% colspan=" 4" %)(% colspan="4" %)85 +|(% colspan="3" %)(% colspan="3" %) 201 201 ((( 202 202 == 3.00 == 203 203 ))) ... ... @@ -210,13 +210,10 @@ 210 210 )))|(% colspan="1" %)(% colspan="1" %) 211 211 ((( 212 212 Changed behaviour of script action **<get_suitable_job/>** 213 -)))|(% colspan="1" %)(% colspan="1" %) 214 -((( 215 - 216 216 ))) 217 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)99 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 218 218 ((( 219 - //<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.//101 +<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. 220 220 ))) 221 221 |(% colspan="1" %)(% colspan="1" %) 222 222 ((( ... ... @@ -227,11 +227,8 @@ 227 227 )))|(% colspan="1" %)(% colspan="1" %) 228 228 ((( 229 229 Changed behaviour of script action **<get_ware_definition/>** 230 -)))|(% colspan="1" %)(% colspan="1" %) 231 -((( 232 - 233 233 ))) 234 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)113 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 235 235 ((( 236 236 //<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.// 237 237 ))) ... ... @@ -244,11 +244,8 @@ 244 244 )))|(% colspan="1" %)(% colspan="1" %) 245 245 ((( 246 246 Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case 247 -)))|(% colspan="1" %)(% colspan="1" %) 248 -((( 249 - 250 250 ))) 251 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)127 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 252 252 ((( 253 253 //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.)\\ 254 254 ... ... @@ -263,11 +263,8 @@ 263 263 )))|(% colspan="1" %)(% colspan="1" %) 264 264 ((( 265 265 Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions> 266 -)))|(% colspan="1" %)(% colspan="1" %) 267 -((( 268 - 269 269 ))) 270 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)143 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 271 271 ((( 272 272 //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.// 273 273 ))) ... ... @@ -280,11 +280,8 @@ 280 280 )))|(% colspan="1" %)(% colspan="1" %) 281 281 ((( 282 282 Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos** 283 -)))|(% colspan="1" %)(% colspan="1" %) 284 -((( 285 - 286 286 ))) 287 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)157 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 288 288 ((( 289 289 //Before the change, positions are relative to $dockingbay.parent. 290 290 After the change, positions are relative to $dockingbay as specified in the documentation.// ... ... @@ -298,11 +298,8 @@ 298 298 )))|(% colspan="1" %)(% colspan="1" %) 299 299 ((( 300 300 Support for entity flag "**skillsvisible**" dropped 301 -)))|(% colspan="1" %)(% colspan="1" %) 302 -((( 303 - 304 304 ))) 305 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)172 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 306 306 ((( 307 307 //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().// 308 308 ))) ... ... @@ -312,11 +312,8 @@ 312 312 3.0 Beta 2 313 313 )))|((( 314 314 Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**. 315 -)))|(% colspan="1" %)(% colspan="1" %) 316 -((( 317 - 318 318 ))) 319 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)183 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 320 320 ((( 321 321 //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. 322 322 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. ... ... @@ -332,11 +332,8 @@ 332 332 )))|(% colspan="1" %)(% colspan="1" %) 333 333 ((( 334 334 **MissionBoard** support dropped 335 -)))|(% colspan="1" %)(% colspan="1" %) 336 -((( 337 - 338 338 ))) 339 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)200 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 340 340 ((( 341 341 //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.// 342 342 ))) ... ... @@ -346,11 +346,8 @@ 346 346 3.0 Beta 1 347 347 )))|((( 348 348 By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined 349 -)))|(% colspan="1" %)(% colspan="1" %) 350 -((( 351 - 352 352 ))) 353 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)211 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 354 354 ((( 355 355 //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.// 356 356 ))) ... ... @@ -363,11 +363,8 @@ 363 363 )))|(% colspan="1" %)(% colspan="1" %) 364 364 ((( 365 365 Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'** 366 -)))|(% colspan="1" %)(% colspan="1" %) 367 -((( 368 - 369 369 ))) 370 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)225 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 371 371 ((( 372 372 //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.// 373 373 ))) ... ... @@ -380,11 +380,8 @@ 380 380 )))|(% colspan="1" %)(% colspan="1" %) 381 381 ((( 382 382 Script action **<set_doors_locked/>** attribute **'group'** changed 383 -)))|(% colspan="1" %)(% colspan="1" %) 384 -((( 385 - 386 386 ))) 387 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)239 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 388 388 ((( 389 389 //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.// 390 390 ))) ... ... @@ -397,11 +397,8 @@ 397 397 )))|(% colspan="1" %)(% colspan="1" %) 398 398 ((( 399 399 Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed 400 -)))|(% colspan="1" %)(% colspan="1" %) 401 -((( 402 - 403 403 ))) 404 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)253 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 405 405 ((( 406 406 //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.// 407 407 ))) ... ... @@ -414,11 +414,8 @@ 414 414 )))|(% colspan="1" %)(% colspan="1" %) 415 415 ((( 416 416 Script actions **<set_hack_target/>** and **<abort_hack/>** removed 417 -)))|(% colspan="1" %)(% colspan="1" %) 418 -((( 419 - 420 420 ))) 421 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)267 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 422 422 ((( 423 423 //These actions had no effect and were removed.// 424 424 ))) ... ... @@ -431,11 +431,8 @@ 431 431 )))|(% colspan="1" %)(% colspan="1" %) 432 432 ((( 433 433 **<setup_conversation_minigame/>** script action removed 434 -)))|(% colspan="1" %)(% colspan="1" %) 435 -((( 436 - 437 437 ))) 438 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)281 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 439 439 ((( 440 440 //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.// 441 441 ))) ... ... @@ -448,11 +448,8 @@ 448 448 )))|(% colspan="1" %)(% colspan="1" %) 449 449 ((( 450 450 <add_player_choice_*> **confidence** attribute removed 451 -)))|(% colspan="1" %)(% colspan="1" %) 452 -((( 453 - 454 454 ))) 455 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)295 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 456 456 ((( 457 457 //The default confidence of player options is another leftover from the XR era and had no effect in X4.// 458 458 ))) ... ... @@ -465,11 +465,8 @@ 465 465 )))|(% colspan="1" %)(% colspan="1" %) 466 466 ((( 467 467 **<hack_via_control_panel/>** script action removed 468 -)))|(% colspan="1" %)(% colspan="1" %) 469 -((( 470 - 471 471 ))) 472 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)309 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 473 473 ((( 474 474 //Unused script action <hack_via_control_panel/> was removed.// 475 475 ))) ... ... @@ -482,11 +482,8 @@ 482 482 )))|(% colspan="1" %)(% colspan="1" %) 483 483 ((( 484 484 **Lua: **GetMiniGameCursorPosition() removed 485 -)))|(% colspan="1" %)(% colspan="1" %) 486 -((( 487 - 488 488 ))) 489 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)323 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 490 490 ((( 491 491 //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.// 492 492 ))) ... ... @@ -496,11 +496,8 @@ 496 496 3.0 Beta 1 497 497 )))|((( 498 498 **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders 499 -)))|(% colspan="1" %)(% colspan="1" %) 500 -((( 501 - 502 502 ))) 503 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)334 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 504 504 ((( 505 505 //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.// 506 506 ))) ... ... @@ -513,11 +513,8 @@ 513 513 )))|(% colspan="1" %)(% colspan="1" %) 514 514 ((( 515 515 **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor 516 -)))|(% colspan="1" %)(% colspan="1" %) 517 -((( 518 - 519 519 ))) 520 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)348 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 521 521 ((( 522 522 //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.// 523 523 ))) ... ... @@ -530,11 +530,8 @@ 530 530 )))|(% colspan="1" %)(% colspan="1" %) 531 531 ((( 532 532 **$ware.illegal** updated 533 -)))|(% colspan="1" %)(% colspan="1" %) 534 -((( 535 - 536 536 ))) 537 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)362 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 538 538 ((( 539 539 //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.// 540 540 //It now returns true if $ware is illegal to any faction in the game.// ... ... @@ -548,11 +548,8 @@ 548 548 )))|(% colspan="1" %)(% colspan="1" %) 549 549 ((( 550 550 MD script **RML_Flight_Along_Path** removed 551 -)))|(% colspan="1" %)(% colspan="1" %) 552 -((( 553 - 554 554 ))) 555 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)377 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 556 556 ((( 557 557 //The MD script RML_Flight_Along_Path was not referened and was removed.// 558 558 ))) ... ... @@ -565,11 +565,8 @@ 565 565 )))|(% colspan="1" %)(% colspan="1" %) 566 566 ((( 567 567 parameters of **<event_venture_mission_completed/>** changed 568 -)))|(% colspan="1" %)(% colspan="1" %) 569 -((( 570 - 571 571 ))) 572 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)391 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 573 573 ((( 574 574 //old params: param = venture details, param2 = ships involved, param3 = duration// 575 575 //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration// ... ... @@ -581,11 +581,8 @@ 581 581 )))|((( 582 582 **<set_object_wing_name/>** removed, 583 583 **<set_object_fleet_name/>** added 584 -)))|(% colspan="1" %)(% colspan="1" %) 585 -((( 586 - 587 587 ))) 588 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)404 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 589 589 ((( 590 590 //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>// 591 591 ))) ... ... @@ -596,15 +596,12 @@ 596 596 )))|((( 597 597 **$controllable.wing.*** removed, 598 598 **$controllable.fleet.*** added 599 -)))|(% colspan="1" %)(% colspan="1" %) 600 -((( 601 - 602 602 ))) 603 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)416 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 604 604 ((( 605 605 $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander 606 606 ))) 607 -|(% colspan=" 4" %)(% colspan="4" %)420 +|(% colspan="3" %)(% colspan="3" %) 608 608 ((( 609 609 == 2.60 == 610 610 ))) ... ... @@ -614,11 +614,8 @@ 614 614 2.60 Beta 1 615 615 )))|((( 616 616 '**checkoperational**' filter behaviour changed 617 -)))|(% colspan="1" %)(% colspan="1" %) 618 -((( 619 - 620 620 ))) 621 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)431 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 622 622 ((( 623 623 //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.// 624 624 ... ... @@ -630,15 +630,12 @@ 630 630 2.60 Beta 1 631 631 )))|((( 632 632 $container.**supplyresources** behavior changed 633 -)))|(% colspan="1" %)(% colspan="1" %) 634 -((( 635 - 636 636 ))) 637 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)444 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 638 638 ((( 639 639 //The script keyword $container.supplyresources now includes reserved wares.// 640 640 ))) 641 -|(% colspan=" 4" %)(% colspan="4" %)448 +|(% colspan="3" %)(% colspan="3" %) 642 642 ((( 643 643 == 2.20 == 644 644 ))) ... ... @@ -651,11 +651,8 @@ 651 651 )))|(% colspan="1" %)(% colspan="1" %) 652 652 ((( 653 653 **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined. 654 -)))|(% colspan="1" %)(% colspan="1" %) 655 -((( 656 - 657 657 ))) 658 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)462 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 659 659 ((( 660 660 //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. 661 661 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.// ... ... @@ -672,15 +672,12 @@ 672 672 )))|(% colspan="1" %)(% colspan="1" %) 673 673 ((( 674 674 Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor' 675 -)))|(% colspan="1" %)(% colspan="1" %) 676 -((( 677 - 678 678 ))) 679 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)480 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 680 680 ((( 681 681 //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.// 682 682 ))) 683 -|(% colspan=" 4" %)(% colspan="4" %)484 +|(% colspan="3" %)(% colspan="3" %) 684 684 ((( 685 685 == 2.00 == 686 686 ))) ... ... @@ -693,11 +693,8 @@ 693 693 )))|(% colspan="1" %)(% colspan="1" %) 694 694 ((( 695 695 **<event_build_finished/> **param2 now returns null instead of a construction sequence 696 -)))|(% colspan="1" %)(% colspan="1" %) 697 -((( 698 - 699 699 ))) 700 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)498 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 701 701 ((( 702 702 //The construction sequence which was finished should now be accessed via the buildtask provided via param3.// 703 703 ))) ... ... @@ -710,11 +710,8 @@ 710 710 )))|(% colspan="1" %)(% colspan="1" %) 711 711 ((( 712 712 **param.boarding.{...}** strength parameters removed 713 -)))|(% colspan="1" %)(% colspan="1" %) 714 -((( 715 - 716 716 ))) 717 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)512 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 718 718 ((( 719 719 //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.// 720 720 ))) ... ... @@ -727,11 +727,8 @@ 727 727 )))|(% colspan="1" %)(% colspan="1" %) 728 728 ((( 729 729 **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed 730 -)))|(% colspan="1" %)(% colspan="1" %) 731 -((( 732 - 733 733 ))) 734 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)526 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 735 735 ((( 736 736 //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.// 737 737 ))) ... ... @@ -741,11 +741,8 @@ 741 741 2.00 Beta 1 742 742 )))|((( 743 743 **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals 744 -)))|(% colspan="1" %)(% colspan="1" %) 745 -((( 746 - 747 747 ))) 748 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)537 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 749 749 ((( 750 750 //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.// 751 751 ))) ... ... @@ -755,11 +755,8 @@ 755 755 2.00 Beta 1 756 756 )))|((( 757 757 **FFI: SetFormationShape()** no longer indicates an error upon certain error cases 758 -)))|(% colspan="1" %)(% colspan="1" %) 759 -((( 760 - 761 761 ))) 762 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)548 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 763 763 ((( 764 764 //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.// 765 765 //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.// ... ... @@ -770,11 +770,8 @@ 770 770 2.00 Beta 1 771 771 )))|((( 772 772 **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated. 773 -)))|(% colspan="1" %)(% colspan="1" %) 774 -((( 775 - 776 776 ))) 777 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)560 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 778 778 ((( 779 779 //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.// 780 780 ))) ... ... @@ -784,11 +784,8 @@ 784 784 2.00 Beta 1 785 785 )))|((( 786 786 **<event_player_changed_target/>** now fires and returns null if the player deselects a target. 787 -)))|(% colspan="1" %)(% colspan="1" %) 788 -((( 789 - 790 790 ))) 791 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)571 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 792 792 ((( 793 793 //For prior behavior, check for event.param being non-null.// 794 794 ))) ... ... @@ -798,11 +798,8 @@ 798 798 2.00 Beta 1 799 799 )))|((( 800 800 **<shoot/>/<shoot_at/>** attribute changes. 801 -)))|(% colspan="1" %)(% colspan="1" %) 802 -((( 803 - 804 804 ))) 805 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)582 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 806 806 ((( 807 807 //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.// 808 808 //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.// ... ... @@ -816,11 +816,8 @@ 816 816 2.00 Beta 1 817 817 )))|((( 818 818 **FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% class="confluenceTd" %) 819 -)))|(% colspan="1" %)(% colspan="1" %) 820 -((( 821 - 822 822 ))) 823 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)597 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 824 824 ((( 825 825 //Added possibility to query build tasks of a certain buildmodule.// 826 826 ))) ... ... @@ -830,11 +830,8 @@ 830 830 2.00 Beta 1 831 831 )))|((( 832 832 **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field. 833 -)))|(% colspan="1" %)(% colspan="1" %) 834 -((( 835 - 836 836 ))) 837 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)608 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 838 838 ((( 839 839 //Added list of resources a buildmodule needs to build.// 840 840 ))) ... ... @@ -844,11 +844,8 @@ 844 844 2.00 Beta 1 845 845 )))|((( 846 846 (% style="color: rgb(0,0,0);" %)**Lua:**(% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)** CalculateTotalHullFraction()**(% style="color: rgb(0,0,0);" %)** **(%%)was removed.(% style="color: rgb(0,0,0);" %) 847 -)))|(% colspan="1" %)(% colspan="1" %) 848 -((( 849 - 850 850 ))) 851 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)619 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 852 852 ((( 853 853 //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.// 854 854 ))) ... ... @@ -858,15 +858,12 @@ 858 858 2.00 Beta 1 859 859 )))|((( 860 860 **FFI: (% style="color: rgb(0,0,0);" %)RequestDockAtReason()/(% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)UndockPlayerShip()(%%) **changed their return values.(% style="color: rgb(0,0,0);" class="confluenceTd" %) 861 -)))|(% colspan="1" %)(% colspan="1" %) 862 -((( 863 - 864 864 ))) 865 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)630 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 866 866 ((( 867 867 //Changed return value type to const char* to better identify failure reasons in Lua script.// 868 868 ))) 869 -|(% colspan=" 4" %)(% colspan="4" %)634 +|(% colspan="3" %)(% colspan="3" %) 870 870 ((( 871 871 == 1.50 == 872 872 ))) ... ... @@ -876,11 +876,8 @@ 876 876 1.50 Beta 3 877 877 )))|((( 878 878 **Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %) 879 -)))|(% colspan="1" %)(% colspan="1" %) 880 -((( 881 - 882 882 ))) 883 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)645 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 884 884 ((( 885 885 //The "docksizes" property no longer includes internal ship storage docks.// 886 886 ))) ... ... @@ -890,11 +890,8 @@ 890 890 1.50 Beta 2 891 891 )))|((( 892 892 **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR). 893 -)))|(% colspan="1" %)(% colspan="1" %) 894 -((( 895 - 896 896 ))) 897 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)656 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 898 898 ((( 899 899 //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".// 900 900 ... ... @@ -908,11 +908,8 @@ 908 908 1.50 Beta 2 909 909 )))|((( 910 910 **FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %) 911 -)))|(% colspan="1" %)(% colspan="1" %) 912 -((( 913 - 914 914 ))) 915 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)671 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 916 916 ((( 917 917 //Added new "operational" field to retrieve information about number of operational upgrades in a group.// 918 918 ))) ... ... @@ -925,11 +925,8 @@ 925 925 )))|(% colspan="1" %)(% colspan="1" %) 926 926 ((( 927 927 **FFI: SetGuidance()** removed useinfopoint argument. 928 -)))|(% colspan="1" %)(% colspan="1" %) 929 -((( 930 - 931 931 ))) 932 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)685 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 933 933 ((( 934 934 //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. 935 935 // ... ... @@ -942,15 +942,12 @@ 942 942 1.50 Beta 1 943 943 )))|((( 944 944 **FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %) 945 -)))|(% colspan="1" %)(% colspan="1" %) 946 -((( 947 - 948 948 ))) 949 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)699 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 950 950 ((( 951 951 (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. // 952 952 ))) 953 -|(% colspan=" 4" %)(% colspan="4" %)703 +|(% colspan="3" %)(% colspan="3" %) 954 954 ((( 955 955 == 1.32 == 956 956 ))) ... ... @@ -960,15 +960,12 @@ 960 960 1.32 961 961 )))|((( 962 962 **Lua: GetComponentData() **removed the "nextdestname" property. 963 -)))|(% colspan="1" %)(% colspan="1" %) 964 -((( 965 - 966 966 ))) 967 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)714 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 968 968 ((( 969 969 //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.// 970 970 ))) 971 -|(% colspan=" 4" %)(% colspan="4" %)718 +|(% colspan="3" %)(% colspan="3" %) 972 972 ((( 973 973 == 1.20 == 974 974 ))) ... ... @@ -978,11 +978,8 @@ 978 978 1.20 979 979 )))|((( 980 980 **FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %) 981 -)))|(% colspan="1" %)(% colspan="1" %) 982 -((( 983 - 984 984 ))) 985 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)729 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 986 986 ((( 987 987 //The AA setting was changed to check the new setting with the user. In order to restore the old setting (% style="color: rgb(0,0,0);" %)GetAAOption() gets the option to retrieve the config settings.// 988 988 )))
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 -1 015480821 +91947560 - url
-
... ... @@ -1,1 +1,1 @@ 1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/1 01548082/Breaking Changes1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/91947560/Breaking Changes