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