Changes for page Breaking Changes
Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 113.1
edited by Volodymyr Boichuk
on 2023/11/30 12:02
on 2023/11/30 12:02
Change comment:
There is no comment for this version
To version 101.1
edited by klaus
on 2023/01/20 15:19
on 2023/01/20 15:19
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Parent
-
... ... @@ -1,1 +1,0 @@ 1 -X4 Foundations Wiki.Modding Support.WebHome - Author
-
... ... @@ -1,1 +1,1 @@ 1 -xwiki:XWiki. Volodymyr1 +xwiki:XWiki.klaus - Content
-
... ... @@ -4,13 +4,13 @@ 4 4 The following table provides an overview about all breaking changes. This should help you to make any necessary changes to restore compatibility of older mods with new versions of X4. 5 5 Feel free to drop a note if a certain breaking change is breaking your mod and you have difficulties finding a way to work around the issue. 6 6 7 -{{ info}}8 - ⚠The list of breaking changes does7 +{{note}} 8 +The list of breaking changes does **NOT** cover changes in the provided/shipped scripts (for instance UI scripts like the ones located under ui/addons/XXX or ui/core/Lua). These scripts can change anytime without explicit notice. If you hook into one of these scripts or provide replacements for these, please check the script for possible breaking changes yourself. 9 9 10 10 Further note that the list provides information about breaking changes which are in the pipeline of being released. This is meant merely as an informational heads up. Neither do mistake this as an announcement of that version becoming available soon nor take it for granted that such a change will go live. Any information provided for not yet released versions can change (and even be removed) prior to such version having seen the light of day. 11 11 12 12 As a final note, please be aware that issues introduced during the beta phase might not be explicitly mentioned in the list below, if things would only be broken in-between two beta versions. While we still aim to document any (potential) breaking change here, there might be circumstances for which we divert from that procedure (especially in case of only minor issues which are considered merely bugfixes rather than an intended behavior change). 13 -{{/ info}}13 +{{/note}} 14 14 15 15 {{warning title="UI modding considered unstable until further notice..."}} 16 16 Please note that UI modding must be considered **unstable** in the current version. While we are working hard to get the UI modding integration into a stable state, we might have to introduce larger backwards incompatibilities in the following patches. This means that you might have to modify any mod using UI modding capabilities to a larger extend to keep it compatible with certain patches. Still, we are doing our best not to unnecessarily break things for modders and certainly will announce such changes on this page here. ... ... @@ -18,101 +18,29 @@ 18 18 19 19 = Breaking Changes = 20 20 21 -{{toc scope="LOCAL" start="3"/}} 22 - 23 -=== Version 7.00 === 24 - 25 - 26 -|(% colspan="1" style="width:117px" %)(% colspan="1" %) 27 -((( 28 -UI extensions 29 -)))|(% colspan="1" style="width:119px" %)((( 30 -7.00 Beta 1 31 -)))|(% colspan="2" style="width:1625px" %)((( 32 -**FFI**: RemoveBuildPlot() changed 33 -))) 34 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 35 -((( 36 -// 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.// 37 -))) 38 - 39 39 (% class="wrapped" %) 40 -|(% colspan="1" style="width:117px" %)(% colspan="1" %) 41 -((( 42 -Assets 43 -)))|(% colspan="1" style="width:119px" %)((( 44 -7.00 Beta 1 45 -)))|(% colspan="2" style="width:1625px" %)((( 46 -**Some Split DLC materials moved to base game** 22 +|=((( 23 +Type 24 +)))|=((( 25 +Version 26 +)))|=((( 27 +Summary 47 47 ))) 48 -|(% c lass="highlight-grey" colspan="7"data-highlight-colour="grey" title="Background colour :"%)(% class="highlight-grey" colspan="3"data-highlight-colour="grey" title="Background colour :"%)29 +|(% colspan="3" %)(% colspan="3" %) 49 49 ((( 50 - ////"spl_p1_fx" AND "split_p1_hulltexture_01"were moved from Split DLC to base game31 +== 6.00 == 51 51 ))) 52 - 53 ----- 54 - 55 -=== Version 6.00 === 56 - 57 -(% class="wrapped" %) 58 -|((( 59 -Libraries 60 -)))|((( 61 -6.00 Beta 7 62 -)))|(% colspan="2" %)((( 63 -Updated weights for ship groups in shipgroups.xml libraries of base game and all DLCs. 64 -))) 65 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 66 -((( 67 -//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.// 68 - 69 -//All groups should now have "weight" parameter added and old "weights" were updated to not have single-digit numbers.// 70 -))) 71 71 |(% colspan="1" %)(% colspan="1" %) 72 72 ((( 73 73 Scripts 74 74 )))|(% colspan="1" %)(% colspan="1" %) 75 75 ((( 76 -6.00 Beta 4 77 -)))|(% colspan="2" %)(% colspan="1" %) 78 -((( 79 -Changed conditions for **<event_player_travelmode_started> <event_player_travelmode_stopped> <event_player_travelmode_charge_started> <event_player_travelmode_charge_aborted>** to be raised. 80 -))) 81 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 82 -((( 83 -//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. // 84 - 85 -//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.// 86 -))) 87 -|(% colspan="1" %)(% colspan="1" %) 88 -((( 89 -Scripts 38 +6.00 Beta 1 90 90 )))|(% colspan="1" %)(% colspan="1" %) 91 91 ((( 92 -6.00 Beta 3 93 -)))|(% colspan="2" %)(% colspan="1" %) 94 -((( 95 -Changed result of **<find_object_surface>** action in the case of a failure 96 -))) 97 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 98 -((( 99 -//The 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.// 100 - 101 -//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.// 102 - 103 -//The action itself has been improved to increase the chance of finding suitable surface positions.// 104 -))) 105 -|(% colspan="1" %)(% colspan="1" %) 106 -((( 107 -Scripts 108 -)))|(% colspan="1" %)(% colspan="1" %) 109 -((( 110 -6.00 Beta 1 111 -)))|(% colspan="2" %)(% colspan="1" %) 112 -((( 113 113 Behaviour change for **<match_dock>** script component filter 114 114 ))) 115 -|(% 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 +|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %) 116 116 ((( 117 117 //<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes. 118 118 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.// ... ... @@ -123,11 +123,11 @@ 123 123 )))|(% colspan="1" %)(% colspan="1" %) 124 124 ((( 125 125 6.00 Beta 1 126 -)))|(% colspan=" 2" %)(% colspan="1" %)54 +)))|(% colspan="1" %)(% colspan="1" %) 127 127 ((( 128 128 Changed result attribute location for **<get_attackstrength>** 129 129 ))) 130 -|(% 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 +|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %) 131 131 ((( 132 132 //The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.// 133 133 ))) ... ... @@ -135,10 +135,10 @@ 135 135 Assets 136 136 )))|((( 137 137 6.00 Beta 1 138 -)))|( % colspan="2" %)(((66 +)))|((( 139 139 Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons 140 140 ))) 141 -|(% 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%" %)69 +|(% 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" %) 142 142 ((( 143 143 //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. 144 144 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.// ... ... @@ -149,11 +149,11 @@ 149 149 )))|(% colspan="1" %)(% colspan="1" %) 150 150 ((( 151 151 6.00 Beta 1 152 -)))|(% colspan=" 2" %)(% colspan="1" %)80 +)))|(% colspan="1" %)(% colspan="1" %) 153 153 ((( 154 154 Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects 155 155 ))) 156 -|(% 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%" %)84 +|(% 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" %) 157 157 ((( 158 158 //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.// 159 159 ))) ... ... @@ -161,10 +161,10 @@ 161 161 Scripts 162 162 )))|((( 163 163 6.00 Beta 1 164 -)))|( % colspan="2" %)(((92 +)))|((( 165 165 **<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards. 166 166 ))) 167 -|(% 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%" %)95 +|(% 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" %) 168 168 ((( 169 169 //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.// 170 170 ))) ... ... @@ -172,36 +172,32 @@ 172 172 Cutscenes 173 173 )))|((( 174 174 6.00 Beta 1 175 -)))|( % colspan="2" %)(((103 +)))|((( 176 176 Changed behaviour of **<angles>** in cutscenes 177 177 ))) 178 -|(% 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%" %)106 +|(% 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" %) 179 179 ((( 180 180 //The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.// 181 181 ))) 182 - 183 ----- 184 - 185 -=== Version 5.00 === 186 - 187 -(% class="wrapped" %) 110 +|(% colspan="3" %)(% colspan="3" %) 111 +((( 112 +== 5.00 == 113 +))) 188 188 |((( 189 189 Parameters 190 190 )))|((( 191 191 5.00 Beta 1 192 -)))|( % colspan="2" %)(((118 +)))|((( 193 193 **<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration 194 194 ))) 195 -|(% class="highlight-grey" colspan=" 7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)121 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 196 196 ((( 197 197 //'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.// 198 198 ))) 199 - 200 ----- 201 - 202 -=== Version 4.10 === 203 - 204 -(% class="wrapped" %) 125 +|(% colspan="3" %)(% colspan="3" %) 126 +((( 127 +== 4.10 == 128 +))) 205 205 |(% colspan="1" %)(% colspan="1" %) 206 206 ((( 207 207 UI extensions ... ... @@ -208,13 +208,13 @@ 208 208 )))|(% colspan="1" %)(% colspan="1" %) 209 209 ((( 210 210 4.10 Beta 7 211 -)))|(% colspan=" 2" %)(% colspan="1" %)135 +)))|(% colspan="1" %)(% colspan="1" %) 212 212 ((( 213 -**FFI**: SetMapRenderCargoContents(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos() deprecated 137 +**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()(%%) deprecated 214 214 ))) 215 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)139 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 216 216 ((( 217 -//The functionality represented by SetMapRenderCargoContents(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos() has been removed and the function was therefore stubbed.// 141 +//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.// 218 218 ))) 219 219 |(% colspan="1" %)(% colspan="1" %) 220 220 ((( ... ... @@ -222,11 +222,11 @@ 222 222 )))|(% colspan="1" %)(% colspan="1" %) 223 223 ((( 224 224 4.10 Beta 6 225 -)))|(% colspan=" 2" %)(% colspan="1" %)149 +)))|(% colspan="1" %)(% colspan="1" %) 226 226 ((( 227 227 **FFI**: CustomGameStartPlayerProperty2 changed 228 228 ))) 229 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)153 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 230 230 ((( 231 231 //This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.// 232 232 ))) ... ... @@ -236,11 +236,11 @@ 236 236 )))|(% colspan="1" %)(% colspan="1" %) 237 237 ((( 238 238 4.10 Beta 3 239 -)))|(% colspan=" 2" %)(% colspan="1" %)163 +)))|(% colspan="1" %)(% colspan="1" %) 240 240 ((( 241 241 Renamed **<stationinfobox>** to **<infobox>** 242 242 ))) 243 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)167 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 244 244 ((( 245 245 //Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.// 246 246 ))) ... ... @@ -250,11 +250,11 @@ 250 250 )))|(% colspan="1" %)(% colspan="1" %) 251 251 ((( 252 252 4.10 Beta 2 253 -)))|(% colspan=" 2" %)(% colspan="1" %)177 +)))|(% colspan="1" %)(% colspan="1" %) 254 254 ((( 255 255 **FFI**: SetMacroMapPlayerSectorOffset() deprecated 256 256 ))) 257 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)181 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 258 258 ((( 259 259 //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.// 260 260 ))) ... ... @@ -262,10 +262,10 @@ 262 262 UI extensions 263 263 )))|((( 264 264 4.10 Beta 2 265 -)))|( % colspan="2" %)(((266 -**FFI**: FilterComponentForMapMode() and SetMapObjectFilter() changed 189 +)))|((( 190 +**FFI**: (% style="color: rgb(0,0,0);" %)FilterComponentForMapMode(%%)() and (% style="color: rgb(0,0,0);" %)SetMapObjectFilter() changed 267 267 ))) 268 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)192 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 269 269 ((( 270 270 //These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.// 271 271 ))) ... ... @@ -273,10 +273,10 @@ 273 273 Scripts 274 274 )))|((( 275 275 4.10 Beta 1 276 -)))|( % colspan="2" %)(((277 -People related attributes of mission** 200 +)))|((( 201 +People related attributes of mission** <delivery> **node moved 278 278 ))) 279 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)203 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 280 280 ((( 281 281 //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.// 282 282 ))) ... ... @@ -286,11 +286,11 @@ 286 286 )))|(% colspan="1" %)(% colspan="1" %) 287 287 ((( 288 288 4.10 Beta 1 289 -)))|(% colspan=" 2" %)(% colspan="1" %)213 +)))|(% colspan="1" %)(% colspan="1" %) 290 290 ((( 291 291 **$destructible.productions** replaced with $defensible.productions 292 292 ))) 293 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)217 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 294 294 ((( 295 295 //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.// 296 296 ))) ... ... @@ -298,19 +298,17 @@ 298 298 Scripts 299 299 )))|((( 300 300 4.10 Beta 1 301 -)))|( % colspan="2" %)(((225 +)))|((( 302 302 Removed script property **$object.spawnsourceseed** 303 303 ))) 304 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)228 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 305 305 ((( 306 306 //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.// 307 307 ))) 308 - 309 ----- 310 - 311 -=== Version 4.00 === 312 - 313 -(% class="wrapped" %) 232 +|(% colspan="3" %)(% colspan="3" %) 233 +((( 234 +== 4.00 == 235 +))) 314 314 |(% colspan="1" %)(% colspan="1" %) 315 315 ((( 316 316 UI core ... ... @@ -317,23 +317,24 @@ 317 317 )))|(% colspan="1" %)(% colspan="1" %) 318 318 ((( 319 319 4.00 Beta 10 320 -)))|(% colspan=" 2" %)(% colspan="1" %)242 +)))|(% colspan="1" %)(% colspan="1" %) 321 321 ((( 322 322 Controlled ship can change without a **gameplanchange-event** occurring. 323 323 ))) 324 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)246 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 325 325 ((( 326 326 //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). 327 -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.// 249 +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. 250 +// 328 328 ))) 329 329 |((( 330 330 Scripts 331 331 )))|((( 332 332 4.00 Beta 7 333 -)))|( % colspan="2" %)(((256 +)))|((( 334 334 Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed 335 335 ))) 336 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)259 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 337 337 ((( 338 338 //Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects? 339 339 New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits ... ... @@ -345,16 +345,17 @@ 345 345 )))|(% colspan="1" %)(% colspan="1" %) 346 346 ((( 347 347 4.00 Beta 6 348 -)))|(% colspan=" 2" %)(% colspan="1" %)271 +)))|(% colspan="1" %)(% colspan="1" %) 349 349 ((( 350 350 **FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed 351 351 ))) 352 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)275 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 353 353 ((( 354 354 //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. 355 355 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).// 356 356 357 -//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.// 280 +//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead. 281 +// 358 358 ))) 359 359 |(% colspan="1" %)(% colspan="1" %) 360 360 ((( ... ... @@ -362,11 +362,11 @@ 362 362 )))|(% colspan="1" %)(% colspan="1" %) 363 363 ((( 364 364 4.00 Beta 5 365 -)))|(% colspan=" 2" %)(% colspan="1" %)289 +)))|(% colspan="1" %)(% colspan="1" %) 366 366 ((( 367 367 **FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed 368 368 ))) 369 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)293 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 370 370 ((( 371 371 //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.// 372 372 ... ... @@ -376,10 +376,10 @@ 376 376 Parameters 377 377 )))|((( 378 378 4.00 Beta 1 379 -)))|( % colspan="2" %)(((303 +)))|((( 380 380 **requiresconstructionvessel** parameter moved 381 381 ))) 382 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)306 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 383 383 ((( 384 384 //The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.// 385 385 ))) ... ... @@ -387,44 +387,40 @@ 387 387 Scripts 388 388 )))|((( 389 389 4.00 Beta 1 390 -)))|( % colspan="2" %)(((314 +)))|((( 391 391 Changed behaviour of **gatedistance** script property 392 392 ))) 393 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)317 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 394 394 ((( 395 395 //The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.// 396 396 ))) 397 - 398 ----- 399 - 400 -=== Version 3.30 === 401 - 402 -(% class="wrapped" %) 321 +|(% colspan="3" %)(% colspan="3" %) 322 +((( 323 +== 3.30 == 324 +))) 403 403 |((( 404 404 UI extensions 405 405 )))|((( 406 406 3.30 Beta 3 407 -)))|( % colspan="2" %)(((408 -**FFI: **Removed** 329 +)))|((( 330 +**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()** 409 409 ))) 410 -|(% class="highlight-grey" colspan=" 7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)332 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 411 411 ((( 412 -//These mission limit-related functions (added in 3.30 Beta 1 and 2) are replaced with FFI IsMissionLimitReached()// 334 +//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()// 413 413 ))) 414 - 415 ----- 416 - 417 -=== Version 3.20 === 418 - 419 -(% class="wrapped" %) 336 +|(% colspan="3" %)(% colspan="3" %) 337 +((( 338 +== 3.20 == 339 +))) 420 420 |((( 421 421 Scripts 422 422 )))|((( 423 423 3.20 Beta 1 424 -)))|( % colspan="2" %)(((344 +)))|((( 425 425 Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed 426 426 ))) 427 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)347 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 428 428 ((( 429 429 //Old params: param = attacked object, param2 = attack method, param3 = attacked component// 430 430 //New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon] ... ... @@ -436,11 +436,11 @@ 436 436 )))|(% colspan="1" %)(% colspan="1" %) 437 437 ((( 438 438 3.20 Beta 1 439 -)))|(% colspan=" 2" %)(% colspan="1" %)359 +)))|(% colspan="1" %)(% colspan="1" %) 440 440 ((( 441 441 Removed script property $trade.**restriction.faction** 442 442 ))) 443 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)363 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 444 444 ((( 445 445 //$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.// 446 446 ))) ... ... @@ -448,19 +448,17 @@ 448 448 UI extensions 449 449 )))|((( 450 450 3.20 Beta 1 451 -)))|( % colspan="2" %)(((371 +)))|((( 452 452 **Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete! 453 453 ))) 454 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)374 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 455 455 ((( 456 456 //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.// 457 457 ))) 458 - 459 ----- 460 - 461 -=== Version 3.10 === 462 - 463 -(% class="wrapped" %) 378 +|(% colspan="3" %)(% colspan="3" %) 379 +((( 380 +== 3.10 == 381 +))) 464 464 |(% colspan="1" %)(% colspan="1" %) 465 465 ((( 466 466 Scripts ... ... @@ -467,20 +467,18 @@ 467 467 )))|(% colspan="1" %)(% colspan="1" %) 468 468 ((( 469 469 3.10 Beta 1 470 -)))|(% colspan=" 2" %)(% colspan="1" %)388 +)))|(% colspan="1" %)(% colspan="1" %) 471 471 ((( 472 472 Removed script action **<add_build/>** 473 473 ))) 474 -|(% class="highlight-grey" colspan=" 7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)392 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 475 475 ((( 476 476 //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.// 477 477 ))) 478 - 479 ----- 480 - 481 -=== Version 3.00 === 482 - 483 -(% class="wrapped" %) 396 +|(% colspan="3" %)(% colspan="3" %) 397 +((( 398 +== 3.00 == 399 +))) 484 484 |(% colspan="1" %)(% colspan="1" %) 485 485 ((( 486 486 Scripts ... ... @@ -487,11 +487,11 @@ 487 487 )))|(% colspan="1" %)(% colspan="1" %) 488 488 ((( 489 489 3.0 Beta 6 490 -)))|(% colspan=" 2" %)(% colspan="1" %)406 +)))|(% colspan="1" %)(% colspan="1" %) 491 491 ((( 492 492 Changed behaviour of script action **<get_suitable_job/>** 493 493 ))) 494 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)410 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 495 495 ((( 496 496 //<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.// 497 497 ))) ... ... @@ -501,11 +501,11 @@ 501 501 )))|(% colspan="1" %)(% colspan="1" %) 502 502 ((( 503 503 3.0 Beta 6 504 -)))|(% colspan=" 2" %)(% colspan="1" %)420 +)))|(% colspan="1" %)(% colspan="1" %) 505 505 ((( 506 506 Changed behaviour of script action **<get_ware_definition/>** 507 507 ))) 508 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)424 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 509 509 ((( 510 510 //<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.// 511 511 ))) ... ... @@ -515,13 +515,13 @@ 515 515 )))|(% colspan="1" %)(% colspan="1" %) 516 516 ((( 517 517 3.0 Beta 5 518 -)))|(% colspan=" 2" %)(% colspan="1" %)434 +)))|(% colspan="1" %)(% colspan="1" %) 519 519 ((( 520 520 Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case 521 521 ))) 522 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)438 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 523 523 ((( 524 -//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.) 440 +//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.)\\ 525 525 526 526 //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).// 527 527 ))) ... ... @@ -531,11 +531,11 @@ 531 531 )))|(% colspan="1" %)(% colspan="1" %) 532 532 ((( 533 533 3.0 Beta 5 534 -)))|(% colspan=" 2" %)(% colspan="1" %)450 +)))|(% colspan="1" %)(% colspan="1" %) 535 535 ((( 536 536 Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions> 537 537 ))) 538 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)454 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 539 539 ((( 540 540 //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.// 541 541 ))) ... ... @@ -545,11 +545,11 @@ 545 545 )))|(% colspan="1" %)(% colspan="1" %) 546 546 ((( 547 547 3.0 Beta 5 548 -)))|(% colspan=" 2" %)(% colspan="1" %)464 +)))|(% colspan="1" %)(% colspan="1" %) 549 549 ((( 550 550 Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos** 551 551 ))) 552 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)468 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 553 553 ((( 554 554 //Before the change, positions are relative to $dockingbay.parent. 555 555 After the change, positions are relative to $dockingbay as specified in the documentation.// ... ... @@ -560,11 +560,11 @@ 560 560 )))|(% colspan="1" %)(% colspan="1" %) 561 561 ((( 562 562 3.0 Beta 2 563 -)))|(% colspan=" 2" %)(% colspan="1" %)479 +)))|(% colspan="1" %)(% colspan="1" %) 564 564 ((( 565 565 Support for entity flag "**skillsvisible**" dropped 566 566 ))) 567 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)483 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 568 568 ((( 569 569 //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().// 570 570 ))) ... ... @@ -572,10 +572,10 @@ 572 572 Scripts 573 573 )))|((( 574 574 3.0 Beta 2 575 -)))|( % colspan="2" %)(((491 +)))|((( 576 576 Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**. 577 577 ))) 578 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)494 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 579 579 ((( 580 580 //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. 581 581 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. ... ... @@ -588,11 +588,11 @@ 588 588 )))|(% colspan="1" %)(% colspan="1" %) 589 589 ((( 590 590 3.0 Beta 1 591 -)))|(% colspan=" 2" %)(% colspan="1" %)507 +)))|(% colspan="1" %)(% colspan="1" %) 592 592 ((( 593 593 **MissionBoard** support dropped 594 594 ))) 595 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)511 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 596 596 ((( 597 597 //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.// 598 598 ))) ... ... @@ -600,10 +600,10 @@ 600 600 Job/God 601 601 )))|((( 602 602 3.0 Beta 1 603 -)))|( % colspan="2" %)(((519 +)))|((( 604 604 By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined 605 605 ))) 606 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)522 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 607 607 ((( 608 608 //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.// 609 609 ))) ... ... @@ -613,11 +613,11 @@ 613 613 )))|(% colspan="1" %)(% colspan="1" %) 614 614 ((( 615 615 3.0 Beta 1 616 -)))|(% colspan=" 2" %)(% colspan="1" %)532 +)))|(% colspan="1" %)(% colspan="1" %) 617 617 ((( 618 618 Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'** 619 619 ))) 620 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)536 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 621 621 ((( 622 622 //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.// 623 623 ))) ... ... @@ -627,11 +627,11 @@ 627 627 )))|(% colspan="1" %)(% colspan="1" %) 628 628 ((( 629 629 3.0 Beta 1 630 -)))|(% colspan=" 2" %)(% colspan="1" %)546 +)))|(% colspan="1" %)(% colspan="1" %) 631 631 ((( 632 632 Script action **<set_doors_locked/>** attribute **'group'** changed 633 633 ))) 634 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)550 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 635 635 ((( 636 636 //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.// 637 637 ))) ... ... @@ -641,11 +641,11 @@ 641 641 )))|(% colspan="1" %)(% colspan="1" %) 642 642 ((( 643 643 3.0 Beta 1 644 -)))|(% colspan=" 2" %)(% colspan="1" %)560 +)))|(% colspan="1" %)(% colspan="1" %) 645 645 ((( 646 646 Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed 647 647 ))) 648 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)564 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 649 649 ((( 650 650 //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.// 651 651 ))) ... ... @@ -655,11 +655,11 @@ 655 655 )))|(% colspan="1" %)(% colspan="1" %) 656 656 ((( 657 657 3.0 Beta 1 658 -)))|(% colspan=" 2" %)(% colspan="1" %)574 +)))|(% colspan="1" %)(% colspan="1" %) 659 659 ((( 660 660 Script actions **<set_hack_target/>** and **<abort_hack/>** removed 661 661 ))) 662 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)578 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 663 663 ((( 664 664 //These actions had no effect and were removed.// 665 665 ))) ... ... @@ -669,11 +669,11 @@ 669 669 )))|(% colspan="1" %)(% colspan="1" %) 670 670 ((( 671 671 3.0 Beta 1 672 -)))|(% colspan=" 2" %)(% colspan="1" %)588 +)))|(% colspan="1" %)(% colspan="1" %) 673 673 ((( 674 674 **<setup_conversation_minigame/>** script action removed 675 675 ))) 676 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)592 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 677 677 ((( 678 678 //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.// 679 679 ))) ... ... @@ -683,11 +683,11 @@ 683 683 )))|(% colspan="1" %)(% colspan="1" %) 684 684 ((( 685 685 3.0 Beta 1 686 -)))|(% colspan=" 2" %)(% colspan="1" %)602 +)))|(% colspan="1" %)(% colspan="1" %) 687 687 ((( 688 688 <add_player_choice_*> **confidence** attribute removed 689 689 ))) 690 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)606 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 691 691 ((( 692 692 //The default confidence of player options is another leftover from the XR era and had no effect in X4.// 693 693 ))) ... ... @@ -697,11 +697,11 @@ 697 697 )))|(% colspan="1" %)(% colspan="1" %) 698 698 ((( 699 699 3.0 Beta 1 700 -)))|(% colspan=" 2" %)(% colspan="1" %)616 +)))|(% colspan="1" %)(% colspan="1" %) 701 701 ((( 702 702 **<hack_via_control_panel/>** script action removed 703 703 ))) 704 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)620 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 705 705 ((( 706 706 //Unused script action <hack_via_control_panel/> was removed.// 707 707 ))) ... ... @@ -711,11 +711,11 @@ 711 711 )))|(% colspan="1" %)(% colspan="1" %) 712 712 ((( 713 713 3.0 Beta 1 714 -)))|(% colspan=" 2" %)(% colspan="1" %)630 +)))|(% colspan="1" %)(% colspan="1" %) 715 715 ((( 716 716 **Lua: **GetMiniGameCursorPosition() removed 717 717 ))) 718 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)634 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 719 719 ((( 720 720 //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.// 721 721 ))) ... ... @@ -723,10 +723,10 @@ 723 723 UI core 724 724 )))|((( 725 725 3.0 Beta 1 726 -)))|( % colspan="2" %)(((642 +)))|((( 727 727 **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders 728 728 ))) 729 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)645 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 730 730 ((( 731 731 //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.// 732 732 ))) ... ... @@ -736,11 +736,11 @@ 736 736 )))|(% colspan="1" %)(% colspan="1" %) 737 737 ((( 738 738 3.0 Beta 1 739 -)))|(% colspan=" 2" %)(% colspan="1" %)655 +)))|(% colspan="1" %)(% colspan="1" %) 740 740 ((( 741 741 **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor 742 742 ))) 743 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)659 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 744 744 ((( 745 745 //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.// 746 746 ))) ... ... @@ -750,11 +750,11 @@ 750 750 )))|(% colspan="1" %)(% colspan="1" %) 751 751 ((( 752 752 3.0 Beta 1 753 -)))|(% colspan=" 2" %)(% colspan="1" %)669 +)))|(% colspan="1" %)(% colspan="1" %) 754 754 ((( 755 755 **$ware.illegal** updated 756 756 ))) 757 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)673 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 758 758 ((( 759 759 //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.// 760 760 //It now returns true if $ware is illegal to any faction in the game.// ... ... @@ -765,11 +765,11 @@ 765 765 )))|(% colspan="1" %)(% colspan="1" %) 766 766 ((( 767 767 3.0 Beta 1 768 -)))|(% colspan=" 2" %)(% colspan="1" %)684 +)))|(% colspan="1" %)(% colspan="1" %) 769 769 ((( 770 770 MD script **RML_Flight_Along_Path** removed 771 771 ))) 772 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)688 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 773 773 ((( 774 774 //The MD script RML_Flight_Along_Path was not referened and was removed.// 775 775 ))) ... ... @@ -779,11 +779,11 @@ 779 779 )))|(% colspan="1" %)(% colspan="1" %) 780 780 ((( 781 781 3.0 Beta 1 782 -)))|(% colspan=" 2" %)(% colspan="1" %)698 +)))|(% colspan="1" %)(% colspan="1" %) 783 783 ((( 784 784 parameters of **<event_venture_mission_completed/>** changed 785 785 ))) 786 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)702 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 787 787 ((( 788 788 //old params: param = venture details, param2 = ships involved, param3 = duration// 789 789 //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration// ... ... @@ -792,11 +792,11 @@ 792 792 Scripts 793 793 )))|((( 794 794 3.0 Beta 1 795 -)))|( % colspan="2" %)(((711 +)))|((( 796 796 **<set_object_wing_name/>** removed, 797 797 **<set_object_fleet_name/>** added 798 798 ))) 799 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)715 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 800 800 ((( 801 801 //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>// 802 802 ))) ... ... @@ -804,28 +804,26 @@ 804 804 Scripts 805 805 )))|((( 806 806 3.0 Beta 1 807 -)))|( % colspan="2" %)(((723 +)))|((( 808 808 **$controllable.wing.*** removed, 809 809 **$controllable.fleet.*** added 810 810 ))) 811 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)727 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 812 812 ((( 813 813 $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander 814 814 ))) 815 - 816 ----- 817 - 818 -=== Version 2.60 === 819 - 820 -(% class="wrapped" %) 731 +|(% colspan="3" %)(% colspan="3" %) 732 +((( 733 +== 2.60 == 734 +))) 821 821 |((( 822 822 Scripts 823 823 )))|((( 824 824 2.60 Beta 1 825 -)))|( % colspan="2" %)(((739 +)))|((( 826 826 '**checkoperational**' filter behaviour changed 827 827 ))) 828 -|(% class="highlight-grey" colspan=" 10" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)742 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 829 829 ((( 830 830 //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.// 831 831 ... ... @@ -835,19 +835,17 @@ 835 835 Scripts 836 836 )))|((( 837 837 2.60 Beta 1 838 -)))|( % colspan="2" %)(((752 +)))|((( 839 839 $container.**supplyresources** behavior changed 840 -))) | | |841 -|(% class="highlight-grey" colspan=" 10" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)754 +))) 755 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 842 842 ((( 843 843 //The script keyword $container.supplyresources now includes reserved wares.// 844 844 ))) 845 - 846 ----- 847 - 848 -=== Version 2.20 === 849 - 850 -(% class="wrapped" %) 759 +|(% colspan="3" %)(% colspan="3" %) 760 +((( 761 +== 2.20 == 762 +))) 851 851 |(% colspan="1" %)(% colspan="1" %) 852 852 ((( 853 853 UI core ... ... @@ -854,16 +854,17 @@ 854 854 )))|(% colspan="1" %)(% colspan="1" %) 855 855 ((( 856 856 2.20 Beta 3/4 857 -)))|(% colspan=" 2" %)(% colspan="1" %)769 +)))|(% colspan="1" %)(% colspan="1" %) 858 858 ((( 859 859 **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined. 860 860 ))) 861 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)773 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 862 862 ((( 863 863 //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. 864 864 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.// 865 865 866 -//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.// 778 +//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. 779 +// 867 867 ))) 868 868 |(% colspan="1" %)(% colspan="1" %) 869 869 ((( ... ... @@ -871,20 +871,18 @@ 871 871 )))|(% colspan="1" %)(% colspan="1" %) 872 872 ((( 873 873 2.20 Beta 3 874 -)))|(% colspan=" 2" %)(% colspan="1" %)787 +)))|(% colspan="1" %)(% colspan="1" %) 875 875 ((( 876 876 Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor' 877 877 ))) 878 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)791 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 879 879 ((( 880 880 //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.// 881 881 ))) 882 - 883 ----- 884 - 885 -=== Version 2.00 === 886 - 887 -(% class="wrapped" %) 795 +|(% colspan="3" %)(% colspan="3" %) 796 +((( 797 +== 2.00 == 798 +))) 888 888 |(% colspan="1" %)(% colspan="1" %) 889 889 ((( 890 890 Scripts ... ... @@ -891,11 +891,11 @@ 891 891 )))|(% colspan="1" %)(% colspan="1" %) 892 892 ((( 893 893 2.00 Beta 1 894 -)))|(% colspan=" 2" %)(% colspan="1" %)805 +)))|(% colspan="1" %)(% colspan="1" %) 895 895 ((( 896 896 **<event_build_finished/> **param2 now returns null instead of a construction sequence 897 897 ))) 898 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)809 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 899 899 ((( 900 900 //The construction sequence which was finished should now be accessed via the buildtask provided via param3.// 901 901 ))) ... ... @@ -905,11 +905,11 @@ 905 905 )))|(% colspan="1" %)(% colspan="1" %) 906 906 ((( 907 907 2.00 Beta 1 908 -)))|(% colspan=" 2" %)(% colspan="1" %)819 +)))|(% colspan="1" %)(% colspan="1" %) 909 909 ((( 910 910 **param.boarding.{...}** strength parameters removed 911 911 ))) 912 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)823 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 913 913 ((( 914 914 //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.// 915 915 ))) ... ... @@ -919,11 +919,11 @@ 919 919 )))|(% colspan="1" %)(% colspan="1" %) 920 920 ((( 921 921 2.00 Beta 1 922 -)))|(% colspan=" 2" %)(% colspan="1" %)833 +)))|(% colspan="1" %)(% colspan="1" %) 923 923 ((( 924 924 **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed 925 925 ))) 926 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)837 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 927 927 ((( 928 928 //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.// 929 929 ))) ... ... @@ -931,10 +931,10 @@ 931 931 UI extensions 932 932 )))|((( 933 933 2.00 Beta 1 934 -)))|( % colspan="2" %)(((845 +)))|((( 935 935 **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals 936 936 ))) 937 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)848 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 938 938 ((( 939 939 //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.// 940 940 ))) ... ... @@ -942,10 +942,10 @@ 942 942 UI extensions 943 943 )))|((( 944 944 2.00 Beta 1 945 -)))|( % colspan="2" %)(((856 +)))|((( 946 946 **FFI: SetFormationShape()** no longer indicates an error upon certain error cases 947 947 ))) 948 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)859 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 949 949 ((( 950 950 //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.// 951 951 //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.// ... ... @@ -954,10 +954,10 @@ 954 954 Scripts 955 955 )))|((( 956 956 2.00 Beta 1 957 -)))|( % colspan="2" %)(((868 +)))|((( 958 958 **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated. 959 959 ))) 960 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)871 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 961 961 ((( 962 962 //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.// 963 963 ))) ... ... @@ -965,10 +965,10 @@ 965 965 Scripts 966 966 )))|((( 967 967 2.00 Beta 1 968 -)))|( % colspan="2" %)(((879 +)))|((( 969 969 **<event_player_changed_target/>** now fires and returns null if the player deselects a target. 970 970 ))) 971 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)882 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 972 972 ((( 973 973 //For prior behavior, check for event.param being non-null.// 974 974 ))) ... ... @@ -976,10 +976,10 @@ 976 976 AI Scripts 977 977 )))|((( 978 978 2.00 Beta 1 979 -)))|( % colspan="2" %)(((890 +)))|((( 980 980 **<shoot/>/<shoot_at/>** attribute changes. 981 981 ))) 982 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)893 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 983 983 ((( 984 984 //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.// 985 985 //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.// ... ... @@ -991,10 +991,10 @@ 991 991 UI extensions 992 992 )))|((( 993 993 2.00 Beta 1 994 -)))|( % colspan="2" %)(((905 +)))|((( 995 995 **FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter. 996 996 ))) 997 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)908 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 998 998 ((( 999 999 //Added possibility to query build tasks of a certain buildmodule.// 1000 1000 ))) ... ... @@ -1002,10 +1002,10 @@ 1002 1002 UI extensions 1003 1003 )))|((( 1004 1004 2.00 Beta 1 1005 -)))|( % colspan="2" %)(((916 +)))|((( 1006 1006 **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field. 1007 1007 ))) 1008 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)919 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1009 1009 ((( 1010 1010 //Added list of resources a buildmodule needs to build.// 1011 1011 ))) ... ... @@ -1013,10 +1013,10 @@ 1013 1013 UI extensions 1014 1014 )))|((( 1015 1015 2.00 Beta 1 1016 -)))|( % colspan="2" %)(((1017 -**Lua: 927 +)))|((( 928 +(% 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);" %) 1018 1018 ))) 1019 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)930 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1020 1020 ((( 1021 1021 //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.// 1022 1022 ))) ... ... @@ -1024,27 +1024,25 @@ 1024 1024 UI extensions 1025 1025 )))|((( 1026 1026 2.00 Beta 1 1027 -)))|( % colspan="2" %)(((1028 -**FFI: RequestDockAtReason()/UndockPlayerShip() **changed their return values. 938 +)))|((( 939 +**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. 1029 1029 ))) 1030 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)941 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1031 1031 ((( 1032 1032 //Changed return value type to const char* to better identify failure reasons in Lua script.// 1033 1033 ))) 1034 - 1035 ----- 1036 - 1037 -=== Version 1.50 === 1038 - 1039 -(% class="wrapped" %) 945 +|(% colspan="3" %)(% colspan="3" %) 946 +((( 947 +== 1.50 == 948 +))) 1040 1040 |((( 1041 1041 UI extensions 1042 1042 )))|((( 1043 1043 1.50 Beta 3 1044 -)))|( % colspan="2" %)(((953 +)))|((( 1045 1045 **Lua: GetComponentData() **changed behavior of "docksizes" property. 1046 1046 ))) 1047 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)956 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1048 1048 ((( 1049 1049 //The "docksizes" property no longer includes internal ship storage docks.// 1050 1050 ))) ... ... @@ -1052,10 +1052,10 @@ 1052 1052 All 1053 1053 )))|((( 1054 1054 1.50 Beta 2 1055 -)))|( % colspan="2" %)(((964 +)))|((( 1056 1056 **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR). 1057 1057 ))) 1058 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)967 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1059 1059 ((( 1060 1060 //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".// 1061 1061 ... ... @@ -1067,10 +1067,10 @@ 1067 1067 UI extensions 1068 1068 )))|((( 1069 1069 1.50 Beta 2 1070 -)))|( % colspan="2" %)(((979 +)))|((( 1071 1071 **FFI: UpgradeGroupInfo **datatype was changed. 1072 1072 ))) 1073 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)982 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1074 1074 ((( 1075 1075 //Added new "operational" field to retrieve information about number of operational upgrades in a group.// 1076 1076 ))) ... ... @@ -1080,13 +1080,14 @@ 1080 1080 )))|(% colspan="1" %)(% colspan="1" %) 1081 1081 ((( 1082 1082 1.50 Beta 1 1083 -)))|(% colspan=" 2" %)(% colspan="1" %)992 +)))|(% colspan="1" %)(% colspan="1" %) 1084 1084 ((( 1085 1085 **FFI: SetGuidance()** removed useinfopoint argument. 1086 1086 ))) 1087 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)996 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1088 1088 ((( 1089 -//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.// 998 +//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. 999 +// 1090 1090 1091 1091 //The new function declaration is: void SetGuidance(UniverseID componentid, UIPosRot offset)// 1092 1092 ))) ... ... @@ -1094,44 +1094,40 @@ 1094 1094 UI extensions 1095 1095 )))|((( 1096 1096 1.50 Beta 1 1097 -)))|( % colspan="2" %)(((1007 +)))|((( 1098 1098 **FFI: CancelConstruction() **changed its return value. 1099 1099 ))) 1100 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1010 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1101 1101 ((( 1102 -//CancelConstruction() now returns if the cancellation was successful. // 1012 +(% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. // 1103 1103 ))) 1104 - 1105 ----- 1106 - 1107 -=== Version 1.32 === 1108 - 1109 -(% class="wrapped" %) 1014 +|(% colspan="3" %)(% colspan="3" %) 1015 +((( 1016 +== 1.32 == 1017 +))) 1110 1110 |((( 1111 1111 UI extensions 1112 1112 )))|((( 1113 1113 1.32 1114 -)))|( % colspan="2" %)(((1022 +)))|((( 1115 1115 **Lua: GetComponentData() **removed the "nextdestname" property. 1116 1116 ))) 1117 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1025 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1118 1118 ((( 1119 1119 //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.// 1120 1120 ))) 1121 - 1122 ----- 1123 - 1124 -=== Version 1.20 === 1125 - 1126 -(% class="wrapped" %) 1029 +|(% colspan="3" %)(% colspan="3" %) 1030 +((( 1031 +== 1.20 == 1032 +))) 1127 1127 |((( 1128 1128 UI extensions 1129 1129 )))|((( 1130 1130 1.20 1131 -)))|( % colspan="2" %)(((1037 +)))|((( 1132 1132 **FFI: GetAAOption()** got a new "useconfig" parameter. 1133 1133 ))) 1134 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1040 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1135 1135 ((( 1136 -//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.// 1042 +//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.// 1137 1137 )))
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 - 785778541 +138870946 - url
-
... ... @@ -1,1 +1,1 @@ 1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/ 78577854/Breaking Changes1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/138870946/Breaking Changes