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