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