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.klaus - Content
-
... ... @@ -24,220 +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 10 41 -)))|(% colspan="1" %)(% colspan="1" %) 42 -((( 43 -Controlled ship can change without a **gameplanchange-event** occurring. 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 -//Before 4.00 Beta 10 it was ensured that there is no direct transition between the 'cockpit ui mode' of one ship to another. Instead, it was always ensured that the UI first transitions into the firstperson mode and then back into the cockpit mode (controlling then the other ship). 51 -In order to support the new emergency eject feature which was added in 4.00 Beta 7, this assurance was dropped. As of 4.00 Beta 10 it is now possible that the ship the player controls can swap without the gameplanchange-event being risen which one could rely upon in previous versions. If your addon relied on the fact that the ship would not change without first going into first person mode, you will have to adjust your addon accordingly.// 52 -)))|(% colspan="1" %)(% colspan="1" %) 53 -((( 54 - 55 -))) 56 -|((( 57 -Scripts 58 -)))|((( 59 -4.00 Beta 7 60 -)))|((( 61 -Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed 62 -)))|((( 63 - 64 -))) 65 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 66 -((( 67 -//Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects? 68 -New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits 69 -Note: param3 only exists in <event_terraforming_project_succeeded> and not in <event_terraforming_project_failed>, but both now have the booleans in a list for consistency// 70 -)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %) 71 -((( 72 - 73 -))) 74 -|(% colspan="1" %)(% colspan="1" %) 75 -((( 76 -UI core 77 -)))|(% colspan="1" %)(% colspan="1" %) 78 -((( 79 -4.00 Beta 6 80 -)))|(% colspan="1" %)(% colspan="1" %) 81 -((( 82 -**FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed 83 -)))|(% colspan="1" %)(% colspan="1" %) 84 -((( 85 - 86 -))) 87 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 88 -((( 89 -//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. 90 -Factions with a relation rating between -20 and -10 will now report a relation status of 'neutral' (aka: 1) instead of 'hostile'/'enemy' (aka: 0).// 91 - 92 -//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead. 93 -// 94 -)))|(% colspan="1" %)(% colspan="1" %) 95 -((( 96 - 97 -))) 98 -|(% colspan="1" %)(% colspan="1" %) 99 -((( 100 -UI core 101 -)))|(% colspan="1" %)(% colspan="1" %) 102 -((( 103 -4.00 Beta 5 104 -)))|(% colspan="1" %)(% colspan="1" %) 105 -((( 106 -**FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed 107 -)))|(% colspan="1" %)(% colspan="1" %) 108 -((( 109 - 110 -))) 111 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 112 -((( 113 -//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.// 114 - 115 -//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). 116 -)))|(% colspan="1" %)(% colspan="1" %) 117 -((( 118 - 119 -))) 120 -|((( 121 -Parameters 122 -)))|((( 123 -4.00 Beta 1 124 -)))|((( 125 -**requiresconstructionvessel** parameter moved 126 -)))|((( 127 - 128 -))) 129 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 130 -((( 131 -//The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.// 132 -))) 133 -|((( 134 -Scripts 135 -)))|((( 136 -4.00 Beta 1 137 -)))|((( 138 -Changed behaviour of **gatedistance** script property 139 -)))|((( 140 - 141 -))) 142 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 143 -((( 144 -//The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.// 145 -)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %) 146 -((( 147 - 148 -))) 149 -|(% colspan="4" %)(% colspan="4" %) 150 -((( 151 -== 3.30 == 152 -))) 153 -|((( 154 -UI extensions 155 -)))|((( 156 -3.30 Beta 3 157 -)))|((( 158 -**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()** 159 -)))|(% colspan="1" %)(% colspan="1" %) 160 -((( 161 - 162 -))) 163 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 164 -((( 165 -//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()// 166 -))) 167 -|(% colspan="4" %)(% colspan="4" %) 168 -((( 169 -== 3.20 == 170 -))) 171 -|((( 172 -Scripts 173 -)))|((( 174 -3.20 Beta 1 175 -)))|((( 176 -Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed 177 -)))|(% colspan="1" %)(% colspan="1" %) 178 -((( 179 - 180 -))) 181 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 182 -((( 183 -//Old params: param = attacked object, param2 = attack method, param3 = attacked component// 184 -//New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon] 185 -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// 186 -))) 187 -|(% colspan="1" %)(% colspan="1" %) 188 -((( 189 -Scripts 190 -)))|(% colspan="1" %)(% colspan="1" %) 191 -((( 192 -3.20 Beta 1 193 -)))|(% colspan="1" %)(% colspan="1" %) 194 -((( 195 -Removed script property $trade.**restriction.faction** 196 -)))|(% colspan="1" %)(% colspan="1" %) 197 -((( 198 - 199 -))) 200 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 201 -((( 202 -//$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.// 203 -))) 204 -|((( 205 -UI extensions 206 -)))|((( 207 -3.20 Beta 1 208 -)))|((( 209 -**Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete! 210 -)))|(% colspan="1" %)(% colspan="1" %) 211 -((( 212 - 213 -))) 214 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 215 -((( 216 -//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.// 217 -))) 218 -|(% colspan="4" %)(% colspan="4" %) 219 -((( 220 -== 3.10 == 221 -))) 222 -|(% colspan="1" %)(% colspan="1" %) 223 -((( 224 -Scripts 225 -)))|(% colspan="1" %)(% colspan="1" %) 226 -((( 227 -3.10 Beta 1 228 -)))|(% colspan="1" %)(% colspan="1" %) 229 -((( 230 -Removed script action **<add_build/>** 231 -)))|(% colspan="1" %)(% colspan="1" %) 232 -((( 233 - 234 -))) 235 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 236 -((( 237 -//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.// 238 -))) 239 -|(% colspan="4" %)(% colspan="4" %) 240 -((( 241 241 == 3.00 == 242 242 ))) 243 243 |(% colspan="1" %)(% colspan="1" %) ... ... @@ -245,68 +245,12 @@ 245 245 Scripts 246 246 )))|(% colspan="1" %)(% colspan="1" %) 247 247 ((( 248 -3.0 Beta 6 249 -)))|(% colspan="1" %)(% colspan="1" %) 250 -((( 251 -Changed behaviour of script action **<get_suitable_job/>** 252 -)))|(% colspan="1" %)(% colspan="1" %) 253 -((( 254 - 255 -))) 256 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 257 -((( 258 -//<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.// 259 -))) 260 -|(% colspan="1" %)(% colspan="1" %) 261 -((( 262 -Scripts 263 -)))|(% colspan="1" %)(% colspan="1" %) 264 -((( 265 -3.0 Beta 6 266 -)))|(% colspan="1" %)(% colspan="1" %) 267 -((( 268 -Changed behaviour of script action **<get_ware_definition/>** 269 -)))|(% colspan="1" %)(% colspan="1" %) 270 -((( 271 - 272 -))) 273 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 274 -((( 275 -//<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.// 276 -))) 277 -|(% colspan="1" %)(% colspan="1" %) 278 -((( 279 -Global 280 -)))|(% colspan="1" %)(% colspan="1" %) 281 -((( 282 282 3.0 Beta 5 283 283 )))|(% colspan="1" %)(% colspan="1" %) 284 284 ((( 285 -Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case 286 -)))|(% colspan="1" %)(% colspan="1" %) 287 -((( 288 - 289 -))) 290 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 291 -((( 292 -//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.)\\ 293 - 294 -//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).// 295 -))) 296 -|(% colspan="1" %)(% colspan="1" %) 297 -((( 298 -Scripts 299 -)))|(% colspan="1" %)(% colspan="1" %) 300 -((( 301 -3.0 Beta 5 302 -)))|(% colspan="1" %)(% colspan="1" %) 303 -((( 304 304 Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions> 305 -)))|(% colspan="1" %)(% colspan="1" %) 306 -((( 307 - 308 308 ))) 309 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)42 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 310 310 ((( 311 311 //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.// 312 312 ))) ... ... @@ -319,11 +319,8 @@ 319 319 )))|(% colspan="1" %)(% colspan="1" %) 320 320 ((( 321 321 Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos** 322 -)))|(% colspan="1" %)(% colspan="1" %) 323 -((( 324 - 325 325 ))) 326 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)56 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 327 327 ((( 328 328 //Before the change, positions are relative to $dockingbay.parent. 329 329 After the change, positions are relative to $dockingbay as specified in the documentation.// ... ... @@ -337,11 +337,8 @@ 337 337 )))|(% colspan="1" %)(% colspan="1" %) 338 338 ((( 339 339 Support for entity flag "**skillsvisible**" dropped 340 -)))|(% colspan="1" %)(% colspan="1" %) 341 -((( 342 - 343 343 ))) 344 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)71 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 345 345 ((( 346 346 //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().// 347 347 ))) ... ... @@ -351,11 +351,8 @@ 351 351 3.0 Beta 2 352 352 )))|((( 353 353 Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**. 354 -)))|(% colspan="1" %)(% colspan="1" %) 355 -((( 356 - 357 357 ))) 358 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)82 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 359 359 ((( 360 360 //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. 361 361 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. ... ... @@ -371,11 +371,8 @@ 371 371 )))|(% colspan="1" %)(% colspan="1" %) 372 372 ((( 373 373 **MissionBoard** support dropped 374 -)))|(% colspan="1" %)(% colspan="1" %) 375 -((( 376 - 377 377 ))) 378 -|(% 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" %) 379 379 ((( 380 380 //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.// 381 381 ))) ... ... @@ -385,11 +385,8 @@ 385 385 3.0 Beta 1 386 386 )))|((( 387 387 By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined 388 -)))|(% colspan="1" %)(% colspan="1" %) 389 -((( 390 - 391 391 ))) 392 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)110 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 393 393 ((( 394 394 //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.// 395 395 ))) ... ... @@ -402,11 +402,8 @@ 402 402 )))|(% colspan="1" %)(% colspan="1" %) 403 403 ((( 404 404 Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'** 405 -)))|(% colspan="1" %)(% colspan="1" %) 406 -((( 407 - 408 408 ))) 409 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)124 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 410 410 ((( 411 411 //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.// 412 412 ))) ... ... @@ -419,11 +419,8 @@ 419 419 )))|(% colspan="1" %)(% colspan="1" %) 420 420 ((( 421 421 Script action **<set_doors_locked/>** attribute **'group'** changed 422 -)))|(% colspan="1" %)(% colspan="1" %) 423 -((( 424 - 425 425 ))) 426 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)138 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 427 427 ((( 428 428 //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.// 429 429 ))) ... ... @@ -436,11 +436,8 @@ 436 436 )))|(% colspan="1" %)(% colspan="1" %) 437 437 ((( 438 438 Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed 439 -)))|(% colspan="1" %)(% colspan="1" %) 440 -((( 441 - 442 442 ))) 443 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)152 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 444 444 ((( 445 445 //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.// 446 446 ))) ... ... @@ -453,11 +453,8 @@ 453 453 )))|(% colspan="1" %)(% colspan="1" %) 454 454 ((( 455 455 Script actions **<set_hack_target/>** and **<abort_hack/>** removed 456 -)))|(% colspan="1" %)(% colspan="1" %) 457 -((( 458 - 459 459 ))) 460 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)166 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 461 461 ((( 462 462 //These actions had no effect and were removed.// 463 463 ))) ... ... @@ -470,11 +470,8 @@ 470 470 )))|(% colspan="1" %)(% colspan="1" %) 471 471 ((( 472 472 **<setup_conversation_minigame/>** script action removed 473 -)))|(% colspan="1" %)(% colspan="1" %) 474 -((( 475 - 476 476 ))) 477 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)180 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 478 478 ((( 479 479 //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.// 480 480 ))) ... ... @@ -487,11 +487,8 @@ 487 487 )))|(% colspan="1" %)(% colspan="1" %) 488 488 ((( 489 489 <add_player_choice_*> **confidence** attribute removed 490 -)))|(% colspan="1" %)(% colspan="1" %) 491 -((( 492 - 493 493 ))) 494 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)194 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 495 495 ((( 496 496 //The default confidence of player options is another leftover from the XR era and had no effect in X4.// 497 497 ))) ... ... @@ -504,11 +504,8 @@ 504 504 )))|(% colspan="1" %)(% colspan="1" %) 505 505 ((( 506 506 **<hack_via_control_panel/>** script action removed 507 -)))|(% colspan="1" %)(% colspan="1" %) 508 -((( 509 - 510 510 ))) 511 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)208 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 512 512 ((( 513 513 //Unused script action <hack_via_control_panel/> was removed.// 514 514 ))) ... ... @@ -521,11 +521,8 @@ 521 521 )))|(% colspan="1" %)(% colspan="1" %) 522 522 ((( 523 523 **Lua: **GetMiniGameCursorPosition() removed 524 -)))|(% colspan="1" %)(% colspan="1" %) 525 -((( 526 - 527 527 ))) 528 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)222 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 529 529 ((( 530 530 //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.// 531 531 ))) ... ... @@ -535,11 +535,8 @@ 535 535 3.0 Beta 1 536 536 )))|((( 537 537 **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders 538 -)))|(% colspan="1" %)(% colspan="1" %) 539 -((( 540 - 541 541 ))) 542 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)233 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 543 543 ((( 544 544 //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.// 545 545 ))) ... ... @@ -552,11 +552,8 @@ 552 552 )))|(% colspan="1" %)(% colspan="1" %) 553 553 ((( 554 554 **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor 555 -)))|(% colspan="1" %)(% colspan="1" %) 556 -((( 557 - 558 558 ))) 559 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)247 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 560 560 ((( 561 561 //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.// 562 562 ))) ... ... @@ -569,11 +569,8 @@ 569 569 )))|(% colspan="1" %)(% colspan="1" %) 570 570 ((( 571 571 **$ware.illegal** updated 572 -)))|(% colspan="1" %)(% colspan="1" %) 573 -((( 574 - 575 575 ))) 576 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)261 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 577 577 ((( 578 578 //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.// 579 579 //It now returns true if $ware is illegal to any faction in the game.// ... ... @@ -587,11 +587,8 @@ 587 587 )))|(% colspan="1" %)(% colspan="1" %) 588 588 ((( 589 589 MD script **RML_Flight_Along_Path** removed 590 -)))|(% colspan="1" %)(% colspan="1" %) 591 -((( 592 - 593 593 ))) 594 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)276 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 595 595 ((( 596 596 //The MD script RML_Flight_Along_Path was not referened and was removed.// 597 597 ))) ... ... @@ -604,11 +604,8 @@ 604 604 )))|(% colspan="1" %)(% colspan="1" %) 605 605 ((( 606 606 parameters of **<event_venture_mission_completed/>** changed 607 -)))|(% colspan="1" %)(% colspan="1" %) 608 -((( 609 - 610 610 ))) 611 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)290 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 612 612 ((( 613 613 //old params: param = venture details, param2 = ships involved, param3 = duration// 614 614 //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration// ... ... @@ -620,11 +620,8 @@ 620 620 )))|((( 621 621 **<set_object_wing_name/>** removed, 622 622 **<set_object_fleet_name/>** added 623 -)))|(% colspan="1" %)(% colspan="1" %) 624 -((( 625 - 626 626 ))) 627 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)303 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 628 628 ((( 629 629 //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>// 630 630 ))) ... ... @@ -635,15 +635,12 @@ 635 635 )))|((( 636 636 **$controllable.wing.*** removed, 637 637 **$controllable.fleet.*** added 638 -)))|(% colspan="1" %)(% colspan="1" %) 639 -((( 640 - 641 641 ))) 642 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)315 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 643 643 ((( 644 644 $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander 645 645 ))) 646 -|(% colspan=" 4" %)(% colspan="4" %)319 +|(% colspan="3" %)(% colspan="3" %) 647 647 ((( 648 648 == 2.60 == 649 649 ))) ... ... @@ -653,11 +653,8 @@ 653 653 2.60 Beta 1 654 654 )))|((( 655 655 '**checkoperational**' filter behaviour changed 656 -)))|(% colspan="1" %)(% colspan="1" %) 657 -((( 658 - 659 659 ))) 660 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)330 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 661 661 ((( 662 662 //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.// 663 663 ... ... @@ -669,15 +669,12 @@ 669 669 2.60 Beta 1 670 670 )))|((( 671 671 $container.**supplyresources** behavior changed 672 -)))|(% colspan="1" %)(% colspan="1" %) 673 -((( 674 - 675 675 ))) 676 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)343 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 677 677 ((( 678 678 //The script keyword $container.supplyresources now includes reserved wares.// 679 679 ))) 680 -|(% colspan=" 4" %)(% colspan="4" %)347 +|(% colspan="3" %)(% colspan="3" %) 681 681 ((( 682 682 == 2.20 == 683 683 ))) ... ... @@ -690,11 +690,8 @@ 690 690 )))|(% colspan="1" %)(% colspan="1" %) 691 691 ((( 692 692 **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined. 693 -)))|(% colspan="1" %)(% colspan="1" %) 694 -((( 695 - 696 696 ))) 697 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)361 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 698 698 ((( 699 699 //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. 700 700 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.// ... ... @@ -711,15 +711,12 @@ 711 711 )))|(% colspan="1" %)(% colspan="1" %) 712 712 ((( 713 713 Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor' 714 -)))|(% colspan="1" %)(% colspan="1" %) 715 -((( 716 - 717 717 ))) 718 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)379 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 719 719 ((( 720 720 //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.// 721 721 ))) 722 -|(% colspan=" 4" %)(% colspan="4" %)383 +|(% colspan="3" %)(% colspan="3" %) 723 723 ((( 724 724 == 2.00 == 725 725 ))) ... ... @@ -732,11 +732,8 @@ 732 732 )))|(% colspan="1" %)(% colspan="1" %) 733 733 ((( 734 734 **<event_build_finished/> **param2 now returns null instead of a construction sequence 735 -)))|(% colspan="1" %)(% colspan="1" %) 736 -((( 737 - 738 738 ))) 739 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)397 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 740 740 ((( 741 741 //The construction sequence which was finished should now be accessed via the buildtask provided via param3.// 742 742 ))) ... ... @@ -749,11 +749,8 @@ 749 749 )))|(% colspan="1" %)(% colspan="1" %) 750 750 ((( 751 751 **param.boarding.{...}** strength parameters removed 752 -)))|(% colspan="1" %)(% colspan="1" %) 753 -((( 754 - 755 755 ))) 756 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)411 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 757 757 ((( 758 758 //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.// 759 759 ))) ... ... @@ -766,11 +766,8 @@ 766 766 )))|(% colspan="1" %)(% colspan="1" %) 767 767 ((( 768 768 **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed 769 -)))|(% colspan="1" %)(% colspan="1" %) 770 -((( 771 - 772 772 ))) 773 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)425 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 774 774 ((( 775 775 //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.// 776 776 ))) ... ... @@ -780,11 +780,8 @@ 780 780 2.00 Beta 1 781 781 )))|((( 782 782 **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals 783 -)))|(% colspan="1" %)(% colspan="1" %) 784 -((( 785 - 786 786 ))) 787 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)436 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 788 788 ((( 789 789 //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.// 790 790 ))) ... ... @@ -794,11 +794,8 @@ 794 794 2.00 Beta 1 795 795 )))|((( 796 796 **FFI: SetFormationShape()** no longer indicates an error upon certain error cases 797 -)))|(% colspan="1" %)(% colspan="1" %) 798 -((( 799 - 800 800 ))) 801 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)447 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 802 802 ((( 803 803 //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.// 804 804 //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.// ... ... @@ -809,11 +809,8 @@ 809 809 2.00 Beta 1 810 810 )))|((( 811 811 **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated. 812 -)))|(% colspan="1" %)(% colspan="1" %) 813 -((( 814 - 815 815 ))) 816 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)459 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 817 817 ((( 818 818 //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.// 819 819 ))) ... ... @@ -823,11 +823,8 @@ 823 823 2.00 Beta 1 824 824 )))|((( 825 825 **<event_player_changed_target/>** now fires and returns null if the player deselects a target. 826 -)))|(% colspan="1" %)(% colspan="1" %) 827 -((( 828 - 829 829 ))) 830 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)470 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 831 831 ((( 832 832 //For prior behavior, check for event.param being non-null.// 833 833 ))) ... ... @@ -837,11 +837,8 @@ 837 837 2.00 Beta 1 838 838 )))|((( 839 839 **<shoot/>/<shoot_at/>** attribute changes. 840 -)))|(% colspan="1" %)(% colspan="1" %) 841 -((( 842 - 843 843 ))) 844 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)481 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 845 845 ((( 846 846 //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.// 847 847 //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.// ... ... @@ -855,11 +855,8 @@ 855 855 2.00 Beta 1 856 856 )))|((( 857 857 **FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% class="confluenceTd" %) 858 -)))|(% colspan="1" %)(% colspan="1" %) 859 -((( 860 - 861 861 ))) 862 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)496 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 863 863 ((( 864 864 //Added possibility to query build tasks of a certain buildmodule.// 865 865 ))) ... ... @@ -869,11 +869,8 @@ 869 869 2.00 Beta 1 870 870 )))|((( 871 871 **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field. 872 -)))|(% colspan="1" %)(% colspan="1" %) 873 -((( 874 - 875 875 ))) 876 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)507 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 877 877 ((( 878 878 //Added list of resources a buildmodule needs to build.// 879 879 ))) ... ... @@ -883,11 +883,8 @@ 883 883 2.00 Beta 1 884 884 )))|((( 885 885 (% 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);" %) 886 -)))|(% colspan="1" %)(% colspan="1" %) 887 -((( 888 - 889 889 ))) 890 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)518 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 891 891 ((( 892 892 //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.// 893 893 ))) ... ... @@ -897,15 +897,12 @@ 897 897 2.00 Beta 1 898 898 )))|((( 899 899 **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" %) 900 -)))|(% colspan="1" %)(% colspan="1" %) 901 -((( 902 - 903 903 ))) 904 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)529 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 905 905 ((( 906 906 //Changed return value type to const char* to better identify failure reasons in Lua script.// 907 907 ))) 908 -|(% colspan=" 4" %)(% colspan="4" %)533 +|(% colspan="3" %)(% colspan="3" %) 909 909 ((( 910 910 == 1.50 == 911 911 ))) ... ... @@ -915,11 +915,8 @@ 915 915 1.50 Beta 3 916 916 )))|((( 917 917 **Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %) 918 -)))|(% colspan="1" %)(% colspan="1" %) 919 -((( 920 - 921 921 ))) 922 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)544 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 923 923 ((( 924 924 //The "docksizes" property no longer includes internal ship storage docks.// 925 925 ))) ... ... @@ -929,11 +929,8 @@ 929 929 1.50 Beta 2 930 930 )))|((( 931 931 **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR). 932 -)))|(% colspan="1" %)(% colspan="1" %) 933 -((( 934 - 935 935 ))) 936 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)555 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 937 937 ((( 938 938 //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".// 939 939 ... ... @@ -947,11 +947,8 @@ 947 947 1.50 Beta 2 948 948 )))|((( 949 949 **FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %) 950 -)))|(% colspan="1" %)(% colspan="1" %) 951 -((( 952 - 953 953 ))) 954 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)570 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 955 955 ((( 956 956 //Added new "operational" field to retrieve information about number of operational upgrades in a group.// 957 957 ))) ... ... @@ -964,11 +964,8 @@ 964 964 )))|(% colspan="1" %)(% colspan="1" %) 965 965 ((( 966 966 **FFI: SetGuidance()** removed useinfopoint argument. 967 -)))|(% colspan="1" %)(% colspan="1" %) 968 -((( 969 - 970 970 ))) 971 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)584 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 972 972 ((( 973 973 //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. 974 974 // ... ... @@ -981,15 +981,12 @@ 981 981 1.50 Beta 1 982 982 )))|((( 983 983 **FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %) 984 -)))|(% colspan="1" %)(% colspan="1" %) 985 -((( 986 - 987 987 ))) 988 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)598 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 989 989 ((( 990 990 (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. // 991 991 ))) 992 -|(% colspan=" 4" %)(% colspan="4" %)602 +|(% colspan="3" %)(% colspan="3" %) 993 993 ((( 994 994 == 1.32 == 995 995 ))) ... ... @@ -999,15 +999,12 @@ 999 999 1.32 1000 1000 )))|((( 1001 1001 **Lua: GetComponentData() **removed the "nextdestname" property. 1002 -)))|(% colspan="1" %)(% colspan="1" %) 1003 -((( 1004 - 1005 1005 ))) 1006 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)613 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1007 1007 ((( 1008 1008 //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.// 1009 1009 ))) 1010 -|(% colspan=" 4" %)(% colspan="4" %)617 +|(% colspan="3" %)(% colspan="3" %) 1011 1011 ((( 1012 1012 == 1.20 == 1013 1013 ))) ... ... @@ -1017,11 +1017,8 @@ 1017 1017 1.20 1018 1018 )))|((( 1019 1019 **FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %) 1020 -)))|(% colspan="1" %)(% colspan="1" %) 1021 -((( 1022 - 1023 1023 ))) 1024 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)628 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1025 1025 ((( 1026 1026 //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.// 1027 1027 )))
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 - 1019093001 +89148312 - url
-
... ... @@ -1,1 +1,1 @@ 1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/ 101909300/Breaking Changes1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/89148312/Breaking Changes