Changes for page Breaking Changes
Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 95.1
edited by matthias
on 2021/12/21 15:34
on 2021/12/21 15:34
Change comment:
There is no comment for this version
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,543 +24,25 @@ 24 24 Version 25 25 )))|=((( 26 26 Summary 27 -)))|=(% colspan="1" %)(% colspan="1" %) 28 -((( 29 - 30 30 ))) 31 -|(% colspan=" 4" %)(% colspan="4" %)28 +|(% colspan="3" %)(% colspan="3" %) 32 32 ((( 33 -== 5.00 == 34 -))) 35 -|((( 36 -Parameters 37 -)))|((( 38 -5.00 Beta 1 39 -)))|((( 40 -**<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration 41 -)))|((( 42 - 43 -))) 44 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 45 -((( 46 -//'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.// 47 -)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %) 48 -((( 49 - 50 -))) 51 -|(% colspan="4" %)(% colspan="4" %) 52 -((( 53 -== 4.10 == 54 -))) 55 -|(% colspan="1" %)(% colspan="1" %) 56 -((( 57 -UI extensions 58 -)))|(% colspan="1" %)(% colspan="1" %) 59 -((( 60 -4.10 Beta 7 61 -)))|(% colspan="1" %)(% colspan="1" %) 62 -((( 63 -**FFI**: (% style="color: rgb(0,0,0);" %)SetMapRenderCargoContents(%%)(), (% style="color: rgb(0,0,0);" %)SetMapRenderWorkForceInfo(), (% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)SetMapRenderCrewInfo() and (% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)SetMapRenderDockedShipInfos()(%%) 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 (% style="color: rgb(0,0,0);" %)SetMapRenderCargoContents(%%)(), (% style="color: rgb(0,0,0);" %)SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos()(%%) has been removed and the function was therefore stubbed.// 71 -)))|(% colspan="1" %)(% colspan="1" %) 72 -((( 73 - 74 -))) 75 -|(% colspan="1" %)(% colspan="1" %) 76 -((( 77 -UI extensions 78 -)))|(% colspan="1" %)(% colspan="1" %) 79 -((( 80 -4.10 Beta 6 81 -)))|(% colspan="1" %)(% colspan="1" %) 82 -((( 83 -**FFI**: CustomGameStartPlayerProperty2 changed 84 -)))|(% colspan="1" %)(% colspan="1" %) 85 -((( 86 - 87 -))) 88 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 89 -((( 90 -//This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.// 91 -)))|(% colspan="1" %)(% colspan="1" %) 92 -((( 93 - 94 -))) 95 -|(% colspan="1" %)(% colspan="1" %) 96 -((( 97 -Parameters 98 -)))|(% colspan="1" %)(% colspan="1" %) 99 -((( 100 -4.10 Beta 3 101 -)))|(% colspan="1" %)(% colspan="1" %) 102 -((( 103 -Renamed **<stationinfobox>** to **<infobox>** 104 -)))|(% colspan="1" %)(% colspan="1" %) 105 -((( 106 - 107 -))) 108 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 109 -((( 110 -//Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.// 111 -)))|(% colspan="1" %)(% colspan="1" %) 112 -((( 113 - 114 -))) 115 -|(% colspan="1" %)(% colspan="1" %) 116 -((( 117 -UI extensions 118 -)))|(% colspan="1" %)(% colspan="1" %) 119 -((( 120 -4.10 Beta 2 121 -)))|(% colspan="1" %)(% colspan="1" %) 122 -((( 123 -**FFI**: SetMacroMapPlayerSectorOffset() deprecated 124 -)))|(% colspan="1" %)(% colspan="1" %) 125 -((( 126 - 127 -))) 128 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 129 -((( 130 -//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.// 131 -)))|(% colspan="1" %)(% colspan="1" %) 132 -((( 133 - 134 -))) 135 -|((( 136 -UI extensions 137 -)))|((( 138 -4.10 Beta 2 139 -)))|((( 140 -**FFI**: (% style="color: rgb(0,0,0);" %)FilterComponentForMapMode(%%)() and (% style="color: rgb(0,0,0);" %)SetMapObjectFilter() changed 141 -)))|(% colspan="1" %)(% colspan="1" %) 142 -((( 143 - 144 -))) 145 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 146 -((( 147 -//These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.// 148 -)))|(% colspan="1" %)(% colspan="1" %) 149 -((( 150 - 151 -))) 152 -|((( 153 -Scripts 154 -)))|((( 155 -4.10 Beta 1 156 -)))|((( 157 -People related attributes of mission** <delivery> **node moved 158 -)))|((( 159 - 160 -))) 161 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 162 -((( 163 -//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.// 164 -))) 165 -|(% colspan="1" %)(% colspan="1" %) 166 -((( 167 -Scripts 168 -)))|(% colspan="1" %)(% colspan="1" %) 169 -((( 170 -4.10 Beta 1 171 -)))|(% colspan="1" %)(% colspan="1" %) 172 -((( 173 -**$destructible.productions** replaced with $defensible.productions 174 -)))|(% colspan="1" %)(% colspan="1" %) 175 -((( 176 - 177 -))) 178 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 179 -((( 180 -//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.// 181 -)))|(% colspan="1" %)(% colspan="1" %) 182 -((( 183 - 184 -))) 185 -|((( 186 -Scripts 187 -)))|((( 188 -4.10 Beta 1 189 -)))|((( 190 -Removed script property **$object.spawnsourceseed** 191 -)))|((( 192 - 193 -))) 194 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 195 -((( 196 -//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.// 197 -))) 198 -|(% colspan="4" %)(% colspan="4" %) 199 -((( 200 -== 4.00 == 201 -))) 202 -|(% colspan="1" %)(% colspan="1" %) 203 -((( 204 -UI core 205 -)))|(% colspan="1" %)(% colspan="1" %) 206 -((( 207 -4.00 Beta 10 208 -)))|(% colspan="1" %)(% colspan="1" %) 209 -((( 210 -Controlled ship can change without a **gameplanchange-event** occurring. 211 -)))|(% colspan="1" %)(% colspan="1" %) 212 -((( 213 - 214 -))) 215 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 216 -((( 217 -//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). 218 -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. 219 -// 220 -)))|(% colspan="1" %)(% colspan="1" %) 221 -((( 222 - 223 -))) 224 -|((( 225 -Scripts 226 -)))|((( 227 -4.00 Beta 7 228 -)))|((( 229 -Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed 230 -)))|((( 231 - 232 -))) 233 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 234 -((( 235 -//Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects? 236 -New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits 237 -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// 238 -)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %) 239 -((( 240 - 241 -))) 242 -|(% colspan="1" %)(% colspan="1" %) 243 -((( 244 -UI core 245 -)))|(% colspan="1" %)(% colspan="1" %) 246 -((( 247 -4.00 Beta 6 248 -)))|(% colspan="1" %)(% colspan="1" %) 249 -((( 250 -**FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed 251 -)))|(% colspan="1" %)(% colspan="1" %) 252 -((( 253 - 254 -))) 255 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 256 -((( 257 -//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. 258 -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).// 259 - 260 -//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead. 261 -// 262 -)))|(% colspan="1" %)(% colspan="1" %) 263 -((( 264 - 265 -))) 266 -|(% colspan="1" %)(% colspan="1" %) 267 -((( 268 -UI core 269 -)))|(% colspan="1" %)(% colspan="1" %) 270 -((( 271 -4.00 Beta 5 272 -)))|(% colspan="1" %)(% colspan="1" %) 273 -((( 274 -**FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed 275 -)))|(% colspan="1" %)(% colspan="1" %) 276 -((( 277 - 278 -))) 279 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 280 -((( 281 -//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.// 282 - 283 -//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). 284 -)))|(% colspan="1" %)(% colspan="1" %) 285 -((( 286 - 287 -))) 288 -|((( 289 -Parameters 290 -)))|((( 291 -4.00 Beta 1 292 -)))|((( 293 -**requiresconstructionvessel** parameter moved 294 -)))|((( 295 - 296 -))) 297 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 298 -((( 299 -//The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.// 300 -))) 301 -|((( 302 -Scripts 303 -)))|((( 304 -4.00 Beta 1 305 -)))|((( 306 -Changed behaviour of **gatedistance** script property 307 -)))|((( 308 - 309 -))) 310 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 311 -((( 312 -//The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.// 313 -)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %) 314 -((( 315 - 316 -))) 317 -|(% colspan="4" %)(% colspan="4" %) 318 -((( 319 -== 3.30 == 320 -))) 321 -|((( 322 -UI extensions 323 -)))|((( 324 -3.30 Beta 3 325 -)))|((( 326 -**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()** 327 -)))|(% colspan="1" %)(% colspan="1" %) 328 -((( 329 - 330 -))) 331 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 332 -((( 333 -//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()// 334 -))) 335 -|(% colspan="4" %)(% colspan="4" %) 336 -((( 337 -== 3.20 == 338 -))) 339 -|((( 340 -Scripts 341 -)))|((( 342 -3.20 Beta 1 343 -)))|((( 344 -Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed 345 -)))|(% colspan="1" %)(% colspan="1" %) 346 -((( 347 - 348 -))) 349 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 350 -((( 351 -//Old params: param = attacked object, param2 = attack method, param3 = attacked component// 352 -//New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon] 353 -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// 354 -))) 355 -|(% colspan="1" %)(% colspan="1" %) 356 -((( 357 -Scripts 358 -)))|(% colspan="1" %)(% colspan="1" %) 359 -((( 360 -3.20 Beta 1 361 -)))|(% colspan="1" %)(% colspan="1" %) 362 -((( 363 -Removed script property $trade.**restriction.faction** 364 -)))|(% colspan="1" %)(% colspan="1" %) 365 -((( 366 - 367 -))) 368 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 369 -((( 370 -//$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.// 371 -))) 372 -|((( 373 -UI extensions 374 -)))|((( 375 -3.20 Beta 1 376 -)))|((( 377 -**Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete! 378 -)))|(% colspan="1" %)(% colspan="1" %) 379 -((( 380 - 381 -))) 382 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 383 -((( 384 -//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.// 385 -))) 386 -|(% colspan="4" %)(% colspan="4" %) 387 -((( 388 -== 3.10 == 389 -))) 390 -|(% colspan="1" %)(% colspan="1" %) 391 -((( 392 -Scripts 393 -)))|(% colspan="1" %)(% colspan="1" %) 394 -((( 395 -3.10 Beta 1 396 -)))|(% colspan="1" %)(% colspan="1" %) 397 -((( 398 -Removed script action **<add_build/>** 399 -)))|(% colspan="1" %)(% colspan="1" %) 400 -((( 401 - 402 -))) 403 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 404 -((( 405 -//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.// 406 -))) 407 -|(% colspan="4" %)(% colspan="4" %) 408 -((( 409 409 == 3.00 == 410 410 ))) 411 411 |(% colspan="1" %)(% colspan="1" %) 412 412 ((( 413 -Scripts 414 -)))|(% colspan="1" %)(% colspan="1" %) 415 -((( 416 -3.0 Beta 6 417 -)))|(% colspan="1" %)(% colspan="1" %) 418 -((( 419 -Changed behaviour of script action **<get_suitable_job/>** 420 -)))|(% colspan="1" %)(% colspan="1" %) 421 -((( 422 - 423 -))) 424 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 425 -((( 426 -//<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.// 427 -))) 428 -|(% colspan="1" %)(% colspan="1" %) 429 -((( 430 -Scripts 431 -)))|(% colspan="1" %)(% colspan="1" %) 432 -((( 433 -3.0 Beta 6 434 -)))|(% colspan="1" %)(% colspan="1" %) 435 -((( 436 -Changed behaviour of script action **<get_ware_definition/>** 437 -)))|(% colspan="1" %)(% colspan="1" %) 438 -((( 439 - 440 -))) 441 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 442 -((( 443 -//<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.// 444 -))) 445 -|(% colspan="1" %)(% colspan="1" %) 446 -((( 447 447 Global 448 448 )))|(% colspan="1" %)(% colspan="1" %) 449 449 ((( 450 -3.0 Beta 5 451 -)))|(% colspan="1" %)(% colspan="1" %) 452 -((( 453 -Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case 454 -)))|(% colspan="1" %)(% colspan="1" %) 455 -((( 456 - 457 -))) 458 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 459 -((( 460 -//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.)\\ 461 - 462 -//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).// 463 -))) 464 -|(% colspan="1" %)(% colspan="1" %) 465 -((( 466 -Scripts 467 -)))|(% colspan="1" %)(% colspan="1" %) 468 -((( 469 -3.0 Beta 5 470 -)))|(% colspan="1" %)(% colspan="1" %) 471 -((( 472 -Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions> 473 -)))|(% colspan="1" %)(% colspan="1" %) 474 -((( 475 - 476 -))) 477 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 478 -((( 479 -//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.// 480 -))) 481 -|(% colspan="1" %)(% colspan="1" %) 482 -((( 483 -Scripts 484 -)))|(% colspan="1" %)(% colspan="1" %) 485 -((( 486 -3.0 Beta 5 487 -)))|(% colspan="1" %)(% colspan="1" %) 488 -((( 489 -Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos** 490 -)))|(% colspan="1" %)(% colspan="1" %) 491 -((( 492 - 493 -))) 494 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 495 -((( 496 -//Before the change, positions are relative to $dockingbay.parent. 497 -After the change, positions are relative to $dockingbay as specified in the documentation.// 498 -))) 499 -|(% colspan="1" %)(% colspan="1" %) 500 -((( 501 -Global 502 -)))|(% colspan="1" %)(% colspan="1" %) 503 -((( 504 -3.0 Beta 2 505 -)))|(% colspan="1" %)(% colspan="1" %) 506 -((( 507 -Support for entity flag "**skillsvisible**" dropped 508 -)))|(% colspan="1" %)(% colspan="1" %) 509 -((( 510 - 511 -))) 512 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 513 -((( 514 -//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().// 515 -))) 516 -|((( 517 -Scripts 518 -)))|((( 519 -3.0 Beta 2 520 -)))|((( 521 -Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**. 522 -)))|(% colspan="1" %)(% colspan="1" %) 523 -((( 524 - 525 -))) 526 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 527 -((( 528 -//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. 529 -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. 530 -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. 531 -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). 532 -))) 533 -|(% colspan="1" %)(% colspan="1" %) 534 -((( 535 -Global 536 -)))|(% colspan="1" %)(% colspan="1" %) 537 -((( 538 538 3.0 Beta 1 539 539 )))|(% colspan="1" %)(% colspan="1" %) 540 540 ((( 541 -**MissionBoard** support dropped 542 -)))|(% colspan="1" %)(% colspan="1" %) 543 -((( 544 - 40 +MissionBoard support dropped. 545 545 ))) 546 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)42 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 547 547 ((( 548 -//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 behavio ur would occur. Therefore we cleaned things up in 3.0 Beta 1 including deprecating/removing any related UI/script function.//44 +//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 behavior would occur. Therefore we cleaned things up in 3.0 Beta 1 including deprecating/removing any related UI/script function.// 549 549 ))) 550 -|((( 551 -Job/God 552 -)))|((( 553 -3.0 Beta 1 554 -)))|((( 555 -By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined 556 -)))|(% colspan="1" %)(% colspan="1" %) 557 -((( 558 - 559 -))) 560 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 561 -((( 562 -//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.// 563 -))) 564 564 |(% colspan="1" %)(% colspan="1" %) 565 565 ((( 566 566 Scripts ... ... @@ -570,11 +570,8 @@ 570 570 )))|(% colspan="1" %)(% colspan="1" %) 571 571 ((( 572 572 Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'** 573 -)))|(% colspan="1" %)(% colspan="1" %) 574 -((( 575 - 576 576 ))) 577 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)56 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 578 578 ((( 579 579 //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.// 580 580 ))) ... ... @@ -587,11 +587,8 @@ 587 587 )))|(% colspan="1" %)(% colspan="1" %) 588 588 ((( 589 589 Script action **<set_doors_locked/>** attribute **'group'** changed 590 -)))|(% colspan="1" %)(% colspan="1" %) 591 -((( 592 - 593 593 ))) 594 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)70 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 595 595 ((( 596 596 //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.// 597 597 ))) ... ... @@ -604,11 +604,8 @@ 604 604 )))|(% colspan="1" %)(% colspan="1" %) 605 605 ((( 606 606 Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed 607 -)))|(% colspan="1" %)(% colspan="1" %) 608 -((( 609 - 610 610 ))) 611 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)84 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 612 612 ((( 613 613 //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.// 614 614 ))) ... ... @@ -621,11 +621,8 @@ 621 621 )))|(% colspan="1" %)(% colspan="1" %) 622 622 ((( 623 623 Script actions **<set_hack_target/>** and **<abort_hack/>** removed 624 -)))|(% colspan="1" %)(% colspan="1" %) 625 -((( 626 - 627 627 ))) 628 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)98 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 629 629 ((( 630 630 //These actions had no effect and were removed.// 631 631 ))) ... ... @@ -638,11 +638,8 @@ 638 638 )))|(% colspan="1" %)(% colspan="1" %) 639 639 ((( 640 640 **<setup_conversation_minigame/>** script action removed 641 -)))|(% colspan="1" %)(% colspan="1" %) 642 -((( 643 - 644 644 ))) 645 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)112 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 646 646 ((( 647 647 //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.// 648 648 ))) ... ... @@ -655,11 +655,8 @@ 655 655 )))|(% colspan="1" %)(% colspan="1" %) 656 656 ((( 657 657 <add_player_choice_*> **confidence** attribute removed 658 -)))|(% colspan="1" %)(% colspan="1" %) 659 -((( 660 - 661 661 ))) 662 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)126 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 663 663 ((( 664 664 //The default confidence of player options is another leftover from the XR era and had no effect in X4.// 665 665 ))) ... ... @@ -672,11 +672,8 @@ 672 672 )))|(% colspan="1" %)(% colspan="1" %) 673 673 ((( 674 674 **<hack_via_control_panel/>** script action removed 675 -)))|(% colspan="1" %)(% colspan="1" %) 676 -((( 677 - 678 678 ))) 679 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)140 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 680 680 ((( 681 681 //Unused script action <hack_via_control_panel/> was removed.// 682 682 ))) ... ... @@ -689,11 +689,8 @@ 689 689 )))|(% colspan="1" %)(% colspan="1" %) 690 690 ((( 691 691 **Lua: **GetMiniGameCursorPosition() removed 692 -)))|(% colspan="1" %)(% colspan="1" %) 693 -((( 694 - 695 695 ))) 696 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)154 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 697 697 ((( 698 698 //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.// 699 699 ))) ... ... @@ -703,33 +703,13 @@ 703 703 3.0 Beta 1 704 704 )))|((( 705 705 **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders 706 -)))|(% colspan="1" %)(% colspan="1" %) 707 -((( 708 - 709 709 ))) 710 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)165 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 711 711 ((( 712 712 //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.// 713 713 ))) 714 714 |(% colspan="1" %)(% colspan="1" %) 715 715 ((( 716 -UI extensions 717 -)))|(% colspan="1" %)(% colspan="1" %) 718 -((( 719 -3.0 Beta 1 720 -)))|(% colspan="1" %)(% colspan="1" %) 721 -((( 722 -**FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor 723 -)))|(% colspan="1" %)(% colspan="1" %) 724 -((( 725 - 726 -))) 727 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 728 -((( 729 -//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.// 730 -))) 731 -|(% colspan="1" %)(% colspan="1" %) 732 -((( 733 733 Scripts 734 734 )))|(% colspan="1" %)(% colspan="1" %) 735 735 ((( ... ... @@ -737,11 +737,8 @@ 737 737 )))|(% colspan="1" %)(% colspan="1" %) 738 738 ((( 739 739 **$ware.illegal** updated 740 -)))|(% colspan="1" %)(% colspan="1" %) 741 -((( 742 - 743 743 ))) 744 -|(% 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" %) 745 745 ((( 746 746 //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.// 747 747 //It now returns true if $ware is illegal to any faction in the game.// ... ... @@ -755,11 +755,8 @@ 755 755 )))|(% colspan="1" %)(% colspan="1" %) 756 756 ((( 757 757 MD script **RML_Flight_Along_Path** removed 758 -)))|(% colspan="1" %)(% colspan="1" %) 759 -((( 760 - 761 761 ))) 762 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)194 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 763 763 ((( 764 764 //The MD script RML_Flight_Along_Path was not referened and was removed.// 765 765 ))) ... ... @@ -772,47 +772,14 @@ 772 772 )))|(% colspan="1" %)(% colspan="1" %) 773 773 ((( 774 774 parameters of **<event_venture_mission_completed/>** changed 775 -)))|(% colspan="1" %)(% colspan="1" %) 776 -((( 777 - 778 778 ))) 779 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)208 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 780 780 ((( 781 781 //old params: param = venture details, param2 = ships involved, param3 = duration// 782 782 //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration// 783 783 ))) 784 -|((( 785 -Scripts 786 -)))|((( 787 -3.0 Beta 1 788 -)))|((( 789 -**<set_object_wing_name/>** removed, 790 -**<set_object_fleet_name/>** added 791 -)))|(% colspan="1" %)(% colspan="1" %) 213 +|(% colspan="3" %)(% colspan="3" %) 792 792 ((( 793 - 794 -))) 795 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 796 -((( 797 -//The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>// 798 -))) 799 -|((( 800 -Scripts 801 -)))|((( 802 -3.0 Beta 1 803 -)))|((( 804 -**$controllable.wing.*** removed, 805 -**$controllable.fleet.*** added 806 -)))|(% colspan="1" %)(% colspan="1" %) 807 -((( 808 - 809 -))) 810 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 811 -((( 812 -$controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander 813 -))) 814 -|(% colspan="4" %)(% colspan="4" %) 815 -((( 816 816 == 2.60 == 817 817 ))) 818 818 |((( ... ... @@ -821,11 +821,8 @@ 821 821 2.60 Beta 1 822 822 )))|((( 823 823 '**checkoperational**' filter behaviour changed 824 -)))|(% colspan="1" %)(% colspan="1" %) 825 -((( 826 - 827 827 ))) 828 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)224 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 829 829 ((( 830 830 //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.// 831 831 ... ... @@ -837,15 +837,12 @@ 837 837 2.60 Beta 1 838 838 )))|((( 839 839 $container.**supplyresources** behavior changed 840 -)))|(% colspan="1" %)(% colspan="1" %) 841 -((( 842 - 843 843 ))) 844 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)237 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 845 845 ((( 846 846 //The script keyword $container.supplyresources now includes reserved wares.// 847 847 ))) 848 -|(% colspan=" 4" %)(% colspan="4" %)241 +|(% colspan="3" %)(% colspan="3" %) 849 849 ((( 850 850 == 2.20 == 851 851 ))) ... ... @@ -858,11 +858,8 @@ 858 858 )))|(% colspan="1" %)(% colspan="1" %) 859 859 ((( 860 860 **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined. 861 -)))|(% colspan="1" %)(% colspan="1" %) 862 -((( 863 - 864 864 ))) 865 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)255 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 866 866 ((( 867 867 //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. 868 868 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.// ... ... @@ -879,15 +879,12 @@ 879 879 )))|(% colspan="1" %)(% colspan="1" %) 880 880 ((( 881 881 Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor' 882 -)))|(% colspan="1" %)(% colspan="1" %) 883 -((( 884 - 885 885 ))) 886 -|(% 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" %) 887 887 ((( 888 888 //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.// 889 889 ))) 890 -|(% colspan=" 4" %)(% colspan="4" %)277 +|(% colspan="3" %)(% colspan="3" %) 891 891 ((( 892 892 == 2.00 == 893 893 ))) ... ... @@ -900,11 +900,8 @@ 900 900 )))|(% colspan="1" %)(% colspan="1" %) 901 901 ((( 902 902 **<event_build_finished/> **param2 now returns null instead of a construction sequence 903 -)))|(% colspan="1" %)(% colspan="1" %) 904 -((( 905 - 906 906 ))) 907 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)291 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 908 908 ((( 909 909 //The construction sequence which was finished should now be accessed via the buildtask provided via param3.// 910 910 ))) ... ... @@ -917,11 +917,8 @@ 917 917 )))|(% colspan="1" %)(% colspan="1" %) 918 918 ((( 919 919 **param.boarding.{...}** strength parameters removed 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" %)305 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 925 925 ((( 926 926 //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.// 927 927 ))) ... ... @@ -934,11 +934,8 @@ 934 934 )))|(% colspan="1" %)(% colspan="1" %) 935 935 ((( 936 936 **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed 937 -)))|(% colspan="1" %)(% colspan="1" %) 938 -((( 939 - 940 940 ))) 941 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)319 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 942 942 ((( 943 943 //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.// 944 944 ))) ... ... @@ -948,11 +948,8 @@ 948 948 2.00 Beta 1 949 949 )))|((( 950 950 **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals 951 -)))|(% colspan="1" %)(% colspan="1" %) 952 -((( 953 - 954 954 ))) 955 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)330 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 956 956 ((( 957 957 //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.// 958 958 ))) ... ... @@ -962,11 +962,8 @@ 962 962 2.00 Beta 1 963 963 )))|((( 964 964 **FFI: SetFormationShape()** no longer indicates an error upon certain error cases 965 -)))|(% colspan="1" %)(% colspan="1" %) 966 -((( 967 - 968 968 ))) 969 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)341 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 970 970 ((( 971 971 //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.// 972 972 //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.// ... ... @@ -977,11 +977,8 @@ 977 977 2.00 Beta 1 978 978 )))|((( 979 979 **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated. 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" %)353 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 985 985 ((( 986 986 //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.// 987 987 ))) ... ... @@ -991,11 +991,8 @@ 991 991 2.00 Beta 1 992 992 )))|((( 993 993 **<event_player_changed_target/>** now fires and returns null if the player deselects a target. 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" %)364 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 999 999 ((( 1000 1000 //For prior behavior, check for event.param being non-null.// 1001 1001 ))) ... ... @@ -1005,11 +1005,8 @@ 1005 1005 2.00 Beta 1 1006 1006 )))|((( 1007 1007 **<shoot/>/<shoot_at/>** attribute changes. 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" %)375 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1013 1013 ((( 1014 1014 //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.// 1015 1015 //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.// ... ... @@ -1023,11 +1023,8 @@ 1023 1023 2.00 Beta 1 1024 1024 )))|((( 1025 1025 **FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% 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" %)390 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1031 1031 ((( 1032 1032 //Added possibility to query build tasks of a certain buildmodule.// 1033 1033 ))) ... ... @@ -1037,11 +1037,8 @@ 1037 1037 2.00 Beta 1 1038 1038 )))|((( 1039 1039 **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field. 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" %)401 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1045 1045 ((( 1046 1046 //Added list of resources a buildmodule needs to build.// 1047 1047 ))) ... ... @@ -1051,11 +1051,8 @@ 1051 1051 2.00 Beta 1 1052 1052 )))|((( 1053 1053 (% 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);" %) 1054 -)))|(% colspan="1" %)(% colspan="1" %) 1055 -((( 1056 - 1057 1057 ))) 1058 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)412 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1059 1059 ((( 1060 1060 //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.// 1061 1061 ))) ... ... @@ -1065,15 +1065,12 @@ 1065 1065 2.00 Beta 1 1066 1066 )))|((( 1067 1067 **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" %) 1068 -)))|(% colspan="1" %)(% colspan="1" %) 1069 -((( 1070 - 1071 1071 ))) 1072 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)423 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1073 1073 ((( 1074 1074 //Changed return value type to const char* to better identify failure reasons in Lua script.// 1075 1075 ))) 1076 -|(% colspan=" 4" %)(% colspan="4" %)427 +|(% colspan="3" %)(% colspan="3" %) 1077 1077 ((( 1078 1078 == 1.50 == 1079 1079 ))) ... ... @@ -1083,11 +1083,8 @@ 1083 1083 1.50 Beta 3 1084 1084 )))|((( 1085 1085 **Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %) 1086 -)))|(% colspan="1" %)(% colspan="1" %) 1087 -((( 1088 - 1089 1089 ))) 1090 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)438 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1091 1091 ((( 1092 1092 //The "docksizes" property no longer includes internal ship storage docks.// 1093 1093 ))) ... ... @@ -1097,11 +1097,8 @@ 1097 1097 1.50 Beta 2 1098 1098 )))|((( 1099 1099 **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR). 1100 -)))|(% colspan="1" %)(% colspan="1" %) 1101 -((( 1102 - 1103 1103 ))) 1104 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)449 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1105 1105 ((( 1106 1106 //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".// 1107 1107 ... ... @@ -1115,11 +1115,8 @@ 1115 1115 1.50 Beta 2 1116 1116 )))|((( 1117 1117 **FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %) 1118 -)))|(% colspan="1" %)(% colspan="1" %) 1119 -((( 1120 - 1121 1121 ))) 1122 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)464 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1123 1123 ((( 1124 1124 //Added new "operational" field to retrieve information about number of operational upgrades in a group.// 1125 1125 ))) ... ... @@ -1132,11 +1132,8 @@ 1132 1132 )))|(% colspan="1" %)(% colspan="1" %) 1133 1133 ((( 1134 1134 **FFI: SetGuidance()** removed useinfopoint argument. 1135 -)))|(% colspan="1" %)(% colspan="1" %) 1136 -((( 1137 - 1138 1138 ))) 1139 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)478 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1140 1140 ((( 1141 1141 //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. 1142 1142 // ... ... @@ -1149,15 +1149,12 @@ 1149 1149 1.50 Beta 1 1150 1150 )))|((( 1151 1151 **FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %) 1152 -)))|(% colspan="1" %)(% colspan="1" %) 1153 -((( 1154 - 1155 1155 ))) 1156 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)492 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1157 1157 ((( 1158 1158 (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. // 1159 1159 ))) 1160 -|(% colspan=" 4" %)(% colspan="4" %)496 +|(% colspan="3" %)(% colspan="3" %) 1161 1161 ((( 1162 1162 == 1.32 == 1163 1163 ))) ... ... @@ -1167,15 +1167,12 @@ 1167 1167 1.32 1168 1168 )))|((( 1169 1169 **Lua: GetComponentData() **removed the "nextdestname" property. 1170 -)))|(% colspan="1" %)(% colspan="1" %) 1171 -((( 1172 - 1173 1173 ))) 1174 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)507 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1175 1175 ((( 1176 1176 //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.// 1177 1177 ))) 1178 -|(% colspan=" 4" %)(% colspan="4" %)511 +|(% colspan="3" %)(% colspan="3" %) 1179 1179 ((( 1180 1180 == 1.20 == 1181 1181 ))) ... ... @@ -1185,11 +1185,8 @@ 1185 1185 1.20 1186 1186 )))|((( 1187 1187 **FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %) 1188 -)))|(% colspan="1" %)(% colspan="1" %) 1189 -((( 1190 - 1191 1191 ))) 1192 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)522 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1193 1193 ((( 1194 1194 //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.// 1195 1195 )))
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 - 1358564981 +87916742 - url
-
... ... @@ -1,1 +1,1 @@ 1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/ 135856498/Breaking Changes1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/87916742/Breaking Changes