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. matthias1 +xwiki:XWiki.stefan - Content
-
... ... @@ -24,773 +24,68 @@ 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 35 |(% colspan="1" %)(% colspan="1" %) 36 36 ((( 37 - Parameters30 +UI core 38 38 )))|(% colspan="1" %)(% colspan="1" %) 39 39 ((( 40 - 4.10 Beta333 +3.0 Beta 1 41 41 )))|(% colspan="1" %)(% colspan="1" %) 42 42 ((( 43 -Renamed **<stationinfobox>** to **<infobox>** 44 -)))|(% colspan="1" %)(% colspan="1" %) 45 -((( 46 - 36 +**Lua: **GetMiniGameCursorPosition() removed 47 47 ))) 48 48 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 49 49 ((( 50 -Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that. 51 -)))|(% colspan="1" %)(% colspan="1" %) 52 -((( 53 - 40 +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. 54 54 ))) 55 55 |(% colspan="1" %)(% colspan="1" %) 56 56 ((( 57 -UI extensions 58 -)))|(% colspan="1" %)(% colspan="1" %) 59 -((( 60 -4.10 Beta 2 61 -)))|(% colspan="1" %)(% colspan="1" %) 62 -((( 63 -**FFI**: SetMacroMapPlayerSectorOffset() deprecated 64 -)))|(% colspan="1" %)(% colspan="1" %) 65 -((( 66 - 67 -))) 68 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 69 -((( 70 -The functionality represented by //SetMacroMapPlayerSectorOffset//() has been removed and the function was therefore stubbed. Setting the gamestart properties "sector" and "offset" will affect the universe macro map instead directly. 71 -)))|(% colspan="1" %)(% colspan="1" %) 72 -((( 73 - 74 -))) 75 -|((( 76 -UI extensions 77 -)))|((( 78 -4.10 Beta 2 79 -)))|((( 80 -**FFI**: (% style="color: rgb(0,0,0);" %)FilterComponentForMapMode(%%)() and (% style="color: rgb(0,0,0);" %)SetMapObjectFilter() changed 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 -//These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.// 88 -)))|(% colspan="1" %)(% colspan="1" %) 89 -((( 90 - 91 -))) 92 -|((( 93 93 Scripts 94 -)))|((( 95 -4.10 Beta 1 96 -)))|((( 97 -People related attributes of mission** <delivery> **node moved 98 -)))|((( 99 - 100 -))) 101 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 102 -((( 103 -//The <delivery> node of <create_mission> and <update_mission> has been changed to support a new <wares> subnode. The people related attributes: 'people' and 'skills' have been moved from the <delivery> node itself to a <people> subnode.// 104 -))) 105 -|(% colspan="1" %)(% colspan="1" %) 106 -((( 107 -Scripts 108 108 )))|(% colspan="1" %)(% colspan="1" %) 109 109 ((( 110 - 4.10 Beta 147 +3.0 Beta 1 111 111 )))|(% colspan="1" %)(% colspan="1" %) 112 112 ((( 113 -**$destructible.productions** replaced with $defensible.productions 114 -)))|(% colspan="1" %)(% colspan="1" %) 115 -((( 116 - 50 +$ware.illegal updated 117 117 ))) 118 118 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 119 119 ((( 120 -//The $destructible.productions script property was removed and reimplemented as $defensible.productions meaning some old uses may no longer work unless the destructible is also a defensible. The old implementation functioned by finding the containing object of the destructible (including itself) to query for the production modules.// 121 -)))|(% colspan="1" %)(% colspan="1" %) 122 -((( 123 - 54 +$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used. 55 +\\It now returns true if $ware is illegal to any faction in the game. 124 124 ))) 125 -|((( 126 -Scripts 127 -)))|((( 128 -4.10 Beta 1 129 -)))|((( 130 -Removed script property **$object.spawnsourceseed** 131 -)))|((( 132 - 133 -))) 134 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 135 -((( 136 -//The spawnsource seed is no longer directly accessible by scripts. Use $component.seed, which will internally use the spawnsource seed if able. Note: An improvement is that .seed on objects without a spawnsource seed will now result in a value that differs between objects of the same macro, meaning it can now reliably be used for player property or job ships.// 137 -))) 138 -|(% colspan="4" %)(% colspan="4" %) 139 -((( 140 -== 4.00 == 141 -))) 142 142 |(% colspan="1" %)(% colspan="1" %) 143 143 ((( 144 -UI core 145 -)))|(% colspan="1" %)(% colspan="1" %) 146 -((( 147 -4.00 Beta 10 148 -)))|(% colspan="1" %)(% colspan="1" %) 149 -((( 150 -Controlled ship can change without a **gameplanchange-event** occurring. 151 -)))|(% colspan="1" %)(% colspan="1" %) 152 -((( 153 - 154 -))) 155 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 156 -((( 157 -//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). 158 -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. 159 -// 160 -)))|(% colspan="1" %)(% colspan="1" %) 161 -((( 162 - 163 -))) 164 -|((( 165 165 Scripts 166 -)))|((( 167 -4.00 Beta 7 168 -)))|((( 169 -Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed 170 -)))|((( 171 - 172 -))) 173 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 174 -((( 175 -//Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects? 176 -New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits 177 -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// 178 -)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %) 179 -((( 180 - 181 -))) 182 -|(% colspan="1" %)(% colspan="1" %) 183 -((( 184 -UI core 185 185 )))|(% colspan="1" %)(% colspan="1" %) 186 186 ((( 187 - 4.00Beta662 +3.0 Beta 1 188 188 )))|(% colspan="1" %)(% colspan="1" %) 189 189 ((( 190 -**FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed 191 -)))|(% colspan="1" %)(% colspan="1" %) 192 -((( 193 - 65 +'checkoperational' filter behaviour changed 194 194 ))) 195 195 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 196 196 ((( 197 -//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. 198 -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).// 69 +//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.// 199 199 200 -//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead. 201 -// 202 -)))|(% colspan="1" %)(% colspan="1" %) 203 -((( 204 - 71 +//Sub nodes such as match_child will have checkoperational default to false. Existing uses may find that results now include non-operational components.// 205 205 ))) 206 206 |(% colspan="1" %)(% colspan="1" %) 207 207 ((( 208 -UI core 209 -)))|(% colspan="1" %)(% colspan="1" %) 210 -((( 211 -4.00 Beta 5 212 -)))|(% colspan="1" %)(% colspan="1" %) 213 -((( 214 -**FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed 215 -)))|(% colspan="1" %)(% colspan="1" %) 216 -((( 217 - 218 -))) 219 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 220 -((( 221 -//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.// 222 - 223 -//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). 224 -)))|(% colspan="1" %)(% colspan="1" %) 225 -((( 226 - 227 -))) 228 -|((( 229 -Parameters 230 -)))|((( 231 -4.00 Beta 1 232 -)))|((( 233 -**requiresconstructionvessel** parameter moved 234 -)))|((( 235 - 236 -))) 237 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 238 -((( 239 -//The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.// 240 -))) 241 -|((( 242 242 Scripts 243 -)))|((( 244 -4.00 Beta 1 245 -)))|((( 246 -Changed behaviour of **gatedistance** script property 247 -)))|((( 248 - 249 -))) 250 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 251 -((( 252 -//The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.// 253 -)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %) 254 -((( 255 - 256 -))) 257 -|(% colspan="4" %)(% colspan="4" %) 258 -((( 259 -== 3.30 == 260 -))) 261 -|((( 262 -UI extensions 263 -)))|((( 264 -3.30 Beta 3 265 -)))|((( 266 -**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()** 267 267 )))|(% colspan="1" %)(% colspan="1" %) 268 268 ((( 269 - 270 -))) 271 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 272 -((( 273 -//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()// 274 -))) 275 -|(% colspan="4" %)(% colspan="4" %) 276 -((( 277 -== 3.20 == 278 -))) 279 -|((( 280 -Scripts 281 -)))|((( 282 -3.20 Beta 1 283 -)))|((( 284 -Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed 285 -)))|(% colspan="1" %)(% colspan="1" %) 286 -((( 287 - 288 -))) 289 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 290 -((( 291 -//Old params: param = attacked object, param2 = attack method, param3 = attacked component// 292 -//New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon] 293 -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// 294 -))) 295 -|(% colspan="1" %)(% colspan="1" %) 296 -((( 297 -Scripts 298 -)))|(% colspan="1" %)(% colspan="1" %) 299 -((( 300 -3.20 Beta 1 301 -)))|(% colspan="1" %)(% colspan="1" %) 302 -((( 303 -Removed script property $trade.**restriction.faction** 304 -)))|(% colspan="1" %)(% colspan="1" %) 305 -((( 306 - 307 -))) 308 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 309 -((( 310 -//$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.// 311 -))) 312 -|((( 313 -UI extensions 314 -)))|((( 315 -3.20 Beta 1 316 -)))|((( 317 -**Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete! 318 -)))|(% colspan="1" %)(% colspan="1" %) 319 -((( 320 - 321 -))) 322 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 323 -((( 324 -//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.// 325 -))) 326 -|(% colspan="4" %)(% colspan="4" %) 327 -((( 328 -== 3.10 == 329 -))) 330 -|(% colspan="1" %)(% colspan="1" %) 331 -((( 332 -Scripts 333 -)))|(% colspan="1" %)(% colspan="1" %) 334 -((( 335 -3.10 Beta 1 336 -)))|(% colspan="1" %)(% colspan="1" %) 337 -((( 338 -Removed script action **<add_build/>** 339 -)))|(% colspan="1" %)(% colspan="1" %) 340 -((( 341 - 342 -))) 343 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 344 -((( 345 -//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.// 346 -))) 347 -|(% colspan="4" %)(% colspan="4" %) 348 -((( 349 -== 3.00 == 350 -))) 351 -|(% colspan="1" %)(% colspan="1" %) 352 -((( 353 -Scripts 354 -)))|(% colspan="1" %)(% colspan="1" %) 355 -((( 356 -3.0 Beta 6 357 -)))|(% colspan="1" %)(% colspan="1" %) 358 -((( 359 -Changed behaviour of script action **<get_suitable_job/>** 360 -)))|(% colspan="1" %)(% colspan="1" %) 361 -((( 362 - 363 -))) 364 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 365 -((( 366 -//<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.// 367 -))) 368 -|(% colspan="1" %)(% colspan="1" %) 369 -((( 370 -Scripts 371 -)))|(% colspan="1" %)(% colspan="1" %) 372 -((( 373 -3.0 Beta 6 374 -)))|(% colspan="1" %)(% colspan="1" %) 375 -((( 376 -Changed behaviour of script action **<get_ware_definition/>** 377 -)))|(% colspan="1" %)(% colspan="1" %) 378 -((( 379 - 380 -))) 381 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 382 -((( 383 -//<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.// 384 -))) 385 -|(% colspan="1" %)(% colspan="1" %) 386 -((( 387 -Global 388 -)))|(% colspan="1" %)(% colspan="1" %) 389 -((( 390 -3.0 Beta 5 391 -)))|(% colspan="1" %)(% colspan="1" %) 392 -((( 393 -Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case 394 -)))|(% colspan="1" %)(% colspan="1" %) 395 -((( 396 - 397 -))) 398 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 399 -((( 400 -//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.)\\ 401 - 402 -//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).// 403 -))) 404 -|(% colspan="1" %)(% colspan="1" %) 405 -((( 406 -Scripts 407 -)))|(% colspan="1" %)(% colspan="1" %) 408 -((( 409 -3.0 Beta 5 410 -)))|(% colspan="1" %)(% colspan="1" %) 411 -((( 412 -Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions> 413 -)))|(% colspan="1" %)(% colspan="1" %) 414 -((( 415 - 416 -))) 417 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 418 -((( 419 -//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.// 420 -))) 421 -|(% colspan="1" %)(% colspan="1" %) 422 -((( 423 -Scripts 424 -)))|(% colspan="1" %)(% colspan="1" %) 425 -((( 426 -3.0 Beta 5 427 -)))|(% colspan="1" %)(% colspan="1" %) 428 -((( 429 -Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos** 430 -)))|(% colspan="1" %)(% colspan="1" %) 431 -((( 432 - 433 -))) 434 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 435 -((( 436 -//Before the change, positions are relative to $dockingbay.parent. 437 -After the change, positions are relative to $dockingbay as specified in the documentation.// 438 -))) 439 -|(% colspan="1" %)(% colspan="1" %) 440 -((( 441 -Global 442 -)))|(% colspan="1" %)(% colspan="1" %) 443 -((( 444 -3.0 Beta 2 445 -)))|(% colspan="1" %)(% colspan="1" %) 446 -((( 447 -Support for entity flag "**skillsvisible**" dropped 448 -)))|(% colspan="1" %)(% colspan="1" %) 449 -((( 450 - 451 -))) 452 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 453 -((( 454 -//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().// 455 -))) 456 -|((( 457 -Scripts 458 -)))|((( 459 -3.0 Beta 2 460 -)))|((( 461 -Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**. 462 -)))|(% colspan="1" %)(% colspan="1" %) 463 -((( 464 - 465 -))) 466 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 467 -((( 468 -//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. 469 -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. 470 -If in your scripts you make use of the <event_object_changed_owner> condition you need to verify that you indeed want to work with the "effective" component owner or whether your script code actually should work with the true owner of an object and update your code accordingly. 471 -On top of that the 3rd parameter of <event_object_changed_owner> (trueprevious) was dropped as the event is no longer triggered upon a change of the true owner alone (i.e. only if the change of the true owner has also an effect on the "effective" component owner). 472 -))) 473 -|(% colspan="1" %)(% colspan="1" %) 474 -((( 475 -Global 476 -)))|(% colspan="1" %)(% colspan="1" %) 477 -((( 478 478 3.0 Beta 1 479 479 )))|(% colspan="1" %)(% colspan="1" %) 480 480 ((( 481 -**MissionBoard** support dropped 482 -)))|(% colspan="1" %)(% colspan="1" %) 483 -((( 484 - 485 -))) 486 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 487 -((( 488 -//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.// 489 -))) 490 -|((( 491 -Job/God 492 -)))|((( 493 -3.0 Beta 1 494 -)))|((( 495 -By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined 496 -)))|(% colspan="1" %)(% colspan="1" %) 497 -((( 498 - 499 -))) 500 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 501 -((( 502 -//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.// 503 -))) 504 -|(% colspan="1" %)(% colspan="1" %) 505 -((( 506 -Scripts 507 -)))|(% colspan="1" %)(% colspan="1" %) 508 -((( 509 -3.0 Beta 1 510 -)))|(% colspan="1" %)(% colspan="1" %) 511 -((( 512 -Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'** 513 -)))|(% colspan="1" %)(% colspan="1" %) 514 -((( 515 - 516 -))) 517 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 518 -((( 519 -//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.// 520 -))) 521 -|(% colspan="1" %)(% colspan="1" %) 522 -((( 523 -Scripts 524 -)))|(% colspan="1" %)(% colspan="1" %) 525 -((( 526 -3.0 Beta 1 527 -)))|(% colspan="1" %)(% colspan="1" %) 528 -((( 529 -Script action **<set_doors_locked/>** attribute **'group'** changed 530 -)))|(% colspan="1" %)(% colspan="1" %) 531 -((( 532 - 533 -))) 534 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 535 -((( 536 -//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.// 537 -))) 538 -|(% colspan="1" %)(% colspan="1" %) 539 -((( 540 -Scripts 541 -)))|(% colspan="1" %)(% colspan="1" %) 542 -((( 543 -3.0 Beta 1 544 -)))|(% colspan="1" %)(% colspan="1" %) 545 -((( 546 -Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed 547 -)))|(% colspan="1" %)(% colspan="1" %) 548 -((( 549 - 550 -))) 551 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 552 -((( 553 -//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.// 554 -))) 555 -|(% colspan="1" %)(% colspan="1" %) 556 -((( 557 -Scripts 558 -)))|(% colspan="1" %)(% colspan="1" %) 559 -((( 560 -3.0 Beta 1 561 -)))|(% colspan="1" %)(% colspan="1" %) 562 -((( 563 -Script actions **<set_hack_target/>** and **<abort_hack/>** removed 564 -)))|(% colspan="1" %)(% colspan="1" %) 565 -((( 566 - 567 -))) 568 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 569 -((( 570 -//These actions had no effect and were removed.// 571 -))) 572 -|(% colspan="1" %)(% colspan="1" %) 573 -((( 574 -Scripts 575 -)))|(% colspan="1" %)(% colspan="1" %) 576 -((( 577 -3.0 Beta 1 578 -)))|(% colspan="1" %)(% colspan="1" %) 579 -((( 580 -**<setup_conversation_minigame/>** script action removed 581 -)))|(% colspan="1" %)(% colspan="1" %) 582 -((( 583 - 584 -))) 585 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 586 -((( 587 -//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.// 588 -))) 589 -|(% colspan="1" %)(% colspan="1" %) 590 -((( 591 -Scripts 592 -)))|(% colspan="1" %)(% colspan="1" %) 593 -((( 594 -3.0 Beta 1 595 -)))|(% colspan="1" %)(% colspan="1" %) 596 -((( 597 -<add_player_choice_*> **confidence** attribute removed 598 -)))|(% colspan="1" %)(% colspan="1" %) 599 -((( 600 - 601 -))) 602 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 603 -((( 604 -//The default confidence of player options is another leftover from the XR era and had no effect in X4.// 605 -))) 606 -|(% colspan="1" %)(% colspan="1" %) 607 -((( 608 -Scripts 609 -)))|(% colspan="1" %)(% colspan="1" %) 610 -((( 611 -3.0 Beta 1 612 -)))|(% colspan="1" %)(% colspan="1" %) 613 -((( 614 -**<hack_via_control_panel/>** script action removed 615 -)))|(% colspan="1" %)(% colspan="1" %) 616 -((( 617 - 618 -))) 619 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 620 -((( 621 -//Unused script action <hack_via_control_panel/> was removed.// 622 -))) 623 -|(% colspan="1" %)(% colspan="1" %) 624 -((( 625 -UI core 626 -)))|(% colspan="1" %)(% colspan="1" %) 627 -((( 628 -3.0 Beta 1 629 -)))|(% colspan="1" %)(% colspan="1" %) 630 -((( 631 -**Lua: **GetMiniGameCursorPosition() removed 632 -)))|(% colspan="1" %)(% colspan="1" %) 633 -((( 634 - 635 -))) 636 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 637 -((( 638 -//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.// 639 -))) 640 -|((( 641 -UI core 642 -)))|((( 643 -3.0 Beta 1 644 -)))|((( 645 -**FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders 646 -)))|(% colspan="1" %)(% colspan="1" %) 647 -((( 648 - 649 -))) 650 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 651 -((( 652 -//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.// 653 -))) 654 -|(% colspan="1" %)(% colspan="1" %) 655 -((( 656 -UI extensions 657 -)))|(% colspan="1" %)(% colspan="1" %) 658 -((( 659 -3.0 Beta 1 660 -)))|(% colspan="1" %)(% colspan="1" %) 661 -((( 662 -**FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor 663 -)))|(% colspan="1" %)(% colspan="1" %) 664 -((( 665 - 666 -))) 667 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 668 -((( 669 -//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.// 670 -))) 671 -|(% colspan="1" %)(% colspan="1" %) 672 -((( 673 -Scripts 674 -)))|(% colspan="1" %)(% colspan="1" %) 675 -((( 676 -3.0 Beta 1 677 -)))|(% colspan="1" %)(% colspan="1" %) 678 -((( 679 -**$ware.illegal** updated 680 -)))|(% colspan="1" %)(% colspan="1" %) 681 -((( 682 - 683 -))) 684 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 685 -((( 686 -//$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.// 687 -//It now returns true if $ware is illegal to any faction in the game.// 688 -))) 689 -|(% colspan="1" %)(% colspan="1" %) 690 -((( 691 -Scripts 692 -)))|(% colspan="1" %)(% colspan="1" %) 693 -((( 694 -3.0 Beta 1 695 -)))|(% colspan="1" %)(% colspan="1" %) 696 -((( 697 697 MD script **RML_Flight_Along_Path** removed 698 -)))|(% colspan="1" %)(% colspan="1" %) 699 -((( 700 - 701 701 ))) 702 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)83 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 703 703 ((( 704 704 //The MD script RML_Flight_Along_Path was not referened and was removed.// 705 705 ))) 706 706 |(% colspan="1" %)(% colspan="1" %) 707 707 ((( 708 -Scripts 709 -)))|(% colspan="1" %)(% colspan="1" %) 710 -((( 711 -3.0 Beta 1 712 -)))|(% colspan="1" %)(% colspan="1" %) 713 -((( 714 -parameters of **<event_venture_mission_completed/>** changed 715 -)))|(% colspan="1" %)(% colspan="1" %) 716 -((( 717 - 718 -))) 719 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 720 -((( 721 -//old params: param = venture details, param2 = ships involved, param3 = duration// 722 -//new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration// 723 -))) 724 -|((( 725 -Scripts 726 -)))|((( 727 -3.0 Beta 1 728 -)))|((( 729 -**<set_object_wing_name/>** removed, 730 -**<set_object_fleet_name/>** added 731 -)))|(% colspan="1" %)(% colspan="1" %) 732 -((( 733 - 734 -))) 735 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 736 -((( 737 -//The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>// 738 -))) 739 -|((( 740 -Scripts 741 -)))|((( 742 -3.0 Beta 1 743 -)))|((( 744 -**$controllable.wing.*** removed, 745 -**$controllable.fleet.*** added 746 -)))|(% colspan="1" %)(% colspan="1" %) 747 -((( 748 - 749 -))) 750 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 751 -((( 752 -$controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander 753 -))) 754 -|(% colspan="4" %)(% colspan="4" %) 755 -((( 756 -== 2.60 == 757 -))) 758 -|((( 759 -Scripts 760 -)))|((( 761 -2.60 Beta 1 762 -)))|((( 763 -'**checkoperational**' filter behaviour changed 764 -)))|(% colspan="1" %)(% colspan="1" %) 765 -((( 766 - 767 -))) 768 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 769 -((( 770 -//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.// 771 - 772 -//Sub nodes such as match_child will have checkoperational default to false. Existing uses may find that results now include non-operational components.// 773 -))) 774 -|((( 775 -Scripts 776 -)))|((( 777 -2.60 Beta 1 778 -)))|((( 779 -$container.**supplyresources** behavior changed 780 -)))|(% colspan="1" %)(% colspan="1" %) 781 -((( 782 - 783 -))) 784 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 785 -((( 786 -//The script keyword $container.supplyresources now includes reserved wares.// 787 -))) 788 -|(% colspan="4" %)(% colspan="4" %) 789 -((( 790 -== 2.20 == 791 -))) 792 -|(% colspan="1" %)(% colspan="1" %) 793 -((( 794 794 UI core 795 795 )))|(% colspan="1" %)(% colspan="1" %) 796 796 ((( ... ... @@ -798,11 +798,8 @@ 798 798 )))|(% colspan="1" %)(% colspan="1" %) 799 799 ((( 800 800 **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined. 801 -)))|(% colspan="1" %)(% colspan="1" %) 802 -((( 803 - 804 804 ))) 805 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)97 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 806 806 ((( 807 807 //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. 808 808 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.// ... ... @@ -819,18 +819,11 @@ 819 819 )))|(% colspan="1" %)(% colspan="1" %) 820 820 ((( 821 821 Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor' 822 -)))|(% colspan="1" %)(% colspan="1" %) 823 -((( 824 - 825 825 ))) 826 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)115 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 827 827 ((( 828 828 //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.// 829 829 ))) 830 -|(% colspan="4" %)(% colspan="4" %) 831 -((( 832 -== 2.00 == 833 -))) 834 834 |(% colspan="1" %)(% colspan="1" %) 835 835 ((( 836 836 Scripts ... ... @@ -840,11 +840,8 @@ 840 840 )))|(% colspan="1" %)(% colspan="1" %) 841 841 ((( 842 842 **<event_build_finished/> **param2 now returns null instead of a construction sequence 843 -)))|(% colspan="1" %)(% colspan="1" %) 844 -((( 845 - 846 846 ))) 847 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)129 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 848 848 ((( 849 849 //The construction sequence which was finished should now be accessed via the buildtask provided via param3.// 850 850 ))) ... ... @@ -857,11 +857,8 @@ 857 857 )))|(% colspan="1" %)(% colspan="1" %) 858 858 ((( 859 859 **param.boarding.{...}** strength parameters removed 860 -)))|(% colspan="1" %)(% colspan="1" %) 861 -((( 862 - 863 863 ))) 864 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)143 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 865 865 ((( 866 866 //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.// 867 867 ))) ... ... @@ -874,11 +874,8 @@ 874 874 )))|(% colspan="1" %)(% colspan="1" %) 875 875 ((( 876 876 **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed 877 -)))|(% colspan="1" %)(% colspan="1" %) 878 -((( 879 - 880 880 ))) 881 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)157 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 882 882 ((( 883 883 //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.// 884 884 ))) ... ... @@ -888,11 +888,8 @@ 888 888 2.00 Beta 1 889 889 )))|((( 890 890 **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals 891 -)))|(% colspan="1" %)(% colspan="1" %) 892 -((( 893 - 894 894 ))) 895 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)168 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 896 896 ((( 897 897 //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.// 898 898 ))) ... ... @@ -902,11 +902,8 @@ 902 902 2.00 Beta 1 903 903 )))|((( 904 904 **FFI: SetFormationShape()** no longer indicates an error upon certain error cases 905 -)))|(% colspan="1" %)(% colspan="1" %) 906 -((( 907 - 908 908 ))) 909 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)179 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 910 910 ((( 911 911 //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.// 912 912 //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.// ... ... @@ -917,11 +917,8 @@ 917 917 2.00 Beta 1 918 918 )))|((( 919 919 **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated. 920 -)))|(% colspan="1" %)(% colspan="1" %) 921 -((( 922 - 923 923 ))) 924 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)191 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 925 925 ((( 926 926 //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.// 927 927 ))) ... ... @@ -931,11 +931,8 @@ 931 931 2.00 Beta 1 932 932 )))|((( 933 933 **<event_player_changed_target/>** now fires and returns null if the player deselects a target. 934 -)))|(% colspan="1" %)(% colspan="1" %) 935 -((( 936 - 937 937 ))) 938 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)202 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 939 939 ((( 940 940 //For prior behavior, check for event.param being non-null.// 941 941 ))) ... ... @@ -945,11 +945,8 @@ 945 945 2.00 Beta 1 946 946 )))|((( 947 947 **<shoot/>/<shoot_at/>** attribute changes. 948 -)))|(% colspan="1" %)(% colspan="1" %) 949 -((( 950 - 951 951 ))) 952 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)213 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 953 953 ((( 954 954 //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.// 955 955 //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.// ... ... @@ -963,11 +963,8 @@ 963 963 2.00 Beta 1 964 964 )))|((( 965 965 **FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% class="confluenceTd" %) 966 -)))|(% colspan="1" %)(% colspan="1" %) 967 -((( 968 - 969 969 ))) 970 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)228 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 971 971 ((( 972 972 //Added possibility to query build tasks of a certain buildmodule.// 973 973 ))) ... ... @@ -977,11 +977,8 @@ 977 977 2.00 Beta 1 978 978 )))|((( 979 979 **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field. 980 -)))|(% colspan="1" %)(% colspan="1" %) 981 -((( 982 - 983 983 ))) 984 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)239 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 985 985 ((( 986 986 //Added list of resources a buildmodule needs to build.// 987 987 ))) ... ... @@ -991,11 +991,8 @@ 991 991 2.00 Beta 1 992 992 )))|((( 993 993 (% 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);" %) 994 -)))|(% colspan="1" %)(% colspan="1" %) 995 -((( 996 - 997 997 ))) 998 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)250 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 999 999 ((( 1000 1000 //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.// 1001 1001 ))) ... ... @@ -1005,18 +1005,11 @@ 1005 1005 2.00 Beta 1 1006 1006 )))|((( 1007 1007 **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" %) 1008 -)))|(% colspan="1" %)(% colspan="1" %) 1009 -((( 1010 - 1011 1011 ))) 1012 -|(% 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" %) 1013 1013 ((( 1014 1014 //Changed return value type to const char* to better identify failure reasons in Lua script.// 1015 1015 ))) 1016 -|(% colspan="4" %)(% colspan="4" %) 1017 -((( 1018 -== 1.50 == 1019 -))) 1020 1020 |((( 1021 1021 UI extensions 1022 1022 )))|((( ... ... @@ -1023,11 +1023,8 @@ 1023 1023 1.50 Beta 3 1024 1024 )))|((( 1025 1025 **Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %) 1026 -)))|(% colspan="1" %)(% colspan="1" %) 1027 -((( 1028 - 1029 1029 ))) 1030 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)272 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1031 1031 ((( 1032 1032 //The "docksizes" property no longer includes internal ship storage docks.// 1033 1033 ))) ... ... @@ -1037,11 +1037,8 @@ 1037 1037 1.50 Beta 2 1038 1038 )))|((( 1039 1039 **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR). 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" %)283 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1045 1045 ((( 1046 1046 //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".// 1047 1047 ... ... @@ -1055,11 +1055,8 @@ 1055 1055 1.50 Beta 2 1056 1056 )))|((( 1057 1057 **FFI: UpgradeGroupInfo **datatype was changed.(% 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" %)298 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1063 1063 ((( 1064 1064 //Added new "operational" field to retrieve information about number of operational upgrades in a group.// 1065 1065 ))) ... ... @@ -1072,11 +1072,8 @@ 1072 1072 )))|(% colspan="1" %)(% colspan="1" %) 1073 1073 ((( 1074 1074 **FFI: SetGuidance()** removed useinfopoint argument. 1075 -)))|(% colspan="1" %)(% colspan="1" %) 1076 -((( 1077 - 1078 1078 ))) 1079 -|(% 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" %) 1080 1080 ((( 1081 1081 //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. 1082 1082 // ... ... @@ -1089,18 +1089,11 @@ 1089 1089 1.50 Beta 1 1090 1090 )))|((( 1091 1091 **FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %) 1092 -)))|(% colspan="1" %)(% colspan="1" %) 1093 -((( 1094 - 1095 1095 ))) 1096 -|(% 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" %) 1097 1097 ((( 1098 1098 (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. // 1099 1099 ))) 1100 -|(% colspan="4" %)(% colspan="4" %) 1101 -((( 1102 -== 1.32 == 1103 -))) 1104 1104 |((( 1105 1105 UI extensions 1106 1106 )))|((( ... ... @@ -1107,18 +1107,11 @@ 1107 1107 1.32 1108 1108 )))|((( 1109 1109 **Lua: GetComponentData() **removed the "nextdestname" property. 1110 -)))|(% colspan="1" %)(% colspan="1" %) 1111 -((( 1112 - 1113 1113 ))) 1114 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)337 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1115 1115 ((( 1116 1116 //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.// 1117 1117 ))) 1118 -|(% colspan="4" %)(% colspan="4" %) 1119 -((( 1120 -== 1.20 == 1121 -))) 1122 1122 |((( 1123 1123 UI extensions 1124 1124 )))|((( ... ... @@ -1125,11 +1125,8 @@ 1125 1125 1.20 1126 1126 )))|((( 1127 1127 **FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %) 1128 -)))|(% colspan="1" %)(% colspan="1" %) 1129 -((( 1130 - 1131 1131 ))) 1132 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)348 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1133 1133 ((( 1134 1134 //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.// 1135 1135 )))
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 - 1045960461 +83460733 - url
-
... ... @@ -1,1 +1,1 @@ 1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/ 104596046/Breaking Changes1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/83460733/Breaking Changes