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