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. owen1 +xwiki:XWiki.cbj - Content
-
... ... @@ -24,186 +24,9 @@ 24 24 Version 25 25 )))|=((( 26 26 Summary 27 -)))|=(% colspan="1" %)(% colspan="1" %) 28 -((( 29 - 30 30 ))) 31 -|(% colspan="4" %)(% colspan="4" %) 32 -((( 33 -== 4.10 == 34 -))) 35 -|(% colspan="1" %)(% colspan="1" %) 36 -((( 37 -Scripts 38 -)))|(% colspan="1" %)(% colspan="1" %) 39 -((( 40 -4.10 Beta 1 41 -)))|(% colspan="1" %)(% colspan="1" %) 42 -((( 43 -$destructible.productions replaced with $defensible.productions 44 -)))|(% colspan="1" %)(% colspan="1" %) 45 -((( 46 - 47 -))) 48 48 |(% colspan="3" %)(% colspan="3" %) 49 49 ((( 50 -The $destructible.productions was reimplemented as $defensible.productions. The old implementation found the containing object of the destructible to query for the production modules. It should now be directly called defensible objects. 51 -)))|(% colspan="1" %)(% colspan="1" %) 52 -((( 53 - 54 -))) 55 -|((( 56 -Scripts 57 -)))|((( 58 -4.10 Beta 1 59 -)))|((( 60 -Removed script property $object.spawnsourceseed 61 -)))|((( 62 - 63 -))) 64 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 65 -((( 66 -The spawnsource seed is no longer directly accessable by scripts. Use $component.seed, which will internally use the spawnsource seed if able. Note: An improvement is that .seed on objects without a spawnsource seed will now return a result that differs between objects of the same macro, meaning it can now reliably be used for player property or job ships. 67 -))) 68 -|(% colspan="4" %)(% colspan="4" %) 69 -((( 70 -== 4.00 == 71 -))) 72 -|(% colspan="1" %)(% colspan="1" %) 73 -((( 74 -UI core 75 -)))|(% colspan="1" %)(% colspan="1" %) 76 -((( 77 -4.00 Beta 10 78 -)))|(% colspan="1" %)(% colspan="1" %) 79 -((( 80 -Controlled ship can change without a **gameplanchange-event** occurring. 81 -)))|(% colspan="1" %)(% colspan="1" %) 82 -((( 83 - 84 -))) 85 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 86 -((( 87 -//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). 88 -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. 89 -// 90 -)))|(% colspan="1" %)(% colspan="1" %) 91 -((( 92 - 93 -))) 94 -|((( 95 -Scripts 96 -)))|((( 97 -4.00 Beta 7 98 -)))|((( 99 -Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed 100 -)))|((( 101 - 102 -))) 103 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 104 -((( 105 -//Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects? 106 -New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits 107 -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// 108 -)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %) 109 -((( 110 - 111 -))) 112 -|(% colspan="1" %)(% colspan="1" %) 113 -((( 114 -UI core 115 -)))|(% colspan="1" %)(% colspan="1" %) 116 -((( 117 -4.00 Beta 6 118 -)))|(% colspan="1" %)(% colspan="1" %) 119 -((( 120 -**FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed 121 -)))|(% colspan="1" %)(% colspan="1" %) 122 -((( 123 - 124 -))) 125 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 126 -((( 127 -//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. 128 -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).// 129 - 130 -//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead. 131 -// 132 -)))|(% colspan="1" %)(% colspan="1" %) 133 -((( 134 - 135 -))) 136 -|(% colspan="1" %)(% colspan="1" %) 137 -((( 138 -UI core 139 -)))|(% colspan="1" %)(% colspan="1" %) 140 -((( 141 -4.00 Beta 5 142 -)))|(% colspan="1" %)(% colspan="1" %) 143 -((( 144 -**FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed 145 -)))|(% colspan="1" %)(% colspan="1" %) 146 -((( 147 - 148 -))) 149 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 150 -((( 151 -//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.// 152 - 153 -//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). 154 -)))|(% colspan="1" %)(% colspan="1" %) 155 -((( 156 - 157 -))) 158 -|((( 159 -Parameters 160 -)))|((( 161 -4.00 Beta 1 162 -)))|((( 163 -**requiresconstructionvessel** parameter moved 164 -)))|((( 165 - 166 -))) 167 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 168 -((( 169 -//The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.// 170 -))) 171 -|((( 172 -Scripts 173 -)))|((( 174 -4.00 Beta 1 175 -)))|((( 176 -Changed behaviour of **gatedistance** script property 177 -)))|((( 178 - 179 -))) 180 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 181 -((( 182 -//The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.// 183 -)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %) 184 -((( 185 - 186 -))) 187 -|(% colspan="4" %)(% colspan="4" %) 188 -((( 189 -== 3.30 == 190 -))) 191 -|((( 192 -UI extensions 193 -)))|((( 194 -3.30 Beta 3 195 -)))|((( 196 -**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()** 197 -)))|(% colspan="1" %)(% colspan="1" %) 198 -((( 199 - 200 -))) 201 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 202 -((( 203 -//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()// 204 -))) 205 -|(% colspan="4" %)(% colspan="4" %) 206 -((( 207 207 == 3.20 == 208 208 ))) 209 209 |((( ... ... @@ -212,49 +212,15 @@ 212 212 3.20 Beta 1 213 213 )))|((( 214 214 Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed 215 -)))|(% colspan="1" %)(% colspan="1" %) 216 -((( 217 - 218 218 ))) 219 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)39 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 220 220 ((( 221 221 //Old params: param = attacked object, param2 = attack method, param3 = attacked component// 222 222 //New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon] 223 223 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// 224 224 ))) 225 -|(% colspan=" 1" %)(% colspan="1" %)45 +|(% colspan="3" %)(% colspan="3" %) 226 226 ((( 227 -Scripts 228 -)))|(% colspan="1" %)(% colspan="1" %) 229 -((( 230 -3.20 Beta 1 231 -)))|(% colspan="1" %)(% colspan="1" %) 232 -((( 233 -Removed script property $trade.**restriction.faction** 234 -)))|(% colspan="1" %)(% colspan="1" %) 235 -((( 236 - 237 -))) 238 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 239 -((( 240 -//$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.// 241 -))) 242 -|((( 243 -UI extensions 244 -)))|((( 245 -3.20 Beta 1 246 -)))|((( 247 -**Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete! 248 -)))|(% colspan="1" %)(% colspan="1" %) 249 -((( 250 - 251 -))) 252 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 253 -((( 254 -//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.// 255 -))) 256 -|(% colspan="4" %)(% colspan="4" %) 257 -((( 258 258 == 3.10 == 259 259 ))) 260 260 |(% colspan="1" %)(% colspan="1" %) ... ... @@ -266,15 +266,12 @@ 266 266 )))|(% colspan="1" %)(% colspan="1" %) 267 267 ((( 268 268 Removed script action **<add_build/>** 269 -)))|(% colspan="1" %)(% colspan="1" %) 270 -((( 271 - 272 272 ))) 273 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)59 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 274 274 ((( 275 - //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.//61 +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. 276 276 ))) 277 -|(% colspan=" 4" %)(% colspan="4" %)63 +|(% colspan="3" %)(% colspan="3" %) 278 278 ((( 279 279 == 3.00 == 280 280 ))) ... ... @@ -287,13 +287,10 @@ 287 287 )))|(% colspan="1" %)(% colspan="1" %) 288 288 ((( 289 289 Changed behaviour of script action **<get_suitable_job/>** 290 -)))|(% colspan="1" %)(% colspan="1" %) 291 -((( 292 - 293 293 ))) 294 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)77 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 295 295 ((( 296 - //<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.//79 +<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. 297 297 ))) 298 298 |(% colspan="1" %)(% colspan="1" %) 299 299 ((( ... ... @@ -304,11 +304,8 @@ 304 304 )))|(% colspan="1" %)(% colspan="1" %) 305 305 ((( 306 306 Changed behaviour of script action **<get_ware_definition/>** 307 -)))|(% colspan="1" %)(% colspan="1" %) 308 -((( 309 - 310 310 ))) 311 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)91 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 312 312 ((( 313 313 //<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.// 314 314 ))) ... ... @@ -321,11 +321,8 @@ 321 321 )))|(% colspan="1" %)(% colspan="1" %) 322 322 ((( 323 323 Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case 324 -)))|(% colspan="1" %)(% colspan="1" %) 325 -((( 326 - 327 327 ))) 328 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)105 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 329 329 ((( 330 330 //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.)\\ 331 331 ... ... @@ -340,11 +340,8 @@ 340 340 )))|(% colspan="1" %)(% colspan="1" %) 341 341 ((( 342 342 Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions> 343 -)))|(% colspan="1" %)(% colspan="1" %) 344 -((( 345 - 346 346 ))) 347 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)121 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 348 348 ((( 349 349 //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.// 350 350 ))) ... ... @@ -357,11 +357,8 @@ 357 357 )))|(% colspan="1" %)(% colspan="1" %) 358 358 ((( 359 359 Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos** 360 -)))|(% colspan="1" %)(% colspan="1" %) 361 -((( 362 - 363 363 ))) 364 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)135 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 365 365 ((( 366 366 //Before the change, positions are relative to $dockingbay.parent. 367 367 After the change, positions are relative to $dockingbay as specified in the documentation.// ... ... @@ -375,11 +375,8 @@ 375 375 )))|(% colspan="1" %)(% colspan="1" %) 376 376 ((( 377 377 Support for entity flag "**skillsvisible**" dropped 378 -)))|(% colspan="1" %)(% colspan="1" %) 379 -((( 380 - 381 381 ))) 382 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)150 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 383 383 ((( 384 384 //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().// 385 385 ))) ... ... @@ -389,11 +389,8 @@ 389 389 3.0 Beta 2 390 390 )))|((( 391 391 Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**. 392 -)))|(% colspan="1" %)(% colspan="1" %) 393 -((( 394 - 395 395 ))) 396 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)161 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 397 397 ((( 398 398 //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. 399 399 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. ... ... @@ -409,11 +409,8 @@ 409 409 )))|(% colspan="1" %)(% colspan="1" %) 410 410 ((( 411 411 **MissionBoard** support dropped 412 -)))|(% colspan="1" %)(% colspan="1" %) 413 -((( 414 - 415 415 ))) 416 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)178 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 417 417 ((( 418 418 //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.// 419 419 ))) ... ... @@ -423,11 +423,8 @@ 423 423 3.0 Beta 1 424 424 )))|((( 425 425 By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined 426 -)))|(% colspan="1" %)(% colspan="1" %) 427 -((( 428 - 429 429 ))) 430 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)189 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 431 431 ((( 432 432 //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.// 433 433 ))) ... ... @@ -440,11 +440,8 @@ 440 440 )))|(% colspan="1" %)(% colspan="1" %) 441 441 ((( 442 442 Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'** 443 -)))|(% colspan="1" %)(% colspan="1" %) 444 -((( 445 - 446 446 ))) 447 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)203 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 448 448 ((( 449 449 //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.// 450 450 ))) ... ... @@ -457,11 +457,8 @@ 457 457 )))|(% colspan="1" %)(% colspan="1" %) 458 458 ((( 459 459 Script action **<set_doors_locked/>** attribute **'group'** changed 460 -)))|(% colspan="1" %)(% colspan="1" %) 461 -((( 462 - 463 463 ))) 464 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)217 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 465 465 ((( 466 466 //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.// 467 467 ))) ... ... @@ -474,11 +474,8 @@ 474 474 )))|(% colspan="1" %)(% colspan="1" %) 475 475 ((( 476 476 Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed 477 -)))|(% colspan="1" %)(% colspan="1" %) 478 -((( 479 - 480 480 ))) 481 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)231 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 482 482 ((( 483 483 //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.// 484 484 ))) ... ... @@ -491,11 +491,8 @@ 491 491 )))|(% colspan="1" %)(% colspan="1" %) 492 492 ((( 493 493 Script actions **<set_hack_target/>** and **<abort_hack/>** removed 494 -)))|(% colspan="1" %)(% colspan="1" %) 495 -((( 496 - 497 497 ))) 498 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)245 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 499 499 ((( 500 500 //These actions had no effect and were removed.// 501 501 ))) ... ... @@ -508,11 +508,8 @@ 508 508 )))|(% colspan="1" %)(% colspan="1" %) 509 509 ((( 510 510 **<setup_conversation_minigame/>** script action removed 511 -)))|(% colspan="1" %)(% colspan="1" %) 512 -((( 513 - 514 514 ))) 515 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)259 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 516 516 ((( 517 517 //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.// 518 518 ))) ... ... @@ -525,11 +525,8 @@ 525 525 )))|(% colspan="1" %)(% colspan="1" %) 526 526 ((( 527 527 <add_player_choice_*> **confidence** attribute removed 528 -)))|(% colspan="1" %)(% colspan="1" %) 529 -((( 530 - 531 531 ))) 532 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)273 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 533 533 ((( 534 534 //The default confidence of player options is another leftover from the XR era and had no effect in X4.// 535 535 ))) ... ... @@ -542,11 +542,8 @@ 542 542 )))|(% colspan="1" %)(% colspan="1" %) 543 543 ((( 544 544 **<hack_via_control_panel/>** script action removed 545 -)))|(% colspan="1" %)(% colspan="1" %) 546 -((( 547 - 548 548 ))) 549 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)287 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 550 550 ((( 551 551 //Unused script action <hack_via_control_panel/> was removed.// 552 552 ))) ... ... @@ -559,11 +559,8 @@ 559 559 )))|(% colspan="1" %)(% colspan="1" %) 560 560 ((( 561 561 **Lua: **GetMiniGameCursorPosition() removed 562 -)))|(% colspan="1" %)(% colspan="1" %) 563 -((( 564 - 565 565 ))) 566 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)301 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 567 567 ((( 568 568 //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.// 569 569 ))) ... ... @@ -573,11 +573,8 @@ 573 573 3.0 Beta 1 574 574 )))|((( 575 575 **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders 576 -)))|(% colspan="1" %)(% colspan="1" %) 577 -((( 578 - 579 579 ))) 580 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)312 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 581 581 ((( 582 582 //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.// 583 583 ))) ... ... @@ -590,11 +590,8 @@ 590 590 )))|(% colspan="1" %)(% colspan="1" %) 591 591 ((( 592 592 **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor 593 -)))|(% colspan="1" %)(% colspan="1" %) 594 -((( 595 - 596 596 ))) 597 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)326 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 598 598 ((( 599 599 //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.// 600 600 ))) ... ... @@ -607,11 +607,8 @@ 607 607 )))|(% colspan="1" %)(% colspan="1" %) 608 608 ((( 609 609 **$ware.illegal** updated 610 -)))|(% colspan="1" %)(% colspan="1" %) 611 -((( 612 - 613 613 ))) 614 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)340 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 615 615 ((( 616 616 //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.// 617 617 //It now returns true if $ware is illegal to any faction in the game.// ... ... @@ -625,11 +625,8 @@ 625 625 )))|(% colspan="1" %)(% colspan="1" %) 626 626 ((( 627 627 MD script **RML_Flight_Along_Path** removed 628 -)))|(% colspan="1" %)(% colspan="1" %) 629 -((( 630 - 631 631 ))) 632 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)355 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 633 633 ((( 634 634 //The MD script RML_Flight_Along_Path was not referened and was removed.// 635 635 ))) ... ... @@ -642,11 +642,8 @@ 642 642 )))|(% colspan="1" %)(% colspan="1" %) 643 643 ((( 644 644 parameters of **<event_venture_mission_completed/>** changed 645 -)))|(% colspan="1" %)(% colspan="1" %) 646 -((( 647 - 648 648 ))) 649 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)369 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 650 650 ((( 651 651 //old params: param = venture details, param2 = ships involved, param3 = duration// 652 652 //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration// ... ... @@ -658,11 +658,8 @@ 658 658 )))|((( 659 659 **<set_object_wing_name/>** removed, 660 660 **<set_object_fleet_name/>** added 661 -)))|(% colspan="1" %)(% colspan="1" %) 662 -((( 663 - 664 664 ))) 665 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)382 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 666 666 ((( 667 667 //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>// 668 668 ))) ... ... @@ -673,15 +673,12 @@ 673 673 )))|((( 674 674 **$controllable.wing.*** removed, 675 675 **$controllable.fleet.*** added 676 -)))|(% colspan="1" %)(% colspan="1" %) 677 -((( 678 - 679 679 ))) 680 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)394 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 681 681 ((( 682 682 $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander 683 683 ))) 684 -|(% colspan=" 4" %)(% colspan="4" %)398 +|(% colspan="3" %)(% colspan="3" %) 685 685 ((( 686 686 == 2.60 == 687 687 ))) ... ... @@ -691,11 +691,8 @@ 691 691 2.60 Beta 1 692 692 )))|((( 693 693 '**checkoperational**' filter behaviour changed 694 -)))|(% colspan="1" %)(% colspan="1" %) 695 -((( 696 - 697 697 ))) 698 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)409 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 699 699 ((( 700 700 //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.// 701 701 ... ... @@ -707,15 +707,12 @@ 707 707 2.60 Beta 1 708 708 )))|((( 709 709 $container.**supplyresources** behavior changed 710 -)))|(% colspan="1" %)(% colspan="1" %) 711 -((( 712 - 713 713 ))) 714 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)422 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 715 715 ((( 716 716 //The script keyword $container.supplyresources now includes reserved wares.// 717 717 ))) 718 -|(% colspan=" 4" %)(% colspan="4" %)426 +|(% colspan="3" %)(% colspan="3" %) 719 719 ((( 720 720 == 2.20 == 721 721 ))) ... ... @@ -728,11 +728,8 @@ 728 728 )))|(% colspan="1" %)(% colspan="1" %) 729 729 ((( 730 730 **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined. 731 -)))|(% colspan="1" %)(% colspan="1" %) 732 -((( 733 - 734 734 ))) 735 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)440 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 736 736 ((( 737 737 //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. 738 738 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.// ... ... @@ -749,15 +749,12 @@ 749 749 )))|(% colspan="1" %)(% colspan="1" %) 750 750 ((( 751 751 Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor' 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" %)458 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 757 757 ((( 758 758 //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.// 759 759 ))) 760 -|(% colspan=" 4" %)(% colspan="4" %)462 +|(% colspan="3" %)(% colspan="3" %) 761 761 ((( 762 762 == 2.00 == 763 763 ))) ... ... @@ -770,11 +770,8 @@ 770 770 )))|(% colspan="1" %)(% colspan="1" %) 771 771 ((( 772 772 **<event_build_finished/> **param2 now returns null instead of a construction sequence 773 -)))|(% colspan="1" %)(% colspan="1" %) 774 -((( 775 - 776 776 ))) 777 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)476 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 778 778 ((( 779 779 //The construction sequence which was finished should now be accessed via the buildtask provided via param3.// 780 780 ))) ... ... @@ -787,11 +787,8 @@ 787 787 )))|(% colspan="1" %)(% colspan="1" %) 788 788 ((( 789 789 **param.boarding.{...}** strength parameters removed 790 -)))|(% colspan="1" %)(% colspan="1" %) 791 -((( 792 - 793 793 ))) 794 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)490 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 795 795 ((( 796 796 //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.// 797 797 ))) ... ... @@ -804,11 +804,8 @@ 804 804 )))|(% colspan="1" %)(% colspan="1" %) 805 805 ((( 806 806 **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed 807 -)))|(% colspan="1" %)(% colspan="1" %) 808 -((( 809 - 810 810 ))) 811 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)504 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 812 812 ((( 813 813 //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.// 814 814 ))) ... ... @@ -818,11 +818,8 @@ 818 818 2.00 Beta 1 819 819 )))|((( 820 820 **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals 821 -)))|(% colspan="1" %)(% colspan="1" %) 822 -((( 823 - 824 824 ))) 825 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)515 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 826 826 ((( 827 827 //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.// 828 828 ))) ... ... @@ -832,11 +832,8 @@ 832 832 2.00 Beta 1 833 833 )))|((( 834 834 **FFI: SetFormationShape()** no longer indicates an error upon certain error cases 835 -)))|(% colspan="1" %)(% colspan="1" %) 836 -((( 837 - 838 838 ))) 839 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)526 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 840 840 ((( 841 841 //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.// 842 842 //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.// ... ... @@ -847,11 +847,8 @@ 847 847 2.00 Beta 1 848 848 )))|((( 849 849 **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated. 850 -)))|(% colspan="1" %)(% colspan="1" %) 851 -((( 852 - 853 853 ))) 854 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)538 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 855 855 ((( 856 856 //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.// 857 857 ))) ... ... @@ -861,11 +861,8 @@ 861 861 2.00 Beta 1 862 862 )))|((( 863 863 **<event_player_changed_target/>** now fires and returns null if the player deselects a target. 864 -)))|(% colspan="1" %)(% colspan="1" %) 865 -((( 866 - 867 867 ))) 868 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)549 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 869 869 ((( 870 870 //For prior behavior, check for event.param being non-null.// 871 871 ))) ... ... @@ -875,11 +875,8 @@ 875 875 2.00 Beta 1 876 876 )))|((( 877 877 **<shoot/>/<shoot_at/>** attribute changes. 878 -)))|(% colspan="1" %)(% colspan="1" %) 879 -((( 880 - 881 881 ))) 882 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)560 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 883 883 ((( 884 884 //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.// 885 885 //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.// ... ... @@ -893,11 +893,8 @@ 893 893 2.00 Beta 1 894 894 )))|((( 895 895 **FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% class="confluenceTd" %) 896 -)))|(% colspan="1" %)(% colspan="1" %) 897 -((( 898 - 899 899 ))) 900 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)575 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 901 901 ((( 902 902 //Added possibility to query build tasks of a certain buildmodule.// 903 903 ))) ... ... @@ -907,11 +907,8 @@ 907 907 2.00 Beta 1 908 908 )))|((( 909 909 **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field. 910 -)))|(% colspan="1" %)(% colspan="1" %) 911 -((( 912 - 913 913 ))) 914 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)586 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 915 915 ((( 916 916 //Added list of resources a buildmodule needs to build.// 917 917 ))) ... ... @@ -921,11 +921,8 @@ 921 921 2.00 Beta 1 922 922 )))|((( 923 923 (% 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);" %) 924 -)))|(% colspan="1" %)(% colspan="1" %) 925 -((( 926 - 927 927 ))) 928 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)597 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 929 929 ((( 930 930 //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.// 931 931 ))) ... ... @@ -935,15 +935,12 @@ 935 935 2.00 Beta 1 936 936 )))|((( 937 937 **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" %) 938 -)))|(% colspan="1" %)(% colspan="1" %) 939 -((( 940 - 941 941 ))) 942 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)608 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 943 943 ((( 944 944 //Changed return value type to const char* to better identify failure reasons in Lua script.// 945 945 ))) 946 -|(% colspan=" 4" %)(% colspan="4" %)612 +|(% colspan="3" %)(% colspan="3" %) 947 947 ((( 948 948 == 1.50 == 949 949 ))) ... ... @@ -953,11 +953,8 @@ 953 953 1.50 Beta 3 954 954 )))|((( 955 955 **Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %) 956 -)))|(% colspan="1" %)(% colspan="1" %) 957 -((( 958 - 959 959 ))) 960 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)623 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 961 961 ((( 962 962 //The "docksizes" property no longer includes internal ship storage docks.// 963 963 ))) ... ... @@ -967,11 +967,8 @@ 967 967 1.50 Beta 2 968 968 )))|((( 969 969 **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR). 970 -)))|(% colspan="1" %)(% colspan="1" %) 971 -((( 972 - 973 973 ))) 974 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)634 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 975 975 ((( 976 976 //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".// 977 977 ... ... @@ -985,11 +985,8 @@ 985 985 1.50 Beta 2 986 986 )))|((( 987 987 **FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %) 988 -)))|(% colspan="1" %)(% colspan="1" %) 989 -((( 990 - 991 991 ))) 992 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)649 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 993 993 ((( 994 994 //Added new "operational" field to retrieve information about number of operational upgrades in a group.// 995 995 ))) ... ... @@ -1002,11 +1002,8 @@ 1002 1002 )))|(% colspan="1" %)(% colspan="1" %) 1003 1003 ((( 1004 1004 **FFI: SetGuidance()** removed useinfopoint argument. 1005 -)))|(% colspan="1" %)(% colspan="1" %) 1006 -((( 1007 - 1008 1008 ))) 1009 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)663 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1010 1010 ((( 1011 1011 //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. 1012 1012 // ... ... @@ -1019,15 +1019,12 @@ 1019 1019 1.50 Beta 1 1020 1020 )))|((( 1021 1021 **FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %) 1022 -)))|(% colspan="1" %)(% colspan="1" %) 1023 -((( 1024 - 1025 1025 ))) 1026 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)677 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1027 1027 ((( 1028 1028 (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. // 1029 1029 ))) 1030 -|(% colspan=" 4" %)(% colspan="4" %)681 +|(% colspan="3" %)(% colspan="3" %) 1031 1031 ((( 1032 1032 == 1.32 == 1033 1033 ))) ... ... @@ -1037,15 +1037,12 @@ 1037 1037 1.32 1038 1038 )))|((( 1039 1039 **Lua: GetComponentData() **removed the "nextdestname" property. 1040 -)))|(% colspan="1" %)(% colspan="1" %) 1041 -((( 1042 - 1043 1043 ))) 1044 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)692 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1045 1045 ((( 1046 1046 //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.// 1047 1047 ))) 1048 -|(% colspan=" 4" %)(% colspan="4" %)696 +|(% colspan="3" %)(% colspan="3" %) 1049 1049 ((( 1050 1050 == 1.20 == 1051 1051 ))) ... ... @@ -1055,11 +1055,8 @@ 1055 1055 1.20 1056 1056 )))|((( 1057 1057 **FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %) 1058 -)))|(% colspan="1" %)(% colspan="1" %) 1059 -((( 1060 - 1061 1061 ))) 1062 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)707 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1063 1063 ((( 1064 1064 //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.// 1065 1065 )))
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 -1 029247861 +91947541 - url
-
... ... @@ -1,1 +1,1 @@ 1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/1 02924786/Breaking Changes1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/91947541/Breaking Changes