Changes for page Breaking Changes
Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 117.1
edited by Matthias Haan
on 2024/05/22 12:24
on 2024/05/22 12:24
Change comment:
There is no comment for this version
To version 50.1
edited by nick
on 2020/01/08 16:26
on 2020/01/08 16:26
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Parent
-
... ... @@ -1,1 +1,0 @@ 1 -X4 Foundations Wiki.Modding Support.WebHome - Author
-
... ... @@ -1,1 +1,1 @@ 1 -xwiki:XWiki. Matthias1 +xwiki:XWiki.nick - Content
-
... ... @@ -4,13 +4,13 @@ 4 4 The following table provides an overview about all breaking changes. This should help you to make any necessary changes to restore compatibility of older mods with new versions of X4. 5 5 Feel free to drop a note if a certain breaking change is breaking your mod and you have difficulties finding a way to work around the issue. 6 6 7 -{{ info}}8 - ⚠The list of breaking changes does7 +{{note}} 8 +The list of breaking changes does **NOT** cover changes in the provided/shipped scripts (for instance UI scripts like the ones located under ui/addons/XXX or ui/core/Lua). These scripts can change anytime without explicit notice. If you hook into one of these scripts or provide replacements for these, please check the script for possible breaking changes yourself. 9 9 10 10 Further note that the list provides information about breaking changes which are in the pipeline of being released. This is meant merely as an informational heads up. Neither do mistake this as an announcement of that version becoming available soon nor take it for granted that such a change will go live. Any information provided for not yet released versions can change (and even be removed) prior to such version having seen the light of day. 11 11 12 12 As a final note, please be aware that issues introduced during the beta phase might not be explicitly mentioned in the list below, if things would only be broken in-between two beta versions. While we still aim to document any (potential) breaking change here, there might be circumstances for which we divert from that procedure (especially in case of only minor issues which are considered merely bugfixes rather than an intended behavior change). 13 -{{/ info}}13 +{{/note}} 14 14 15 15 {{warning title="UI modding considered unstable until further notice..."}} 16 16 Please note that UI modding must be considered **unstable** in the current version. While we are working hard to get the UI modding integration into a stable state, we might have to introduce larger backwards incompatibilities in the following patches. This means that you might have to modify any mod using UI modding capabilities to a larger extend to keep it compatible with certain patches. Still, we are doing our best not to unnecessarily break things for modders and certainly will announce such changes on this page here. ... ... @@ -18,108 +18,30 @@ 18 18 19 19 = Breaking Changes = 20 20 21 -{{toc scope="LOCAL" start="3"/}} 22 - 23 -=== Version 7.00 === 24 - 25 - 26 -(% class="wrapped" %) 27 -|(% colspan="1" style="width:117px" %)Scripts|(% colspan="1" style="width:119px" %)7.00 Beta 6|(% colspan="2" style="width:1625px" %)MD action **<set_holomap_target>** parameter change. 28 -|(% colspan="4" style="width:117px" %)((( 29 -//The **pantime** parameter has never actually done anything beyond turning panning on or making the transition instant. To make this clear it has been** **replaced with the boolean parameter **instant.**// 21 +|=((( 22 +Type 23 +)))|=((( 24 +Version 25 +)))|=((( 26 +Summary 30 30 ))) 31 -|(% colspan="1" style="width:117px" %)Assets|(% colspan="1" style="width:119px" %)7.00 Beta 1|(% colspan="2" style="width:1625px" %)Renamed some material names and changed file paths for textures. 32 -|(% colspan="4" style="width:117px" %)((( 33 -(% style="color:#ffffff" %)//Some material names and texture paths were changed. Please DIFF the materiallibrary.xml from 6.20 with 7.0 to see the difference// 34 -))) 35 -|(% colspan="1" style="width:117px" %)(% colspan="1" %) 28 +|(% colspan="3" %)(% colspan="3" %) 36 36 ((( 37 -Scripts 38 -)))|(% colspan="1" style="width:119px" %)((( 39 -7.00 Beta 1 40 -)))|(% colspan="2" style="width:1625px" %)((( 41 -MD action **<set_presentation_cluster_persistence/>** now requires the cluster to be a presentation cluster. 30 +== 3.00 == 42 42 ))) 43 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 44 -((( 45 -// Previously it was possible to set normal clusters to be persistent presentation clusters which was an invalid state.// 46 -))) 47 -|(% colspan="1" style="width:117px" %)(% colspan="1" %) 48 -((( 49 -UI extensions 50 -)))|(% colspan="1" style="width:119px" %)((( 51 -7.00 Beta 1 52 -)))|(% colspan="2" style="width:1625px" %)((( 53 -**FFI**: RemoveBuildPlot() changed 54 -))) 55 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 56 -((( 57 -// The build plot's buildstorage is no longer removed implicitly. The buildstorage will instead be cleaned-up once it is empty and no ships are docked.// 58 -))) 59 -|(% colspan="1" style="width:117px" %)(% colspan="1" %) 60 -((( 61 -Assets 62 -)))|(% colspan="1" style="width:119px" %)((( 63 -7.00 Beta 1 64 -)))|(% colspan="2" style="width:1625px" %)((( 65 -**Some Split DLC materials moved to base game** 66 -))) 67 -|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 68 -((( 69 -// //"spl_p1_fx" AND "split_p1_hulltexture_01" were moved from Split DLC to base game 70 -))) 71 - 72 ----- 73 - 74 -=== Version 6.00 === 75 - 76 -(% class="wrapped" %) 77 -|((( 78 -Libraries 79 -)))|((( 80 -6.00 Beta 7 81 -)))|(% colspan="2" %)((( 82 -Updated weights for ship groups in shipgroups.xml libraries of base game and all DLCs. 83 -))) 84 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 85 -((( 86 -//Previously some entries were lacking "weight" parameter, causing it to default to "1", which prevent adding new ships to the group with appropriate/configurable granularity.// 87 - 88 -//All groups should now have "weight" parameter added and old "weights" were updated to not have single-digit numbers.// 89 -))) 90 90 |(% colspan="1" %)(% colspan="1" %) 91 91 ((( 92 - Scripts34 +Global 93 93 )))|(% colspan="1" %)(% colspan="1" %) 94 94 ((( 95 -6.00 Beta 4 96 -)))|(% colspan="2" %)(% colspan="1" %) 97 -((( 98 -Changed conditions for **<event_player_travelmode_started> <event_player_travelmode_stopped> <event_player_travelmode_charge_started> <event_player_travelmode_charge_aborted>** to be raised. 99 -))) 100 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 101 -((( 102 -//The <event_player_travelmode_started>, <event_player_travelmode_stopped>, <event_player_travelmode_charge_started> and <event_player_travelmode_charge_aborted> events will no longer be raised if the player is a passenger on board a ship which enters or leaves travel mode. Previously these events would be raised whether the player was the pilot or a passenger. // 103 - 104 -//Scripts that need to check whether the player exits travel mode may also need to consider checking whether the player leaves the control seat using <event_player_stopped_control> since this will also result in travel mode stopping.// 105 -))) 106 -|(% colspan="1" %)(% colspan="1" %) 107 -((( 108 -Scripts 37 +3.0 Beta 2 109 109 )))|(% colspan="1" %)(% colspan="1" %) 110 110 ((( 111 -6.00 Beta 3 112 -)))|(% colspan="2" %)(% colspan="1" %) 113 -((( 114 -Changed result of **<find_object_surface>** action in the case of a failure 40 +Support for entity flag "**skillsvisible**" dropped 115 115 ))) 116 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey"title="Background colour :"%)(% class="highlight-grey" colspan="3" data-highlight-colour="grey"title="Background colour :"%)42 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 117 117 ((( 118 -//The 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.// 119 - 120 -//Previously, it returned null only if there was a physics error. It however returned a valid, somewhat-random, position if physics were fine but it was still unable to find a suitable surface position. This position was often unsuitable to use for gameplay purposes so it is now null so the caller can handle the situation.// 121 - 122 -//The action itself has been improved to increase the chance of finding suitable surface positions.// 44 +//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().// 123 123 ))) 124 124 |(% colspan="1" %)(% colspan="1" %) 125 125 ((( ... ... @@ -126,475 +126,24 @@ 126 126 Scripts 127 127 )))|(% colspan="1" %)(% colspan="1" %) 128 128 ((( 129 -6.00 Beta 1 130 -)))|(% colspan="2" %)(% colspan="1" %) 131 -((( 132 -Behaviour change for **<match_dock>** script component filter 133 -))) 134 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 135 -((( 136 -//<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes. 137 -This has introduced a new potential pitfall: If finding or counting contained components be wary that there may be multiple positive results, even if there is only one dockingbay. e.g. matching contents for a station will include the dockingbay but also its containing walkable module as that also contains the dockingbay. To only account for docking bays, also filter by dockingbay class.// 138 -))) 139 -|(% colspan="1" %)(% colspan="1" %) 140 -((( 141 -Scripts 142 -)))|(% colspan="1" %)(% colspan="1" %) 143 -((( 144 -6.00 Beta 1 145 -)))|(% colspan="2" %)(% colspan="1" %) 146 -((( 147 -Changed result attribute location for **<get_attackstrength>** 148 -))) 149 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 150 -((( 151 -//The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.// 152 -))) 153 -|((( 154 -Assets 155 -)))|((( 156 -6.00 Beta 1 157 -)))|(% colspan="2" %)((( 158 -Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons 159 -))) 160 -|(% class="highlight-grey" colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% class="highlight-grey" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %) 161 -((( 162 -//Connection tags used to specify compatibilities in component templates between a ship or station module and engines or shields now additionally require the use of the "standard" tag matching weapon or turret logic. For weapons that are neither Missile Launcher nor Mining Laser, the tag "combat" is also required. 163 -Exception: special equipment that is deliberately not compatible with the majority of slots may use another tag instead of "standard", e.g. "highpower" for certain Terran weapons.// 164 -))) 165 -|(% colspan="1" %)(% colspan="1" %) 166 -((( 167 -Scripts 168 -)))|(% colspan="1" %)(% colspan="1" %) 169 -((( 170 -6.00 Beta 1 171 -)))|(% colspan="2" %)(% colspan="1" %) 172 -((( 173 -Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects 174 -))) 175 -|(% class="highlight-grey" colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% class="highlight-grey" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %) 176 -((( 177 -//When finding components with attribute "sortbygatedistanceto", e.g. in <find_object>, any objects with a negative gatedistance (i.e. unreachable objects) are automatically excluded from the result.// 178 -))) 179 -|((( 180 -Scripts 181 -)))|((( 182 -6.00 Beta 1 183 -)))|(% colspan="2" %)((( 184 -**<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards. 185 -))) 186 -|(% class="highlight-grey" colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% class="highlight-grey" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %) 187 -((( 188 -//The order of events was adjusted, allowing handlers of <event_player_owned_killed_object> and <event_player_owned_destroyed> to access commander/subordinate relationship of the destroyed object.// 189 -))) 190 -|((( 191 -Cutscenes 192 -)))|((( 193 -6.00 Beta 1 194 -)))|(% colspan="2" %)((( 195 -Changed behaviour of **<angles>** in cutscenes 196 -))) 197 -|(% class="highlight-grey" colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% class="highlight-grey" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %) 198 -((( 199 -//The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.// 200 -))) 201 - 202 ----- 203 - 204 -=== Version 5.00 === 205 - 206 -(% class="wrapped" %) 207 -|((( 208 -Parameters 209 -)))|((( 210 -5.00 Beta 1 211 -)))|(% colspan="2" %)((( 212 -**<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration 213 -))) 214 -|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 215 -((( 216 -//'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.// 217 -))) 218 - 219 ----- 220 - 221 -=== Version 4.10 === 222 - 223 -(% class="wrapped" %) 224 -|(% colspan="1" %)(% colspan="1" %) 225 -((( 226 -UI extensions 227 -)))|(% colspan="1" %)(% colspan="1" %) 228 -((( 229 -4.10 Beta 7 230 -)))|(% colspan="2" %)(% colspan="1" %) 231 -((( 232 -**FFI**: SetMapRenderCargoContents(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos() deprecated 233 -))) 234 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 235 -((( 236 -//The functionality represented by SetMapRenderCargoContents(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos() has been removed and the function was therefore stubbed.// 237 -))) 238 -|(% colspan="1" %)(% colspan="1" %) 239 -((( 240 -UI extensions 241 -)))|(% colspan="1" %)(% colspan="1" %) 242 -((( 243 -4.10 Beta 6 244 -)))|(% colspan="2" %)(% colspan="1" %) 245 -((( 246 -**FFI**: CustomGameStartPlayerProperty2 changed 247 -))) 248 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 249 -((( 250 -//This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.// 251 -))) 252 -|(% colspan="1" %)(% colspan="1" %) 253 -((( 254 -Parameters 255 -)))|(% colspan="1" %)(% colspan="1" %) 256 -((( 257 -4.10 Beta 3 258 -)))|(% colspan="2" %)(% colspan="1" %) 259 -((( 260 -Renamed **<stationinfobox>** to **<infobox>** 261 -))) 262 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 263 -((( 264 -//Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.// 265 -))) 266 -|(% colspan="1" %)(% colspan="1" %) 267 -((( 268 -UI extensions 269 -)))|(% colspan="1" %)(% colspan="1" %) 270 -((( 271 -4.10 Beta 2 272 -)))|(% colspan="2" %)(% colspan="1" %) 273 -((( 274 -**FFI**: SetMacroMapPlayerSectorOffset() deprecated 275 -))) 276 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 277 -((( 278 -//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.// 279 -))) 280 -|((( 281 -UI extensions 282 -)))|((( 283 -4.10 Beta 2 284 -)))|(% colspan="2" %)((( 285 -**FFI**: FilterComponentForMapMode() and SetMapObjectFilter() changed 286 -))) 287 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 288 -((( 289 -//These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.// 290 -))) 291 -|((( 292 -Scripts 293 -)))|((( 294 -4.10 Beta 1 295 -)))|(% colspan="2" %)((( 296 -People related attributes of mission** <delivery> **node moved 297 -))) 298 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 299 -((( 300 -//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.// 301 -))) 302 -|(% colspan="1" %)(% colspan="1" %) 303 -((( 304 -Scripts 305 -)))|(% colspan="1" %)(% colspan="1" %) 306 -((( 307 -4.10 Beta 1 308 -)))|(% colspan="2" %)(% colspan="1" %) 309 -((( 310 -**$destructible.productions** replaced with $defensible.productions 311 -))) 312 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 313 -((( 314 -//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.// 315 -))) 316 -|((( 317 -Scripts 318 -)))|((( 319 -4.10 Beta 1 320 -)))|(% colspan="2" %)((( 321 -Removed script property **$object.spawnsourceseed** 322 -))) 323 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 324 -((( 325 -//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.// 326 -))) 327 - 328 ----- 329 - 330 -=== Version 4.00 === 331 - 332 -(% class="wrapped" %) 333 -|(% colspan="1" %)(% colspan="1" %) 334 -((( 335 -UI core 336 -)))|(% colspan="1" %)(% colspan="1" %) 337 -((( 338 -4.00 Beta 10 339 -)))|(% colspan="2" %)(% colspan="1" %) 340 -((( 341 -Controlled ship can change without a **gameplanchange-event** occurring. 342 -))) 343 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 344 -((( 345 -//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). 346 -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.// 347 -))) 348 -|((( 349 -Scripts 350 -)))|((( 351 -4.00 Beta 7 352 -)))|(% colspan="2" %)((( 353 -Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed 354 -))) 355 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 356 -((( 357 -//Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects? 358 -New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits 359 -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// 360 -))) 361 -|(% colspan="1" %)(% colspan="1" %) 362 -((( 363 -UI core 364 -)))|(% colspan="1" %)(% colspan="1" %) 365 -((( 366 -4.00 Beta 6 367 -)))|(% colspan="2" %)(% colspan="1" %) 368 -((( 369 -**FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed 370 -))) 371 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 372 -((( 373 -//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. 374 -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).// 375 - 376 -//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.// 377 -))) 378 -|(% colspan="1" %)(% colspan="1" %) 379 -((( 380 -UI core 381 -)))|(% colspan="1" %)(% colspan="1" %) 382 -((( 383 -4.00 Beta 5 384 -)))|(% colspan="2" %)(% colspan="1" %) 385 -((( 386 -**FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed 387 -))) 388 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 389 -((( 390 -//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.// 391 - 392 -//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). 393 -))) 394 -|((( 395 -Parameters 396 -)))|((( 397 -4.00 Beta 1 398 -)))|(% colspan="2" %)((( 399 -**requiresconstructionvessel** parameter moved 400 -))) 401 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 402 -((( 403 -//The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.// 404 -))) 405 -|((( 406 -Scripts 407 -)))|((( 408 -4.00 Beta 1 409 -)))|(% colspan="2" %)((( 410 -Changed behaviour of **gatedistance** script property 411 -))) 412 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 413 -((( 414 -//The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.// 415 -))) 416 - 417 ----- 418 - 419 -=== Version 3.30 === 420 - 421 -(% class="wrapped" %) 422 -|((( 423 -UI extensions 424 -)))|((( 425 -3.30 Beta 3 426 -)))|(% colspan="2" %)((( 427 -**FFI: **Removed** GetMissionLimit() **and** IsMissionLimitEnabled()** 428 -))) 429 -|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 430 -((( 431 -//These mission limit-related functions (added in 3.30 Beta 1 and 2) are replaced with FFI IsMissionLimitReached()// 432 -))) 433 - 434 ----- 435 - 436 -=== Version 3.20 === 437 - 438 -(% class="wrapped" %) 439 -|((( 440 -Scripts 441 -)))|((( 442 -3.20 Beta 1 443 -)))|(% colspan="2" %)((( 444 -Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed 445 -))) 446 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 447 -((( 448 -//Old params: param = attacked object, param2 = attack method, param3 = attacked component// 449 -//New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon] 450 -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// 451 -))) 452 -|(% colspan="1" %)(% colspan="1" %) 453 -((( 454 -Scripts 455 -)))|(% colspan="1" %)(% colspan="1" %) 456 -((( 457 -3.20 Beta 1 458 -)))|(% colspan="2" %)(% colspan="1" %) 459 -((( 460 -Removed script property $trade.**restriction.faction** 461 -))) 462 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 463 -((( 464 -//$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.// 465 -))) 466 -|((( 467 -UI extensions 468 -)))|((( 469 -3.20 Beta 1 470 -)))|(% colspan="2" %)((( 471 -**Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete! 472 -))) 473 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 474 -((( 475 -//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.// 476 -))) 477 - 478 ----- 479 - 480 -=== Version 3.10 === 481 - 482 -(% class="wrapped" %) 483 -|(% colspan="1" %)(% colspan="1" %) 484 -((( 485 -Scripts 486 -)))|(% colspan="1" %)(% colspan="1" %) 487 -((( 488 -3.10 Beta 1 489 -)))|(% colspan="2" %)(% colspan="1" %) 490 -((( 491 -Removed script action **<add_build/>** 492 -))) 493 -|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 494 -((( 495 -//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.// 496 -))) 497 - 498 ----- 499 - 500 -=== Version 3.00 === 501 - 502 -(% class="wrapped" %) 503 -|(% colspan="1" %)(% colspan="1" %) 504 -((( 505 -Scripts 506 -)))|(% colspan="1" %)(% colspan="1" %) 507 -((( 508 -3.0 Beta 6 509 -)))|(% colspan="2" %)(% colspan="1" %) 510 -((( 511 -Changed behaviour of script action **<get_suitable_job/>** 512 -))) 513 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 514 -((( 515 -//<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.// 516 -))) 517 -|(% colspan="1" %)(% colspan="1" %) 518 -((( 519 -Scripts 520 -)))|(% colspan="1" %)(% colspan="1" %) 521 -((( 522 -3.0 Beta 6 523 -)))|(% colspan="2" %)(% colspan="1" %) 524 -((( 525 -Changed behaviour of script action **<get_ware_definition/>** 526 -))) 527 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 528 -((( 529 -//<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.// 530 -))) 531 -|(% colspan="1" %)(% colspan="1" %) 532 -((( 533 -Global 534 -)))|(% colspan="1" %)(% colspan="1" %) 535 -((( 536 536 3.0 Beta 5 537 -)))|(% colspan="2" %)(% colspan="1" %) 538 -((( 539 -Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case 540 -))) 541 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 542 -((( 543 -//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.) 544 - 545 -//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).// 546 -))) 547 -|(% colspan="1" %)(% colspan="1" %) 548 -((( 549 -Scripts 550 550 )))|(% colspan="1" %)(% colspan="1" %) 551 551 ((( 552 -3.0 Beta 5 553 -)))|(% colspan="2" %)(% colspan="1" %) 554 -((( 555 -Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions> 54 +Changes to $dockingbay.todockpos and $dockingbay.launchpos 556 556 ))) 557 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)56 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 558 558 ((( 559 -//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.// 560 -))) 561 -|(% colspan="1" %)(% colspan="1" %) 562 -((( 563 -Scripts 564 -)))|(% colspan="1" %)(% colspan="1" %) 565 -((( 566 -3.0 Beta 5 567 -)))|(% colspan="2" %)(% colspan="1" %) 568 -((( 569 -Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos** 570 -))) 571 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 572 -((( 573 573 //Before the change, positions are relative to $dockingbay.parent. 574 574 After the change, positions are relative to $dockingbay as specified in the documentation.// 575 575 ))) 576 -|(% colspan="1" %)(% colspan="1" %) 577 -((( 578 -Global 579 -)))|(% colspan="1" %)(% colspan="1" %) 580 -((( 581 -3.0 Beta 2 582 -)))|(% colspan="2" %)(% colspan="1" %) 583 -((( 584 -Support for entity flag "**skillsvisible**" dropped 585 -))) 586 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 587 -((( 588 -//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().// 589 -))) 590 590 |((( 591 591 Scripts 592 592 )))|((( 593 593 3.0 Beta 2 594 -)))|( % colspan="2" %)(((65 +)))|((( 595 595 Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**. 596 596 ))) 597 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)68 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 598 598 ((( 599 599 //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. 600 600 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. ... ... @@ -607,11 +607,11 @@ 607 607 )))|(% colspan="1" %)(% colspan="1" %) 608 608 ((( 609 609 3.0 Beta 1 610 -)))|(% colspan=" 2" %)(% colspan="1" %)81 +)))|(% colspan="1" %)(% colspan="1" %) 611 611 ((( 612 - **MissionBoard**support dropped83 +MissionBoard support dropped 613 613 ))) 614 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)85 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 615 615 ((( 616 616 //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.// 617 617 ))) ... ... @@ -619,10 +619,10 @@ 619 619 Job/God 620 620 )))|((( 621 621 3.0 Beta 1 622 -)))|( % colspan="2" %)(((623 -By default, **job/god entries**now only spawn objects in space added by the extension in which they are defined93 +)))|((( 94 +By default, job/god entries now only spawn objects in space added by the extension in which they are defined 624 624 ))) 625 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)96 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 626 626 ((( 627 627 //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.// 628 628 ))) ... ... @@ -632,11 +632,11 @@ 632 632 )))|(% colspan="1" %)(% colspan="1" %) 633 633 ((( 634 634 3.0 Beta 1 635 -)))|(% colspan=" 2" %)(% colspan="1" %)106 +)))|(% colspan="1" %)(% colspan="1" %) 636 636 ((( 637 637 Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'** 638 638 ))) 639 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)110 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 640 640 ((( 641 641 //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.// 642 642 ))) ... ... @@ -646,11 +646,11 @@ 646 646 )))|(% colspan="1" %)(% colspan="1" %) 647 647 ((( 648 648 3.0 Beta 1 649 -)))|(% colspan=" 2" %)(% colspan="1" %)120 +)))|(% colspan="1" %)(% colspan="1" %) 650 650 ((( 651 651 Script action **<set_doors_locked/>** attribute **'group'** changed 652 652 ))) 653 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)124 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 654 654 ((( 655 655 //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.// 656 656 ))) ... ... @@ -660,11 +660,11 @@ 660 660 )))|(% colspan="1" %)(% colspan="1" %) 661 661 ((( 662 662 3.0 Beta 1 663 -)))|(% colspan=" 2" %)(% colspan="1" %)134 +)))|(% colspan="1" %)(% colspan="1" %) 664 664 ((( 665 665 Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed 666 666 ))) 667 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)138 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 668 668 ((( 669 669 //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.// 670 670 ))) ... ... @@ -674,11 +674,11 @@ 674 674 )))|(% colspan="1" %)(% colspan="1" %) 675 675 ((( 676 676 3.0 Beta 1 677 -)))|(% colspan=" 2" %)(% colspan="1" %)148 +)))|(% colspan="1" %)(% colspan="1" %) 678 678 ((( 679 679 Script actions **<set_hack_target/>** and **<abort_hack/>** removed 680 680 ))) 681 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)152 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 682 682 ((( 683 683 //These actions had no effect and were removed.// 684 684 ))) ... ... @@ -688,11 +688,11 @@ 688 688 )))|(% colspan="1" %)(% colspan="1" %) 689 689 ((( 690 690 3.0 Beta 1 691 -)))|(% colspan=" 2" %)(% colspan="1" %)162 +)))|(% colspan="1" %)(% colspan="1" %) 692 692 ((( 693 693 **<setup_conversation_minigame/>** script action removed 694 694 ))) 695 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)166 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 696 696 ((( 697 697 //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.// 698 698 ))) ... ... @@ -702,11 +702,11 @@ 702 702 )))|(% colspan="1" %)(% colspan="1" %) 703 703 ((( 704 704 3.0 Beta 1 705 -)))|(% colspan=" 2" %)(% colspan="1" %)176 +)))|(% colspan="1" %)(% colspan="1" %) 706 706 ((( 707 707 <add_player_choice_*> **confidence** attribute removed 708 708 ))) 709 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)180 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 710 710 ((( 711 711 //The default confidence of player options is another leftover from the XR era and had no effect in X4.// 712 712 ))) ... ... @@ -716,11 +716,11 @@ 716 716 )))|(% colspan="1" %)(% colspan="1" %) 717 717 ((( 718 718 3.0 Beta 1 719 -)))|(% colspan=" 2" %)(% colspan="1" %)190 +)))|(% colspan="1" %)(% colspan="1" %) 720 720 ((( 721 721 **<hack_via_control_panel/>** script action removed 722 722 ))) 723 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)194 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 724 724 ((( 725 725 //Unused script action <hack_via_control_panel/> was removed.// 726 726 ))) ... ... @@ -730,11 +730,11 @@ 730 730 )))|(% colspan="1" %)(% colspan="1" %) 731 731 ((( 732 732 3.0 Beta 1 733 -)))|(% colspan=" 2" %)(% colspan="1" %)204 +)))|(% colspan="1" %)(% colspan="1" %) 734 734 ((( 735 735 **Lua: **GetMiniGameCursorPosition() removed 736 736 ))) 737 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)208 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 738 738 ((( 739 739 //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.// 740 740 ))) ... ... @@ -742,10 +742,10 @@ 742 742 UI core 743 743 )))|((( 744 744 3.0 Beta 1 745 -)))|( % colspan="2" %)(((216 +)))|((( 746 746 **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders 747 747 ))) 748 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)219 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 749 749 ((( 750 750 //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.// 751 751 ))) ... ... @@ -755,11 +755,11 @@ 755 755 )))|(% colspan="1" %)(% colspan="1" %) 756 756 ((( 757 757 3.0 Beta 1 758 -)))|(% colspan=" 2" %)(% colspan="1" %)229 +)))|(% colspan="1" %)(% colspan="1" %) 759 759 ((( 760 760 **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor 761 761 ))) 762 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)233 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 763 763 ((( 764 764 //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.// 765 765 ))) ... ... @@ -769,11 +769,11 @@ 769 769 )))|(% colspan="1" %)(% colspan="1" %) 770 770 ((( 771 771 3.0 Beta 1 772 -)))|(% colspan=" 2" %)(% colspan="1" %)243 +)))|(% colspan="1" %)(% colspan="1" %) 773 773 ((( 774 774 **$ware.illegal** updated 775 775 ))) 776 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)247 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 777 777 ((( 778 778 //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.// 779 779 //It now returns true if $ware is illegal to any faction in the game.// ... ... @@ -784,11 +784,11 @@ 784 784 )))|(% colspan="1" %)(% colspan="1" %) 785 785 ((( 786 786 3.0 Beta 1 787 -)))|(% colspan=" 2" %)(% colspan="1" %)258 +)))|(% colspan="1" %)(% colspan="1" %) 788 788 ((( 789 789 MD script **RML_Flight_Along_Path** removed 790 790 ))) 791 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)262 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 792 792 ((( 793 793 //The MD script RML_Flight_Along_Path was not referened and was removed.// 794 794 ))) ... ... @@ -798,11 +798,11 @@ 798 798 )))|(% colspan="1" %)(% colspan="1" %) 799 799 ((( 800 800 3.0 Beta 1 801 -)))|(% colspan=" 2" %)(% colspan="1" %)272 +)))|(% colspan="1" %)(% colspan="1" %) 802 802 ((( 803 803 parameters of **<event_venture_mission_completed/>** changed 804 804 ))) 805 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)276 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 806 806 ((( 807 807 //old params: param = venture details, param2 = ships involved, param3 = duration// 808 808 //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration// ... ... @@ -811,11 +811,11 @@ 811 811 Scripts 812 812 )))|((( 813 813 3.0 Beta 1 814 -)))|( % colspan="2" %)(((285 +)))|((( 815 815 **<set_object_wing_name/>** removed, 816 816 **<set_object_fleet_name/>** added 817 817 ))) 818 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)289 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 819 819 ((( 820 820 //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>// 821 821 ))) ... ... @@ -823,28 +823,26 @@ 823 823 Scripts 824 824 )))|((( 825 825 3.0 Beta 1 826 -)))|( % colspan="2" %)(((297 +)))|((( 827 827 **$controllable.wing.*** removed, 828 828 **$controllable.fleet.*** added 829 829 ))) 830 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)301 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 831 831 ((( 832 832 $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander 833 833 ))) 834 - 835 ----- 836 - 837 -=== Version 2.60 === 838 - 839 -(% class="wrapped" %) 305 +|(% colspan="3" %)(% colspan="3" %) 306 +((( 307 +== 2.60 == 308 +))) 840 840 |((( 841 841 Scripts 842 842 )))|((( 843 843 2.60 Beta 1 844 -)))|( % colspan="2" %)(((313 +)))|((( 845 845 '**checkoperational**' filter behaviour changed 846 846 ))) 847 -|(% class="highlight-grey" colspan=" 10" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)316 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 848 848 ((( 849 849 //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.// 850 850 ... ... @@ -854,19 +854,17 @@ 854 854 Scripts 855 855 )))|((( 856 856 2.60 Beta 1 857 -)))|( % colspan="2" %)(((326 +)))|((( 858 858 $container.**supplyresources** behavior changed 859 -))) | | |860 -|(% class="highlight-grey" colspan=" 10" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)328 +))) 329 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 861 861 ((( 862 862 //The script keyword $container.supplyresources now includes reserved wares.// 863 863 ))) 864 - 865 ----- 866 - 867 -=== Version 2.20 === 868 - 869 -(% class="wrapped" %) 333 +|(% colspan="3" %)(% colspan="3" %) 334 +((( 335 +== 2.20 == 336 +))) 870 870 |(% colspan="1" %)(% colspan="1" %) 871 871 ((( 872 872 UI core ... ... @@ -873,16 +873,17 @@ 873 873 )))|(% colspan="1" %)(% colspan="1" %) 874 874 ((( 875 875 2.20 Beta 3/4 876 -)))|(% colspan=" 2" %)(% colspan="1" %)343 +)))|(% colspan="1" %)(% colspan="1" %) 877 877 ((( 878 878 **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined. 879 879 ))) 880 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)347 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 881 881 ((( 882 882 //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. 883 883 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.// 884 884 885 -//It's a pending change to ensure that the returned mode is more reasonable in an upcoming patch. So be aware that another breaking change might be introduced at some point.// 352 +//It's a pending change to ensure that the returned mode is more reasonable in an upcoming patch. So be aware that another breaking change might be introduced at some point. 353 +// 886 886 ))) 887 887 |(% colspan="1" %)(% colspan="1" %) 888 888 ((( ... ... @@ -890,20 +890,18 @@ 890 890 )))|(% colspan="1" %)(% colspan="1" %) 891 891 ((( 892 892 2.20 Beta 3 893 -)))|(% colspan=" 2" %)(% colspan="1" %)361 +)))|(% colspan="1" %)(% colspan="1" %) 894 894 ((( 895 895 Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor' 896 896 ))) 897 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)365 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 898 898 ((( 899 899 //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.// 900 900 ))) 901 - 902 ----- 903 - 904 -=== Version 2.00 === 905 - 906 -(% class="wrapped" %) 369 +|(% colspan="3" %)(% colspan="3" %) 370 +((( 371 +== 2.00 == 372 +))) 907 907 |(% colspan="1" %)(% colspan="1" %) 908 908 ((( 909 909 Scripts ... ... @@ -910,11 +910,11 @@ 910 910 )))|(% colspan="1" %)(% colspan="1" %) 911 911 ((( 912 912 2.00 Beta 1 913 -)))|(% colspan=" 2" %)(% colspan="1" %)379 +)))|(% colspan="1" %)(% colspan="1" %) 914 914 ((( 915 915 **<event_build_finished/> **param2 now returns null instead of a construction sequence 916 916 ))) 917 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)383 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 918 918 ((( 919 919 //The construction sequence which was finished should now be accessed via the buildtask provided via param3.// 920 920 ))) ... ... @@ -924,11 +924,11 @@ 924 924 )))|(% colspan="1" %)(% colspan="1" %) 925 925 ((( 926 926 2.00 Beta 1 927 -)))|(% colspan=" 2" %)(% colspan="1" %)393 +)))|(% colspan="1" %)(% colspan="1" %) 928 928 ((( 929 929 **param.boarding.{...}** strength parameters removed 930 930 ))) 931 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)397 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 932 932 ((( 933 933 //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.// 934 934 ))) ... ... @@ -938,11 +938,11 @@ 938 938 )))|(% colspan="1" %)(% colspan="1" %) 939 939 ((( 940 940 2.00 Beta 1 941 -)))|(% colspan=" 2" %)(% colspan="1" %)407 +)))|(% colspan="1" %)(% colspan="1" %) 942 942 ((( 943 943 **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed 944 944 ))) 945 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)411 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 946 946 ((( 947 947 //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.// 948 948 ))) ... ... @@ -950,10 +950,10 @@ 950 950 UI extensions 951 951 )))|((( 952 952 2.00 Beta 1 953 -)))|( % colspan="2" %)(((419 +)))|((( 954 954 **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals 955 955 ))) 956 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)422 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 957 957 ((( 958 958 //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.// 959 959 ))) ... ... @@ -961,10 +961,10 @@ 961 961 UI extensions 962 962 )))|((( 963 963 2.00 Beta 1 964 -)))|( % colspan="2" %)(((430 +)))|((( 965 965 **FFI: SetFormationShape()** no longer indicates an error upon certain error cases 966 966 ))) 967 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)433 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 968 968 ((( 969 969 //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.// 970 970 //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.// ... ... @@ -973,10 +973,10 @@ 973 973 Scripts 974 974 )))|((( 975 975 2.00 Beta 1 976 -)))|( % colspan="2" %)(((442 +)))|((( 977 977 **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated. 978 978 ))) 979 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)445 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 980 980 ((( 981 981 //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.// 982 982 ))) ... ... @@ -984,10 +984,10 @@ 984 984 Scripts 985 985 )))|((( 986 986 2.00 Beta 1 987 -)))|( % colspan="2" %)(((453 +)))|((( 988 988 **<event_player_changed_target/>** now fires and returns null if the player deselects a target. 989 989 ))) 990 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)456 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 991 991 ((( 992 992 //For prior behavior, check for event.param being non-null.// 993 993 ))) ... ... @@ -995,10 +995,10 @@ 995 995 AI Scripts 996 996 )))|((( 997 997 2.00 Beta 1 998 -)))|( % colspan="2" %)(((464 +)))|((( 999 999 **<shoot/>/<shoot_at/>** attribute changes. 1000 1000 ))) 1001 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)467 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1002 1002 ((( 1003 1003 //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.// 1004 1004 //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.// ... ... @@ -1010,10 +1010,10 @@ 1010 1010 UI extensions 1011 1011 )))|((( 1012 1012 2.00 Beta 1 1013 -)))|( % colspan="2" %)(((1014 -**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter. 479 +)))|((( 480 +**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% class="confluenceTd" %) 1015 1015 ))) 1016 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)482 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1017 1017 ((( 1018 1018 //Added possibility to query build tasks of a certain buildmodule.// 1019 1019 ))) ... ... @@ -1021,10 +1021,10 @@ 1021 1021 UI extensions 1022 1022 )))|((( 1023 1023 2.00 Beta 1 1024 -)))|( % colspan="2" %)(((490 +)))|((( 1025 1025 **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field. 1026 1026 ))) 1027 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)493 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1028 1028 ((( 1029 1029 //Added list of resources a buildmodule needs to build.// 1030 1030 ))) ... ... @@ -1032,10 +1032,10 @@ 1032 1032 UI extensions 1033 1033 )))|((( 1034 1034 2.00 Beta 1 1035 -)))|( % colspan="2" %)(((1036 -**Lua: 501 +)))|((( 502 +(% 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);" %) 1037 1037 ))) 1038 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)504 +|(% 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 ))) ... ... @@ -1043,27 +1043,25 @@ 1043 1043 UI extensions 1044 1044 )))|((( 1045 1045 2.00 Beta 1 1046 -)))|( % colspan="2" %)(((1047 -**FFI: RequestDockAtReason()/UndockPlayerShip() **changed their return values. 512 +)))|((( 513 +**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 1048 ))) 1049 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)515 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1050 1050 ((( 1051 1051 //Changed return value type to const char* to better identify failure reasons in Lua script.// 1052 1052 ))) 1053 - 1054 ----- 1055 - 1056 -=== Version 1.50 === 1057 - 1058 -(% class="wrapped" %) 519 +|(% colspan="3" %)(% colspan="3" %) 520 +((( 521 +== 1.50 == 522 +))) 1059 1059 |((( 1060 1060 UI extensions 1061 1061 )))|((( 1062 1062 1.50 Beta 3 1063 -)))|( % colspan="2" %)(((1064 -**Lua: GetComponentData() **changed behavior of "docksizes" property. 527 +)))|((( 528 +**Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %) 1065 1065 ))) 1066 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)530 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1067 1067 ((( 1068 1068 //The "docksizes" property no longer includes internal ship storage docks.// 1069 1069 ))) ... ... @@ -1071,10 +1071,10 @@ 1071 1071 All 1072 1072 )))|((( 1073 1073 1.50 Beta 2 1074 -)))|( % colspan="2" %)(((538 +)))|((( 1075 1075 **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR). 1076 1076 ))) 1077 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)541 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1078 1078 ((( 1079 1079 //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".// 1080 1080 ... ... @@ -1086,10 +1086,10 @@ 1086 1086 UI extensions 1087 1087 )))|((( 1088 1088 1.50 Beta 2 1089 -)))|( % colspan="2" %)(((1090 -**FFI: UpgradeGroupInfo **datatype was changed. 553 +)))|((( 554 +**FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %) 1091 1091 ))) 1092 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)556 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1093 1093 ((( 1094 1094 //Added new "operational" field to retrieve information about number of operational upgrades in a group.// 1095 1095 ))) ... ... @@ -1099,13 +1099,14 @@ 1099 1099 )))|(% colspan="1" %)(% colspan="1" %) 1100 1100 ((( 1101 1101 1.50 Beta 1 1102 -)))|(% colspan=" 2" %)(% colspan="1" %)566 +)))|(% colspan="1" %)(% colspan="1" %) 1103 1103 ((( 1104 1104 **FFI: SetGuidance()** removed useinfopoint argument. 1105 1105 ))) 1106 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)570 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1107 1107 ((( 1108 -//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.// 572 +//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. 573 +// 1109 1109 1110 1110 //The new function declaration is: void SetGuidance(UniverseID componentid, UIPosRot offset)// 1111 1111 ))) ... ... @@ -1113,44 +1113,40 @@ 1113 1113 UI extensions 1114 1114 )))|((( 1115 1115 1.50 Beta 1 1116 -)))|( % colspan="2" %)(((1117 -**FFI: CancelConstruction() **changed its return value. 581 +)))|((( 582 +**FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %) 1118 1118 ))) 1119 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" 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 -//CancelConstruction() now returns if the cancellation was successful. // 586 +(% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. // 1122 1122 ))) 1123 - 1124 ----- 1125 - 1126 -=== Version 1.32 === 1127 - 1128 -(% class="wrapped" %) 588 +|(% colspan="3" %)(% colspan="3" %) 589 +((( 590 +== 1.32 == 591 +))) 1129 1129 |((( 1130 1130 UI extensions 1131 1131 )))|((( 1132 1132 1.32 1133 -)))|( % colspan="2" %)(((596 +)))|((( 1134 1134 **Lua: GetComponentData() **removed the "nextdestname" property. 1135 1135 ))) 1136 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)599 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1137 1137 ((( 1138 1138 //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.// 1139 1139 ))) 1140 - 1141 ----- 1142 - 1143 -=== Version 1.20 === 1144 - 1145 -(% class="wrapped" %) 603 +|(% colspan="3" %)(% colspan="3" %) 604 +((( 605 +== 1.20 == 606 +))) 1146 1146 |((( 1147 1147 UI extensions 1148 1148 )))|((( 1149 1149 1.20 1150 -)))|( % colspan="2" %)(((1151 -**FFI: GetAAOption()** got a new "useconfig" parameter. 611 +)))|((( 612 +**FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %) 1152 1152 ))) 1153 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)614 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1154 1154 ((( 1155 -//The AA setting was changed to check the new setting with the user. In order to restore the old setting GetAAOption() gets the option to retrieve the config settings.// 616 +//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.// 1156 1156 )))
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 - 785778541 +89144012 - url
-
... ... @@ -1,1 +1,1 @@ 1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/ 78577854/Breaking Changes1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/89144012/Breaking Changes