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