Changes for page Breaking Changes
Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 105.1
edited by Daniel Turner
on 2023/08/25 09:46
on 2023/08/25 09:46
Change comment:
There is no comment for this version
To version 75.1
edited by stefan
on 2021/02/01 04:38
on 2021/02/01 04:38
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. Daniel1 +xwiki:XWiki.stefan - 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,7 +18,6 @@ 18 18 19 19 = Breaking Changes = 20 20 21 -(% class="wrapped" %) 22 22 |=((( 23 23 Type 24 24 )))|=((( ... ... @@ -25,259 +25,12 @@ 25 25 Version 26 26 )))|=((( 27 27 Summary 28 -))) 29 -|(% colspan="3" %)(% colspan="3" %) 27 +)))|=(% colspan="1" %)(% colspan="1" %) 30 30 ((( 31 - ==6.00 ==29 + 32 32 ))) 33 -|((( 34 -Libraries 35 -)))|((( 36 -6.00 Beta 7 37 -)))|((( 38 -Updated weights for ship groups in shipgroups.xml libraries of base game and all DLCs. 39 -))) 40 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 31 +|(% colspan="4" %)(% colspan="4" %) 41 41 ((( 42 -//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.// 43 - 44 -//All groups should now have "weight" parameter added and old "weights" were updated to not have single-digit numbers.// 45 -))) 46 -|(% colspan="1" %)(% colspan="1" %) 47 -((( 48 -Scripts 49 -)))|(% colspan="1" %)(% colspan="1" %) 50 -((( 51 -6.00 Beta 4 52 -)))|(% colspan="1" %)(% colspan="1" %) 53 -((( 54 -Changed conditions for **<event_player_travelmode_started> <event_player_travelmode_stopped> <event_player_travelmode_charge_started> <event_player_travelmode_charge_aborted>** to be raised. 55 -))) 56 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 57 -((( 58 -//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. // 59 - 60 -//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.// 61 -))) 62 -|(% colspan="1" %)(% colspan="1" %) 63 -((( 64 -Scripts 65 -)))|(% colspan="1" %)(% colspan="1" %) 66 -((( 67 -6.00 Beta 3 68 -)))|(% colspan="1" %)(% colspan="1" %) 69 -((( 70 -Changed result of **<find_object_surface>** action in the case of a failure 71 -))) 72 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 73 -((( 74 -//The 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.// 75 - 76 -//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.// 77 - 78 -//The action itself has been improved to increase the chance of finding suitable surface positions.// 79 -))) 80 -|(% colspan="1" %)(% colspan="1" %) 81 -((( 82 -Scripts 83 -)))|(% colspan="1" %)(% colspan="1" %) 84 -((( 85 -6.00 Beta 1 86 -)))|(% colspan="1" %)(% colspan="1" %) 87 -((( 88 -Behaviour change for **<match_dock>** script component filter 89 -))) 90 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 91 -((( 92 -//<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes. 93 -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.// 94 -))) 95 -|(% colspan="1" %)(% colspan="1" %) 96 -((( 97 -Scripts 98 -)))|(% colspan="1" %)(% colspan="1" %) 99 -((( 100 -6.00 Beta 1 101 -)))|(% colspan="1" %)(% colspan="1" %) 102 -((( 103 -Changed result attribute location for **<get_attackstrength>** 104 -))) 105 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 106 -((( 107 -//The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.// 108 -))) 109 -|((( 110 -Assets 111 -)))|((( 112 -6.00 Beta 1 113 -)))|((( 114 -Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons 115 -))) 116 -|(% class="highlight-#f4f5f7" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% class="highlight-#f4f5f7" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %) 117 -((( 118 -//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. 119 -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.// 120 -))) 121 -|(% colspan="1" %)(% colspan="1" %) 122 -((( 123 -Scripts 124 -)))|(% colspan="1" %)(% colspan="1" %) 125 -((( 126 -6.00 Beta 1 127 -)))|(% colspan="1" %)(% colspan="1" %) 128 -((( 129 -Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects 130 -))) 131 -|(% class="highlight-#f4f5f7" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% class="highlight-#f4f5f7" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %) 132 -((( 133 -//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.// 134 -))) 135 -|((( 136 -Scripts 137 -)))|((( 138 -6.00 Beta 1 139 -)))|((( 140 -**<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards. 141 -))) 142 -|(% class="highlight-#f4f5f7" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% class="highlight-#f4f5f7" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %) 143 -((( 144 -//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.// 145 -))) 146 -|((( 147 -Cutscenes 148 -)))|((( 149 -6.00 Beta 1 150 -)))|((( 151 -Changed behaviour of **<angles>** in cutscenes 152 -))) 153 -|(% class="highlight-#f4f5f7" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% class="highlight-#f4f5f7" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %) 154 -((( 155 -//The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.// 156 -))) 157 -|(% colspan="3" %)(% colspan="3" %) 158 -((( 159 -== 5.00 == 160 -))) 161 -|((( 162 -Parameters 163 -)))|((( 164 -5.00 Beta 1 165 -)))|((( 166 -**<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration 167 -))) 168 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 169 -((( 170 -//'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.// 171 -))) 172 -|(% colspan="3" %)(% colspan="3" %) 173 -((( 174 -== 4.10 == 175 -))) 176 -|(% colspan="1" %)(% colspan="1" %) 177 -((( 178 -UI extensions 179 -)))|(% colspan="1" %)(% colspan="1" %) 180 -((( 181 -4.10 Beta 7 182 -)))|(% colspan="1" %)(% colspan="1" %) 183 -((( 184 -**FFI**: (% style="color:#000000" %)SetMapRenderCargoContents(%%)(), (% style="color:#000000" %)SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos()(%%) deprecated 185 -))) 186 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 187 -((( 188 -//The functionality represented by (% style="color:#000000" %)SetMapRenderCargoContents(%%)(), (% style="color:#000000" %)SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos()(%%) has been removed and the function was therefore stubbed.// 189 -))) 190 -|(% colspan="1" %)(% colspan="1" %) 191 -((( 192 -UI extensions 193 -)))|(% colspan="1" %)(% colspan="1" %) 194 -((( 195 -4.10 Beta 6 196 -)))|(% colspan="1" %)(% colspan="1" %) 197 -((( 198 -**FFI**: CustomGameStartPlayerProperty2 changed 199 -))) 200 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 201 -((( 202 -//This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.// 203 -))) 204 -|(% colspan="1" %)(% colspan="1" %) 205 -((( 206 -Parameters 207 -)))|(% colspan="1" %)(% colspan="1" %) 208 -((( 209 -4.10 Beta 3 210 -)))|(% colspan="1" %)(% colspan="1" %) 211 -((( 212 -Renamed **<stationinfobox>** to **<infobox>** 213 -))) 214 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 215 -((( 216 -//Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.// 217 -))) 218 -|(% colspan="1" %)(% colspan="1" %) 219 -((( 220 -UI extensions 221 -)))|(% colspan="1" %)(% colspan="1" %) 222 -((( 223 -4.10 Beta 2 224 -)))|(% colspan="1" %)(% colspan="1" %) 225 -((( 226 -**FFI**: SetMacroMapPlayerSectorOffset() deprecated 227 -))) 228 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 229 -((( 230 -//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.// 231 -))) 232 -|((( 233 -UI extensions 234 -)))|((( 235 -4.10 Beta 2 236 -)))|((( 237 -**FFI**: (% style="color:#000000" %)FilterComponentForMapMode(%%)() and (% style="color:#000000" %)SetMapObjectFilter() changed 238 -))) 239 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 240 -((( 241 -//These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.// 242 -))) 243 -|((( 244 -Scripts 245 -)))|((( 246 -4.10 Beta 1 247 -)))|((( 248 -People related attributes of mission** <delivery> **node moved 249 -))) 250 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 251 -((( 252 -//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.// 253 -))) 254 -|(% colspan="1" %)(% colspan="1" %) 255 -((( 256 -Scripts 257 -)))|(% colspan="1" %)(% colspan="1" %) 258 -((( 259 -4.10 Beta 1 260 -)))|(% colspan="1" %)(% colspan="1" %) 261 -((( 262 -**$destructible.productions** replaced with $defensible.productions 263 -))) 264 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 265 -((( 266 -//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.// 267 -))) 268 -|((( 269 -Scripts 270 -)))|((( 271 -4.10 Beta 1 272 -)))|((( 273 -Removed script property **$object.spawnsourceseed** 274 -))) 275 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 276 -((( 277 -//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.// 278 -))) 279 -|(% colspan="3" %)(% colspan="3" %) 280 -((( 281 281 == 4.00 == 282 282 ))) 283 283 |(% colspan="1" %)(% colspan="1" %) ... ... @@ -285,62 +285,22 @@ 285 285 UI core 286 286 )))|(% colspan="1" %)(% colspan="1" %) 287 287 ((( 288 -4.00 Beta 1040 +4.00 Beta 5 289 289 )))|(% colspan="1" %)(% colspan="1" %) 290 290 ((( 291 -Controlled ship can change without a **gameplanchange-event** occurring. 292 -))) 293 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 294 -((( 295 -//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). 296 -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.// 297 -))) 298 -|((( 299 -Scripts 300 -)))|((( 301 -4.00 Beta 7 302 -)))|((( 303 -Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed 304 -))) 305 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 306 -((( 307 -//Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects? 308 -New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits 309 -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// 310 -))) 311 -|(% colspan="1" %)(% colspan="1" %) 312 -((( 313 -UI core 43 +**FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed 314 314 )))|(% colspan="1" %)(% colspan="1" %) 315 315 ((( 316 -4.00 Beta 6 317 -)))|(% colspan="1" %)(% colspan="1" %) 318 -((( 319 -**FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed 46 + 320 320 ))) 321 321 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 322 322 ((( 323 -//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. 324 -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).// 325 - 326 -//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.// 327 -))) 328 -|(% colspan="1" %)(% colspan="1" %) 329 -((( 330 -UI core 50 +//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. 51 +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). 331 331 )))|(% colspan="1" %)(% colspan="1" %) 332 332 ((( 333 -4.00 Beta 5 334 -)))|(% colspan="1" %)(% colspan="1" %) 335 -((( 336 -**FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed 54 + 337 337 ))) 338 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 339 -((( 340 -//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.// 341 - 342 -//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). 343 -))) 344 344 |((( 345 345 Parameters 346 346 )))|((( ... ... @@ -347,8 +347,10 @@ 347 347 4.00 Beta 1 348 348 )))|((( 349 349 **requiresconstructionvessel** parameter moved 62 +)))|((( 63 + 350 350 ))) 351 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)65 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 352 352 ((( 353 353 //The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.// 354 354 ))) ... ... @@ -358,12 +358,17 @@ 358 358 4.00 Beta 1 359 359 )))|((( 360 360 Changed behaviour of **gatedistance** script property 75 +)))|((( 76 + 361 361 ))) 362 362 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 363 363 ((( 364 364 //The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.// 81 +)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %) 82 +((( 83 + 365 365 ))) 366 -|(% colspan=" 3" %)(% colspan="3" %)85 +|(% colspan="4" %)(% colspan="4" %) 367 367 ((( 368 368 == 3.30 == 369 369 ))) ... ... @@ -372,13 +372,16 @@ 372 372 )))|((( 373 373 3.30 Beta 3 374 374 )))|((( 375 -**FFI: **Removed** (% style="color:#000000" %)GetMissionLimit() (%%)**(% style="color:#000000" %)and** IsMissionLimit**(%%)**Enabled()** 94 +**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()** 95 +)))|(% colspan="1" %)(% colspan="1" %) 96 +((( 97 + 376 376 ))) 377 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)99 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 378 378 ((( 379 -//These mission limit-related functions (added in 3.30 Beta 1 and 2) are replaced with FFI (% style="color: #000000" %)IsMissionLimit(%%)Reach(% style="color:#000000" %)ed()//101 +//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()// 380 380 ))) 381 -|(% colspan=" 3" %)(% colspan="3" %)103 +|(% colspan="4" %)(% colspan="4" %) 382 382 ((( 383 383 == 3.20 == 384 384 ))) ... ... @@ -388,8 +388,11 @@ 388 388 3.20 Beta 1 389 389 )))|((( 390 390 Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed 113 +)))|(% colspan="1" %)(% colspan="1" %) 114 +((( 115 + 391 391 ))) 392 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)117 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 393 393 ((( 394 394 //Old params: param = attacked object, param2 = attack method, param3 = attacked component// 395 395 //New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon] ... ... @@ -404,8 +404,11 @@ 404 404 )))|(% colspan="1" %)(% colspan="1" %) 405 405 ((( 406 406 Removed script property $trade.**restriction.faction** 132 +)))|(% colspan="1" %)(% colspan="1" %) 133 +((( 134 + 407 407 ))) 408 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)136 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 409 409 ((( 410 410 //$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.// 411 411 ))) ... ... @@ -415,12 +415,15 @@ 415 415 3.20 Beta 1 416 416 )))|((( 417 417 **Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete! 146 +)))|(% colspan="1" %)(% colspan="1" %) 147 +((( 148 + 418 418 ))) 419 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)150 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 420 420 ((( 421 421 //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.// 422 422 ))) 423 -|(% colspan=" 3" %)(% colspan="3" %)154 +|(% colspan="4" %)(% colspan="4" %) 424 424 ((( 425 425 == 3.10 == 426 426 ))) ... ... @@ -433,12 +433,15 @@ 433 433 )))|(% colspan="1" %)(% colspan="1" %) 434 434 ((( 435 435 Removed script action **<add_build/>** 167 +)))|(% colspan="1" %)(% colspan="1" %) 168 +((( 169 + 436 436 ))) 437 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)171 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 438 438 ((( 439 439 //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.// 440 440 ))) 441 -|(% colspan=" 3" %)(% colspan="3" %)175 +|(% colspan="4" %)(% colspan="4" %) 442 442 ((( 443 443 == 3.00 == 444 444 ))) ... ... @@ -451,8 +451,11 @@ 451 451 )))|(% colspan="1" %)(% colspan="1" %) 452 452 ((( 453 453 Changed behaviour of script action **<get_suitable_job/>** 188 +)))|(% colspan="1" %)(% colspan="1" %) 189 +((( 190 + 454 454 ))) 455 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)192 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 456 456 ((( 457 457 //<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.// 458 458 ))) ... ... @@ -465,8 +465,11 @@ 465 465 )))|(% colspan="1" %)(% colspan="1" %) 466 466 ((( 467 467 Changed behaviour of script action **<get_ware_definition/>** 205 +)))|(% colspan="1" %)(% colspan="1" %) 206 +((( 207 + 468 468 ))) 469 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)209 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 470 470 ((( 471 471 //<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.// 472 472 ))) ... ... @@ -479,10 +479,13 @@ 479 479 )))|(% colspan="1" %)(% colspan="1" %) 480 480 ((( 481 481 Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case 222 +)))|(% colspan="1" %)(% colspan="1" %) 223 +((( 224 + 482 482 ))) 483 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)226 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 484 484 ((( 485 -//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.) 228 +//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.)\\ 486 486 487 487 //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).// 488 488 ))) ... ... @@ -495,8 +495,11 @@ 495 495 )))|(% colspan="1" %)(% colspan="1" %) 496 496 ((( 497 497 Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions> 241 +)))|(% colspan="1" %)(% colspan="1" %) 242 +((( 243 + 498 498 ))) 499 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)245 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 500 500 ((( 501 501 //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.// 502 502 ))) ... ... @@ -509,8 +509,11 @@ 509 509 )))|(% colspan="1" %)(% colspan="1" %) 510 510 ((( 511 511 Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos** 258 +)))|(% colspan="1" %)(% colspan="1" %) 259 +((( 260 + 512 512 ))) 513 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)262 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 514 514 ((( 515 515 //Before the change, positions are relative to $dockingbay.parent. 516 516 After the change, positions are relative to $dockingbay as specified in the documentation.// ... ... @@ -524,8 +524,11 @@ 524 524 )))|(% colspan="1" %)(% colspan="1" %) 525 525 ((( 526 526 Support for entity flag "**skillsvisible**" dropped 276 +)))|(% colspan="1" %)(% colspan="1" %) 277 +((( 278 + 527 527 ))) 528 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)280 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 529 529 ((( 530 530 //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().// 531 531 ))) ... ... @@ -535,8 +535,11 @@ 535 535 3.0 Beta 2 536 536 )))|((( 537 537 Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**. 290 +)))|(% colspan="1" %)(% colspan="1" %) 291 +((( 292 + 538 538 ))) 539 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)294 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 540 540 ((( 541 541 //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. 542 542 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. ... ... @@ -552,8 +552,11 @@ 552 552 )))|(% colspan="1" %)(% colspan="1" %) 553 553 ((( 554 554 **MissionBoard** support dropped 310 +)))|(% colspan="1" %)(% colspan="1" %) 311 +((( 312 + 555 555 ))) 556 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)314 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 557 557 ((( 558 558 //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.// 559 559 ))) ... ... @@ -563,8 +563,11 @@ 563 563 3.0 Beta 1 564 564 )))|((( 565 565 By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined 324 +)))|(% colspan="1" %)(% colspan="1" %) 325 +((( 326 + 566 566 ))) 567 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)328 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 568 568 ((( 569 569 //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.// 570 570 ))) ... ... @@ -577,8 +577,11 @@ 577 577 )))|(% colspan="1" %)(% colspan="1" %) 578 578 ((( 579 579 Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'** 341 +)))|(% colspan="1" %)(% colspan="1" %) 342 +((( 343 + 580 580 ))) 581 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)345 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 582 582 ((( 583 583 //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.// 584 584 ))) ... ... @@ -591,8 +591,11 @@ 591 591 )))|(% colspan="1" %)(% colspan="1" %) 592 592 ((( 593 593 Script action **<set_doors_locked/>** attribute **'group'** changed 358 +)))|(% colspan="1" %)(% colspan="1" %) 359 +((( 360 + 594 594 ))) 595 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)362 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 596 596 ((( 597 597 //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.// 598 598 ))) ... ... @@ -605,8 +605,11 @@ 605 605 )))|(% colspan="1" %)(% colspan="1" %) 606 606 ((( 607 607 Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed 375 +)))|(% colspan="1" %)(% colspan="1" %) 376 +((( 377 + 608 608 ))) 609 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)379 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 610 610 ((( 611 611 //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.// 612 612 ))) ... ... @@ -619,8 +619,11 @@ 619 619 )))|(% colspan="1" %)(% colspan="1" %) 620 620 ((( 621 621 Script actions **<set_hack_target/>** and **<abort_hack/>** removed 392 +)))|(% colspan="1" %)(% colspan="1" %) 393 +((( 394 + 622 622 ))) 623 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)396 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 624 624 ((( 625 625 //These actions had no effect and were removed.// 626 626 ))) ... ... @@ -633,8 +633,11 @@ 633 633 )))|(% colspan="1" %)(% colspan="1" %) 634 634 ((( 635 635 **<setup_conversation_minigame/>** script action removed 409 +)))|(% colspan="1" %)(% colspan="1" %) 410 +((( 411 + 636 636 ))) 637 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)413 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 638 638 ((( 639 639 //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.// 640 640 ))) ... ... @@ -647,8 +647,11 @@ 647 647 )))|(% colspan="1" %)(% colspan="1" %) 648 648 ((( 649 649 <add_player_choice_*> **confidence** attribute removed 426 +)))|(% colspan="1" %)(% colspan="1" %) 427 +((( 428 + 650 650 ))) 651 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)430 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 652 652 ((( 653 653 //The default confidence of player options is another leftover from the XR era and had no effect in X4.// 654 654 ))) ... ... @@ -661,8 +661,11 @@ 661 661 )))|(% colspan="1" %)(% colspan="1" %) 662 662 ((( 663 663 **<hack_via_control_panel/>** script action removed 443 +)))|(% colspan="1" %)(% colspan="1" %) 444 +((( 445 + 664 664 ))) 665 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)447 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 666 666 ((( 667 667 //Unused script action <hack_via_control_panel/> was removed.// 668 668 ))) ... ... @@ -675,8 +675,11 @@ 675 675 )))|(% colspan="1" %)(% colspan="1" %) 676 676 ((( 677 677 **Lua: **GetMiniGameCursorPosition() removed 460 +)))|(% colspan="1" %)(% colspan="1" %) 461 +((( 462 + 678 678 ))) 679 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)464 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 680 680 ((( 681 681 //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.// 682 682 ))) ... ... @@ -686,8 +686,11 @@ 686 686 3.0 Beta 1 687 687 )))|((( 688 688 **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders 474 +)))|(% colspan="1" %)(% colspan="1" %) 475 +((( 476 + 689 689 ))) 690 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)478 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" 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,8 +700,11 @@ 700 700 )))|(% colspan="1" %)(% colspan="1" %) 701 701 ((( 702 702 **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor 491 +)))|(% colspan="1" %)(% colspan="1" %) 492 +((( 493 + 703 703 ))) 704 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)495 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 705 705 ((( 706 706 //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.// 707 707 ))) ... ... @@ -714,8 +714,11 @@ 714 714 )))|(% colspan="1" %)(% colspan="1" %) 715 715 ((( 716 716 **$ware.illegal** updated 508 +)))|(% colspan="1" %)(% colspan="1" %) 509 +((( 510 + 717 717 ))) 718 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)512 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 719 719 ((( 720 720 //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.// 721 721 //It now returns true if $ware is illegal to any faction in the game.// ... ... @@ -729,8 +729,11 @@ 729 729 )))|(% colspan="1" %)(% colspan="1" %) 730 730 ((( 731 731 MD script **RML_Flight_Along_Path** removed 526 +)))|(% colspan="1" %)(% colspan="1" %) 527 +((( 528 + 732 732 ))) 733 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)530 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 734 734 ((( 735 735 //The MD script RML_Flight_Along_Path was not referened and was removed.// 736 736 ))) ... ... @@ -743,8 +743,11 @@ 743 743 )))|(% colspan="1" %)(% colspan="1" %) 744 744 ((( 745 745 parameters of **<event_venture_mission_completed/>** changed 543 +)))|(% colspan="1" %)(% colspan="1" %) 544 +((( 545 + 746 746 ))) 747 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)547 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 748 748 ((( 749 749 //old params: param = venture details, param2 = ships involved, param3 = duration// 750 750 //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration// ... ... @@ -756,8 +756,11 @@ 756 756 )))|((( 757 757 **<set_object_wing_name/>** removed, 758 758 **<set_object_fleet_name/>** added 559 +)))|(% colspan="1" %)(% colspan="1" %) 560 +((( 561 + 759 759 ))) 760 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)563 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 761 761 ((( 762 762 //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>// 763 763 ))) ... ... @@ -768,12 +768,15 @@ 768 768 )))|((( 769 769 **$controllable.wing.*** removed, 770 770 **$controllable.fleet.*** added 574 +)))|(% colspan="1" %)(% colspan="1" %) 575 +((( 576 + 771 771 ))) 772 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)578 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 773 773 ((( 774 774 $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander 775 775 ))) 776 -|(% colspan=" 3" %)(% colspan="3" %)582 +|(% colspan="4" %)(% colspan="4" %) 777 777 ((( 778 778 == 2.60 == 779 779 ))) ... ... @@ -783,8 +783,11 @@ 783 783 2.60 Beta 1 784 784 )))|((( 785 785 '**checkoperational**' filter behaviour changed 592 +)))|(% colspan="1" %)(% colspan="1" %) 593 +((( 594 + 786 786 ))) 787 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)596 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 788 788 ((( 789 789 //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.// 790 790 ... ... @@ -796,12 +796,15 @@ 796 796 2.60 Beta 1 797 797 )))|((( 798 798 $container.**supplyresources** behavior changed 608 +)))|(% colspan="1" %)(% colspan="1" %) 609 +((( 610 + 799 799 ))) 800 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)612 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 801 801 ((( 802 802 //The script keyword $container.supplyresources now includes reserved wares.// 803 803 ))) 804 -|(% colspan=" 3" %)(% colspan="3" %)616 +|(% colspan="4" %)(% colspan="4" %) 805 805 ((( 806 806 == 2.20 == 807 807 ))) ... ... @@ -814,13 +814,17 @@ 814 814 )))|(% colspan="1" %)(% colspan="1" %) 815 815 ((( 816 816 **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined. 629 +)))|(% colspan="1" %)(% colspan="1" %) 630 +((( 631 + 817 817 ))) 818 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)633 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 819 819 ((( 820 820 //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. 821 821 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.// 822 822 823 -//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.// 638 +//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. 639 +// 824 824 ))) 825 825 |(% colspan="1" %)(% colspan="1" %) 826 826 ((( ... ... @@ -831,12 +831,15 @@ 831 831 )))|(% colspan="1" %)(% colspan="1" %) 832 832 ((( 833 833 Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor' 650 +)))|(% colspan="1" %)(% colspan="1" %) 651 +((( 652 + 834 834 ))) 835 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)654 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 836 836 ((( 837 837 //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.// 838 838 ))) 839 -|(% colspan=" 3" %)(% colspan="3" %)658 +|(% colspan="4" %)(% colspan="4" %) 840 840 ((( 841 841 == 2.00 == 842 842 ))) ... ... @@ -849,8 +849,11 @@ 849 849 )))|(% colspan="1" %)(% colspan="1" %) 850 850 ((( 851 851 **<event_build_finished/> **param2 now returns null instead of a construction sequence 671 +)))|(% colspan="1" %)(% colspan="1" %) 672 +((( 673 + 852 852 ))) 853 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)675 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 854 854 ((( 855 855 //The construction sequence which was finished should now be accessed via the buildtask provided via param3.// 856 856 ))) ... ... @@ -863,8 +863,11 @@ 863 863 )))|(% colspan="1" %)(% colspan="1" %) 864 864 ((( 865 865 **param.boarding.{...}** strength parameters removed 688 +)))|(% colspan="1" %)(% colspan="1" %) 689 +((( 690 + 866 866 ))) 867 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)692 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 868 868 ((( 869 869 //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.// 870 870 ))) ... ... @@ -877,8 +877,11 @@ 877 877 )))|(% colspan="1" %)(% colspan="1" %) 878 878 ((( 879 879 **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed 705 +)))|(% colspan="1" %)(% colspan="1" %) 706 +((( 707 + 880 880 ))) 881 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)709 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 882 882 ((( 883 883 //Due to changes to boarding in X4, the boarding connections accessed by these script properties and actions became redundent and thus, removed. Any connections set by these actions in a savegame will not survive loading.// 884 884 ))) ... ... @@ -888,8 +888,11 @@ 888 888 2.00 Beta 1 889 889 )))|((( 890 890 **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals 719 +)))|(% colspan="1" %)(% colspan="1" %) 720 +((( 721 + 891 891 ))) 892 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)723 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 893 893 ((( 894 894 //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.// 895 895 ))) ... ... @@ -899,8 +899,11 @@ 899 899 2.00 Beta 1 900 900 )))|((( 901 901 **FFI: SetFormationShape()** no longer indicates an error upon certain error cases 733 +)))|(% colspan="1" %)(% colspan="1" %) 734 +((( 735 + 902 902 ))) 903 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)737 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 904 904 ((( 905 905 //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.// 906 906 //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.// ... ... @@ -911,8 +911,11 @@ 911 911 2.00 Beta 1 912 912 )))|((( 913 913 **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated. 748 +)))|(% colspan="1" %)(% colspan="1" %) 749 +((( 750 + 914 914 ))) 915 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)752 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 916 916 ((( 917 917 //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.// 918 918 ))) ... ... @@ -922,8 +922,11 @@ 922 922 2.00 Beta 1 923 923 )))|((( 924 924 **<event_player_changed_target/>** now fires and returns null if the player deselects a target. 762 +)))|(% colspan="1" %)(% colspan="1" %) 763 +((( 764 + 925 925 ))) 926 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)766 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 927 927 ((( 928 928 //For prior behavior, check for event.param being non-null.// 929 929 ))) ... ... @@ -933,8 +933,11 @@ 933 933 2.00 Beta 1 934 934 )))|((( 935 935 **<shoot/>/<shoot_at/>** attribute changes. 776 +)))|(% colspan="1" %)(% colspan="1" %) 777 +((( 778 + 936 936 ))) 937 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)780 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 938 938 ((( 939 939 //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.// 940 940 //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.// ... ... @@ -947,9 +947,12 @@ 947 947 )))|((( 948 948 2.00 Beta 1 949 949 )))|((( 950 -**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter. 793 +**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% class="confluenceTd" %) 794 +)))|(% colspan="1" %)(% colspan="1" %) 795 +((( 796 + 951 951 ))) 952 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)798 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 953 953 ((( 954 954 //Added possibility to query build tasks of a certain buildmodule.// 955 955 ))) ... ... @@ -959,8 +959,11 @@ 959 959 2.00 Beta 1 960 960 )))|((( 961 961 **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field. 808 +)))|(% colspan="1" %)(% colspan="1" %) 809 +((( 810 + 962 962 ))) 963 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)812 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 964 964 ((( 965 965 //Added list of resources a buildmodule needs to build.// 966 966 ))) ... ... @@ -969,9 +969,12 @@ 969 969 )))|((( 970 970 2.00 Beta 1 971 971 )))|((( 972 -(% style="color:#000000" %)**Lua: CalculateTotalHullFraction() **(%%)was removed.(% style="color:#000000" %) 821 +(% 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);" %) 822 +)))|(% colspan="1" %)(% colspan="1" %) 823 +((( 824 + 973 973 ))) 974 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)826 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 975 975 ((( 976 976 //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.// 977 977 ))) ... ... @@ -980,13 +980,16 @@ 980 980 )))|((( 981 981 2.00 Beta 1 982 982 )))|((( 983 -**FFI: (% style="color:#000000" %)RequestDockAtReason()/UndockPlayerShip()(%%) **changed their return values. 835 +**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" %) 836 +)))|(% colspan="1" %)(% colspan="1" %) 837 +((( 838 + 984 984 ))) 985 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)840 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 986 986 ((( 987 987 //Changed return value type to const char* to better identify failure reasons in Lua script.// 988 988 ))) 989 -|(% colspan=" 3" %)(% colspan="3" %)844 +|(% colspan="4" %)(% colspan="4" %) 990 990 ((( 991 991 == 1.50 == 992 992 ))) ... ... @@ -995,9 +995,12 @@ 995 995 )))|((( 996 996 1.50 Beta 3 997 997 )))|((( 998 -**Lua: GetComponentData() **changed behavior of "docksizes" property. 853 +**Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %) 854 +)))|(% colspan="1" %)(% colspan="1" %) 855 +((( 856 + 999 999 ))) 1000 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)858 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 1001 1001 ((( 1002 1002 //The "docksizes" property no longer includes internal ship storage docks.// 1003 1003 ))) ... ... @@ -1007,8 +1007,11 @@ 1007 1007 1.50 Beta 2 1008 1008 )))|((( 1009 1009 **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR). 868 +)))|(% colspan="1" %)(% colspan="1" %) 869 +((( 870 + 1010 1010 ))) 1011 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)872 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 1012 1012 ((( 1013 1013 //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".// 1014 1014 ... ... @@ -1021,9 +1021,12 @@ 1021 1021 )))|((( 1022 1022 1.50 Beta 2 1023 1023 )))|((( 1024 -**FFI: UpgradeGroupInfo **datatype was changed. 885 +**FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %) 886 +)))|(% colspan="1" %)(% colspan="1" %) 887 +((( 888 + 1025 1025 ))) 1026 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)890 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 1027 1027 ((( 1028 1028 //Added new "operational" field to retrieve information about number of operational upgrades in a group.// 1029 1029 ))) ... ... @@ -1036,10 +1036,14 @@ 1036 1036 )))|(% colspan="1" %)(% colspan="1" %) 1037 1037 ((( 1038 1038 **FFI: SetGuidance()** removed useinfopoint argument. 903 +)))|(% colspan="1" %)(% colspan="1" %) 904 +((( 905 + 1039 1039 ))) 1040 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)907 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 1041 1041 ((( 1042 -//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.// 909 +//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. 910 +// 1043 1043 1044 1044 //The new function declaration is: void SetGuidance(UniverseID componentid, UIPosRot offset)// 1045 1045 ))) ... ... @@ -1048,13 +1048,16 @@ 1048 1048 )))|((( 1049 1049 1.50 Beta 1 1050 1050 )))|((( 1051 -**FFI: CancelConstruction() **changed its return value. 919 +**FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %) 920 +)))|(% colspan="1" %)(% colspan="1" %) 921 +((( 922 + 1052 1052 ))) 1053 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)924 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 1054 1054 ((( 1055 -(% style="color: #000000" %)//CancelConstruction() now returns if the cancellation was successful. //926 +(% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. // 1056 1056 ))) 1057 -|(% colspan=" 3" %)(% colspan="3" %)928 +|(% colspan="4" %)(% colspan="4" %) 1058 1058 ((( 1059 1059 == 1.32 == 1060 1060 ))) ... ... @@ -1064,12 +1064,15 @@ 1064 1064 1.32 1065 1065 )))|((( 1066 1066 **Lua: GetComponentData() **removed the "nextdestname" property. 938 +)))|(% colspan="1" %)(% colspan="1" %) 939 +((( 940 + 1067 1067 ))) 1068 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)942 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 1069 1069 ((( 1070 1070 //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.// 1071 1071 ))) 1072 -|(% colspan=" 3" %)(% colspan="3" %)946 +|(% colspan="4" %)(% colspan="4" %) 1073 1073 ((( 1074 1074 == 1.20 == 1075 1075 ))) ... ... @@ -1078,9 +1078,12 @@ 1078 1078 )))|((( 1079 1079 1.20 1080 1080 )))|((( 1081 -**FFI: GetAAOption()** got a new "useconfig" parameter. 955 +**FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %) 956 +)))|(% colspan="1" %)(% colspan="1" %) 957 +((( 958 + 1082 1082 ))) 1083 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)960 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 1084 1084 ((( 1085 -//The AA setting was changed to check the new setting with the user. In order to restore the old setting (% style="color: #000000" %)GetAAOption() gets the option to retrieve the config settings.//962 +//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.// 1086 1086 )))
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 - 785778541 +101548080 - 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/101548080/Breaking Changes