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