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