Changes for page Breaking Changes
Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 92.1
edited by matthias
on 2021/06/30 12:44
on 2021/06/30 12:44
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. matthias1 +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,87 +18,253 @@ 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.10==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 - Parameters65 +Scripts 38 38 )))|(% colspan="1" %)(% colspan="1" %) 39 39 ((( 40 -4.10 Beta 3 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 -Renamed **<stationinfobox>** to **<infobox>** 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 -Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that. 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 51 51 )))|(% colspan="1" %)(% colspan="1" %) 52 52 ((( 53 - 117 +6.00 Beta 1 118 +)))|(% colspan="2" %)(% colspan="1" %) 119 +((( 120 +Changed result attribute location for **<get_attackstrength>** 54 54 ))) 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 +))) 126 +|((( 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 +))) 55 55 |(% colspan="1" %)(% colspan="1" %) 56 56 ((( 140 +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 154 +)))|((( 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 165 +)))|((( 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 180 +)))|((( 181 +5.00 Beta 1 182 +)))|(% colspan="2" %)((( 183 +**<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration 184 +))) 185 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 186 +((( 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 +((( 57 57 UI extensions 58 58 )))|(% colspan="1" %)(% colspan="1" %) 59 59 ((( 60 -4.10 Beta 2 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 61 61 )))|(% colspan="1" %)(% colspan="1" %) 62 62 ((( 63 -**FFI**: SetMacroMapPlayerSectorOffset() deprecated 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 64 64 )))|(% colspan="1" %)(% colspan="1" %) 65 65 ((( 66 - 226 +4.10 Beta 3 227 +)))|(% colspan="2" %)(% colspan="1" %) 228 +((( 229 +Renamed **<stationinfobox>** to **<infobox>** 67 67 ))) 68 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)231 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 69 69 ((( 70 -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. 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 71 71 )))|(% colspan="1" %)(% colspan="1" %) 72 72 ((( 73 - 240 +4.10 Beta 2 241 +)))|(% colspan="2" %)(% colspan="1" %) 242 +((( 243 +**FFI**: SetMacroMapPlayerSectorOffset() deprecated 74 74 ))) 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 +))) 75 75 |((( 76 76 UI extensions 77 77 )))|((( 78 78 4.10 Beta 2 79 -)))|((( 80 -**FFI**: (% style="color: rgb(0,0,0);" %)FilterComponentForMapMode(%%)() and (% style="color: rgb(0,0,0);" %)SetMapObjectFilter() changed 81 -)))|(% colspan="1" %)(% colspan="1" %) 82 -((( 83 - 253 +)))|(% colspan="2" %)((( 254 +**FFI**: FilterComponentForMapMode() and SetMapObjectFilter() changed 84 84 ))) 85 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)256 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 86 86 ((( 87 87 //These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.// 88 -)))|(% colspan="1" %)(% colspan="1" %) 89 -((( 90 - 91 91 ))) 92 92 |((( 93 93 Scripts 94 94 )))|((( 95 95 4.10 Beta 1 96 -)))|((( 97 -People related attributes of mission** <delivery> **node moved 98 -)))|((( 99 - 264 +)))|(% colspan="2" %)((( 265 +People related attributes of mission** <delivery> **node moved 100 100 ))) 101 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)267 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 102 102 ((( 103 103 //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.// 104 104 ))) ... ... @@ -108,34 +108,26 @@ 108 108 )))|(% colspan="1" %)(% colspan="1" %) 109 109 ((( 110 110 4.10 Beta 1 111 -)))|(% colspan=" 1" %)(% colspan="1" %)277 +)))|(% colspan="2" %)(% colspan="1" %) 112 112 ((( 113 113 **$destructible.productions** replaced with $defensible.productions 114 -)))|(% colspan="1" %)(% colspan="1" %) 115 -((( 116 - 117 117 ))) 118 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)281 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 119 119 ((( 120 120 //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.// 121 -)))|(% colspan="1" %)(% colspan="1" %) 122 -((( 123 - 124 124 ))) 125 125 |((( 126 126 Scripts 127 127 )))|((( 128 128 4.10 Beta 1 129 -)))|((( 289 +)))|(% colspan="2" %)((( 130 130 Removed script property **$object.spawnsourceseed** 131 -)))|((( 132 - 133 133 ))) 134 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)292 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 135 135 ((( 136 136 //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.// 137 137 ))) 138 -|(% colspan="4" %)(% colspan=" 4" %)296 +|(% colspan="4" %)(% colspan="3" %) 139 139 ((( 140 140 == 4.00 == 141 141 ))) ... ... @@ -145,39 +145,27 @@ 145 145 )))|(% colspan="1" %)(% colspan="1" %) 146 146 ((( 147 147 4.00 Beta 10 148 -)))|(% colspan=" 1" %)(% colspan="1" %)306 +)))|(% colspan="2" %)(% colspan="1" %) 149 149 ((( 150 150 Controlled ship can change without a **gameplanchange-event** occurring. 151 -)))|(% colspan="1" %)(% colspan="1" %) 152 -((( 153 - 154 154 ))) 155 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)310 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 156 156 ((( 157 157 //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). 158 -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. 159 -// 160 -)))|(% colspan="1" %)(% colspan="1" %) 161 -((( 162 - 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.// 163 163 ))) 164 164 |((( 165 165 Scripts 166 166 )))|((( 167 167 4.00 Beta 7 168 -)))|((( 319 +)))|(% colspan="2" %)((( 169 169 Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed 170 -)))|((( 171 - 172 172 ))) 173 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)322 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 174 174 ((( 175 175 //Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects? 176 176 New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits 177 177 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// 178 -)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %) 179 -((( 180 - 181 181 ))) 182 182 |(% colspan="1" %)(% colspan="1" %) 183 183 ((( ... ... @@ -185,23 +185,16 @@ 185 185 )))|(% colspan="1" %)(% colspan="1" %) 186 186 ((( 187 187 4.00 Beta 6 188 -)))|(% colspan=" 1" %)(% colspan="1" %)334 +)))|(% colspan="2" %)(% colspan="1" %) 189 189 ((( 190 190 **FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed 191 -)))|(% colspan="1" %)(% colspan="1" %) 192 -((( 193 - 194 194 ))) 195 -|(% 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" %) 196 196 ((( 197 197 //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. 198 198 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).// 199 199 200 -//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead. 201 -// 202 -)))|(% colspan="1" %)(% colspan="1" %) 203 -((( 204 - 343 +//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.// 205 205 ))) 206 206 |(% colspan="1" %)(% colspan="1" %) 207 207 ((( ... ... @@ -209,32 +209,24 @@ 209 209 )))|(% colspan="1" %)(% colspan="1" %) 210 210 ((( 211 211 4.00 Beta 5 212 -)))|(% colspan=" 1" %)(% colspan="1" %)351 +)))|(% colspan="2" %)(% colspan="1" %) 213 213 ((( 214 214 **FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed 215 -)))|(% colspan="1" %)(% colspan="1" %) 216 -((( 217 - 218 218 ))) 219 -|(% 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" %) 220 220 ((( 221 221 //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.// 222 222 223 223 //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). 224 -)))|(% colspan="1" %)(% colspan="1" %) 225 -((( 226 - 227 227 ))) 228 228 |((( 229 229 Parameters 230 230 )))|((( 231 231 4.00 Beta 1 232 -)))|((( 365 +)))|(% colspan="2" %)((( 233 233 **requiresconstructionvessel** parameter moved 234 -)))|((( 235 - 236 236 ))) 237 -|(% 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" %) 238 238 ((( 239 239 //The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.// 240 240 ))) ... ... @@ -242,19 +242,14 @@ 242 242 Scripts 243 243 )))|((( 244 244 4.00 Beta 1 245 -)))|((( 376 +)))|(% colspan="2" %)((( 246 246 Changed behaviour of **gatedistance** script property 247 -)))|((( 248 - 249 249 ))) 250 -|(% 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" %) 251 251 ((( 252 252 //The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.// 253 -)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %) 254 -((( 255 - 256 256 ))) 257 -|(% colspan="4" %)(% colspan=" 4" %)383 +|(% colspan="4" %)(% colspan="3" %) 258 258 ((( 259 259 == 3.30 == 260 260 ))) ... ... @@ -262,17 +262,14 @@ 262 262 UI extensions 263 263 )))|((( 264 264 3.30 Beta 3 265 -)))|((( 266 -**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()** 267 -)))|(% colspan="1" %)(% colspan="1" %) 268 -((( 269 - 391 +)))|(% colspan="2" %)((( 392 +**FFI: **Removed** GetMissionLimit() **and** IsMissionLimitEnabled()** 270 270 ))) 271 -|(% 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" %) 272 272 ((( 273 -//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()// 274 274 ))) 275 -|(% colspan="4" %)(% colspan=" 4" %)398 +|(% colspan="4" %)(% colspan="3" %) 276 276 ((( 277 277 == 3.20 == 278 278 ))) ... ... @@ -280,13 +280,10 @@ 280 280 Scripts 281 281 )))|((( 282 282 3.20 Beta 1 283 -)))|((( 406 +)))|(% colspan="2" %)((( 284 284 Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed 285 -)))|(% colspan="1" %)(% colspan="1" %) 286 -((( 287 - 288 288 ))) 289 -|(% 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" %) 290 290 ((( 291 291 //Old params: param = attacked object, param2 = attack method, param3 = attacked component// 292 292 //New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon] ... ... @@ -298,14 +298,11 @@ 298 298 )))|(% colspan="1" %)(% colspan="1" %) 299 299 ((( 300 300 3.20 Beta 1 301 -)))|(% colspan=" 1" %)(% colspan="1" %)421 +)))|(% colspan="2" %)(% colspan="1" %) 302 302 ((( 303 303 Removed script property $trade.**restriction.faction** 304 -)))|(% colspan="1" %)(% colspan="1" %) 305 -((( 306 - 307 307 ))) 308 -|(% 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" %) 309 309 ((( 310 310 //$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.// 311 311 ))) ... ... @@ -313,17 +313,14 @@ 313 313 UI extensions 314 314 )))|((( 315 315 3.20 Beta 1 316 -)))|((( 433 +)))|(% colspan="2" %)((( 317 317 **Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete! 318 -)))|(% colspan="1" %)(% colspan="1" %) 319 -((( 320 - 321 321 ))) 322 -|(% 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" %) 323 323 ((( 324 324 //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.// 325 325 ))) 326 -|(% colspan="4" %)(% colspan=" 4" %)440 +|(% colspan="4" %)(% colspan="3" %) 327 327 ((( 328 328 == 3.10 == 329 329 ))) ... ... @@ -333,18 +333,15 @@ 333 333 )))|(% colspan="1" %)(% colspan="1" %) 334 334 ((( 335 335 3.10 Beta 1 336 -)))|(% colspan=" 1" %)(% colspan="1" %)450 +)))|(% colspan="2" %)(% colspan="1" %) 337 337 ((( 338 338 Removed script action **<add_build/>** 339 -)))|(% colspan="1" %)(% colspan="1" %) 340 -((( 341 - 342 342 ))) 343 -|(% 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" %) 344 344 ((( 345 345 //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.// 346 346 ))) 347 -|(% colspan="4" %)(% colspan=" 4" %)458 +|(% colspan="4" %)(% colspan="3" %) 348 348 ((( 349 349 == 3.00 == 350 350 ))) ... ... @@ -354,14 +354,11 @@ 354 354 )))|(% colspan="1" %)(% colspan="1" %) 355 355 ((( 356 356 3.0 Beta 6 357 -)))|(% colspan=" 1" %)(% colspan="1" %)468 +)))|(% colspan="2" %)(% colspan="1" %) 358 358 ((( 359 359 Changed behaviour of script action **<get_suitable_job/>** 360 -)))|(% colspan="1" %)(% colspan="1" %) 361 -((( 362 - 363 363 ))) 364 -|(% 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" %) 365 365 ((( 366 366 //<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.// 367 367 ))) ... ... @@ -371,14 +371,11 @@ 371 371 )))|(% colspan="1" %)(% colspan="1" %) 372 372 ((( 373 373 3.0 Beta 6 374 -)))|(% colspan=" 1" %)(% colspan="1" %)482 +)))|(% colspan="2" %)(% colspan="1" %) 375 375 ((( 376 376 Changed behaviour of script action **<get_ware_definition/>** 377 -)))|(% colspan="1" %)(% colspan="1" %) 378 -((( 379 - 380 380 ))) 381 -|(% 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" %) 382 382 ((( 383 383 //<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.// 384 384 ))) ... ... @@ -388,16 +388,13 @@ 388 388 )))|(% colspan="1" %)(% colspan="1" %) 389 389 ((( 390 390 3.0 Beta 5 391 -)))|(% colspan=" 1" %)(% colspan="1" %)496 +)))|(% colspan="2" %)(% colspan="1" %) 392 392 ((( 393 393 Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case 394 -)))|(% colspan="1" %)(% colspan="1" %) 395 -((( 396 - 397 397 ))) 398 -|(% 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" %) 399 399 ((( 400 -//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.) 401 401 402 402 //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).// 403 403 ))) ... ... @@ -407,14 +407,11 @@ 407 407 )))|(% colspan="1" %)(% colspan="1" %) 408 408 ((( 409 409 3.0 Beta 5 410 -)))|(% colspan=" 1" %)(% colspan="1" %)512 +)))|(% colspan="2" %)(% colspan="1" %) 411 411 ((( 412 412 Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions> 413 -)))|(% colspan="1" %)(% colspan="1" %) 414 -((( 415 - 416 416 ))) 417 -|(% 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" %) 418 418 ((( 419 419 //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.// 420 420 ))) ... ... @@ -424,14 +424,11 @@ 424 424 )))|(% colspan="1" %)(% colspan="1" %) 425 425 ((( 426 426 3.0 Beta 5 427 -)))|(% colspan=" 1" %)(% colspan="1" %)526 +)))|(% colspan="2" %)(% colspan="1" %) 428 428 ((( 429 429 Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos** 430 -)))|(% colspan="1" %)(% colspan="1" %) 431 -((( 432 - 433 433 ))) 434 -|(% 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" %) 435 435 ((( 436 436 //Before the change, positions are relative to $dockingbay.parent. 437 437 After the change, positions are relative to $dockingbay as specified in the documentation.// ... ... @@ -442,14 +442,11 @@ 442 442 )))|(% colspan="1" %)(% colspan="1" %) 443 443 ((( 444 444 3.0 Beta 2 445 -)))|(% colspan=" 1" %)(% colspan="1" %)541 +)))|(% colspan="2" %)(% colspan="1" %) 446 446 ((( 447 447 Support for entity flag "**skillsvisible**" dropped 448 -)))|(% colspan="1" %)(% colspan="1" %) 449 -((( 450 - 451 451 ))) 452 -|(% 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" %) 453 453 ((( 454 454 //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().// 455 455 ))) ... ... @@ -457,13 +457,10 @@ 457 457 Scripts 458 458 )))|((( 459 459 3.0 Beta 2 460 -)))|((( 553 +)))|(% colspan="2" %)((( 461 461 Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**. 462 -)))|(% colspan="1" %)(% colspan="1" %) 463 -((( 464 - 465 465 ))) 466 -|(% 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" %) 467 467 ((( 468 468 //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. 469 469 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. ... ... @@ -476,14 +476,11 @@ 476 476 )))|(% colspan="1" %)(% colspan="1" %) 477 477 ((( 478 478 3.0 Beta 1 479 -)))|(% colspan=" 1" %)(% colspan="1" %)569 +)))|(% colspan="2" %)(% colspan="1" %) 480 480 ((( 481 481 **MissionBoard** support dropped 482 -)))|(% colspan="1" %)(% colspan="1" %) 483 -((( 484 - 485 485 ))) 486 -|(% 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" %) 487 487 ((( 488 488 //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.// 489 489 ))) ... ... @@ -491,13 +491,10 @@ 491 491 Job/God 492 492 )))|((( 493 493 3.0 Beta 1 494 -)))|((( 581 +)))|(% colspan="2" %)((( 495 495 By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined 496 -)))|(% colspan="1" %)(% colspan="1" %) 497 -((( 498 - 499 499 ))) 500 -|(% 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" %) 501 501 ((( 502 502 //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.// 503 503 ))) ... ... @@ -507,14 +507,11 @@ 507 507 )))|(% colspan="1" %)(% colspan="1" %) 508 508 ((( 509 509 3.0 Beta 1 510 -)))|(% colspan=" 1" %)(% colspan="1" %)594 +)))|(% colspan="2" %)(% colspan="1" %) 511 511 ((( 512 512 Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'** 513 -)))|(% colspan="1" %)(% colspan="1" %) 514 -((( 515 - 516 516 ))) 517 -|(% 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" %) 518 518 ((( 519 519 //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.// 520 520 ))) ... ... @@ -524,14 +524,11 @@ 524 524 )))|(% colspan="1" %)(% colspan="1" %) 525 525 ((( 526 526 3.0 Beta 1 527 -)))|(% colspan=" 1" %)(% colspan="1" %)608 +)))|(% colspan="2" %)(% colspan="1" %) 528 528 ((( 529 529 Script action **<set_doors_locked/>** attribute **'group'** changed 530 -)))|(% colspan="1" %)(% colspan="1" %) 531 -((( 532 - 533 533 ))) 534 -|(% 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" %) 535 535 ((( 536 536 //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.// 537 537 ))) ... ... @@ -541,14 +541,11 @@ 541 541 )))|(% colspan="1" %)(% colspan="1" %) 542 542 ((( 543 543 3.0 Beta 1 544 -)))|(% colspan=" 1" %)(% colspan="1" %)622 +)))|(% colspan="2" %)(% colspan="1" %) 545 545 ((( 546 546 Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed 547 -)))|(% colspan="1" %)(% colspan="1" %) 548 -((( 549 - 550 550 ))) 551 -|(% 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" %) 552 552 ((( 553 553 //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.// 554 554 ))) ... ... @@ -558,14 +558,11 @@ 558 558 )))|(% colspan="1" %)(% colspan="1" %) 559 559 ((( 560 560 3.0 Beta 1 561 -)))|(% colspan=" 1" %)(% colspan="1" %)636 +)))|(% colspan="2" %)(% colspan="1" %) 562 562 ((( 563 563 Script actions **<set_hack_target/>** and **<abort_hack/>** removed 564 -)))|(% colspan="1" %)(% colspan="1" %) 565 -((( 566 - 567 567 ))) 568 -|(% 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" %) 569 569 ((( 570 570 //These actions had no effect and were removed.// 571 571 ))) ... ... @@ -575,14 +575,11 @@ 575 575 )))|(% colspan="1" %)(% colspan="1" %) 576 576 ((( 577 577 3.0 Beta 1 578 -)))|(% colspan=" 1" %)(% colspan="1" %)650 +)))|(% colspan="2" %)(% colspan="1" %) 579 579 ((( 580 580 **<setup_conversation_minigame/>** script action removed 581 -)))|(% colspan="1" %)(% colspan="1" %) 582 -((( 583 - 584 584 ))) 585 -|(% 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" %) 586 586 ((( 587 587 //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.// 588 588 ))) ... ... @@ -592,14 +592,11 @@ 592 592 )))|(% colspan="1" %)(% colspan="1" %) 593 593 ((( 594 594 3.0 Beta 1 595 -)))|(% colspan=" 1" %)(% colspan="1" %)664 +)))|(% colspan="2" %)(% colspan="1" %) 596 596 ((( 597 597 <add_player_choice_*> **confidence** attribute removed 598 -)))|(% colspan="1" %)(% colspan="1" %) 599 -((( 600 - 601 601 ))) 602 -|(% 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" %) 603 603 ((( 604 604 //The default confidence of player options is another leftover from the XR era and had no effect in X4.// 605 605 ))) ... ... @@ -609,14 +609,11 @@ 609 609 )))|(% colspan="1" %)(% colspan="1" %) 610 610 ((( 611 611 3.0 Beta 1 612 -)))|(% colspan=" 1" %)(% colspan="1" %)678 +)))|(% colspan="2" %)(% colspan="1" %) 613 613 ((( 614 614 **<hack_via_control_panel/>** script action removed 615 -)))|(% colspan="1" %)(% colspan="1" %) 616 -((( 617 - 618 618 ))) 619 -|(% 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" %) 620 620 ((( 621 621 //Unused script action <hack_via_control_panel/> was removed.// 622 622 ))) ... ... @@ -626,14 +626,11 @@ 626 626 )))|(% colspan="1" %)(% colspan="1" %) 627 627 ((( 628 628 3.0 Beta 1 629 -)))|(% colspan=" 1" %)(% colspan="1" %)692 +)))|(% colspan="2" %)(% colspan="1" %) 630 630 ((( 631 631 **Lua: **GetMiniGameCursorPosition() removed 632 -)))|(% colspan="1" %)(% colspan="1" %) 633 -((( 634 - 635 635 ))) 636 -|(% 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" %) 637 637 ((( 638 638 //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.// 639 639 ))) ... ... @@ -641,13 +641,10 @@ 641 641 UI core 642 642 )))|((( 643 643 3.0 Beta 1 644 -)))|((( 704 +)))|(% colspan="2" %)((( 645 645 **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders 646 -)))|(% colspan="1" %)(% colspan="1" %) 647 -((( 648 - 649 649 ))) 650 -|(% 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" %) 651 651 ((( 652 652 //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.// 653 653 ))) ... ... @@ -657,14 +657,11 @@ 657 657 )))|(% colspan="1" %)(% colspan="1" %) 658 658 ((( 659 659 3.0 Beta 1 660 -)))|(% colspan=" 1" %)(% colspan="1" %)717 +)))|(% colspan="2" %)(% colspan="1" %) 661 661 ((( 662 662 **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor 663 -)))|(% colspan="1" %)(% colspan="1" %) 664 -((( 665 - 666 666 ))) 667 -|(% 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" %) 668 668 ((( 669 669 //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.// 670 670 ))) ... ... @@ -674,14 +674,11 @@ 674 674 )))|(% colspan="1" %)(% colspan="1" %) 675 675 ((( 676 676 3.0 Beta 1 677 -)))|(% colspan=" 1" %)(% colspan="1" %)731 +)))|(% colspan="2" %)(% colspan="1" %) 678 678 ((( 679 679 **$ware.illegal** updated 680 -)))|(% colspan="1" %)(% colspan="1" %) 681 -((( 682 - 683 683 ))) 684 -|(% 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" %) 685 685 ((( 686 686 //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.// 687 687 //It now returns true if $ware is illegal to any faction in the game.// ... ... @@ -692,14 +692,11 @@ 692 692 )))|(% colspan="1" %)(% colspan="1" %) 693 693 ((( 694 694 3.0 Beta 1 695 -)))|(% colspan=" 1" %)(% colspan="1" %)746 +)))|(% colspan="2" %)(% colspan="1" %) 696 696 ((( 697 697 MD script **RML_Flight_Along_Path** removed 698 -)))|(% colspan="1" %)(% colspan="1" %) 699 -((( 700 - 701 701 ))) 702 -|(% 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" %) 703 703 ((( 704 704 //The MD script RML_Flight_Along_Path was not referened and was removed.// 705 705 ))) ... ... @@ -709,14 +709,11 @@ 709 709 )))|(% colspan="1" %)(% colspan="1" %) 710 710 ((( 711 711 3.0 Beta 1 712 -)))|(% colspan=" 1" %)(% colspan="1" %)760 +)))|(% colspan="2" %)(% colspan="1" %) 713 713 ((( 714 714 parameters of **<event_venture_mission_completed/>** changed 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" %)764 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 720 720 ((( 721 721 //old params: param = venture details, param2 = ships involved, param3 = duration// 722 722 //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration// ... ... @@ -725,14 +725,11 @@ 725 725 Scripts 726 726 )))|((( 727 727 3.0 Beta 1 728 -)))|((( 773 +)))|(% colspan="2" %)((( 729 729 **<set_object_wing_name/>** removed, 730 730 **<set_object_fleet_name/>** added 731 -)))|(% colspan="1" %)(% colspan="1" %) 732 -((( 733 - 734 734 ))) 735 -|(% 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" %) 736 736 ((( 737 737 //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>// 738 738 ))) ... ... @@ -740,18 +740,15 @@ 740 740 Scripts 741 741 )))|((( 742 742 3.0 Beta 1 743 -)))|((( 785 +)))|(% colspan="2" %)((( 744 744 **$controllable.wing.*** removed, 745 745 **$controllable.fleet.*** added 746 -)))|(% colspan="1" %)(% colspan="1" %) 747 -((( 748 - 749 749 ))) 750 -|(% 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" %) 751 751 ((( 752 752 $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander 753 753 ))) 754 -|(% colspan="4" %)(% colspan=" 4" %)793 +|(% colspan="4" %)(% colspan="3" %) 755 755 ((( 756 756 == 2.60 == 757 757 ))) ... ... @@ -759,13 +759,10 @@ 759 759 Scripts 760 760 )))|((( 761 761 2.60 Beta 1 762 -)))|((( 801 +)))|(% colspan="2" %)((( 763 763 '**checkoperational**' filter behaviour changed 764 -)))|(% colspan="1" %)(% colspan="1" %) 765 -((( 766 - 767 767 ))) 768 -|(% 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" %) 769 769 ((( 770 770 //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.// 771 771 ... ... @@ -775,17 +775,14 @@ 775 775 Scripts 776 776 )))|((( 777 777 2.60 Beta 1 778 -)))|((( 814 +)))|(% colspan="2" %)((( 779 779 $container.**supplyresources** behavior changed 780 -)))|(% colspan="1" %)(% colspan="1" %) 781 -((( 782 - 783 783 ))) 784 -|(% 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" %) 785 785 ((( 786 786 //The script keyword $container.supplyresources now includes reserved wares.// 787 787 ))) 788 -|(% colspan="4" %)(% colspan=" 4" %)821 +|(% colspan="4" %)(% colspan="3" %) 789 789 ((( 790 790 == 2.20 == 791 791 ))) ... ... @@ -795,20 +795,16 @@ 795 795 )))|(% colspan="1" %)(% colspan="1" %) 796 796 ((( 797 797 2.20 Beta 3/4 798 -)))|(% colspan=" 1" %)(% colspan="1" %)831 +)))|(% colspan="2" %)(% colspan="1" %) 799 799 ((( 800 800 **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined. 801 -)))|(% colspan="1" %)(% colspan="1" %) 802 -((( 803 - 804 804 ))) 805 -|(% 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" %) 806 806 ((( 807 807 //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. 808 808 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.// 809 809 810 -//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. 811 -// 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.// 812 812 ))) 813 813 |(% colspan="1" %)(% colspan="1" %) 814 814 ((( ... ... @@ -816,18 +816,15 @@ 816 816 )))|(% colspan="1" %)(% colspan="1" %) 817 817 ((( 818 818 2.20 Beta 3 819 -)))|(% colspan=" 1" %)(% colspan="1" %)848 +)))|(% colspan="2" %)(% colspan="1" %) 820 820 ((( 821 821 Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor' 822 -)))|(% colspan="1" %)(% colspan="1" %) 823 -((( 824 - 825 825 ))) 826 -|(% 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" %) 827 827 ((( 828 828 //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.// 829 829 ))) 830 -|(% colspan="4" %)(% colspan=" 4" %)856 +|(% colspan="4" %)(% colspan="3" %) 831 831 ((( 832 832 == 2.00 == 833 833 ))) ... ... @@ -837,14 +837,11 @@ 837 837 )))|(% colspan="1" %)(% colspan="1" %) 838 838 ((( 839 839 2.00 Beta 1 840 -)))|(% colspan=" 1" %)(% colspan="1" %)866 +)))|(% colspan="2" %)(% colspan="1" %) 841 841 ((( 842 842 **<event_build_finished/> **param2 now returns null instead of a construction sequence 843 -)))|(% colspan="1" %)(% colspan="1" %) 844 -((( 845 - 846 846 ))) 847 -|(% 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" %) 848 848 ((( 849 849 //The construction sequence which was finished should now be accessed via the buildtask provided via param3.// 850 850 ))) ... ... @@ -854,14 +854,11 @@ 854 854 )))|(% colspan="1" %)(% colspan="1" %) 855 855 ((( 856 856 2.00 Beta 1 857 -)))|(% colspan=" 1" %)(% colspan="1" %)880 +)))|(% colspan="2" %)(% colspan="1" %) 858 858 ((( 859 859 **param.boarding.{...}** strength parameters removed 860 -)))|(% colspan="1" %)(% colspan="1" %) 861 -((( 862 - 863 863 ))) 864 -|(% 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" %) 865 865 ((( 866 866 //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.// 867 867 ))) ... ... @@ -871,14 +871,11 @@ 871 871 )))|(% colspan="1" %)(% colspan="1" %) 872 872 ((( 873 873 2.00 Beta 1 874 -)))|(% colspan=" 1" %)(% colspan="1" %)894 +)))|(% colspan="2" %)(% colspan="1" %) 875 875 ((( 876 876 **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed 877 -)))|(% colspan="1" %)(% colspan="1" %) 878 -((( 879 - 880 880 ))) 881 -|(% 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" %) 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 ))) ... ... @@ -886,13 +886,10 @@ 886 886 UI extensions 887 887 )))|((( 888 888 2.00 Beta 1 889 -)))|((( 906 +)))|(% colspan="2" %)((( 890 890 **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals 891 -)))|(% colspan="1" %)(% colspan="1" %) 892 -((( 893 - 894 894 ))) 895 -|(% 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" %) 896 896 ((( 897 897 //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.// 898 898 ))) ... ... @@ -900,13 +900,10 @@ 900 900 UI extensions 901 901 )))|((( 902 902 2.00 Beta 1 903 -)))|((( 917 +)))|(% colspan="2" %)((( 904 904 **FFI: SetFormationShape()** no longer indicates an error upon certain error cases 905 -)))|(% colspan="1" %)(% colspan="1" %) 906 -((( 907 - 908 908 ))) 909 -|(% 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" %) 910 910 ((( 911 911 //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.// 912 912 //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.// ... ... @@ -915,13 +915,10 @@ 915 915 Scripts 916 916 )))|((( 917 917 2.00 Beta 1 918 -)))|((( 929 +)))|(% colspan="2" %)((( 919 919 **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated. 920 -)))|(% colspan="1" %)(% colspan="1" %) 921 -((( 922 - 923 923 ))) 924 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)932 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 925 925 ((( 926 926 //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.// 927 927 ))) ... ... @@ -929,13 +929,10 @@ 929 929 Scripts 930 930 )))|((( 931 931 2.00 Beta 1 932 -)))|((( 940 +)))|(% colspan="2" %)((( 933 933 **<event_player_changed_target/>** now fires and returns null if the player deselects a target. 934 -)))|(% colspan="1" %)(% colspan="1" %) 935 -((( 936 - 937 937 ))) 938 -|(% 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" %) 939 939 ((( 940 940 //For prior behavior, check for event.param being non-null.// 941 941 ))) ... ... @@ -943,13 +943,10 @@ 943 943 AI Scripts 944 944 )))|((( 945 945 2.00 Beta 1 946 -)))|((( 951 +)))|(% colspan="2" %)((( 947 947 **<shoot/>/<shoot_at/>** attribute changes. 948 -)))|(% colspan="1" %)(% colspan="1" %) 949 -((( 950 - 951 951 ))) 952 -|(% 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" %) 953 953 ((( 954 954 //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.// 955 955 //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.// ... ... @@ -961,13 +961,10 @@ 961 961 UI extensions 962 962 )))|((( 963 963 2.00 Beta 1 964 -)))|((( 965 -**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% class="confluenceTd" %) 966 -)))|(% colspan="1" %)(% colspan="1" %) 967 -((( 968 - 966 +)))|(% colspan="2" %)((( 967 +**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter. 969 969 ))) 970 -|(% 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" %) 971 971 ((( 972 972 //Added possibility to query build tasks of a certain buildmodule.// 973 973 ))) ... ... @@ -975,13 +975,10 @@ 975 975 UI extensions 976 976 )))|((( 977 977 2.00 Beta 1 978 -)))|((( 977 +)))|(% colspan="2" %)((( 979 979 **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field. 980 -)))|(% colspan="1" %)(% colspan="1" %) 981 -((( 982 - 983 983 ))) 984 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)980 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 985 985 ((( 986 986 //Added list of resources a buildmodule needs to build.// 987 987 ))) ... ... @@ -989,13 +989,10 @@ 989 989 UI extensions 990 990 )))|((( 991 991 2.00 Beta 1 992 -)))|((( 993 -(% 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);" %) 994 -)))|(% colspan="1" %)(% colspan="1" %) 995 -((( 996 - 988 +)))|(% colspan="2" %)((( 989 +**Lua: CalculateTotalHullFraction() **was removed. 997 997 ))) 998 -|(% 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" %) 999 999 ((( 1000 1000 //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.// 1001 1001 ))) ... ... @@ -1003,17 +1003,14 @@ 1003 1003 UI extensions 1004 1004 )))|((( 1005 1005 2.00 Beta 1 1006 -)))|((( 1007 -**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" %) 1008 -)))|(% colspan="1" %)(% colspan="1" %) 1009 -((( 1010 - 999 +)))|(% colspan="2" %)((( 1000 +**FFI: RequestDockAtReason()/UndockPlayerShip() **changed their return values. 1011 1011 ))) 1012 -|(% 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" %) 1013 1013 ((( 1014 1014 //Changed return value type to const char* to better identify failure reasons in Lua script.// 1015 1015 ))) 1016 -|(% colspan="4" %)(% colspan=" 4" %)1006 +|(% colspan="4" %)(% colspan="3" %) 1017 1017 ((( 1018 1018 == 1.50 == 1019 1019 ))) ... ... @@ -1021,13 +1021,10 @@ 1021 1021 UI extensions 1022 1022 )))|((( 1023 1023 1.50 Beta 3 1024 -)))|((( 1025 -**Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %) 1026 -)))|(% colspan="1" %)(% colspan="1" %) 1027 -((( 1028 - 1014 +)))|(% colspan="2" %)((( 1015 +**Lua: GetComponentData() **changed behavior of "docksizes" property. 1029 1029 ))) 1030 -|(% 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" %) 1031 1031 ((( 1032 1032 //The "docksizes" property no longer includes internal ship storage docks.// 1033 1033 ))) ... ... @@ -1035,13 +1035,10 @@ 1035 1035 All 1036 1036 )))|((( 1037 1037 1.50 Beta 2 1038 -)))|((( 1025 +)))|(% colspan="2" %)((( 1039 1039 **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR). 1040 -)))|(% colspan="1" %)(% colspan="1" %) 1041 -((( 1042 - 1043 1043 ))) 1044 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)1028 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1045 1045 ((( 1046 1046 //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".// 1047 1047 ... ... @@ -1053,13 +1053,10 @@ 1053 1053 UI extensions 1054 1054 )))|((( 1055 1055 1.50 Beta 2 1056 -)))|((( 1057 -**FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %) 1058 -)))|(% colspan="1" %)(% colspan="1" %) 1059 -((( 1060 - 1040 +)))|(% colspan="2" %)((( 1041 +**FFI: UpgradeGroupInfo **datatype was changed. 1061 1061 ))) 1062 -|(% 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" %) 1063 1063 ((( 1064 1064 //Added new "operational" field to retrieve information about number of operational upgrades in a group.// 1065 1065 ))) ... ... @@ -1069,17 +1069,13 @@ 1069 1069 )))|(% colspan="1" %)(% colspan="1" %) 1070 1070 ((( 1071 1071 1.50 Beta 1 1072 -)))|(% colspan=" 1" %)(% colspan="1" %)1053 +)))|(% colspan="2" %)(% colspan="1" %) 1073 1073 ((( 1074 1074 **FFI: SetGuidance()** removed useinfopoint argument. 1075 -)))|(% colspan="1" %)(% colspan="1" %) 1076 -((( 1077 - 1078 1078 ))) 1079 -|(% 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" %) 1080 1080 ((( 1081 -//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. 1082 -// 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.// 1083 1083 1084 1084 //The new function declaration is: void SetGuidance(UniverseID componentid, UIPosRot offset)// 1085 1085 ))) ... ... @@ -1087,17 +1087,14 @@ 1087 1087 UI extensions 1088 1088 )))|((( 1089 1089 1.50 Beta 1 1090 -)))|((( 1091 -**FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %) 1092 -)))|(% colspan="1" %)(% colspan="1" %) 1093 -((( 1094 - 1067 +)))|(% colspan="2" %)((( 1068 +**FFI: CancelConstruction() **changed its return value. 1095 1095 ))) 1096 -|(% 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" %) 1097 1097 ((( 1098 - (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. //1072 +//CancelConstruction() now returns if the cancellation was successful. // 1099 1099 ))) 1100 -|(% colspan="4" %)(% colspan=" 4" %)1074 +|(% colspan="4" %)(% colspan="3" %) 1101 1101 ((( 1102 1102 == 1.32 == 1103 1103 ))) ... ... @@ -1105,17 +1105,14 @@ 1105 1105 UI extensions 1106 1106 )))|((( 1107 1107 1.32 1108 -)))|((( 1082 +)))|(% colspan="2" %)((( 1109 1109 **Lua: GetComponentData() **removed the "nextdestname" property. 1110 -)))|(% colspan="1" %)(% colspan="1" %) 1111 -((( 1112 - 1113 1113 ))) 1114 -|(% 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" %) 1115 1115 ((( 1116 1116 //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.// 1117 1117 ))) 1118 -|(% colspan="4" %)(% colspan=" 4" %)1089 +|(% colspan="4" %)(% colspan="3" %) 1119 1119 ((( 1120 1120 == 1.20 == 1121 1121 ))) ... ... @@ -1123,13 +1123,10 @@ 1123 1123 UI extensions 1124 1124 )))|((( 1125 1125 1.20 1126 -)))|((( 1127 -**FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %) 1128 -)))|(% colspan="1" %)(% colspan="1" %) 1129 -((( 1130 - 1097 +)))|(% colspan="2" %)((( 1098 +**FFI: GetAAOption()** got a new "useconfig" parameter. 1131 1131 ))) 1132 -|(% 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" %) 1133 1133 ((( 1134 -//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.// 1135 1135 )))
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 - 1045960461 +78577854 - url
-
... ... @@ -1,1 +1,1 @@ 1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/ 104596046/Breaking Changes1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/78577854/Breaking Changes