Changes for page Breaking Changes
Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 104.5
edited by Volodymyr Boichuk
on 2023/08/15 12:09
on 2023/08/15 12:09
Change comment:
Update document after refactoring.
To version 94.1
edited by florian
on 2021/08/26 11:06
on 2021/08/26 11:06
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Parent
-
... ... @@ -1,1 +1,0 @@ 1 -X4 Foundations Wiki.Modding Support.WebHome - Author
-
... ... @@ -1,1 +1,1 @@ 1 -xwiki:XWiki. Volodymyr1 +xwiki:XWiki.florian - Content
-
... ... @@ -18,7 +18,6 @@ 18 18 19 19 = Breaking Changes = 20 20 21 -(% class="wrapped" %) 22 22 |=((( 23 23 Type 24 24 )))|=((( ... ... @@ -25,153 +25,12 @@ 25 25 Version 26 26 )))|=((( 27 27 Summary 28 -))) 29 -|(% colspan="3" %)(% colspan="3" %) 27 +)))|=(% colspan="1" %)(% colspan="1" %) 30 30 ((( 31 - ==6.00 ==29 + 32 32 ))) 33 -|((( 34 -Libraries 35 -)))|((( 36 -6.00 Beta 7 37 -)))|((( 38 -Updated weights for ship groups in shipgroups.xml libraries of base game and all DLCs. 39 -))) 40 -|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %) 31 +|(% colspan="4" %)(% colspan="4" %) 41 41 ((( 42 -//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. 43 -// 44 - 45 -//All groups should now have "weight" parameter added and old "weights" were updated to not have single-digit numbers.// 46 -))) 47 -|(% colspan="1" %)(% colspan="1" %) 48 -((( 49 -Scripts 50 -)))|(% colspan="1" %)(% colspan="1" %) 51 -((( 52 -6.00 Beta 4 53 -)))|(% colspan="1" %)(% colspan="1" %) 54 -((( 55 -Changed conditions for **<event_player_travelmode_started> <event_player_travelmode_stopped> <event_player_travelmode_charge_started> <event_player_travelmode_charge_aborted>** to be raised. 56 -))) 57 -|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %) 58 -((( 59 -//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. // 60 - 61 -//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.// 62 -))) 63 -|(% colspan="1" %)(% colspan="1" %) 64 -((( 65 -Scripts 66 -)))|(% colspan="1" %)(% colspan="1" %) 67 -((( 68 -6.00 Beta 3 69 -)))|(% colspan="1" %)(% colspan="1" %) 70 -((( 71 -Changed result of **<find_object_surface>** action in the case of a failure 72 -))) 73 -|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %) 74 -((( 75 -//The 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.// 76 - 77 -//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.// 78 - 79 -//The action itself has been improved to increase the chance of finding suitable surface positions.// 80 -))) 81 -|(% colspan="1" %)(% colspan="1" %) 82 -((( 83 -Scripts 84 -)))|(% colspan="1" %)(% colspan="1" %) 85 -((( 86 -6.00 Beta 1 87 -)))|(% colspan="1" %)(% colspan="1" %) 88 -((( 89 -Behaviour change for **<match_dock>** script component filter 90 -))) 91 -|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %) 92 -((( 93 -//<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes. 94 -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.// 95 -))) 96 -|(% colspan="1" %)(% colspan="1" %) 97 -((( 98 -Scripts 99 -)))|(% colspan="1" %)(% colspan="1" %) 100 -((( 101 -6.00 Beta 1 102 -)))|(% colspan="1" %)(% colspan="1" %) 103 -((( 104 -Changed result attribute location for **<get_attackstrength>** 105 -))) 106 -|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %) 107 -((( 108 -//The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.// 109 -))) 110 -|((( 111 -Assets 112 -)))|((( 113 -6.00 Beta 1 114 -)))|((( 115 -Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons 116 -))) 117 -|(% 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" %) 118 -((( 119 -//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. 120 -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.// 121 -))) 122 -|(% colspan="1" %)(% colspan="1" %) 123 -((( 124 -Scripts 125 -)))|(% colspan="1" %)(% colspan="1" %) 126 -((( 127 -6.00 Beta 1 128 -)))|(% colspan="1" %)(% colspan="1" %) 129 -((( 130 -Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects 131 -))) 132 -|(% 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" %) 133 -((( 134 -//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.// 135 -))) 136 -|((( 137 -Scripts 138 -)))|((( 139 -6.00 Beta 1 140 -)))|((( 141 -**<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards. 142 -))) 143 -|(% 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" %) 144 -((( 145 -//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.// 146 -))) 147 -|((( 148 -Cutscenes 149 -)))|((( 150 -6.00 Beta 1 151 -)))|((( 152 -Changed behaviour of **<angles>** in cutscenes 153 -))) 154 -|(% 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" %) 155 -((( 156 -//The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.// 157 -))) 158 -|(% colspan="3" %)(% colspan="3" %) 159 -((( 160 -== 5.00 == 161 -))) 162 -|((( 163 -Parameters 164 -)))|((( 165 -5.00 Beta 1 166 -)))|((( 167 -**<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration 168 -))) 169 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 170 -((( 171 -//'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.// 172 -))) 173 -|(% colspan="3" %)(% colspan="3" %) 174 -((( 175 175 == 4.10 == 176 176 ))) 177 177 |(% colspan="1" %)(% colspan="1" %) ... ... @@ -183,10 +183,16 @@ 183 183 )))|(% colspan="1" %)(% colspan="1" %) 184 184 ((( 185 185 **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 44 +)))|(% colspan="1" %)(% colspan="1" %) 45 +((( 46 + 186 186 ))) 187 187 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 188 188 ((( 189 189 //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.// 51 +)))|(% colspan="1" %)(% colspan="1" %) 52 +((( 53 + 190 190 ))) 191 191 |(% colspan="1" %)(% colspan="1" %) 192 192 ((( ... ... @@ -197,10 +197,16 @@ 197 197 )))|(% colspan="1" %)(% colspan="1" %) 198 198 ((( 199 199 **FFI**: CustomGameStartPlayerProperty2 changed 64 +)))|(% colspan="1" %)(% colspan="1" %) 65 +((( 66 + 200 200 ))) 201 201 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 202 202 ((( 203 203 //This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.// 71 +)))|(% colspan="1" %)(% colspan="1" %) 72 +((( 73 + 204 204 ))) 205 205 |(% colspan="1" %)(% colspan="1" %) 206 206 ((( ... ... @@ -211,10 +211,16 @@ 211 211 )))|(% colspan="1" %)(% colspan="1" %) 212 212 ((( 213 213 Renamed **<stationinfobox>** to **<infobox>** 84 +)))|(% colspan="1" %)(% colspan="1" %) 85 +((( 86 + 214 214 ))) 215 215 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 216 216 ((( 217 217 //Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.// 91 +)))|(% colspan="1" %)(% colspan="1" %) 92 +((( 93 + 218 218 ))) 219 219 |(% colspan="1" %)(% colspan="1" %) 220 220 ((( ... ... @@ -225,10 +225,16 @@ 225 225 )))|(% colspan="1" %)(% colspan="1" %) 226 226 ((( 227 227 **FFI**: SetMacroMapPlayerSectorOffset() deprecated 104 +)))|(% colspan="1" %)(% colspan="1" %) 105 +((( 106 + 228 228 ))) 229 229 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 230 230 ((( 231 231 //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.// 111 +)))|(% colspan="1" %)(% colspan="1" %) 112 +((( 113 + 232 232 ))) 233 233 |((( 234 234 UI extensions ... ... @@ -236,10 +236,16 @@ 236 236 4.10 Beta 2 237 237 )))|((( 238 238 **FFI**: (% style="color: rgb(0,0,0);" %)FilterComponentForMapMode(%%)() and (% style="color: rgb(0,0,0);" %)SetMapObjectFilter() changed 121 +)))|(% colspan="1" %)(% colspan="1" %) 122 +((( 123 + 239 239 ))) 240 240 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 241 241 ((( 242 242 //These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.// 128 +)))|(% colspan="1" %)(% colspan="1" %) 129 +((( 130 + 243 243 ))) 244 244 |((( 245 245 Scripts ... ... @@ -247,8 +247,10 @@ 247 247 4.10 Beta 1 248 248 )))|((( 249 249 People related attributes of mission** <delivery> **node moved 138 +)))|((( 139 + 250 250 ))) 251 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)141 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 252 252 ((( 253 253 //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.// 254 254 ))) ... ... @@ -261,10 +261,16 @@ 261 261 )))|(% colspan="1" %)(% colspan="1" %) 262 262 ((( 263 263 **$destructible.productions** replaced with $defensible.productions 154 +)))|(% colspan="1" %)(% colspan="1" %) 155 +((( 156 + 264 264 ))) 265 265 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 266 266 ((( 267 267 //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.// 161 +)))|(% colspan="1" %)(% colspan="1" %) 162 +((( 163 + 268 268 ))) 269 269 |((( 270 270 Scripts ... ... @@ -272,12 +272,14 @@ 272 272 4.10 Beta 1 273 273 )))|((( 274 274 Removed script property **$object.spawnsourceseed** 171 +)))|((( 172 + 275 275 ))) 276 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)174 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 277 277 ((( 278 278 //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.// 279 279 ))) 280 -|(% colspan=" 3" %)(% colspan="3" %)178 +|(% colspan="4" %)(% colspan="4" %) 281 281 ((( 282 282 == 4.00 == 283 283 ))) ... ... @@ -290,6 +290,9 @@ 290 290 )))|(% colspan="1" %)(% colspan="1" %) 291 291 ((( 292 292 Controlled ship can change without a **gameplanchange-event** occurring. 191 +)))|(% colspan="1" %)(% colspan="1" %) 192 +((( 193 + 293 293 ))) 294 294 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 295 295 ((( ... ... @@ -296,6 +296,9 @@ 296 296 //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). 297 297 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. 298 298 // 200 +)))|(% colspan="1" %)(% colspan="1" %) 201 +((( 202 + 299 299 ))) 300 300 |((( 301 301 Scripts ... ... @@ -303,6 +303,8 @@ 303 303 4.00 Beta 7 304 304 )))|((( 305 305 Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed 210 +)))|((( 211 + 306 306 ))) 307 307 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 308 308 ((( ... ... @@ -309,6 +309,9 @@ 309 309 //Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects? 310 310 New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits 311 311 Note: param3 only exists in <event_terraforming_project_succeeded> and not in <event_terraforming_project_failed>, but both now have the booleans in a list for consistency// 218 +)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %) 219 +((( 220 + 312 312 ))) 313 313 |(% colspan="1" %)(% colspan="1" %) 314 314 ((( ... ... @@ -319,6 +319,9 @@ 319 319 )))|(% colspan="1" %)(% colspan="1" %) 320 320 ((( 321 321 **FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed 231 +)))|(% colspan="1" %)(% colspan="1" %) 232 +((( 233 + 322 322 ))) 323 323 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 324 324 ((( ... ... @@ -327,6 +327,9 @@ 327 327 328 328 //If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead. 329 329 // 242 +)))|(% colspan="1" %)(% colspan="1" %) 243 +((( 244 + 330 330 ))) 331 331 |(% colspan="1" %)(% colspan="1" %) 332 332 ((( ... ... @@ -337,6 +337,9 @@ 337 337 )))|(% colspan="1" %)(% colspan="1" %) 338 338 ((( 339 339 **FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed 255 +)))|(% colspan="1" %)(% colspan="1" %) 256 +((( 257 + 340 340 ))) 341 341 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 342 342 ((( ... ... @@ -343,6 +343,9 @@ 343 343 //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.// 344 344 345 345 //If you rely on a handling where they are treated like enemies, please use the new GetRelationStatus3() //function which returns the new range for these objects: 1 (meaning 'enemy' (aka: not yet hostile) here with following relations having been shifted up). 264 +)))|(% colspan="1" %)(% colspan="1" %) 265 +((( 266 + 346 346 ))) 347 347 |((( 348 348 Parameters ... ... @@ -350,8 +350,10 @@ 350 350 4.00 Beta 1 351 351 )))|((( 352 352 **requiresconstructionvessel** parameter moved 274 +)))|((( 275 + 353 353 ))) 354 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)277 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 355 355 ((( 356 356 //The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.// 357 357 ))) ... ... @@ -361,12 +361,17 @@ 361 361 4.00 Beta 1 362 362 )))|((( 363 363 Changed behaviour of **gatedistance** script property 287 +)))|((( 288 + 364 364 ))) 365 365 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 366 366 ((( 367 367 //The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.// 293 +)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %) 294 +((( 295 + 368 368 ))) 369 -|(% colspan=" 3" %)(% colspan="3" %)297 +|(% colspan="4" %)(% colspan="4" %) 370 370 ((( 371 371 == 3.30 == 372 372 ))) ... ... @@ -376,12 +376,15 @@ 376 376 3.30 Beta 3 377 377 )))|((( 378 378 **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()** 307 +)))|(% colspan="1" %)(% colspan="1" %) 308 +((( 309 + 379 379 ))) 380 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)311 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 381 381 ((( 382 382 //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()// 383 383 ))) 384 -|(% colspan=" 3" %)(% colspan="3" %)315 +|(% colspan="4" %)(% colspan="4" %) 385 385 ((( 386 386 == 3.20 == 387 387 ))) ... ... @@ -391,8 +391,11 @@ 391 391 3.20 Beta 1 392 392 )))|((( 393 393 Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed 325 +)))|(% colspan="1" %)(% colspan="1" %) 326 +((( 327 + 394 394 ))) 395 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)329 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 396 396 ((( 397 397 //Old params: param = attacked object, param2 = attack method, param3 = attacked component// 398 398 //New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon] ... ... @@ -407,8 +407,11 @@ 407 407 )))|(% colspan="1" %)(% colspan="1" %) 408 408 ((( 409 409 Removed script property $trade.**restriction.faction** 344 +)))|(% colspan="1" %)(% colspan="1" %) 345 +((( 346 + 410 410 ))) 411 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)348 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 412 412 ((( 413 413 //$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.// 414 414 ))) ... ... @@ -418,12 +418,15 @@ 418 418 3.20 Beta 1 419 419 )))|((( 420 420 **Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete! 358 +)))|(% colspan="1" %)(% colspan="1" %) 359 +((( 360 + 421 421 ))) 422 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)362 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 423 423 ((( 424 424 //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.// 425 425 ))) 426 -|(% colspan=" 3" %)(% colspan="3" %)366 +|(% colspan="4" %)(% colspan="4" %) 427 427 ((( 428 428 == 3.10 == 429 429 ))) ... ... @@ -436,12 +436,15 @@ 436 436 )))|(% colspan="1" %)(% colspan="1" %) 437 437 ((( 438 438 Removed script action **<add_build/>** 379 +)))|(% colspan="1" %)(% colspan="1" %) 380 +((( 381 + 439 439 ))) 440 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)383 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 441 441 ((( 442 442 //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.// 443 443 ))) 444 -|(% colspan=" 3" %)(% colspan="3" %)387 +|(% colspan="4" %)(% colspan="4" %) 445 445 ((( 446 446 == 3.00 == 447 447 ))) ... ... @@ -454,8 +454,11 @@ 454 454 )))|(% colspan="1" %)(% colspan="1" %) 455 455 ((( 456 456 Changed behaviour of script action **<get_suitable_job/>** 400 +)))|(% colspan="1" %)(% colspan="1" %) 401 +((( 402 + 457 457 ))) 458 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)404 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 459 459 ((( 460 460 //<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.// 461 461 ))) ... ... @@ -468,8 +468,11 @@ 468 468 )))|(% colspan="1" %)(% colspan="1" %) 469 469 ((( 470 470 Changed behaviour of script action **<get_ware_definition/>** 417 +)))|(% colspan="1" %)(% colspan="1" %) 418 +((( 419 + 471 471 ))) 472 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)421 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 473 473 ((( 474 474 //<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.// 475 475 ))) ... ... @@ -482,8 +482,11 @@ 482 482 )))|(% colspan="1" %)(% colspan="1" %) 483 483 ((( 484 484 Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case 434 +)))|(% colspan="1" %)(% colspan="1" %) 435 +((( 436 + 485 485 ))) 486 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)438 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 487 487 ((( 488 488 //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.)\\ 489 489 ... ... @@ -498,8 +498,11 @@ 498 498 )))|(% colspan="1" %)(% colspan="1" %) 499 499 ((( 500 500 Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions> 453 +)))|(% colspan="1" %)(% colspan="1" %) 454 +((( 455 + 501 501 ))) 502 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)457 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 503 503 ((( 504 504 //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.// 505 505 ))) ... ... @@ -512,8 +512,11 @@ 512 512 )))|(% colspan="1" %)(% colspan="1" %) 513 513 ((( 514 514 Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos** 470 +)))|(% colspan="1" %)(% colspan="1" %) 471 +((( 472 + 515 515 ))) 516 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)474 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 517 517 ((( 518 518 //Before the change, positions are relative to $dockingbay.parent. 519 519 After the change, positions are relative to $dockingbay as specified in the documentation.// ... ... @@ -527,8 +527,11 @@ 527 527 )))|(% colspan="1" %)(% colspan="1" %) 528 528 ((( 529 529 Support for entity flag "**skillsvisible**" dropped 488 +)))|(% colspan="1" %)(% colspan="1" %) 489 +((( 490 + 530 530 ))) 531 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)492 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 532 532 ((( 533 533 //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().// 534 534 ))) ... ... @@ -538,8 +538,11 @@ 538 538 3.0 Beta 2 539 539 )))|((( 540 540 Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**. 502 +)))|(% colspan="1" %)(% colspan="1" %) 503 +((( 504 + 541 541 ))) 542 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)506 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 543 543 ((( 544 544 //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. 545 545 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. ... ... @@ -555,8 +555,11 @@ 555 555 )))|(% colspan="1" %)(% colspan="1" %) 556 556 ((( 557 557 **MissionBoard** support dropped 522 +)))|(% colspan="1" %)(% colspan="1" %) 523 +((( 524 + 558 558 ))) 559 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)526 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 560 560 ((( 561 561 //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.// 562 562 ))) ... ... @@ -566,8 +566,11 @@ 566 566 3.0 Beta 1 567 567 )))|((( 568 568 By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined 536 +)))|(% colspan="1" %)(% colspan="1" %) 537 +((( 538 + 569 569 ))) 570 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)540 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 571 571 ((( 572 572 //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.// 573 573 ))) ... ... @@ -580,8 +580,11 @@ 580 580 )))|(% colspan="1" %)(% colspan="1" %) 581 581 ((( 582 582 Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'** 553 +)))|(% colspan="1" %)(% colspan="1" %) 554 +((( 555 + 583 583 ))) 584 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)557 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 585 585 ((( 586 586 //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.// 587 587 ))) ... ... @@ -594,8 +594,11 @@ 594 594 )))|(% colspan="1" %)(% colspan="1" %) 595 595 ((( 596 596 Script action **<set_doors_locked/>** attribute **'group'** changed 570 +)))|(% colspan="1" %)(% colspan="1" %) 571 +((( 572 + 597 597 ))) 598 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)574 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 599 599 ((( 600 600 //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.// 601 601 ))) ... ... @@ -608,8 +608,11 @@ 608 608 )))|(% colspan="1" %)(% colspan="1" %) 609 609 ((( 610 610 Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed 587 +)))|(% colspan="1" %)(% colspan="1" %) 588 +((( 589 + 611 611 ))) 612 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)591 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 613 613 ((( 614 614 //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.// 615 615 ))) ... ... @@ -622,8 +622,11 @@ 622 622 )))|(% colspan="1" %)(% colspan="1" %) 623 623 ((( 624 624 Script actions **<set_hack_target/>** and **<abort_hack/>** removed 604 +)))|(% colspan="1" %)(% colspan="1" %) 605 +((( 606 + 625 625 ))) 626 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)608 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 627 627 ((( 628 628 //These actions had no effect and were removed.// 629 629 ))) ... ... @@ -636,8 +636,11 @@ 636 636 )))|(% colspan="1" %)(% colspan="1" %) 637 637 ((( 638 638 **<setup_conversation_minigame/>** script action removed 621 +)))|(% colspan="1" %)(% colspan="1" %) 622 +((( 623 + 639 639 ))) 640 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)625 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 641 641 ((( 642 642 //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.// 643 643 ))) ... ... @@ -650,8 +650,11 @@ 650 650 )))|(% colspan="1" %)(% colspan="1" %) 651 651 ((( 652 652 <add_player_choice_*> **confidence** attribute removed 638 +)))|(% colspan="1" %)(% colspan="1" %) 639 +((( 640 + 653 653 ))) 654 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)642 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 655 655 ((( 656 656 //The default confidence of player options is another leftover from the XR era and had no effect in X4.// 657 657 ))) ... ... @@ -664,8 +664,11 @@ 664 664 )))|(% colspan="1" %)(% colspan="1" %) 665 665 ((( 666 666 **<hack_via_control_panel/>** script action removed 655 +)))|(% colspan="1" %)(% colspan="1" %) 656 +((( 657 + 667 667 ))) 668 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)659 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 669 669 ((( 670 670 //Unused script action <hack_via_control_panel/> was removed.// 671 671 ))) ... ... @@ -678,8 +678,11 @@ 678 678 )))|(% colspan="1" %)(% colspan="1" %) 679 679 ((( 680 680 **Lua: **GetMiniGameCursorPosition() removed 672 +)))|(% colspan="1" %)(% colspan="1" %) 673 +((( 674 + 681 681 ))) 682 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)676 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 683 683 ((( 684 684 //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.// 685 685 ))) ... ... @@ -689,8 +689,11 @@ 689 689 3.0 Beta 1 690 690 )))|((( 691 691 **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders 686 +)))|(% colspan="1" %)(% colspan="1" %) 687 +((( 688 + 692 692 ))) 693 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)690 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 694 694 ((( 695 695 //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.// 696 696 ))) ... ... @@ -703,8 +703,11 @@ 703 703 )))|(% colspan="1" %)(% colspan="1" %) 704 704 ((( 705 705 **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor 703 +)))|(% colspan="1" %)(% colspan="1" %) 704 +((( 705 + 706 706 ))) 707 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)707 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 708 708 ((( 709 709 //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.// 710 710 ))) ... ... @@ -717,8 +717,11 @@ 717 717 )))|(% colspan="1" %)(% colspan="1" %) 718 718 ((( 719 719 **$ware.illegal** updated 720 +)))|(% colspan="1" %)(% colspan="1" %) 721 +((( 722 + 720 720 ))) 721 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)724 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 722 722 ((( 723 723 //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.// 724 724 //It now returns true if $ware is illegal to any faction in the game.// ... ... @@ -732,8 +732,11 @@ 732 732 )))|(% colspan="1" %)(% colspan="1" %) 733 733 ((( 734 734 MD script **RML_Flight_Along_Path** removed 738 +)))|(% colspan="1" %)(% colspan="1" %) 739 +((( 740 + 735 735 ))) 736 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)742 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 737 737 ((( 738 738 //The MD script RML_Flight_Along_Path was not referened and was removed.// 739 739 ))) ... ... @@ -746,8 +746,11 @@ 746 746 )))|(% colspan="1" %)(% colspan="1" %) 747 747 ((( 748 748 parameters of **<event_venture_mission_completed/>** changed 755 +)))|(% colspan="1" %)(% colspan="1" %) 756 +((( 757 + 749 749 ))) 750 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)759 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 751 751 ((( 752 752 //old params: param = venture details, param2 = ships involved, param3 = duration// 753 753 //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration// ... ... @@ -759,8 +759,11 @@ 759 759 )))|((( 760 760 **<set_object_wing_name/>** removed, 761 761 **<set_object_fleet_name/>** added 771 +)))|(% colspan="1" %)(% colspan="1" %) 772 +((( 773 + 762 762 ))) 763 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)775 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 764 764 ((( 765 765 //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>// 766 766 ))) ... ... @@ -771,12 +771,15 @@ 771 771 )))|((( 772 772 **$controllable.wing.*** removed, 773 773 **$controllable.fleet.*** added 786 +)))|(% colspan="1" %)(% colspan="1" %) 787 +((( 788 + 774 774 ))) 775 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)790 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 776 776 ((( 777 777 $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander 778 778 ))) 779 -|(% colspan=" 3" %)(% colspan="3" %)794 +|(% colspan="4" %)(% colspan="4" %) 780 780 ((( 781 781 == 2.60 == 782 782 ))) ... ... @@ -786,8 +786,11 @@ 786 786 2.60 Beta 1 787 787 )))|((( 788 788 '**checkoperational**' filter behaviour changed 804 +)))|(% colspan="1" %)(% colspan="1" %) 805 +((( 806 + 789 789 ))) 790 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)808 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 791 791 ((( 792 792 //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.// 793 793 ... ... @@ -799,12 +799,15 @@ 799 799 2.60 Beta 1 800 800 )))|((( 801 801 $container.**supplyresources** behavior changed 820 +)))|(% colspan="1" %)(% colspan="1" %) 821 +((( 822 + 802 802 ))) 803 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)824 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 804 804 ((( 805 805 //The script keyword $container.supplyresources now includes reserved wares.// 806 806 ))) 807 -|(% colspan=" 3" %)(% colspan="3" %)828 +|(% colspan="4" %)(% colspan="4" %) 808 808 ((( 809 809 == 2.20 == 810 810 ))) ... ... @@ -817,8 +817,11 @@ 817 817 )))|(% colspan="1" %)(% colspan="1" %) 818 818 ((( 819 819 **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined. 841 +)))|(% colspan="1" %)(% colspan="1" %) 842 +((( 843 + 820 820 ))) 821 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)845 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 822 822 ((( 823 823 //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. 824 824 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.// ... ... @@ -835,12 +835,15 @@ 835 835 )))|(% colspan="1" %)(% colspan="1" %) 836 836 ((( 837 837 Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor' 862 +)))|(% colspan="1" %)(% colspan="1" %) 863 +((( 864 + 838 838 ))) 839 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)866 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 840 840 ((( 841 841 //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.// 842 842 ))) 843 -|(% colspan=" 3" %)(% colspan="3" %)870 +|(% colspan="4" %)(% colspan="4" %) 844 844 ((( 845 845 == 2.00 == 846 846 ))) ... ... @@ -853,8 +853,11 @@ 853 853 )))|(% colspan="1" %)(% colspan="1" %) 854 854 ((( 855 855 **<event_build_finished/> **param2 now returns null instead of a construction sequence 883 +)))|(% colspan="1" %)(% colspan="1" %) 884 +((( 885 + 856 856 ))) 857 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)887 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 858 858 ((( 859 859 //The construction sequence which was finished should now be accessed via the buildtask provided via param3.// 860 860 ))) ... ... @@ -867,8 +867,11 @@ 867 867 )))|(% colspan="1" %)(% colspan="1" %) 868 868 ((( 869 869 **param.boarding.{...}** strength parameters removed 900 +)))|(% colspan="1" %)(% colspan="1" %) 901 +((( 902 + 870 870 ))) 871 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)904 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 872 872 ((( 873 873 //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.// 874 874 ))) ... ... @@ -881,8 +881,11 @@ 881 881 )))|(% colspan="1" %)(% colspan="1" %) 882 882 ((( 883 883 **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed 917 +)))|(% colspan="1" %)(% colspan="1" %) 918 +((( 919 + 884 884 ))) 885 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)921 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 886 886 ((( 887 887 //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.// 888 888 ))) ... ... @@ -892,8 +892,11 @@ 892 892 2.00 Beta 1 893 893 )))|((( 894 894 **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals 931 +)))|(% colspan="1" %)(% colspan="1" %) 932 +((( 933 + 895 895 ))) 896 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)935 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 897 897 ((( 898 898 //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.// 899 899 ))) ... ... @@ -903,8 +903,11 @@ 903 903 2.00 Beta 1 904 904 )))|((( 905 905 **FFI: SetFormationShape()** no longer indicates an error upon certain error cases 945 +)))|(% colspan="1" %)(% colspan="1" %) 946 +((( 947 + 906 906 ))) 907 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)949 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 908 908 ((( 909 909 //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.// 910 910 //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.// ... ... @@ -915,8 +915,11 @@ 915 915 2.00 Beta 1 916 916 )))|((( 917 917 **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated. 960 +)))|(% colspan="1" %)(% colspan="1" %) 961 +((( 962 + 918 918 ))) 919 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)964 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 920 920 ((( 921 921 //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.// 922 922 ))) ... ... @@ -926,8 +926,11 @@ 926 926 2.00 Beta 1 927 927 )))|((( 928 928 **<event_player_changed_target/>** now fires and returns null if the player deselects a target. 974 +)))|(% colspan="1" %)(% colspan="1" %) 975 +((( 976 + 929 929 ))) 930 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)978 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 931 931 ((( 932 932 //For prior behavior, check for event.param being non-null.// 933 933 ))) ... ... @@ -937,8 +937,11 @@ 937 937 2.00 Beta 1 938 938 )))|((( 939 939 **<shoot/>/<shoot_at/>** attribute changes. 988 +)))|(% colspan="1" %)(% colspan="1" %) 989 +((( 990 + 940 940 ))) 941 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)992 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 942 942 ((( 943 943 //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.// 944 944 //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.// ... ... @@ -951,9 +951,12 @@ 951 951 )))|((( 952 952 2.00 Beta 1 953 953 )))|((( 954 -**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter. 1005 +**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% class="confluenceTd" %) 1006 +)))|(% colspan="1" %)(% colspan="1" %) 1007 +((( 1008 + 955 955 ))) 956 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1010 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 957 957 ((( 958 958 //Added possibility to query build tasks of a certain buildmodule.// 959 959 ))) ... ... @@ -963,8 +963,11 @@ 963 963 2.00 Beta 1 964 964 )))|((( 965 965 **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field. 1020 +)))|(% colspan="1" %)(% colspan="1" %) 1021 +((( 1022 + 966 966 ))) 967 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1024 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 968 968 ((( 969 969 //Added list of resources a buildmodule needs to build.// 970 970 ))) ... ... @@ -974,8 +974,11 @@ 974 974 2.00 Beta 1 975 975 )))|((( 976 976 (% 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);" %) 1034 +)))|(% colspan="1" %)(% colspan="1" %) 1035 +((( 1036 + 977 977 ))) 978 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1038 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 979 979 ((( 980 980 //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.// 981 981 ))) ... ... @@ -984,13 +984,16 @@ 984 984 )))|((( 985 985 2.00 Beta 1 986 986 )))|((( 987 -**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. 1047 +**FFI: (% style="color: rgb(0,0,0);" %)RequestDockAtReason()/(% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)UndockPlayerShip()(%%) **changed their return values.(% style="color: rgb(0,0,0);" class="confluenceTd" %) 1048 +)))|(% colspan="1" %)(% colspan="1" %) 1049 +((( 1050 + 988 988 ))) 989 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1052 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 990 990 ((( 991 991 //Changed return value type to const char* to better identify failure reasons in Lua script.// 992 992 ))) 993 -|(% colspan=" 3" %)(% colspan="3" %)1056 +|(% colspan="4" %)(% colspan="4" %) 994 994 ((( 995 995 == 1.50 == 996 996 ))) ... ... @@ -999,9 +999,12 @@ 999 999 )))|((( 1000 1000 1.50 Beta 3 1001 1001 )))|((( 1002 -**Lua: GetComponentData() **changed behavior of "docksizes" property. 1065 +**Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %) 1066 +)))|(% colspan="1" %)(% colspan="1" %) 1067 +((( 1068 + 1003 1003 ))) 1004 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1070 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 1005 1005 ((( 1006 1006 //The "docksizes" property no longer includes internal ship storage docks.// 1007 1007 ))) ... ... @@ -1011,8 +1011,11 @@ 1011 1011 1.50 Beta 2 1012 1012 )))|((( 1013 1013 **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR). 1080 +)))|(% colspan="1" %)(% colspan="1" %) 1081 +((( 1082 + 1014 1014 ))) 1015 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1084 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 1016 1016 ((( 1017 1017 //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".// 1018 1018 ... ... @@ -1025,9 +1025,12 @@ 1025 1025 )))|((( 1026 1026 1.50 Beta 2 1027 1027 )))|((( 1028 -**FFI: UpgradeGroupInfo **datatype was changed. 1097 +**FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %) 1098 +)))|(% colspan="1" %)(% colspan="1" %) 1099 +((( 1100 + 1029 1029 ))) 1030 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1102 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 1031 1031 ((( 1032 1032 //Added new "operational" field to retrieve information about number of operational upgrades in a group.// 1033 1033 ))) ... ... @@ -1040,8 +1040,11 @@ 1040 1040 )))|(% colspan="1" %)(% colspan="1" %) 1041 1041 ((( 1042 1042 **FFI: SetGuidance()** removed useinfopoint argument. 1115 +)))|(% colspan="1" %)(% colspan="1" %) 1116 +((( 1117 + 1043 1043 ))) 1044 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1119 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 1045 1045 ((( 1046 1046 //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. 1047 1047 // ... ... @@ -1053,13 +1053,16 @@ 1053 1053 )))|((( 1054 1054 1.50 Beta 1 1055 1055 )))|((( 1056 -**FFI: CancelConstruction() **changed its return value. 1131 +**FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %) 1132 +)))|(% colspan="1" %)(% colspan="1" %) 1133 +((( 1134 + 1057 1057 ))) 1058 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1136 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 1059 1059 ((( 1060 1060 (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. // 1061 1061 ))) 1062 -|(% colspan=" 3" %)(% colspan="3" %)1140 +|(% colspan="4" %)(% colspan="4" %) 1063 1063 ((( 1064 1064 == 1.32 == 1065 1065 ))) ... ... @@ -1069,12 +1069,15 @@ 1069 1069 1.32 1070 1070 )))|((( 1071 1071 **Lua: GetComponentData() **removed the "nextdestname" property. 1150 +)))|(% colspan="1" %)(% colspan="1" %) 1151 +((( 1152 + 1072 1072 ))) 1073 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1154 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 1074 1074 ((( 1075 1075 //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.// 1076 1076 ))) 1077 -|(% colspan=" 3" %)(% colspan="3" %)1158 +|(% colspan="4" %)(% colspan="4" %) 1078 1078 ((( 1079 1079 == 1.20 == 1080 1080 ))) ... ... @@ -1083,9 +1083,12 @@ 1083 1083 )))|((( 1084 1084 1.20 1085 1085 )))|((( 1086 -**FFI: GetAAOption()** got a new "useconfig" parameter. 1167 +**FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %) 1168 +)))|(% colspan="1" %)(% colspan="1" %) 1169 +((( 1170 + 1087 1087 ))) 1088 -|(% class="highlight-grey" colspan=" 3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)1172 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 1089 1089 ((( 1090 1090 //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.// 1091 1091 )))
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 - 785778541 +106890567 - 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/106890567/Breaking Changes