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. florian1 +xwiki:XWiki.klaus - Content
-
... ... @@ -24,368 +24,9 @@ 24 24 Version 25 25 )))|=((( 26 26 Summary 27 -)))|=(% colspan="1" %)(% colspan="1" %) 28 -((( 29 - 30 30 ))) 31 -|(% colspan=" 4" %)(% colspan="4" %)28 +|(% colspan="3" %)(% colspan="3" %) 32 32 ((( 33 -== 4.10 == 34 -))) 35 -|(% colspan="1" %)(% colspan="1" %) 36 -((( 37 -UI extensions 38 -)))|(% colspan="1" %)(% colspan="1" %) 39 -((( 40 -4.10 Beta 7 41 -)))|(% colspan="1" %)(% colspan="1" %) 42 -((( 43 -**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 44 -)))|(% colspan="1" %)(% colspan="1" %) 45 -((( 46 - 47 -))) 48 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 49 -((( 50 -//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.// 51 -)))|(% colspan="1" %)(% colspan="1" %) 52 -((( 53 - 54 -))) 55 -|(% colspan="1" %)(% colspan="1" %) 56 -((( 57 -UI extensions 58 -)))|(% colspan="1" %)(% colspan="1" %) 59 -((( 60 -4.10 Beta 6 61 -)))|(% colspan="1" %)(% colspan="1" %) 62 -((( 63 -**FFI**: CustomGameStartPlayerProperty2 changed 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 -//This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.// 71 -)))|(% colspan="1" %)(% colspan="1" %) 72 -((( 73 - 74 -))) 75 -|(% colspan="1" %)(% colspan="1" %) 76 -((( 77 -Parameters 78 -)))|(% colspan="1" %)(% colspan="1" %) 79 -((( 80 -4.10 Beta 3 81 -)))|(% colspan="1" %)(% colspan="1" %) 82 -((( 83 -Renamed **<stationinfobox>** to **<infobox>** 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 -//Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.// 91 -)))|(% colspan="1" %)(% colspan="1" %) 92 -((( 93 - 94 -))) 95 -|(% colspan="1" %)(% colspan="1" %) 96 -((( 97 -UI extensions 98 -)))|(% colspan="1" %)(% colspan="1" %) 99 -((( 100 -4.10 Beta 2 101 -)))|(% colspan="1" %)(% colspan="1" %) 102 -((( 103 -**FFI**: SetMacroMapPlayerSectorOffset() deprecated 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 -//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.// 111 -)))|(% colspan="1" %)(% colspan="1" %) 112 -((( 113 - 114 -))) 115 -|((( 116 -UI extensions 117 -)))|((( 118 -4.10 Beta 2 119 -)))|((( 120 -**FFI**: (% style="color: rgb(0,0,0);" %)FilterComponentForMapMode(%%)() and (% style="color: rgb(0,0,0);" %)SetMapObjectFilter() changed 121 -)))|(% colspan="1" %)(% colspan="1" %) 122 -((( 123 - 124 -))) 125 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 126 -((( 127 -//These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.// 128 -)))|(% colspan="1" %)(% colspan="1" %) 129 -((( 130 - 131 -))) 132 -|((( 133 -Scripts 134 -)))|((( 135 -4.10 Beta 1 136 -)))|((( 137 -People related attributes of mission** <delivery> **node moved 138 -)))|((( 139 - 140 -))) 141 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 142 -((( 143 -//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.// 144 -))) 145 -|(% colspan="1" %)(% colspan="1" %) 146 -((( 147 -Scripts 148 -)))|(% colspan="1" %)(% colspan="1" %) 149 -((( 150 -4.10 Beta 1 151 -)))|(% colspan="1" %)(% colspan="1" %) 152 -((( 153 -**$destructible.productions** replaced with $defensible.productions 154 -)))|(% colspan="1" %)(% colspan="1" %) 155 -((( 156 - 157 -))) 158 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 159 -((( 160 -//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.// 161 -)))|(% colspan="1" %)(% colspan="1" %) 162 -((( 163 - 164 -))) 165 -|((( 166 -Scripts 167 -)))|((( 168 -4.10 Beta 1 169 -)))|((( 170 -Removed script property **$object.spawnsourceseed** 171 -)))|((( 172 - 173 -))) 174 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 175 -((( 176 -//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.// 177 -))) 178 -|(% colspan="4" %)(% colspan="4" %) 179 -((( 180 -== 4.00 == 181 -))) 182 -|(% colspan="1" %)(% colspan="1" %) 183 -((( 184 -UI core 185 -)))|(% colspan="1" %)(% colspan="1" %) 186 -((( 187 -4.00 Beta 10 188 -)))|(% colspan="1" %)(% colspan="1" %) 189 -((( 190 -Controlled ship can change without a **gameplanchange-event** occurring. 191 -)))|(% colspan="1" %)(% colspan="1" %) 192 -((( 193 - 194 -))) 195 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 196 -((( 197 -//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). 198 -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. 199 -// 200 -)))|(% colspan="1" %)(% colspan="1" %) 201 -((( 202 - 203 -))) 204 -|((( 205 -Scripts 206 -)))|((( 207 -4.00 Beta 7 208 -)))|((( 209 -Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed 210 -)))|((( 211 - 212 -))) 213 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 214 -((( 215 -//Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects? 216 -New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits 217 -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// 218 -)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %) 219 -((( 220 - 221 -))) 222 -|(% colspan="1" %)(% colspan="1" %) 223 -((( 224 -UI core 225 -)))|(% colspan="1" %)(% colspan="1" %) 226 -((( 227 -4.00 Beta 6 228 -)))|(% colspan="1" %)(% colspan="1" %) 229 -((( 230 -**FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed 231 -)))|(% colspan="1" %)(% colspan="1" %) 232 -((( 233 - 234 -))) 235 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 236 -((( 237 -//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. 238 -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).// 239 - 240 -//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead. 241 -// 242 -)))|(% colspan="1" %)(% colspan="1" %) 243 -((( 244 - 245 -))) 246 -|(% colspan="1" %)(% colspan="1" %) 247 -((( 248 -UI core 249 -)))|(% colspan="1" %)(% colspan="1" %) 250 -((( 251 -4.00 Beta 5 252 -)))|(% colspan="1" %)(% colspan="1" %) 253 -((( 254 -**FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed 255 -)))|(% colspan="1" %)(% colspan="1" %) 256 -((( 257 - 258 -))) 259 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 260 -((( 261 -//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.// 262 - 263 -//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). 264 -)))|(% colspan="1" %)(% colspan="1" %) 265 -((( 266 - 267 -))) 268 -|((( 269 -Parameters 270 -)))|((( 271 -4.00 Beta 1 272 -)))|((( 273 -**requiresconstructionvessel** parameter moved 274 -)))|((( 275 - 276 -))) 277 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 278 -((( 279 -//The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.// 280 -))) 281 -|((( 282 -Scripts 283 -)))|((( 284 -4.00 Beta 1 285 -)))|((( 286 -Changed behaviour of **gatedistance** script property 287 -)))|((( 288 - 289 -))) 290 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 291 -((( 292 -//The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.// 293 -)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %) 294 -((( 295 - 296 -))) 297 -|(% colspan="4" %)(% colspan="4" %) 298 -((( 299 -== 3.30 == 300 -))) 301 -|((( 302 -UI extensions 303 -)))|((( 304 -3.30 Beta 3 305 -)))|((( 306 -**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()** 307 -)))|(% colspan="1" %)(% colspan="1" %) 308 -((( 309 - 310 -))) 311 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 312 -((( 313 -//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()// 314 -))) 315 -|(% colspan="4" %)(% colspan="4" %) 316 -((( 317 -== 3.20 == 318 -))) 319 -|((( 320 -Scripts 321 -)))|((( 322 -3.20 Beta 1 323 -)))|((( 324 -Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed 325 -)))|(% colspan="1" %)(% colspan="1" %) 326 -((( 327 - 328 -))) 329 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 330 -((( 331 -//Old params: param = attacked object, param2 = attack method, param3 = attacked component// 332 -//New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon] 333 -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// 334 -))) 335 -|(% colspan="1" %)(% colspan="1" %) 336 -((( 337 -Scripts 338 -)))|(% colspan="1" %)(% colspan="1" %) 339 -((( 340 -3.20 Beta 1 341 -)))|(% colspan="1" %)(% colspan="1" %) 342 -((( 343 -Removed script property $trade.**restriction.faction** 344 -)))|(% colspan="1" %)(% colspan="1" %) 345 -((( 346 - 347 -))) 348 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 349 -((( 350 -//$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.// 351 -))) 352 -|((( 353 -UI extensions 354 -)))|((( 355 -3.20 Beta 1 356 -)))|((( 357 -**Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete! 358 -)))|(% colspan="1" %)(% colspan="1" %) 359 -((( 360 - 361 -))) 362 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 363 -((( 364 -//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.// 365 -))) 366 -|(% colspan="4" %)(% colspan="4" %) 367 -((( 368 -== 3.10 == 369 -))) 370 -|(% colspan="1" %)(% colspan="1" %) 371 -((( 372 -Scripts 373 -)))|(% colspan="1" %)(% colspan="1" %) 374 -((( 375 -3.10 Beta 1 376 -)))|(% colspan="1" %)(% colspan="1" %) 377 -((( 378 -Removed script action **<add_build/>** 379 -)))|(% colspan="1" %)(% colspan="1" %) 380 -((( 381 - 382 -))) 383 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 384 -((( 385 -//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.// 386 -))) 387 -|(% colspan="4" %)(% colspan="4" %) 388 -((( 389 389 == 3.00 == 390 390 ))) 391 391 |(% colspan="1" %)(% colspan="1" %) ... ... @@ -393,69 +393,13 @@ 393 393 Scripts 394 394 )))|(% colspan="1" %)(% colspan="1" %) 395 395 ((( 396 -3.0 Beta 6 397 -)))|(% colspan="1" %)(% colspan="1" %) 398 -((( 399 -Changed behaviour of script action **<get_suitable_job/>** 400 -)))|(% colspan="1" %)(% colspan="1" %) 401 -((( 402 - 403 -))) 404 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 405 -((( 406 -//<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.// 407 -))) 408 -|(% colspan="1" %)(% colspan="1" %) 409 -((( 410 -Scripts 411 -)))|(% colspan="1" %)(% colspan="1" %) 412 -((( 413 -3.0 Beta 6 414 -)))|(% colspan="1" %)(% colspan="1" %) 415 -((( 416 -Changed behaviour of script action **<get_ware_definition/>** 417 -)))|(% colspan="1" %)(% colspan="1" %) 418 -((( 419 - 420 -))) 421 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 422 -((( 423 -//<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.// 424 -))) 425 -|(% colspan="1" %)(% colspan="1" %) 426 -((( 427 -Global 428 -)))|(% colspan="1" %)(% colspan="1" %) 429 -((( 430 430 3.0 Beta 5 431 431 )))|(% colspan="1" %)(% colspan="1" %) 432 432 ((( 433 -Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case 434 -)))|(% colspan="1" %)(% colspan="1" %) 435 -((( 436 - 40 +Adjustments of some **MD library cues** in the base game to change their usage from <include_actions> to <run_actions> 437 437 ))) 438 -|(% 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" %) 439 439 ((( 440 -//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.)\\ 441 - 442 -//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).// 443 -))) 444 -|(% colspan="1" %)(% colspan="1" %) 445 -((( 446 -Scripts 447 -)))|(% colspan="1" %)(% colspan="1" %) 448 -((( 449 -3.0 Beta 5 450 -)))|(% colspan="1" %)(% colspan="1" %) 451 -((( 452 -Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions> 453 -)))|(% colspan="1" %)(% colspan="1" %) 454 -((( 455 - 456 -))) 457 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 458 -((( 459 459 //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.// 460 460 ))) 461 461 |(% colspan="1" %)(% colspan="1" %) ... ... @@ -467,11 +467,8 @@ 467 467 )))|(% colspan="1" %)(% colspan="1" %) 468 468 ((( 469 469 Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos** 470 -)))|(% colspan="1" %)(% colspan="1" %) 471 -((( 472 - 473 473 ))) 474 -|(% 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" %) 475 475 ((( 476 476 //Before the change, positions are relative to $dockingbay.parent. 477 477 After the change, positions are relative to $dockingbay as specified in the documentation.// ... ... @@ -485,11 +485,8 @@ 485 485 )))|(% colspan="1" %)(% colspan="1" %) 486 486 ((( 487 487 Support for entity flag "**skillsvisible**" dropped 488 -)))|(% colspan="1" %)(% colspan="1" %) 489 -((( 490 - 491 491 ))) 492 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)71 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 493 493 ((( 494 494 //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().// 495 495 ))) ... ... @@ -499,11 +499,8 @@ 499 499 3.0 Beta 2 500 500 )))|((( 501 501 Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**. 502 -)))|(% colspan="1" %)(% colspan="1" %) 503 -((( 504 - 505 505 ))) 506 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)82 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 507 507 ((( 508 508 //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. 509 509 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. ... ... @@ -519,11 +519,8 @@ 519 519 )))|(% colspan="1" %)(% colspan="1" %) 520 520 ((( 521 521 **MissionBoard** support dropped 522 -)))|(% colspan="1" %)(% colspan="1" %) 523 -((( 524 - 525 525 ))) 526 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)99 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 527 527 ((( 528 528 //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.// 529 529 ))) ... ... @@ -533,11 +533,8 @@ 533 533 3.0 Beta 1 534 534 )))|((( 535 535 By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined 536 -)))|(% colspan="1" %)(% colspan="1" %) 537 -((( 538 - 539 539 ))) 540 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)110 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 541 541 ((( 542 542 //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.// 543 543 ))) ... ... @@ -550,11 +550,8 @@ 550 550 )))|(% colspan="1" %)(% colspan="1" %) 551 551 ((( 552 552 Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'** 553 -)))|(% colspan="1" %)(% colspan="1" %) 554 -((( 555 - 556 556 ))) 557 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)124 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 558 558 ((( 559 559 //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.// 560 560 ))) ... ... @@ -567,11 +567,8 @@ 567 567 )))|(% colspan="1" %)(% colspan="1" %) 568 568 ((( 569 569 Script action **<set_doors_locked/>** attribute **'group'** changed 570 -)))|(% colspan="1" %)(% colspan="1" %) 571 -((( 572 - 573 573 ))) 574 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)138 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 575 575 ((( 576 576 //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.// 577 577 ))) ... ... @@ -584,11 +584,8 @@ 584 584 )))|(% colspan="1" %)(% colspan="1" %) 585 585 ((( 586 586 Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed 587 -)))|(% colspan="1" %)(% colspan="1" %) 588 -((( 589 - 590 590 ))) 591 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)152 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 592 592 ((( 593 593 //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.// 594 594 ))) ... ... @@ -601,11 +601,8 @@ 601 601 )))|(% colspan="1" %)(% colspan="1" %) 602 602 ((( 603 603 Script actions **<set_hack_target/>** and **<abort_hack/>** removed 604 -)))|(% colspan="1" %)(% colspan="1" %) 605 -((( 606 - 607 607 ))) 608 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)166 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 609 609 ((( 610 610 //These actions had no effect and were removed.// 611 611 ))) ... ... @@ -618,11 +618,8 @@ 618 618 )))|(% colspan="1" %)(% colspan="1" %) 619 619 ((( 620 620 **<setup_conversation_minigame/>** script action removed 621 -)))|(% colspan="1" %)(% colspan="1" %) 622 -((( 623 - 624 624 ))) 625 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)180 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 626 626 ((( 627 627 //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.// 628 628 ))) ... ... @@ -635,11 +635,8 @@ 635 635 )))|(% colspan="1" %)(% colspan="1" %) 636 636 ((( 637 637 <add_player_choice_*> **confidence** attribute removed 638 -)))|(% colspan="1" %)(% colspan="1" %) 639 -((( 640 - 641 641 ))) 642 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)194 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 643 643 ((( 644 644 //The default confidence of player options is another leftover from the XR era and had no effect in X4.// 645 645 ))) ... ... @@ -652,11 +652,8 @@ 652 652 )))|(% colspan="1" %)(% colspan="1" %) 653 653 ((( 654 654 **<hack_via_control_panel/>** script action removed 655 -)))|(% colspan="1" %)(% colspan="1" %) 656 -((( 657 - 658 658 ))) 659 -|(% 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" %) 660 660 ((( 661 661 //Unused script action <hack_via_control_panel/> was removed.// 662 662 ))) ... ... @@ -669,11 +669,8 @@ 669 669 )))|(% colspan="1" %)(% colspan="1" %) 670 670 ((( 671 671 **Lua: **GetMiniGameCursorPosition() removed 672 -)))|(% colspan="1" %)(% colspan="1" %) 673 -((( 674 - 675 675 ))) 676 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)222 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 677 677 ((( 678 678 //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.// 679 679 ))) ... ... @@ -683,11 +683,8 @@ 683 683 3.0 Beta 1 684 684 )))|((( 685 685 **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders 686 -)))|(% colspan="1" %)(% colspan="1" %) 687 -((( 688 - 689 689 ))) 690 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)233 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 691 691 ((( 692 692 //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.// 693 693 ))) ... ... @@ -700,11 +700,8 @@ 700 700 )))|(% colspan="1" %)(% colspan="1" %) 701 701 ((( 702 702 **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor 703 -)))|(% colspan="1" %)(% colspan="1" %) 704 -((( 705 - 706 706 ))) 707 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)247 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 708 708 ((( 709 709 //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.// 710 710 ))) ... ... @@ -717,11 +717,8 @@ 717 717 )))|(% colspan="1" %)(% colspan="1" %) 718 718 ((( 719 719 **$ware.illegal** updated 720 -)))|(% colspan="1" %)(% colspan="1" %) 721 -((( 722 - 723 723 ))) 724 -|(% 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" %) 725 725 ((( 726 726 //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.// 727 727 //It now returns true if $ware is illegal to any faction in the game.// ... ... @@ -735,11 +735,8 @@ 735 735 )))|(% colspan="1" %)(% colspan="1" %) 736 736 ((( 737 737 MD script **RML_Flight_Along_Path** removed 738 -)))|(% colspan="1" %)(% colspan="1" %) 739 -((( 740 - 741 741 ))) 742 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)276 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 743 743 ((( 744 744 //The MD script RML_Flight_Along_Path was not referened and was removed.// 745 745 ))) ... ... @@ -752,11 +752,8 @@ 752 752 )))|(% colspan="1" %)(% colspan="1" %) 753 753 ((( 754 754 parameters of **<event_venture_mission_completed/>** changed 755 -)))|(% colspan="1" %)(% colspan="1" %) 756 -((( 757 - 758 758 ))) 759 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)290 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 760 760 ((( 761 761 //old params: param = venture details, param2 = ships involved, param3 = duration// 762 762 //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration// ... ... @@ -768,11 +768,8 @@ 768 768 )))|((( 769 769 **<set_object_wing_name/>** removed, 770 770 **<set_object_fleet_name/>** added 771 -)))|(% colspan="1" %)(% colspan="1" %) 772 -((( 773 - 774 774 ))) 775 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)303 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 776 776 ((( 777 777 //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>// 778 778 ))) ... ... @@ -783,15 +783,12 @@ 783 783 )))|((( 784 784 **$controllable.wing.*** removed, 785 785 **$controllable.fleet.*** added 786 -)))|(% colspan="1" %)(% colspan="1" %) 787 -((( 788 - 789 789 ))) 790 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)315 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 791 791 ((( 792 792 $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander 793 793 ))) 794 -|(% colspan=" 4" %)(% colspan="4" %)319 +|(% colspan="3" %)(% colspan="3" %) 795 795 ((( 796 796 == 2.60 == 797 797 ))) ... ... @@ -801,11 +801,8 @@ 801 801 2.60 Beta 1 802 802 )))|((( 803 803 '**checkoperational**' filter behaviour changed 804 -)))|(% colspan="1" %)(% colspan="1" %) 805 -((( 806 - 807 807 ))) 808 -|(% 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" %) 809 809 ((( 810 810 //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.// 811 811 ... ... @@ -817,15 +817,12 @@ 817 817 2.60 Beta 1 818 818 )))|((( 819 819 $container.**supplyresources** behavior changed 820 -)))|(% colspan="1" %)(% colspan="1" %) 821 -((( 822 - 823 823 ))) 824 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)343 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 825 825 ((( 826 826 //The script keyword $container.supplyresources now includes reserved wares.// 827 827 ))) 828 -|(% colspan=" 4" %)(% colspan="4" %)347 +|(% colspan="3" %)(% colspan="3" %) 829 829 ((( 830 830 == 2.20 == 831 831 ))) ... ... @@ -838,11 +838,8 @@ 838 838 )))|(% colspan="1" %)(% colspan="1" %) 839 839 ((( 840 840 **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined. 841 -)))|(% colspan="1" %)(% colspan="1" %) 842 -((( 843 - 844 844 ))) 845 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)361 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 846 846 ((( 847 847 //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. 848 848 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.// ... ... @@ -859,15 +859,12 @@ 859 859 )))|(% colspan="1" %)(% colspan="1" %) 860 860 ((( 861 861 Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor' 862 -)))|(% colspan="1" %)(% colspan="1" %) 863 -((( 864 - 865 865 ))) 866 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)379 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 867 867 ((( 868 868 //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.// 869 869 ))) 870 -|(% colspan=" 4" %)(% colspan="4" %)383 +|(% colspan="3" %)(% colspan="3" %) 871 871 ((( 872 872 == 2.00 == 873 873 ))) ... ... @@ -880,11 +880,8 @@ 880 880 )))|(% colspan="1" %)(% colspan="1" %) 881 881 ((( 882 882 **<event_build_finished/> **param2 now returns null instead of a construction sequence 883 -)))|(% colspan="1" %)(% colspan="1" %) 884 -((( 885 - 886 886 ))) 887 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)397 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 888 888 ((( 889 889 //The construction sequence which was finished should now be accessed via the buildtask provided via param3.// 890 890 ))) ... ... @@ -897,11 +897,8 @@ 897 897 )))|(% colspan="1" %)(% colspan="1" %) 898 898 ((( 899 899 **param.boarding.{...}** strength parameters removed 900 -)))|(% colspan="1" %)(% colspan="1" %) 901 -((( 902 - 903 903 ))) 904 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)411 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 905 905 ((( 906 906 //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.// 907 907 ))) ... ... @@ -914,11 +914,8 @@ 914 914 )))|(% colspan="1" %)(% colspan="1" %) 915 915 ((( 916 916 **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed 917 -)))|(% colspan="1" %)(% colspan="1" %) 918 -((( 919 - 920 920 ))) 921 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)425 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 922 922 ((( 923 923 //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.// 924 924 ))) ... ... @@ -928,11 +928,8 @@ 928 928 2.00 Beta 1 929 929 )))|((( 930 930 **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals 931 -)))|(% colspan="1" %)(% colspan="1" %) 932 -((( 933 - 934 934 ))) 935 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)436 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 936 936 ((( 937 937 //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.// 938 938 ))) ... ... @@ -942,11 +942,8 @@ 942 942 2.00 Beta 1 943 943 )))|((( 944 944 **FFI: SetFormationShape()** no longer indicates an error upon certain error cases 945 -)))|(% colspan="1" %)(% colspan="1" %) 946 -((( 947 - 948 948 ))) 949 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)447 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 950 950 ((( 951 951 //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.// 952 952 //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.// ... ... @@ -957,11 +957,8 @@ 957 957 2.00 Beta 1 958 958 )))|((( 959 959 **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated. 960 -)))|(% colspan="1" %)(% colspan="1" %) 961 -((( 962 - 963 963 ))) 964 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)459 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 965 965 ((( 966 966 //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.// 967 967 ))) ... ... @@ -971,11 +971,8 @@ 971 971 2.00 Beta 1 972 972 )))|((( 973 973 **<event_player_changed_target/>** now fires and returns null if the player deselects a target. 974 -)))|(% colspan="1" %)(% colspan="1" %) 975 -((( 976 - 977 977 ))) 978 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)470 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 979 979 ((( 980 980 //For prior behavior, check for event.param being non-null.// 981 981 ))) ... ... @@ -985,11 +985,8 @@ 985 985 2.00 Beta 1 986 986 )))|((( 987 987 **<shoot/>/<shoot_at/>** attribute changes. 988 -)))|(% colspan="1" %)(% colspan="1" %) 989 -((( 990 - 991 991 ))) 992 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)481 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 993 993 ((( 994 994 //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.// 995 995 //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.// ... ... @@ -1003,11 +1003,8 @@ 1003 1003 2.00 Beta 1 1004 1004 )))|((( 1005 1005 **FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% class="confluenceTd" %) 1006 -)))|(% colspan="1" %)(% colspan="1" %) 1007 -((( 1008 - 1009 1009 ))) 1010 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)496 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1011 1011 ((( 1012 1012 //Added possibility to query build tasks of a certain buildmodule.// 1013 1013 ))) ... ... @@ -1017,11 +1017,8 @@ 1017 1017 2.00 Beta 1 1018 1018 )))|((( 1019 1019 **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field. 1020 -)))|(% colspan="1" %)(% colspan="1" %) 1021 -((( 1022 - 1023 1023 ))) 1024 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)507 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1025 1025 ((( 1026 1026 //Added list of resources a buildmodule needs to build.// 1027 1027 ))) ... ... @@ -1031,11 +1031,8 @@ 1031 1031 2.00 Beta 1 1032 1032 )))|((( 1033 1033 (% 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);" %) 1034 -)))|(% colspan="1" %)(% colspan="1" %) 1035 -((( 1036 - 1037 1037 ))) 1038 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)518 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1039 1039 ((( 1040 1040 //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.// 1041 1041 ))) ... ... @@ -1045,15 +1045,12 @@ 1045 1045 2.00 Beta 1 1046 1046 )))|((( 1047 1047 **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" %) 1048 -)))|(% colspan="1" %)(% colspan="1" %) 1049 -((( 1050 - 1051 1051 ))) 1052 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)529 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1053 1053 ((( 1054 1054 //Changed return value type to const char* to better identify failure reasons in Lua script.// 1055 1055 ))) 1056 -|(% colspan=" 4" %)(% colspan="4" %)533 +|(% colspan="3" %)(% colspan="3" %) 1057 1057 ((( 1058 1058 == 1.50 == 1059 1059 ))) ... ... @@ -1063,11 +1063,8 @@ 1063 1063 1.50 Beta 3 1064 1064 )))|((( 1065 1065 **Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %) 1066 -)))|(% colspan="1" %)(% colspan="1" %) 1067 -((( 1068 - 1069 1069 ))) 1070 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)544 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1071 1071 ((( 1072 1072 //The "docksizes" property no longer includes internal ship storage docks.// 1073 1073 ))) ... ... @@ -1077,11 +1077,8 @@ 1077 1077 1.50 Beta 2 1078 1078 )))|((( 1079 1079 **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR). 1080 -)))|(% colspan="1" %)(% colspan="1" %) 1081 -((( 1082 - 1083 1083 ))) 1084 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)555 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1085 1085 ((( 1086 1086 //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".// 1087 1087 ... ... @@ -1095,11 +1095,8 @@ 1095 1095 1.50 Beta 2 1096 1096 )))|((( 1097 1097 **FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %) 1098 -)))|(% colspan="1" %)(% colspan="1" %) 1099 -((( 1100 - 1101 1101 ))) 1102 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)570 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1103 1103 ((( 1104 1104 //Added new "operational" field to retrieve information about number of operational upgrades in a group.// 1105 1105 ))) ... ... @@ -1112,11 +1112,8 @@ 1112 1112 )))|(% colspan="1" %)(% colspan="1" %) 1113 1113 ((( 1114 1114 **FFI: SetGuidance()** removed useinfopoint argument. 1115 -)))|(% colspan="1" %)(% colspan="1" %) 1116 -((( 1117 - 1118 1118 ))) 1119 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)584 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1120 1120 ((( 1121 1121 //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. 1122 1122 // ... ... @@ -1129,15 +1129,12 @@ 1129 1129 1.50 Beta 1 1130 1130 )))|((( 1131 1131 **FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %) 1132 -)))|(% colspan="1" %)(% colspan="1" %) 1133 -((( 1134 - 1135 1135 ))) 1136 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)598 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1137 1137 ((( 1138 1138 (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. // 1139 1139 ))) 1140 -|(% colspan=" 4" %)(% colspan="4" %)602 +|(% colspan="3" %)(% colspan="3" %) 1141 1141 ((( 1142 1142 == 1.32 == 1143 1143 ))) ... ... @@ -1147,15 +1147,12 @@ 1147 1147 1.32 1148 1148 )))|((( 1149 1149 **Lua: GetComponentData() **removed the "nextdestname" property. 1150 -)))|(% colspan="1" %)(% colspan="1" %) 1151 -((( 1152 - 1153 1153 ))) 1154 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)613 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1155 1155 ((( 1156 1156 //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.// 1157 1157 ))) 1158 -|(% colspan=" 4" %)(% colspan="4" %)617 +|(% colspan="3" %)(% colspan="3" %) 1159 1159 ((( 1160 1160 == 1.20 == 1161 1161 ))) ... ... @@ -1165,11 +1165,8 @@ 1165 1165 1.20 1166 1166 )))|((( 1167 1167 **FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %) 1168 -)))|(% colspan="1" %)(% colspan="1" %) 1169 -((( 1170 - 1171 1171 ))) 1172 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)628 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1173 1173 ((( 1174 1174 //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.// 1175 1175 )))
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 - 1068905671 +89144727 - url
-
... ... @@ -1,1 +1,1 @@ 1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/ 106890567/Breaking Changes1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/89144727/Breaking Changes