Changes for page Breaking Changes
Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 114.8
edited by Volodymyr Boichuk
on 2024/04/10 12:52
on 2024/04/10 12:52
Change comment:
There is no comment for this version
To version 103.1
edited by cbj
on 2023/02/20 14:12
on 2023/02/20 14:12
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.cbj - 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,70 +18,18 @@ 18 18 19 19 = Breaking Changes = 20 20 21 -{{toc scope="LOCAL" start="3"/}} 22 - 23 -=== Version 7.00 === 24 - 25 - 26 26 (% class="wrapped" %) 27 -|(% colspan="1" style="width:117px" %)Assets|(% colspan="1" style="width:119px" %)7.00 Beta 1|(% colspan="2" style="width:1625px" %)Renamed some material names and changed file paths for textures. 28 -|(% colspan="4" style="width:117px" %)//Some material names and texture pathes were changed. 29 -Not completele list of texture pathes change~:// 30 -|(% colspan="1" style="width:117px" %)(% colspan="1" %) 31 -((( 32 -Scripts 33 -)))|(% colspan="1" style="width:119px" %)((( 34 -7.00 Beta 1 35 -)))|(% colspan="2" style="width:1625px" %)((( 36 -MD action **<set_presentation_cluster_persistence/>** now requires the cluster to be a presentation cluster. 22 +|=((( 23 +Type 24 +)))|=((( 25 +Version 26 +)))|=((( 27 +Summary 37 37 ))) 38 -|(% c lass="highlight-grey" colspan="4"data-highlight-colour="grey" title="Background colour :"%)(% class="highlight-grey" colspan="3"data-highlight-colour="grey" title="Background colour :"%)29 +|(% colspan="3" %)(% colspan="3" %) 39 39 ((( 40 - //Previously it was possible to set normal clusters to be persistent presentation clusters which was an invalid state.//31 +== 6.00 == 41 41 ))) 42 -|(% colspan="1" style="width:117px" %)(% colspan="1" %) 43 -((( 44 -UI extensions 45 -)))|(% colspan="1" style="width:119px" %)((( 46 -7.00 Beta 1 47 -)))|(% colspan="2" style="width:1625px" %)((( 48 -**FFI**: RemoveBuildPlot() changed 49 -))) 50 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 51 -((( 52 -// 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.// 53 -))) 54 -|(% colspan="1" style="width:117px" %)(% colspan="1" %) 55 -((( 56 -Assets 57 -)))|(% colspan="1" style="width:119px" %)((( 58 -7.00 Beta 1 59 -)))|(% colspan="2" style="width:1625px" %)((( 60 -**Some Split DLC materials moved to base game** 61 -))) 62 -|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 63 -((( 64 -// //"spl_p1_fx" AND "split_p1_hulltexture_01" were moved from Split DLC to base game 65 -))) 66 - 67 ----- 68 - 69 -=== Version 6.00 === 70 - 71 -(% class="wrapped" %) 72 -|((( 73 -Libraries 74 -)))|((( 75 -6.00 Beta 7 76 -)))|(% colspan="2" %)((( 77 -Updated weights for ship groups in shipgroups.xml libraries of base game and all DLCs. 78 -))) 79 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %) 80 -((( 81 -//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.// 82 - 83 -//All groups should now have "weight" parameter added and old "weights" were updated to not have single-digit numbers.// 84 -))) 85 85 |(% colspan="1" %)(% colspan="1" %) 86 86 ((( 87 87 Scripts ... ... @@ -88,11 +88,11 @@ 88 88 )))|(% colspan="1" %)(% colspan="1" %) 89 89 ((( 90 90 6.00 Beta 4 91 -)))|(% colspan=" 2" %)(% colspan="1" %)39 +)))|(% colspan="1" %)(% colspan="1" %) 92 92 ((( 93 93 Changed conditions for **<event_player_travelmode_started> <event_player_travelmode_stopped> <event_player_travelmode_charge_started> <event_player_travelmode_charge_aborted>** to be raised. 94 94 ))) 95 -|(% 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" %) 96 96 ((( 97 97 //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. // 98 98 ... ... @@ -104,11 +104,11 @@ 104 104 )))|(% colspan="1" %)(% colspan="1" %) 105 105 ((( 106 106 6.00 Beta 3 107 -)))|(% colspan=" 2" %)(% colspan="1" %)55 +)))|(% colspan="1" %)(% colspan="1" %) 108 108 ((( 109 109 Changed result of **<find_object_surface>** action in the case of a failure 110 110 ))) 111 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" title="Background colour :"%)(% class="highlight-grey"colspan="3" data-highlight-colour="grey"title="Background colour :"%)59 +|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %) 112 112 ((( 113 113 //The 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.// 114 114 ... ... @@ -122,11 +122,11 @@ 122 122 )))|(% colspan="1" %)(% colspan="1" %) 123 123 ((( 124 124 6.00 Beta 1 125 -)))|(% colspan=" 2" %)(% colspan="1" %)73 +)))|(% colspan="1" %)(% colspan="1" %) 126 126 ((( 127 127 Behaviour change for **<match_dock>** script component filter 128 128 ))) 129 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" title="Background colour :"%)(% class="highlight-grey"colspan="3" data-highlight-colour="grey"title="Background colour :"%)77 +|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %) 130 130 ((( 131 131 //<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes. 132 132 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.// ... ... @@ -137,11 +137,11 @@ 137 137 )))|(% colspan="1" %)(% colspan="1" %) 138 138 ((( 139 139 6.00 Beta 1 140 -)))|(% colspan=" 2" %)(% colspan="1" %)88 +)))|(% colspan="1" %)(% colspan="1" %) 141 141 ((( 142 142 Changed result attribute location for **<get_attackstrength>** 143 143 ))) 144 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" title="Background colour :"%)(% class="highlight-grey"colspan="3" data-highlight-colour="grey"title="Background colour :"%)92 +|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %) 145 145 ((( 146 146 //The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.// 147 147 ))) ... ... @@ -149,10 +149,10 @@ 149 149 Assets 150 150 )))|((( 151 151 6.00 Beta 1 152 -)))|( % colspan="2" %)(((100 +)))|((( 153 153 Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons 154 154 ))) 155 -|(% 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%" %)103 +|(% 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" %) 156 156 ((( 157 157 //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. 158 158 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.// ... ... @@ -163,11 +163,11 @@ 163 163 )))|(% colspan="1" %)(% colspan="1" %) 164 164 ((( 165 165 6.00 Beta 1 166 -)))|(% colspan=" 2" %)(% colspan="1" %)114 +)))|(% colspan="1" %)(% colspan="1" %) 167 167 ((( 168 168 Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects 169 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%" %)118 +|(% 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" %) 171 171 ((( 172 172 //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.// 173 173 ))) ... ... @@ -175,10 +175,10 @@ 175 175 Scripts 176 176 )))|((( 177 177 6.00 Beta 1 178 -)))|( % colspan="2" %)(((126 +)))|((( 179 179 **<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards. 180 180 ))) 181 -|(% 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%" %)129 +|(% 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" %) 182 182 ((( 183 183 //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.// 184 184 ))) ... ... @@ -186,36 +186,32 @@ 186 186 Cutscenes 187 187 )))|((( 188 188 6.00 Beta 1 189 -)))|( % colspan="2" %)(((137 +)))|((( 190 190 Changed behaviour of **<angles>** in cutscenes 191 191 ))) 192 -|(% 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%" %)140 +|(% 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" %) 193 193 ((( 194 194 //The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.// 195 195 ))) 196 - 197 ----- 198 - 199 -=== Version 5.00 === 200 - 201 -(% class="wrapped" %) 144 +|(% colspan="3" %)(% colspan="3" %) 145 +((( 146 +== 5.00 == 147 +))) 202 202 |((( 203 203 Parameters 204 204 )))|((( 205 205 5.00 Beta 1 206 -)))|( % colspan="2" %)(((152 +)))|((( 207 207 **<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration 208 208 ))) 209 -|(% class="highlight-grey" colspan=" 7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)155 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 210 210 ((( 211 211 //'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.// 212 212 ))) 213 - 214 ----- 215 - 216 -=== Version 4.10 === 217 - 218 -(% class="wrapped" %) 159 +|(% colspan="3" %)(% colspan="3" %) 160 +((( 161 +== 4.10 == 162 +))) 219 219 |(% colspan="1" %)(% colspan="1" %) 220 220 ((( 221 221 UI extensions ... ... @@ -222,13 +222,13 @@ 222 222 )))|(% colspan="1" %)(% colspan="1" %) 223 223 ((( 224 224 4.10 Beta 7 225 -)))|(% colspan=" 2" %)(% colspan="1" %)169 +)))|(% colspan="1" %)(% colspan="1" %) 226 226 ((( 227 -**FFI**: SetMapRenderCargoContents(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos() deprecated 171 +**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 228 228 ))) 229 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)173 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 230 230 ((( 231 -//The functionality represented by SetMapRenderCargoContents(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos() has been removed and the function was therefore stubbed.// 175 +//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.// 232 232 ))) 233 233 |(% colspan="1" %)(% colspan="1" %) 234 234 ((( ... ... @@ -236,11 +236,11 @@ 236 236 )))|(% colspan="1" %)(% colspan="1" %) 237 237 ((( 238 238 4.10 Beta 6 239 -)))|(% colspan=" 2" %)(% colspan="1" %)183 +)))|(% colspan="1" %)(% colspan="1" %) 240 240 ((( 241 241 **FFI**: CustomGameStartPlayerProperty2 changed 242 242 ))) 243 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)187 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 244 244 ((( 245 245 //This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.// 246 246 ))) ... ... @@ -250,11 +250,11 @@ 250 250 )))|(% colspan="1" %)(% colspan="1" %) 251 251 ((( 252 252 4.10 Beta 3 253 -)))|(% colspan=" 2" %)(% colspan="1" %)197 +)))|(% colspan="1" %)(% colspan="1" %) 254 254 ((( 255 255 Renamed **<stationinfobox>** to **<infobox>** 256 256 ))) 257 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)201 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 258 258 ((( 259 259 //Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.// 260 260 ))) ... ... @@ -264,11 +264,11 @@ 264 264 )))|(% colspan="1" %)(% colspan="1" %) 265 265 ((( 266 266 4.10 Beta 2 267 -)))|(% colspan=" 2" %)(% colspan="1" %)211 +)))|(% colspan="1" %)(% colspan="1" %) 268 268 ((( 269 269 **FFI**: SetMacroMapPlayerSectorOffset() deprecated 270 270 ))) 271 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)215 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 272 272 ((( 273 273 //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.// 274 274 ))) ... ... @@ -276,10 +276,10 @@ 276 276 UI extensions 277 277 )))|((( 278 278 4.10 Beta 2 279 -)))|( % colspan="2" %)(((280 -**FFI**: FilterComponentForMapMode() and SetMapObjectFilter() changed 223 +)))|((( 224 +**FFI**: (% style="color: rgb(0,0,0);" %)FilterComponentForMapMode(%%)() and (% style="color: rgb(0,0,0);" %)SetMapObjectFilter() changed 281 281 ))) 282 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)226 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 283 283 ((( 284 284 //These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.// 285 285 ))) ... ... @@ -287,10 +287,10 @@ 287 287 Scripts 288 288 )))|((( 289 289 4.10 Beta 1 290 -)))|( % colspan="2" %)(((291 -People related attributes of mission** 234 +)))|((( 235 +People related attributes of mission** <delivery> **node moved 292 292 ))) 293 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)237 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 294 294 ((( 295 295 //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.// 296 296 ))) ... ... @@ -300,11 +300,11 @@ 300 300 )))|(% colspan="1" %)(% colspan="1" %) 301 301 ((( 302 302 4.10 Beta 1 303 -)))|(% colspan=" 2" %)(% colspan="1" %)247 +)))|(% colspan="1" %)(% colspan="1" %) 304 304 ((( 305 305 **$destructible.productions** replaced with $defensible.productions 306 306 ))) 307 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)251 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 308 308 ((( 309 309 //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.// 310 310 ))) ... ... @@ -312,19 +312,17 @@ 312 312 Scripts 313 313 )))|((( 314 314 4.10 Beta 1 315 -)))|( % colspan="2" %)(((259 +)))|((( 316 316 Removed script property **$object.spawnsourceseed** 317 317 ))) 318 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)262 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 319 319 ((( 320 320 //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.// 321 321 ))) 322 - 323 ----- 324 - 325 -=== Version 4.00 === 326 - 327 -(% class="wrapped" %) 266 +|(% colspan="3" %)(% colspan="3" %) 267 +((( 268 +== 4.00 == 269 +))) 328 328 |(% colspan="1" %)(% colspan="1" %) 329 329 ((( 330 330 UI core ... ... @@ -331,23 +331,24 @@ 331 331 )))|(% colspan="1" %)(% colspan="1" %) 332 332 ((( 333 333 4.00 Beta 10 334 -)))|(% colspan=" 2" %)(% colspan="1" %)276 +)))|(% colspan="1" %)(% colspan="1" %) 335 335 ((( 336 336 Controlled ship can change without a **gameplanchange-event** occurring. 337 337 ))) 338 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)280 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 339 339 ((( 340 340 //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). 341 -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.// 283 +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. 284 +// 342 342 ))) 343 343 |((( 344 344 Scripts 345 345 )))|((( 346 346 4.00 Beta 7 347 -)))|( % colspan="2" %)(((290 +)))|((( 348 348 Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed 349 349 ))) 350 -|(% 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" %) 351 351 ((( 352 352 //Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects? 353 353 New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits ... ... @@ -359,16 +359,17 @@ 359 359 )))|(% colspan="1" %)(% colspan="1" %) 360 360 ((( 361 361 4.00 Beta 6 362 -)))|(% colspan=" 2" %)(% colspan="1" %)305 +)))|(% colspan="1" %)(% colspan="1" %) 363 363 ((( 364 364 **FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed 365 365 ))) 366 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)309 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 367 367 ((( 368 368 //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. 369 369 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).// 370 370 371 -//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.// 314 +//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead. 315 +// 372 372 ))) 373 373 |(% colspan="1" %)(% colspan="1" %) 374 374 ((( ... ... @@ -376,11 +376,11 @@ 376 376 )))|(% colspan="1" %)(% colspan="1" %) 377 377 ((( 378 378 4.00 Beta 5 379 -)))|(% colspan=" 2" %)(% colspan="1" %)323 +)))|(% colspan="1" %)(% colspan="1" %) 380 380 ((( 381 381 **FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed 382 382 ))) 383 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)327 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 384 384 ((( 385 385 //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.// 386 386 ... ... @@ -390,10 +390,10 @@ 390 390 Parameters 391 391 )))|((( 392 392 4.00 Beta 1 393 -)))|( % colspan="2" %)(((337 +)))|((( 394 394 **requiresconstructionvessel** parameter moved 395 395 ))) 396 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)340 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 397 397 ((( 398 398 //The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.// 399 399 ))) ... ... @@ -401,44 +401,40 @@ 401 401 Scripts 402 402 )))|((( 403 403 4.00 Beta 1 404 -)))|( % colspan="2" %)(((348 +)))|((( 405 405 Changed behaviour of **gatedistance** script property 406 406 ))) 407 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)351 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 408 408 ((( 409 409 //The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.// 410 410 ))) 411 - 412 ----- 413 - 414 -=== Version 3.30 === 415 - 416 -(% class="wrapped" %) 355 +|(% colspan="3" %)(% colspan="3" %) 356 +((( 357 +== 3.30 == 358 +))) 417 417 |((( 418 418 UI extensions 419 419 )))|((( 420 420 3.30 Beta 3 421 -)))|( % colspan="2" %)(((422 -**FFI: **Removed** 363 +)))|((( 364 +**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()** 423 423 ))) 424 -|(% class="highlight-grey" colspan=" 7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)366 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 425 425 ((( 426 -//These mission limit-related functions (added in 3.30 Beta 1 and 2) are replaced with FFI IsMissionLimitReached()// 368 +//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()// 427 427 ))) 428 - 429 ----- 430 - 431 -=== Version 3.20 === 432 - 433 -(% class="wrapped" %) 370 +|(% colspan="3" %)(% colspan="3" %) 371 +((( 372 +== 3.20 == 373 +))) 434 434 |((( 435 435 Scripts 436 436 )))|((( 437 437 3.20 Beta 1 438 -)))|( % colspan="2" %)(((378 +)))|((( 439 439 Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed 440 440 ))) 441 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)381 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 442 442 ((( 443 443 //Old params: param = attacked object, param2 = attack method, param3 = attacked component// 444 444 //New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon] ... ... @@ -450,11 +450,11 @@ 450 450 )))|(% colspan="1" %)(% colspan="1" %) 451 451 ((( 452 452 3.20 Beta 1 453 -)))|(% colspan=" 2" %)(% colspan="1" %)393 +)))|(% colspan="1" %)(% colspan="1" %) 454 454 ((( 455 455 Removed script property $trade.**restriction.faction** 456 456 ))) 457 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)397 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 458 458 ((( 459 459 //$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.// 460 460 ))) ... ... @@ -462,19 +462,17 @@ 462 462 UI extensions 463 463 )))|((( 464 464 3.20 Beta 1 465 -)))|( % colspan="2" %)(((405 +)))|((( 466 466 **Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete! 467 467 ))) 468 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)408 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 469 469 ((( 470 470 //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.// 471 471 ))) 472 - 473 ----- 474 - 475 -=== Version 3.10 === 476 - 477 -(% class="wrapped" %) 412 +|(% colspan="3" %)(% colspan="3" %) 413 +((( 414 +== 3.10 == 415 +))) 478 478 |(% colspan="1" %)(% colspan="1" %) 479 479 ((( 480 480 Scripts ... ... @@ -481,20 +481,18 @@ 481 481 )))|(% colspan="1" %)(% colspan="1" %) 482 482 ((( 483 483 3.10 Beta 1 484 -)))|(% colspan=" 2" %)(% colspan="1" %)422 +)))|(% colspan="1" %)(% colspan="1" %) 485 485 ((( 486 486 Removed script action **<add_build/>** 487 487 ))) 488 -|(% class="highlight-grey" colspan=" 7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)426 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 489 489 ((( 490 490 //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.// 491 491 ))) 492 - 493 ----- 494 - 495 -=== Version 3.00 === 496 - 497 -(% class="wrapped" %) 430 +|(% colspan="3" %)(% colspan="3" %) 431 +((( 432 +== 3.00 == 433 +))) 498 498 |(% colspan="1" %)(% colspan="1" %) 499 499 ((( 500 500 Scripts ... ... @@ -501,11 +501,11 @@ 501 501 )))|(% colspan="1" %)(% colspan="1" %) 502 502 ((( 503 503 3.0 Beta 6 504 -)))|(% colspan=" 2" %)(% colspan="1" %)440 +)))|(% colspan="1" %)(% colspan="1" %) 505 505 ((( 506 506 Changed behaviour of script action **<get_suitable_job/>** 507 507 ))) 508 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)444 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 509 509 ((( 510 510 //<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.// 511 511 ))) ... ... @@ -515,11 +515,11 @@ 515 515 )))|(% colspan="1" %)(% colspan="1" %) 516 516 ((( 517 517 3.0 Beta 6 518 -)))|(% colspan=" 2" %)(% colspan="1" %)454 +)))|(% colspan="1" %)(% colspan="1" %) 519 519 ((( 520 520 Changed behaviour of script action **<get_ware_definition/>** 521 521 ))) 522 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)458 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 523 523 ((( 524 524 //<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.// 525 525 ))) ... ... @@ -529,13 +529,13 @@ 529 529 )))|(% colspan="1" %)(% colspan="1" %) 530 530 ((( 531 531 3.0 Beta 5 532 -)))|(% colspan=" 2" %)(% colspan="1" %)468 +)))|(% colspan="1" %)(% colspan="1" %) 533 533 ((( 534 534 Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case 535 535 ))) 536 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)472 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 537 537 ((( 538 -//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.) 474 +//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.)\\ 539 539 540 540 //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).// 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" %)484 +)))|(% colspan="1" %)(% colspan="1" %) 549 549 ((( 550 550 Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions> 551 551 ))) 552 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)488 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 553 553 ((( 554 554 //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.// 555 555 ))) ... ... @@ -559,11 +559,11 @@ 559 559 )))|(% colspan="1" %)(% colspan="1" %) 560 560 ((( 561 561 3.0 Beta 5 562 -)))|(% colspan=" 2" %)(% colspan="1" %)498 +)))|(% colspan="1" %)(% colspan="1" %) 563 563 ((( 564 564 Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos** 565 565 ))) 566 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)502 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 567 567 ((( 568 568 //Before the change, positions are relative to $dockingbay.parent. 569 569 After the change, positions are relative to $dockingbay as specified in the documentation.// ... ... @@ -574,11 +574,11 @@ 574 574 )))|(% colspan="1" %)(% colspan="1" %) 575 575 ((( 576 576 3.0 Beta 2 577 -)))|(% colspan=" 2" %)(% colspan="1" %)513 +)))|(% colspan="1" %)(% colspan="1" %) 578 578 ((( 579 579 Support for entity flag "**skillsvisible**" dropped 580 580 ))) 581 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)517 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 582 582 ((( 583 583 //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().// 584 584 ))) ... ... @@ -586,10 +586,10 @@ 586 586 Scripts 587 587 )))|((( 588 588 3.0 Beta 2 589 -)))|( % colspan="2" %)(((525 +)))|((( 590 590 Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**. 591 591 ))) 592 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)528 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 593 593 ((( 594 594 //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. 595 595 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. ... ... @@ -602,11 +602,11 @@ 602 602 )))|(% colspan="1" %)(% colspan="1" %) 603 603 ((( 604 604 3.0 Beta 1 605 -)))|(% colspan=" 2" %)(% colspan="1" %)541 +)))|(% colspan="1" %)(% colspan="1" %) 606 606 ((( 607 607 **MissionBoard** support dropped 608 608 ))) 609 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)545 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 610 610 ((( 611 611 //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.// 612 612 ))) ... ... @@ -614,10 +614,10 @@ 614 614 Job/God 615 615 )))|((( 616 616 3.0 Beta 1 617 -)))|( % colspan="2" %)(((553 +)))|((( 618 618 By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined 619 619 ))) 620 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)556 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 621 621 ((( 622 622 //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.// 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" %)566 +)))|(% colspan="1" %)(% colspan="1" %) 631 631 ((( 632 632 Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'** 633 633 ))) 634 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)570 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 635 635 ((( 636 636 //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.// 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" %)580 +)))|(% colspan="1" %)(% colspan="1" %) 645 645 ((( 646 646 Script action **<set_doors_locked/>** attribute **'group'** changed 647 647 ))) 648 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)584 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 649 649 ((( 650 650 //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.// 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" %)594 +)))|(% colspan="1" %)(% colspan="1" %) 659 659 ((( 660 660 Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed 661 661 ))) 662 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)598 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 663 663 ((( 664 664 //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.// 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" %)608 +)))|(% colspan="1" %)(% colspan="1" %) 673 673 ((( 674 674 Script actions **<set_hack_target/>** and **<abort_hack/>** removed 675 675 ))) 676 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)612 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 677 677 ((( 678 678 //These actions had no effect and were removed.// 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" %)622 +)))|(% colspan="1" %)(% colspan="1" %) 687 687 ((( 688 688 **<setup_conversation_minigame/>** script action removed 689 689 ))) 690 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)626 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 691 691 ((( 692 692 //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.// 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" %)636 +)))|(% colspan="1" %)(% colspan="1" %) 701 701 ((( 702 702 <add_player_choice_*> **confidence** attribute removed 703 703 ))) 704 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)640 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 705 705 ((( 706 706 //The default confidence of player options is another leftover from the XR era and had no effect in X4.// 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" %)650 +)))|(% colspan="1" %)(% colspan="1" %) 715 715 ((( 716 716 **<hack_via_control_panel/>** script action removed 717 717 ))) 718 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)654 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 719 719 ((( 720 720 //Unused script action <hack_via_control_panel/> was removed.// 721 721 ))) ... ... @@ -725,11 +725,11 @@ 725 725 )))|(% colspan="1" %)(% colspan="1" %) 726 726 ((( 727 727 3.0 Beta 1 728 -)))|(% colspan=" 2" %)(% colspan="1" %)664 +)))|(% colspan="1" %)(% colspan="1" %) 729 729 ((( 730 730 **Lua: **GetMiniGameCursorPosition() removed 731 731 ))) 732 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)668 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 733 733 ((( 734 734 //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.// 735 735 ))) ... ... @@ -737,10 +737,10 @@ 737 737 UI core 738 738 )))|((( 739 739 3.0 Beta 1 740 -)))|( % colspan="2" %)(((676 +)))|((( 741 741 **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders 742 742 ))) 743 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)679 +|(% 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 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.// 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" %)689 +)))|(% colspan="1" %)(% colspan="1" %) 754 754 ((( 755 755 **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor 756 756 ))) 757 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)693 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 758 758 ((( 759 759 //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.// 760 760 ))) ... ... @@ -764,11 +764,11 @@ 764 764 )))|(% colspan="1" %)(% colspan="1" %) 765 765 ((( 766 766 3.0 Beta 1 767 -)))|(% colspan=" 2" %)(% colspan="1" %)703 +)))|(% colspan="1" %)(% colspan="1" %) 768 768 ((( 769 769 **$ware.illegal** updated 770 770 ))) 771 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)707 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 772 772 ((( 773 773 //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.// 774 774 //It now returns true if $ware is illegal to any faction in the game.// ... ... @@ -779,11 +779,11 @@ 779 779 )))|(% colspan="1" %)(% colspan="1" %) 780 780 ((( 781 781 3.0 Beta 1 782 -)))|(% colspan=" 2" %)(% colspan="1" %)718 +)))|(% colspan="1" %)(% colspan="1" %) 783 783 ((( 784 784 MD script **RML_Flight_Along_Path** removed 785 785 ))) 786 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)722 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 787 787 ((( 788 788 //The MD script RML_Flight_Along_Path was not referened and was removed.// 789 789 ))) ... ... @@ -793,11 +793,11 @@ 793 793 )))|(% colspan="1" %)(% colspan="1" %) 794 794 ((( 795 795 3.0 Beta 1 796 -)))|(% colspan=" 2" %)(% colspan="1" %)732 +)))|(% colspan="1" %)(% colspan="1" %) 797 797 ((( 798 798 parameters of **<event_venture_mission_completed/>** changed 799 799 ))) 800 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)736 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 801 801 ((( 802 802 //old params: param = venture details, param2 = ships involved, param3 = duration// 803 803 //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration// ... ... @@ -806,11 +806,11 @@ 806 806 Scripts 807 807 )))|((( 808 808 3.0 Beta 1 809 -)))|( % colspan="2" %)(((745 +)))|((( 810 810 **<set_object_wing_name/>** removed, 811 811 **<set_object_fleet_name/>** added 812 812 ))) 813 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)749 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 814 814 ((( 815 815 //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>// 816 816 ))) ... ... @@ -818,28 +818,26 @@ 818 818 Scripts 819 819 )))|((( 820 820 3.0 Beta 1 821 -)))|( % colspan="2" %)(((757 +)))|((( 822 822 **$controllable.wing.*** removed, 823 823 **$controllable.fleet.*** added 824 824 ))) 825 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)761 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 826 826 ((( 827 827 $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander 828 828 ))) 829 - 830 ----- 831 - 832 -=== Version 2.60 === 833 - 834 -(% class="wrapped" %) 765 +|(% colspan="3" %)(% colspan="3" %) 766 +((( 767 +== 2.60 == 768 +))) 835 835 |((( 836 836 Scripts 837 837 )))|((( 838 838 2.60 Beta 1 839 -)))|( % colspan="2" %)(((773 +)))|((( 840 840 '**checkoperational**' filter behaviour changed 841 841 ))) 842 -|(% class="highlight-grey" colspan=" 10" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)776 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 843 843 ((( 844 844 //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.// 845 845 ... ... @@ -849,19 +849,17 @@ 849 849 Scripts 850 850 )))|((( 851 851 2.60 Beta 1 852 -)))|( % colspan="2" %)(((786 +)))|((( 853 853 $container.**supplyresources** behavior changed 854 -))) | | |855 -|(% class="highlight-grey" colspan=" 10" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)788 +))) 789 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 856 856 ((( 857 857 //The script keyword $container.supplyresources now includes reserved wares.// 858 858 ))) 859 - 860 ----- 861 - 862 -=== Version 2.20 === 863 - 864 -(% class="wrapped" %) 793 +|(% colspan="3" %)(% colspan="3" %) 794 +((( 795 +== 2.20 == 796 +))) 865 865 |(% colspan="1" %)(% colspan="1" %) 866 866 ((( 867 867 UI core ... ... @@ -868,16 +868,17 @@ 868 868 )))|(% colspan="1" %)(% colspan="1" %) 869 869 ((( 870 870 2.20 Beta 3/4 871 -)))|(% colspan=" 2" %)(% colspan="1" %)803 +)))|(% colspan="1" %)(% colspan="1" %) 872 872 ((( 873 873 **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined. 874 874 ))) 875 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)807 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 876 876 ((( 877 877 //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. 878 878 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.// 879 879 880 -//It's a pending change to ensure that the returned mode is more reasonable in an upcoming patch. So be aware that another breaking change might be introduced at some point.// 812 +//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. 813 +// 881 881 ))) 882 882 |(% colspan="1" %)(% colspan="1" %) 883 883 ((( ... ... @@ -885,20 +885,18 @@ 885 885 )))|(% colspan="1" %)(% colspan="1" %) 886 886 ((( 887 887 2.20 Beta 3 888 -)))|(% colspan=" 2" %)(% colspan="1" %)821 +)))|(% colspan="1" %)(% colspan="1" %) 889 889 ((( 890 890 Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor' 891 891 ))) 892 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)825 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 893 893 ((( 894 894 //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.// 895 895 ))) 896 - 897 ----- 898 - 899 -=== Version 2.00 === 900 - 901 -(% class="wrapped" %) 829 +|(% colspan="3" %)(% colspan="3" %) 830 +((( 831 +== 2.00 == 832 +))) 902 902 |(% colspan="1" %)(% colspan="1" %) 903 903 ((( 904 904 Scripts ... ... @@ -905,11 +905,11 @@ 905 905 )))|(% colspan="1" %)(% colspan="1" %) 906 906 ((( 907 907 2.00 Beta 1 908 -)))|(% colspan=" 2" %)(% colspan="1" %)839 +)))|(% colspan="1" %)(% colspan="1" %) 909 909 ((( 910 910 **<event_build_finished/> **param2 now returns null instead of a construction sequence 911 911 ))) 912 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)843 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 913 913 ((( 914 914 //The construction sequence which was finished should now be accessed via the buildtask provided via param3.// 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" %)853 +)))|(% colspan="1" %)(% colspan="1" %) 923 923 ((( 924 924 **param.boarding.{...}** strength parameters removed 925 925 ))) 926 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)857 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 927 927 ((( 928 928 //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.// 929 929 ))) ... ... @@ -933,11 +933,11 @@ 933 933 )))|(% colspan="1" %)(% colspan="1" %) 934 934 ((( 935 935 2.00 Beta 1 936 -)))|(% colspan=" 2" %)(% colspan="1" %)867 +)))|(% colspan="1" %)(% colspan="1" %) 937 937 ((( 938 938 **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed 939 939 ))) 940 -|(% 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" %) 941 941 ((( 942 942 //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.// 943 943 ))) ... ... @@ -945,10 +945,10 @@ 945 945 UI extensions 946 946 )))|((( 947 947 2.00 Beta 1 948 -)))|( % colspan="2" %)(((879 +)))|((( 949 949 **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals 950 950 ))) 951 -|(% 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" %) 952 952 ((( 953 953 //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.// 954 954 ))) ... ... @@ -956,10 +956,10 @@ 956 956 UI extensions 957 957 )))|((( 958 958 2.00 Beta 1 959 -)))|( % colspan="2" %)(((890 +)))|((( 960 960 **FFI: SetFormationShape()** no longer indicates an error upon certain error cases 961 961 ))) 962 -|(% 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" %) 963 963 ((( 964 964 //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.// 965 965 //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.// ... ... @@ -968,10 +968,10 @@ 968 968 Scripts 969 969 )))|((( 970 970 2.00 Beta 1 971 -)))|( % colspan="2" %)(((902 +)))|((( 972 972 **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated. 973 973 ))) 974 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)905 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 975 975 ((( 976 976 //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.// 977 977 ))) ... ... @@ -979,10 +979,10 @@ 979 979 Scripts 980 980 )))|((( 981 981 2.00 Beta 1 982 -)))|( % colspan="2" %)(((913 +)))|((( 983 983 **<event_player_changed_target/>** now fires and returns null if the player deselects a target. 984 984 ))) 985 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)916 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 986 986 ((( 987 987 //For prior behavior, check for event.param being non-null.// 988 988 ))) ... ... @@ -990,10 +990,10 @@ 990 990 AI Scripts 991 991 )))|((( 992 992 2.00 Beta 1 993 -)))|( % colspan="2" %)(((924 +)))|((( 994 994 **<shoot/>/<shoot_at/>** attribute changes. 995 995 ))) 996 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)927 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 997 997 ((( 998 998 //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.// 999 999 //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.// ... ... @@ -1005,10 +1005,10 @@ 1005 1005 UI extensions 1006 1006 )))|((( 1007 1007 2.00 Beta 1 1008 -)))|( % colspan="2" %)(((939 +)))|((( 1009 1009 **FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter. 1010 1010 ))) 1011 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)942 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1012 1012 ((( 1013 1013 //Added possibility to query build tasks of a certain buildmodule.// 1014 1014 ))) ... ... @@ -1016,10 +1016,10 @@ 1016 1016 UI extensions 1017 1017 )))|((( 1018 1018 2.00 Beta 1 1019 -)))|( % colspan="2" %)(((950 +)))|((( 1020 1020 **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field. 1021 1021 ))) 1022 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)953 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1023 1023 ((( 1024 1024 //Added list of resources a buildmodule needs to build.// 1025 1025 ))) ... ... @@ -1027,10 +1027,10 @@ 1027 1027 UI extensions 1028 1028 )))|((( 1029 1029 2.00 Beta 1 1030 -)))|( % colspan="2" %)(((1031 -**Lua: 961 +)))|((( 962 +(% 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);" %) 1032 1032 ))) 1033 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)964 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1034 1034 ((( 1035 1035 //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.// 1036 1036 ))) ... ... @@ -1038,27 +1038,25 @@ 1038 1038 UI extensions 1039 1039 )))|((( 1040 1040 2.00 Beta 1 1041 -)))|( % colspan="2" %)(((1042 -**FFI: RequestDockAtReason()/UndockPlayerShip() **changed their return values. 972 +)))|((( 973 +**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. 1043 1043 ))) 1044 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)975 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1045 1045 ((( 1046 1046 //Changed return value type to const char* to better identify failure reasons in Lua script.// 1047 1047 ))) 1048 - 1049 ----- 1050 - 1051 -=== Version 1.50 === 1052 - 1053 -(% class="wrapped" %) 979 +|(% colspan="3" %)(% colspan="3" %) 980 +((( 981 +== 1.50 == 982 +))) 1054 1054 |((( 1055 1055 UI extensions 1056 1056 )))|((( 1057 1057 1.50 Beta 3 1058 -)))|( % colspan="2" %)(((987 +)))|((( 1059 1059 **Lua: GetComponentData() **changed behavior of "docksizes" property. 1060 1060 ))) 1061 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)990 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1062 1062 ((( 1063 1063 //The "docksizes" property no longer includes internal ship storage docks.// 1064 1064 ))) ... ... @@ -1066,10 +1066,10 @@ 1066 1066 All 1067 1067 )))|((( 1068 1068 1.50 Beta 2 1069 -)))|( % colspan="2" %)(((998 +)))|((( 1070 1070 **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR). 1071 1071 ))) 1072 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1001 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1073 1073 ((( 1074 1074 //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".// 1075 1075 ... ... @@ -1081,10 +1081,10 @@ 1081 1081 UI extensions 1082 1082 )))|((( 1083 1083 1.50 Beta 2 1084 -)))|( % colspan="2" %)(((1013 +)))|((( 1085 1085 **FFI: UpgradeGroupInfo **datatype was changed. 1086 1086 ))) 1087 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1016 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1088 1088 ((( 1089 1089 //Added new "operational" field to retrieve information about number of operational upgrades in a group.// 1090 1090 ))) ... ... @@ -1094,13 +1094,14 @@ 1094 1094 )))|(% colspan="1" %)(% colspan="1" %) 1095 1095 ((( 1096 1096 1.50 Beta 1 1097 -)))|(% colspan=" 2" %)(% colspan="1" %)1026 +)))|(% colspan="1" %)(% colspan="1" %) 1098 1098 ((( 1099 1099 **FFI: SetGuidance()** removed useinfopoint argument. 1100 1100 ))) 1101 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1030 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1102 1102 ((( 1103 -//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.// 1032 +//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. 1033 +// 1104 1104 1105 1105 //The new function declaration is: void SetGuidance(UniverseID componentid, UIPosRot offset)// 1106 1106 ))) ... ... @@ -1108,44 +1108,40 @@ 1108 1108 UI extensions 1109 1109 )))|((( 1110 1110 1.50 Beta 1 1111 -)))|( % colspan="2" %)(((1041 +)))|((( 1112 1112 **FFI: CancelConstruction() **changed its return value. 1113 1113 ))) 1114 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1044 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1115 1115 ((( 1116 -//CancelConstruction() now returns if the cancellation was successful. // 1046 +(% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. // 1117 1117 ))) 1118 - 1119 ----- 1120 - 1121 -=== Version 1.32 === 1122 - 1123 -(% class="wrapped" %) 1048 +|(% colspan="3" %)(% colspan="3" %) 1049 +((( 1050 +== 1.32 == 1051 +))) 1124 1124 |((( 1125 1125 UI extensions 1126 1126 )))|((( 1127 1127 1.32 1128 -)))|( % colspan="2" %)(((1056 +)))|((( 1129 1129 **Lua: GetComponentData() **removed the "nextdestname" property. 1130 1130 ))) 1131 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1059 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1132 1132 ((( 1133 1133 //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.// 1134 1134 ))) 1135 - 1136 ----- 1137 - 1138 -=== Version 1.20 === 1139 - 1140 -(% class="wrapped" %) 1063 +|(% colspan="3" %)(% colspan="3" %) 1064 +((( 1065 +== 1.20 == 1066 +))) 1141 1141 |((( 1142 1142 UI extensions 1143 1143 )))|((( 1144 1144 1.20 1145 -)))|( % colspan="2" %)(((1071 +)))|((( 1146 1146 **FFI: GetAAOption()** got a new "useconfig" parameter. 1147 1147 ))) 1148 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1074 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1149 1149 ((( 1150 -//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.// 1076 +//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.// 1151 1151 )))
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 - 785778541 +141329146 - 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/141329146/Breaking Changes