Changes for page Breaking Changes
Last modified by Michael Baumgardt on 2026/04/17 12:03
To version 76.1
edited by stefan
on 2021/02/01 11:51
on 2021/02/01 11:51
Change comment:
added breaking change for GetFactionRelationStatus()
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -24,15 +24,728 @@ 24 24 Version 25 25 )))|=((( 26 26 Summary 27 +)))|=(% colspan="1" %)(% colspan="1" %) 28 +((( 29 + 27 27 ))) 31 +|(% colspan="4" %)(% colspan="4" %) 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 +))) 28 28 |((( 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 +|((( 29 29 UI extensions 30 30 )))|((( 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 +== 3.20 == 131 +))) 132 +|((( 133 +Scripts 134 +)))|((( 135 +3.20 Beta 1 136 +)))|((( 137 +Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed 138 +)))|(% colspan="1" %)(% colspan="1" %) 139 +((( 140 + 141 +))) 142 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 143 +((( 144 +//Old params: param = attacked object, param2 = attack method, param3 = attacked component// 145 +//New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon] 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 +))) 148 +|(% colspan="1" %)(% colspan="1" %) 149 +((( 150 +Scripts 151 +)))|(% colspan="1" %)(% colspan="1" %) 152 +((( 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 + 160 +))) 161 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 162 +((( 163 +//$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.// 164 +))) 165 +|((( 166 +UI extensions 167 +)))|((( 168 +3.20 Beta 1 169 +)))|((( 170 +**Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete! 171 +)))|(% colspan="1" %)(% colspan="1" %) 172 +((( 173 + 174 +))) 175 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 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.// 178 +))) 179 +|(% colspan="4" %)(% colspan="4" %) 180 +((( 181 +== 3.10 == 182 +))) 183 +|(% colspan="1" %)(% colspan="1" %) 184 +((( 185 +Scripts 186 +)))|(% colspan="1" %)(% colspan="1" %) 187 +((( 188 +3.10 Beta 1 189 +)))|(% colspan="1" %)(% colspan="1" %) 190 +((( 191 +Removed script action **<add_build/>** 192 +)))|(% colspan="1" %)(% colspan="1" %) 193 +((( 194 + 195 +))) 196 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 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.// 199 +))) 200 +|(% colspan="4" %)(% colspan="4" %) 201 +((( 202 +== 3.00 == 203 +))) 204 +|(% colspan="1" %)(% colspan="1" %) 205 +((( 206 +Scripts 207 +)))|(% colspan="1" %)(% colspan="1" %) 208 +((( 209 +3.0 Beta 6 210 +)))|(% colspan="1" %)(% colspan="1" %) 211 +((( 212 +Changed behaviour of script action **<get_suitable_job/>** 213 +)))|(% colspan="1" %)(% colspan="1" %) 214 +((( 215 + 216 +))) 217 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 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.// 220 +))) 221 +|(% colspan="1" %)(% colspan="1" %) 222 +((( 223 +Scripts 224 +)))|(% colspan="1" %)(% colspan="1" %) 225 +((( 226 +3.0 Beta 6 227 +)))|(% colspan="1" %)(% colspan="1" %) 228 +((( 229 +Changed behaviour of script action **<get_ware_definition/>** 230 +)))|(% colspan="1" %)(% colspan="1" %) 231 +((( 232 + 233 +))) 234 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 235 +((( 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 +))) 238 +|(% colspan="1" %)(% colspan="1" %) 239 +((( 240 +Global 241 +)))|(% colspan="1" %)(% colspan="1" %) 242 +((( 243 +3.0 Beta 5 244 +)))|(% colspan="1" %)(% colspan="1" %) 245 +((( 246 +Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case 247 +)))|(% colspan="1" %)(% colspan="1" %) 248 +((( 249 + 250 +))) 251 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 252 +((( 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 + 255 +//Note that this change has no effect on the actual content of scripts or cutscenes. The MD script/cutscene names are stored in the files, regardless of the filenames, so that references to them remain unchanged (e.g., "md.Setup.Start" references a cue in setup.xml).// 256 +))) 257 +|(% colspan="1" %)(% colspan="1" %) 258 +((( 259 +Scripts 260 +)))|(% colspan="1" %)(% colspan="1" %) 261 +((( 262 +3.0 Beta 5 263 +)))|(% colspan="1" %)(% colspan="1" %) 264 +((( 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 +))) 270 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 271 +((( 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 +))) 274 +|(% colspan="1" %)(% colspan="1" %) 275 +((( 276 +Scripts 277 +)))|(% colspan="1" %)(% colspan="1" %) 278 +((( 279 +3.0 Beta 5 280 +)))|(% colspan="1" %)(% colspan="1" %) 281 +((( 282 +Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos** 283 +)))|(% colspan="1" %)(% colspan="1" %) 284 +((( 285 + 286 +))) 287 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 288 +((( 289 +//Before the change, positions are relative to $dockingbay.parent. 290 +After the change, positions are relative to $dockingbay as specified in the documentation.// 291 +))) 292 +|(% colspan="1" %)(% colspan="1" %) 293 +((( 294 +Global 295 +)))|(% colspan="1" %)(% colspan="1" %) 296 +((( 297 +3.0 Beta 2 298 +)))|(% colspan="1" %)(% colspan="1" %) 299 +((( 300 +Support for entity flag "**skillsvisible**" dropped 301 +)))|(% colspan="1" %)(% colspan="1" %) 302 +((( 303 + 304 +))) 305 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 306 +((( 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 +))) 309 +|((( 310 +Scripts 311 +)))|((( 312 +3.0 Beta 2 313 +)))|((( 314 +Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**. 315 +)))|(% colspan="1" %)(% colspan="1" %) 316 +((( 317 + 318 +))) 319 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 320 +((( 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 +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. 323 +If in your scripts you make use of the <event_object_changed_owner> condition you need to verify that you indeed want to work with the "effective" component owner or whether your script code actually should work with the true owner of an object and update your code accordingly. 324 +On top of that the 3rd parameter of <event_object_changed_owner> (trueprevious) was dropped as the event is no longer triggered upon a change of the true owner alone (i.e. only if the change of the true owner has also an effect on the "effective" component owner). 325 +))) 326 +|(% colspan="1" %)(% colspan="1" %) 327 +((( 328 +Global 329 +)))|(% colspan="1" %)(% colspan="1" %) 330 +((( 331 +3.0 Beta 1 332 +)))|(% colspan="1" %)(% colspan="1" %) 333 +((( 334 +**MissionBoard** support dropped 335 +)))|(% colspan="1" %)(% colspan="1" %) 336 +((( 337 + 338 +))) 339 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 340 +((( 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 +))) 343 +|((( 344 +Job/God 345 +)))|((( 346 +3.0 Beta 1 347 +)))|((( 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 +))) 353 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 354 +((( 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 +))) 357 +|(% colspan="1" %)(% colspan="1" %) 358 +((( 359 +Scripts 360 +)))|(% colspan="1" %)(% colspan="1" %) 361 +((( 362 +3.0 Beta 1 363 +)))|(% colspan="1" %)(% colspan="1" %) 364 +((( 365 +Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'** 366 +)))|(% colspan="1" %)(% colspan="1" %) 367 +((( 368 + 369 +))) 370 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 371 +((( 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 +))) 374 +|(% colspan="1" %)(% colspan="1" %) 375 +((( 376 +Scripts 377 +)))|(% colspan="1" %)(% colspan="1" %) 378 +((( 379 +3.0 Beta 1 380 +)))|(% colspan="1" %)(% colspan="1" %) 381 +((( 382 +Script action **<set_doors_locked/>** attribute **'group'** changed 383 +)))|(% colspan="1" %)(% colspan="1" %) 384 +((( 385 + 386 +))) 387 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 388 +((( 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 +))) 391 +|(% colspan="1" %)(% colspan="1" %) 392 +((( 393 +Scripts 394 +)))|(% colspan="1" %)(% colspan="1" %) 395 +((( 396 +3.0 Beta 1 397 +)))|(% colspan="1" %)(% colspan="1" %) 398 +((( 399 +Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed 400 +)))|(% colspan="1" %)(% colspan="1" %) 401 +((( 402 + 403 +))) 404 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 405 +((( 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 +))) 408 +|(% colspan="1" %)(% colspan="1" %) 409 +((( 410 +Scripts 411 +)))|(% colspan="1" %)(% colspan="1" %) 412 +((( 413 +3.0 Beta 1 414 +)))|(% colspan="1" %)(% colspan="1" %) 415 +((( 416 +Script actions **<set_hack_target/>** and **<abort_hack/>** removed 417 +)))|(% colspan="1" %)(% colspan="1" %) 418 +((( 419 + 420 +))) 421 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 422 +((( 423 +//These actions had no effect and were removed.// 424 +))) 425 +|(% colspan="1" %)(% colspan="1" %) 426 +((( 427 +Scripts 428 +)))|(% colspan="1" %)(% colspan="1" %) 429 +((( 430 +3.0 Beta 1 431 +)))|(% colspan="1" %)(% colspan="1" %) 432 +((( 433 +**<setup_conversation_minigame/>** script action removed 434 +)))|(% colspan="1" %)(% colspan="1" %) 435 +((( 436 + 437 +))) 438 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 439 +((( 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 +))) 442 +|(% colspan="1" %)(% colspan="1" %) 443 +((( 444 +Scripts 445 +)))|(% colspan="1" %)(% colspan="1" %) 446 +((( 447 +3.0 Beta 1 448 +)))|(% colspan="1" %)(% colspan="1" %) 449 +((( 450 +<add_player_choice_*> **confidence** attribute removed 451 +)))|(% colspan="1" %)(% colspan="1" %) 452 +((( 453 + 454 +))) 455 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 456 +((( 457 +//The default confidence of player options is another leftover from the XR era and had no effect in X4.// 458 +))) 459 +|(% colspan="1" %)(% colspan="1" %) 460 +((( 461 +Scripts 462 +)))|(% colspan="1" %)(% colspan="1" %) 463 +((( 464 +3.0 Beta 1 465 +)))|(% colspan="1" %)(% colspan="1" %) 466 +((( 467 +**<hack_via_control_panel/>** script action removed 468 +)))|(% colspan="1" %)(% colspan="1" %) 469 +((( 470 + 471 +))) 472 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 473 +((( 474 +//Unused script action <hack_via_control_panel/> was removed.// 475 +))) 476 +|(% colspan="1" %)(% colspan="1" %) 477 +((( 478 +UI core 479 +)))|(% colspan="1" %)(% colspan="1" %) 480 +((( 481 +3.0 Beta 1 482 +)))|(% colspan="1" %)(% colspan="1" %) 483 +((( 484 +**Lua: **GetMiniGameCursorPosition() removed 485 +)))|(% colspan="1" %)(% colspan="1" %) 486 +((( 487 + 488 +))) 489 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 490 +((( 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 +))) 493 +|((( 494 +UI core 495 +)))|((( 496 +3.0 Beta 1 497 +)))|((( 498 +**FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders 499 +)))|(% colspan="1" %)(% colspan="1" %) 500 +((( 501 + 502 +))) 503 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 504 +((( 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 +))) 507 +|(% colspan="1" %)(% colspan="1" %) 508 +((( 509 +UI extensions 510 +)))|(% colspan="1" %)(% colspan="1" %) 511 +((( 512 +3.0 Beta 1 513 +)))|(% colspan="1" %)(% colspan="1" %) 514 +((( 515 +**FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor 516 +)))|(% colspan="1" %)(% colspan="1" %) 517 +((( 518 + 519 +))) 520 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 521 +((( 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 +))) 524 +|(% colspan="1" %)(% colspan="1" %) 525 +((( 526 +Scripts 527 +)))|(% colspan="1" %)(% colspan="1" %) 528 +((( 529 +3.0 Beta 1 530 +)))|(% colspan="1" %)(% colspan="1" %) 531 +((( 532 +**$ware.illegal** updated 533 +)))|(% colspan="1" %)(% colspan="1" %) 534 +((( 535 + 536 +))) 537 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 538 +((( 539 +//$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.// 540 +//It now returns true if $ware is illegal to any faction in the game.// 541 +))) 542 +|(% colspan="1" %)(% colspan="1" %) 543 +((( 544 +Scripts 545 +)))|(% colspan="1" %)(% colspan="1" %) 546 +((( 547 +3.0 Beta 1 548 +)))|(% colspan="1" %)(% colspan="1" %) 549 +((( 550 +MD script **RML_Flight_Along_Path** removed 551 +)))|(% colspan="1" %)(% colspan="1" %) 552 +((( 553 + 554 +))) 555 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 556 +((( 557 +//The MD script RML_Flight_Along_Path was not referened and was removed.// 558 +))) 559 +|(% colspan="1" %)(% colspan="1" %) 560 +((( 561 +Scripts 562 +)))|(% colspan="1" %)(% colspan="1" %) 563 +((( 564 +3.0 Beta 1 565 +)))|(% colspan="1" %)(% colspan="1" %) 566 +((( 567 +parameters of **<event_venture_mission_completed/>** changed 568 +)))|(% colspan="1" %)(% colspan="1" %) 569 +((( 570 + 571 +))) 572 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 573 +((( 574 +//old params: param = venture details, param2 = ships involved, param3 = duration// 575 +//new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration// 576 +))) 577 +|((( 578 +Scripts 579 +)))|((( 580 +3.0 Beta 1 581 +)))|((( 582 +**<set_object_wing_name/>** removed, 583 +**<set_object_fleet_name/>** added 584 +)))|(% colspan="1" %)(% colspan="1" %) 585 +((( 586 + 587 +))) 588 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 589 +((( 590 +//The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>// 591 +))) 592 +|((( 593 +Scripts 594 +)))|((( 595 +3.0 Beta 1 596 +)))|((( 597 +**$controllable.wing.*** removed, 598 +**$controllable.fleet.*** added 599 +)))|(% colspan="1" %)(% colspan="1" %) 600 +((( 601 + 602 +))) 603 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 604 +((( 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 +))) 607 +|(% colspan="4" %)(% colspan="4" %) 608 +((( 609 +== 2.60 == 610 +))) 611 +|((( 612 +Scripts 613 +)))|((( 614 +2.60 Beta 1 615 +)))|((( 616 +'**checkoperational**' filter behaviour changed 617 +)))|(% colspan="1" %)(% colspan="1" %) 618 +((( 619 + 620 +))) 621 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 622 +((( 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 + 625 +//Sub nodes such as match_child will have checkoperational default to false. Existing uses may find that results now include non-operational components.// 626 +))) 627 +|((( 628 +Scripts 629 +)))|((( 630 +2.60 Beta 1 631 +)))|((( 632 +$container.**supplyresources** behavior changed 633 +)))|(% colspan="1" %)(% colspan="1" %) 634 +((( 635 + 636 +))) 637 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 638 +((( 639 +//The script keyword $container.supplyresources now includes reserved wares.// 640 +))) 641 +|(% colspan="4" %)(% colspan="4" %) 642 +((( 643 +== 2.20 == 644 +))) 645 +|(% colspan="1" %)(% colspan="1" %) 646 +((( 647 +UI core 648 +)))|(% colspan="1" %)(% colspan="1" %) 649 +((( 650 +2.20 Beta 3/4 651 +)))|(% colspan="1" %)(% colspan="1" %) 652 +((( 653 +**Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined. 654 +)))|(% colspan="1" %)(% colspan="1" %) 655 +((( 656 + 657 +))) 658 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 659 +((( 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 +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.// 662 + 663 +//It's a pending change to ensure that the returned mode is more reasonable in an upcoming patch. So be aware that another breaking change might be introduced at some point. 664 +// 665 +))) 666 +|(% colspan="1" %)(% colspan="1" %) 667 +((( 668 +Scripts 669 +)))|(% colspan="1" %)(% colspan="1" %) 670 +((( 671 +2.20 Beta 3 672 +)))|(% colspan="1" %)(% colspan="1" %) 673 +((( 674 +Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor' 675 +)))|(% colspan="1" %)(% colspan="1" %) 676 +((( 677 + 678 +))) 679 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 680 +((( 681 +//The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.// 682 +))) 683 +|(% colspan="4" %)(% colspan="4" %) 684 +((( 685 +== 2.00 == 686 +))) 687 +|(% colspan="1" %)(% colspan="1" %) 688 +((( 689 +Scripts 690 +)))|(% colspan="1" %)(% colspan="1" %) 691 +((( 31 31 2.00 Beta 1 693 +)))|(% colspan="1" %)(% colspan="1" %) 694 +((( 695 +**<event_build_finished/> **param2 now returns null instead of a construction sequence 696 +)))|(% colspan="1" %)(% colspan="1" %) 697 +((( 698 + 699 +))) 700 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 701 +((( 702 +//The construction sequence which was finished should now be accessed via the buildtask provided via param3.// 703 +))) 704 +|(% colspan="1" %)(% colspan="1" %) 705 +((( 706 +Scripts 707 +)))|(% colspan="1" %)(% colspan="1" %) 708 +((( 709 +2.00 Beta 1 710 +)))|(% colspan="1" %)(% colspan="1" %) 711 +((( 712 +**param.boarding.{...}** strength parameters removed 713 +)))|(% colspan="1" %)(% colspan="1" %) 714 +((( 715 + 716 +))) 717 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 718 +((( 719 +//The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.// 720 +))) 721 +|(% colspan="1" %)(% colspan="1" %) 722 +((( 723 +Scripts 724 +)))|(% colspan="1" %)(% colspan="1" %) 725 +((( 726 +2.00 Beta 1 727 +)))|(% colspan="1" %)(% colspan="1" %) 728 +((( 729 +**$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed 730 +)))|(% colspan="1" %)(% colspan="1" %) 731 +((( 732 + 733 +))) 734 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 735 +((( 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 +))) 738 +|((( 739 +UI extensions 32 32 )))|((( 741 +2.00 Beta 1 742 +)))|((( 33 33 **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals 744 +)))|(% colspan="1" %)(% colspan="1" %) 745 +((( 746 + 34 34 ))) 35 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)748 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 36 36 ((( 37 37 //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.// 38 38 ))) ... ... @@ -42,8 +42,11 @@ 42 42 2.00 Beta 1 43 43 )))|((( 44 44 **FFI: SetFormationShape()** no longer indicates an error upon certain error cases 758 +)))|(% colspan="1" %)(% colspan="1" %) 759 +((( 760 + 45 45 ))) 46 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)762 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 47 47 ((( 48 48 //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.// 49 49 //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.// ... ... @@ -54,8 +54,11 @@ 54 54 2.00 Beta 1 55 55 )))|((( 56 56 **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated. 773 +)))|(% colspan="1" %)(% colspan="1" %) 774 +((( 775 + 57 57 ))) 58 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)777 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 59 59 ((( 60 60 //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.// 61 61 ))) ... ... @@ -65,8 +65,11 @@ 65 65 2.00 Beta 1 66 66 )))|((( 67 67 **<event_player_changed_target/>** now fires and returns null if the player deselects a target. 787 +)))|(% colspan="1" %)(% colspan="1" %) 788 +((( 789 + 68 68 ))) 69 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)791 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 70 70 ((( 71 71 //For prior behavior, check for event.param being non-null.// 72 72 ))) ... ... @@ -76,8 +76,11 @@ 76 76 2.00 Beta 1 77 77 )))|((( 78 78 **<shoot/>/<shoot_at/>** attribute changes. 801 +)))|(% colspan="1" %)(% colspan="1" %) 802 +((( 803 + 79 79 ))) 80 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)805 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 81 81 ((( 82 82 //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.// 83 83 //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.// ... ... @@ -91,8 +91,11 @@ 91 91 2.00 Beta 1 92 92 )))|((( 93 93 **FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% class="confluenceTd" %) 819 +)))|(% colspan="1" %)(% colspan="1" %) 820 +((( 821 + 94 94 ))) 95 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)823 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 96 96 ((( 97 97 //Added possibility to query build tasks of a certain buildmodule.// 98 98 ))) ... ... @@ -102,8 +102,11 @@ 102 102 2.00 Beta 1 103 103 )))|((( 104 104 **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field. 833 +)))|(% colspan="1" %)(% colspan="1" %) 834 +((( 835 + 105 105 ))) 106 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)837 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 107 107 ((( 108 108 //Added list of resources a buildmodule needs to build.// 109 109 ))) ... ... @@ -113,8 +113,11 @@ 113 113 2.00 Beta 1 114 114 )))|((( 115 115 (% 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 + 116 116 ))) 117 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)851 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 118 118 ((( 119 119 //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.// 120 120 ))) ... ... @@ -124,11 +124,18 @@ 124 124 2.00 Beta 1 125 125 )))|((( 126 126 **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 + 127 127 ))) 128 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)865 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 129 129 ((( 130 130 //Changed return value type to const char* to better identify failure reasons in Lua script.// 131 131 ))) 869 +|(% colspan="4" %)(% colspan="4" %) 870 +((( 871 +== 1.50 == 872 +))) 132 132 |((( 133 133 UI extensions 134 134 )))|((( ... ... @@ -135,8 +135,11 @@ 135 135 1.50 Beta 3 136 136 )))|((( 137 137 **Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %) 879 +)))|(% colspan="1" %)(% colspan="1" %) 880 +((( 881 + 138 138 ))) 139 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)883 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 140 140 ((( 141 141 //The "docksizes" property no longer includes internal ship storage docks.// 142 142 ))) ... ... @@ -146,8 +146,11 @@ 146 146 1.50 Beta 2 147 147 )))|((( 148 148 **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 + 149 149 ))) 150 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)897 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 151 151 ((( 152 152 //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".// 153 153 ... ... @@ -161,8 +161,11 @@ 161 161 1.50 Beta 2 162 162 )))|((( 163 163 **FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %) 911 +)))|(% colspan="1" %)(% colspan="1" %) 912 +((( 913 + 164 164 ))) 165 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)915 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 166 166 ((( 167 167 //Added new "operational" field to retrieve information about number of operational upgrades in a group.// 168 168 ))) ... ... @@ -175,8 +175,11 @@ 175 175 )))|(% colspan="1" %)(% colspan="1" %) 176 176 ((( 177 177 **FFI: SetGuidance()** removed useinfopoint argument. 928 +)))|(% colspan="1" %)(% colspan="1" %) 929 +((( 930 + 178 178 ))) 179 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)932 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 180 180 ((( 181 181 //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. 182 182 // ... ... @@ -189,11 +189,18 @@ 189 189 1.50 Beta 1 190 190 )))|((( 191 191 **FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %) 945 +)))|(% colspan="1" %)(% colspan="1" %) 946 +((( 947 + 192 192 ))) 193 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)949 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 194 194 ((( 195 195 (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. // 196 196 ))) 953 +|(% colspan="4" %)(% colspan="4" %) 954 +((( 955 +== 1.32 == 956 +))) 197 197 |((( 198 198 UI extensions 199 199 )))|((( ... ... @@ -200,11 +200,18 @@ 200 200 1.32 201 201 )))|((( 202 202 **Lua: GetComponentData() **removed the "nextdestname" property. 963 +)))|(% colspan="1" %)(% colspan="1" %) 964 +((( 965 + 203 203 ))) 204 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)967 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 205 205 ((( 206 206 //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.// 207 207 ))) 971 +|(% colspan="4" %)(% colspan="4" %) 972 +((( 973 +== 1.20 == 974 +))) 208 208 |((( 209 209 UI extensions 210 210 )))|((( ... ... @@ -211,8 +211,11 @@ 211 211 1.20 212 212 )))|((( 213 213 **FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %) 981 +)))|(% colspan="1" %)(% colspan="1" %) 982 +((( 983 + 214 214 ))) 215 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)985 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 216 216 ((( 217 217 //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.// 218 218 )))
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 - 792658401 +101548082 - url
-
... ... @@ -1,1 +1,1 @@ 1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/ 79265840/Breaking Changes1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/101548082/Breaking Changes