Changes for page Breaking Changes
Last modified by Michael Baumgardt on 2026/04/17 12:03
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -xwiki:XWiki. florian1 +xwiki:XWiki.cbj - Content
-
... ... @@ -18,6 +18,7 @@ 18 18 19 19 = Breaking Changes = 20 20 21 +(% class="wrapped" %) 21 21 |=((( 22 22 Type 23 23 )))|=((( ... ... @@ -24,12 +24,139 @@ 24 24 Version 25 25 )))|=((( 26 26 Summary 27 -)))|=(% colspan="1" %)(% colspan="1" %) 28 +))) 29 +|(% colspan="3" %)(% colspan="3" %) 28 28 ((( 29 - 31 +== 6.00 == 30 30 ))) 31 -|(% colspan=" 4" %)(% colspan="4" %)33 +|(% colspan="1" %)(% colspan="1" %) 32 32 ((( 35 +Scripts 36 +)))|(% colspan="1" %)(% colspan="1" %) 37 +((( 38 +6.00 Beta 4 39 +)))|(% colspan="1" %)(% colspan="1" %) 40 +((( 41 +Changed conditions for **<event_player_travelmode_started> <event_player_travelmode_stopped> <event_player_travelmode_charge_started> <event_player_travelmode_charge_aborted>** to be raised. 42 +))) 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" %) 44 +((( 45 +//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. // 46 + 47 +//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.// 48 +))) 49 +|(% colspan="1" %)(% colspan="1" %) 50 +((( 51 +Scripts 52 +)))|(% colspan="1" %)(% colspan="1" %) 53 +((( 54 +6.00 Beta 3 55 +)))|(% colspan="1" %)(% colspan="1" %) 56 +((( 57 +Changed result of **<find_object_surface>** action in the case of a failure 58 +))) 59 +|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %) 60 +((( 61 +//The 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.// 62 + 63 +//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.// 64 + 65 +//The action itself has been improved to increase the chance of finding suitable surface positions.// 66 +))) 67 +|(% colspan="1" %)(% colspan="1" %) 68 +((( 69 +Scripts 70 +)))|(% colspan="1" %)(% colspan="1" %) 71 +((( 72 +6.00 Beta 1 73 +)))|(% colspan="1" %)(% colspan="1" %) 74 +((( 75 +Behaviour change for **<match_dock>** script component filter 76 +))) 77 +|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %) 78 +((( 79 +//<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes. 80 +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.// 81 +))) 82 +|(% colspan="1" %)(% colspan="1" %) 83 +((( 84 +Scripts 85 +)))|(% colspan="1" %)(% colspan="1" %) 86 +((( 87 +6.00 Beta 1 88 +)))|(% colspan="1" %)(% colspan="1" %) 89 +((( 90 +Changed result attribute location for **<get_attackstrength>** 91 +))) 92 +|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %) 93 +((( 94 +//The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.// 95 +))) 96 +|((( 97 +Assets 98 +)))|((( 99 +6.00 Beta 1 100 +)))|((( 101 +Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons 102 +))) 103 +|(% 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" %) 104 +((( 105 +//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. 106 +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.// 107 +))) 108 +|(% colspan="1" %)(% colspan="1" %) 109 +((( 110 +Scripts 111 +)))|(% colspan="1" %)(% colspan="1" %) 112 +((( 113 +6.00 Beta 1 114 +)))|(% colspan="1" %)(% colspan="1" %) 115 +((( 116 +Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects 117 +))) 118 +|(% 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" %) 119 +((( 120 +//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.// 121 +))) 122 +|((( 123 +Scripts 124 +)))|((( 125 +6.00 Beta 1 126 +)))|((( 127 +**<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards. 128 +))) 129 +|(% 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" %) 130 +((( 131 +//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.// 132 +))) 133 +|((( 134 +Cutscenes 135 +)))|((( 136 +6.00 Beta 1 137 +)))|((( 138 +Changed behaviour of **<angles>** in cutscenes 139 +))) 140 +|(% 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" %) 141 +((( 142 +//The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.// 143 +))) 144 +|(% colspan="3" %)(% colspan="3" %) 145 +((( 146 +== 5.00 == 147 +))) 148 +|((( 149 +Parameters 150 +)))|((( 151 +5.00 Beta 1 152 +)))|((( 153 +**<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration 154 +))) 155 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 156 +((( 157 +//'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.// 158 +))) 159 +|(% colspan="3" %)(% colspan="3" %) 160 +((( 33 33 == 4.10 == 34 34 ))) 35 35 |(% colspan="1" %)(% colspan="1" %) ... ... @@ -41,16 +41,10 @@ 41 41 )))|(% colspan="1" %)(% colspan="1" %) 42 42 ((( 43 43 **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 - 47 47 ))) 48 48 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 49 49 ((( 50 50 //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 - 54 54 ))) 55 55 |(% colspan="1" %)(% colspan="1" %) 56 56 ((( ... ... @@ -61,16 +61,10 @@ 61 61 )))|(% colspan="1" %)(% colspan="1" %) 62 62 ((( 63 63 **FFI**: CustomGameStartPlayerProperty2 changed 64 -)))|(% colspan="1" %)(% colspan="1" %) 65 -((( 66 - 67 67 ))) 68 68 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 69 69 ((( 70 70 //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 - 74 74 ))) 75 75 |(% colspan="1" %)(% colspan="1" %) 76 76 ((( ... ... @@ -81,16 +81,10 @@ 81 81 )))|(% colspan="1" %)(% colspan="1" %) 82 82 ((( 83 83 Renamed **<stationinfobox>** to **<infobox>** 84 -)))|(% colspan="1" %)(% colspan="1" %) 85 -((( 86 - 87 87 ))) 88 88 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 89 89 ((( 90 90 //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 - 94 94 ))) 95 95 |(% colspan="1" %)(% colspan="1" %) 96 96 ((( ... ... @@ -101,16 +101,10 @@ 101 101 )))|(% colspan="1" %)(% colspan="1" %) 102 102 ((( 103 103 **FFI**: SetMacroMapPlayerSectorOffset() deprecated 104 -)))|(% colspan="1" %)(% colspan="1" %) 105 -((( 106 - 107 107 ))) 108 108 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 109 109 ((( 110 110 //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 - 114 114 ))) 115 115 |((( 116 116 UI extensions ... ... @@ -118,16 +118,10 @@ 118 118 4.10 Beta 2 119 119 )))|((( 120 120 **FFI**: (% style="color: rgb(0,0,0);" %)FilterComponentForMapMode(%%)() and (% style="color: rgb(0,0,0);" %)SetMapObjectFilter() changed 121 -)))|(% colspan="1" %)(% colspan="1" %) 122 -((( 123 - 124 124 ))) 125 125 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 126 126 ((( 127 127 //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 - 131 131 ))) 132 132 |((( 133 133 Scripts ... ... @@ -135,10 +135,8 @@ 135 135 4.10 Beta 1 136 136 )))|((( 137 137 People related attributes of mission** <delivery> **node moved 138 -)))|((( 139 - 140 140 ))) 141 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)237 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 142 142 ((( 143 143 //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.// 144 144 ))) ... ... @@ -151,16 +151,10 @@ 151 151 )))|(% colspan="1" %)(% colspan="1" %) 152 152 ((( 153 153 **$destructible.productions** replaced with $defensible.productions 154 -)))|(% colspan="1" %)(% colspan="1" %) 155 -((( 156 - 157 157 ))) 158 158 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 159 159 ((( 160 160 //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 - 164 164 ))) 165 165 |((( 166 166 Scripts ... ... @@ -168,14 +168,12 @@ 168 168 4.10 Beta 1 169 169 )))|((( 170 170 Removed script property **$object.spawnsourceseed** 171 -)))|((( 172 - 173 173 ))) 174 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)262 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 175 175 ((( 176 176 //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.// 177 177 ))) 178 -|(% colspan=" 4" %)(% colspan="4" %)266 +|(% colspan="3" %)(% colspan="3" %) 179 179 ((( 180 180 == 4.00 == 181 181 ))) ... ... @@ -188,9 +188,6 @@ 188 188 )))|(% colspan="1" %)(% colspan="1" %) 189 189 ((( 190 190 Controlled ship can change without a **gameplanchange-event** occurring. 191 -)))|(% colspan="1" %)(% colspan="1" %) 192 -((( 193 - 194 194 ))) 195 195 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 196 196 ((( ... ... @@ -197,9 +197,6 @@ 197 197 //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). 198 198 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. 199 199 // 200 -)))|(% colspan="1" %)(% colspan="1" %) 201 -((( 202 - 203 203 ))) 204 204 |((( 205 205 Scripts ... ... @@ -207,8 +207,6 @@ 207 207 4.00 Beta 7 208 208 )))|((( 209 209 Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed 210 -)))|((( 211 - 212 212 ))) 213 213 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 214 214 ((( ... ... @@ -215,9 +215,6 @@ 215 215 //Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects? 216 216 New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits 217 217 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 - 221 221 ))) 222 222 |(% colspan="1" %)(% colspan="1" %) 223 223 ((( ... ... @@ -228,9 +228,6 @@ 228 228 )))|(% colspan="1" %)(% colspan="1" %) 229 229 ((( 230 230 **FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed 231 -)))|(% colspan="1" %)(% colspan="1" %) 232 -((( 233 - 234 234 ))) 235 235 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 236 236 ((( ... ... @@ -239,9 +239,6 @@ 239 239 240 240 //If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead. 241 241 // 242 -)))|(% colspan="1" %)(% colspan="1" %) 243 -((( 244 - 245 245 ))) 246 246 |(% colspan="1" %)(% colspan="1" %) 247 247 ((( ... ... @@ -252,9 +252,6 @@ 252 252 )))|(% colspan="1" %)(% colspan="1" %) 253 253 ((( 254 254 **FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed 255 -)))|(% colspan="1" %)(% colspan="1" %) 256 -((( 257 - 258 258 ))) 259 259 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 260 260 ((( ... ... @@ -261,9 +261,6 @@ 261 261 //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.// 262 262 263 263 //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 - 267 267 ))) 268 268 |((( 269 269 Parameters ... ... @@ -271,10 +271,8 @@ 271 271 4.00 Beta 1 272 272 )))|((( 273 273 **requiresconstructionvessel** parameter moved 274 -)))|((( 275 - 276 276 ))) 277 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)340 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 278 278 ((( 279 279 //The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.// 280 280 ))) ... ... @@ -284,17 +284,12 @@ 284 284 4.00 Beta 1 285 285 )))|((( 286 286 Changed behaviour of **gatedistance** script property 287 -)))|((( 288 - 289 289 ))) 290 290 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 291 291 ((( 292 292 //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 - 296 296 ))) 297 -|(% colspan=" 4" %)(% colspan="4" %)355 +|(% colspan="3" %)(% colspan="3" %) 298 298 ((( 299 299 == 3.30 == 300 300 ))) ... ... @@ -304,15 +304,12 @@ 304 304 3.30 Beta 3 305 305 )))|((( 306 306 **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 - 310 310 ))) 311 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)366 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 312 312 ((( 313 313 //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()// 314 314 ))) 315 -|(% colspan=" 4" %)(% colspan="4" %)370 +|(% colspan="3" %)(% colspan="3" %) 316 316 ((( 317 317 == 3.20 == 318 318 ))) ... ... @@ -322,11 +322,8 @@ 322 322 3.20 Beta 1 323 323 )))|((( 324 324 Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed 325 -)))|(% colspan="1" %)(% colspan="1" %) 326 -((( 327 - 328 328 ))) 329 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)381 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 330 330 ((( 331 331 //Old params: param = attacked object, param2 = attack method, param3 = attacked component// 332 332 //New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon] ... ... @@ -341,11 +341,8 @@ 341 341 )))|(% colspan="1" %)(% colspan="1" %) 342 342 ((( 343 343 Removed script property $trade.**restriction.faction** 344 -)))|(% colspan="1" %)(% colspan="1" %) 345 -((( 346 - 347 347 ))) 348 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)397 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 349 349 ((( 350 350 //$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.// 351 351 ))) ... ... @@ -355,15 +355,12 @@ 355 355 3.20 Beta 1 356 356 )))|((( 357 357 **Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete! 358 -)))|(% colspan="1" %)(% colspan="1" %) 359 -((( 360 - 361 361 ))) 362 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)408 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 363 363 ((( 364 364 //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.// 365 365 ))) 366 -|(% colspan=" 4" %)(% colspan="4" %)412 +|(% colspan="3" %)(% colspan="3" %) 367 367 ((( 368 368 == 3.10 == 369 369 ))) ... ... @@ -376,15 +376,12 @@ 376 376 )))|(% colspan="1" %)(% colspan="1" %) 377 377 ((( 378 378 Removed script action **<add_build/>** 379 -)))|(% colspan="1" %)(% colspan="1" %) 380 -((( 381 - 382 382 ))) 383 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)426 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 384 384 ((( 385 385 //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.// 386 386 ))) 387 -|(% colspan=" 4" %)(% colspan="4" %)430 +|(% colspan="3" %)(% colspan="3" %) 388 388 ((( 389 389 == 3.00 == 390 390 ))) ... ... @@ -397,11 +397,8 @@ 397 397 )))|(% colspan="1" %)(% colspan="1" %) 398 398 ((( 399 399 Changed behaviour of script action **<get_suitable_job/>** 400 -)))|(% colspan="1" %)(% colspan="1" %) 401 -((( 402 - 403 403 ))) 404 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)444 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 405 405 ((( 406 406 //<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.// 407 407 ))) ... ... @@ -414,11 +414,8 @@ 414 414 )))|(% colspan="1" %)(% colspan="1" %) 415 415 ((( 416 416 Changed behaviour of script action **<get_ware_definition/>** 417 -)))|(% colspan="1" %)(% colspan="1" %) 418 -((( 419 - 420 420 ))) 421 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)458 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 422 422 ((( 423 423 //<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.// 424 424 ))) ... ... @@ -431,11 +431,8 @@ 431 431 )))|(% colspan="1" %)(% colspan="1" %) 432 432 ((( 433 433 Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case 434 -)))|(% colspan="1" %)(% colspan="1" %) 435 -((( 436 - 437 437 ))) 438 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)472 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 439 439 ((( 440 440 //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.)\\ 441 441 ... ... @@ -450,11 +450,8 @@ 450 450 )))|(% colspan="1" %)(% colspan="1" %) 451 451 ((( 452 452 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 - 456 456 ))) 457 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)488 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 458 458 ((( 459 459 //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.// 460 460 ))) ... ... @@ -467,11 +467,8 @@ 467 467 )))|(% colspan="1" %)(% colspan="1" %) 468 468 ((( 469 469 Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos** 470 -)))|(% colspan="1" %)(% colspan="1" %) 471 -((( 472 - 473 473 ))) 474 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)502 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 475 475 ((( 476 476 //Before the change, positions are relative to $dockingbay.parent. 477 477 After the change, positions are relative to $dockingbay as specified in the documentation.// ... ... @@ -485,11 +485,8 @@ 485 485 )))|(% colspan="1" %)(% colspan="1" %) 486 486 ((( 487 487 Support for entity flag "**skillsvisible**" dropped 488 -)))|(% colspan="1" %)(% colspan="1" %) 489 -((( 490 - 491 491 ))) 492 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)517 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 493 493 ((( 494 494 //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().// 495 495 ))) ... ... @@ -499,11 +499,8 @@ 499 499 3.0 Beta 2 500 500 )))|((( 501 501 Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**. 502 -)))|(% colspan="1" %)(% colspan="1" %) 503 -((( 504 - 505 505 ))) 506 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)528 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 507 507 ((( 508 508 //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. 509 509 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. ... ... @@ -519,11 +519,8 @@ 519 519 )))|(% colspan="1" %)(% colspan="1" %) 520 520 ((( 521 521 **MissionBoard** support dropped 522 -)))|(% colspan="1" %)(% colspan="1" %) 523 -((( 524 - 525 525 ))) 526 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)545 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 527 527 ((( 528 528 //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.// 529 529 ))) ... ... @@ -533,11 +533,8 @@ 533 533 3.0 Beta 1 534 534 )))|((( 535 535 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 - 539 539 ))) 540 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)556 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 541 541 ((( 542 542 //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.// 543 543 ))) ... ... @@ -550,11 +550,8 @@ 550 550 )))|(% colspan="1" %)(% colspan="1" %) 551 551 ((( 552 552 Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'** 553 -)))|(% colspan="1" %)(% colspan="1" %) 554 -((( 555 - 556 556 ))) 557 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)570 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 558 558 ((( 559 559 //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.// 560 560 ))) ... ... @@ -567,11 +567,8 @@ 567 567 )))|(% colspan="1" %)(% colspan="1" %) 568 568 ((( 569 569 Script action **<set_doors_locked/>** attribute **'group'** changed 570 -)))|(% colspan="1" %)(% colspan="1" %) 571 -((( 572 - 573 573 ))) 574 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)584 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 575 575 ((( 576 576 //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.// 577 577 ))) ... ... @@ -584,11 +584,8 @@ 584 584 )))|(% colspan="1" %)(% colspan="1" %) 585 585 ((( 586 586 Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed 587 -)))|(% colspan="1" %)(% colspan="1" %) 588 -((( 589 - 590 590 ))) 591 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)598 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 592 592 ((( 593 593 //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.// 594 594 ))) ... ... @@ -601,11 +601,8 @@ 601 601 )))|(% colspan="1" %)(% colspan="1" %) 602 602 ((( 603 603 Script actions **<set_hack_target/>** and **<abort_hack/>** removed 604 -)))|(% colspan="1" %)(% colspan="1" %) 605 -((( 606 - 607 607 ))) 608 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)612 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 609 609 ((( 610 610 //These actions had no effect and were removed.// 611 611 ))) ... ... @@ -618,11 +618,8 @@ 618 618 )))|(% colspan="1" %)(% colspan="1" %) 619 619 ((( 620 620 **<setup_conversation_minigame/>** script action removed 621 -)))|(% colspan="1" %)(% colspan="1" %) 622 -((( 623 - 624 624 ))) 625 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)626 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 626 626 ((( 627 627 //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.// 628 628 ))) ... ... @@ -635,11 +635,8 @@ 635 635 )))|(% colspan="1" %)(% colspan="1" %) 636 636 ((( 637 637 <add_player_choice_*> **confidence** attribute removed 638 -)))|(% colspan="1" %)(% colspan="1" %) 639 -((( 640 - 641 641 ))) 642 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)640 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 643 643 ((( 644 644 //The default confidence of player options is another leftover from the XR era and had no effect in X4.// 645 645 ))) ... ... @@ -652,11 +652,8 @@ 652 652 )))|(% colspan="1" %)(% colspan="1" %) 653 653 ((( 654 654 **<hack_via_control_panel/>** script action removed 655 -)))|(% colspan="1" %)(% colspan="1" %) 656 -((( 657 - 658 658 ))) 659 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)654 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 660 660 ((( 661 661 //Unused script action <hack_via_control_panel/> was removed.// 662 662 ))) ... ... @@ -669,11 +669,8 @@ 669 669 )))|(% colspan="1" %)(% colspan="1" %) 670 670 ((( 671 671 **Lua: **GetMiniGameCursorPosition() removed 672 -)))|(% colspan="1" %)(% colspan="1" %) 673 -((( 674 - 675 675 ))) 676 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)668 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 677 677 ((( 678 678 //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.// 679 679 ))) ... ... @@ -683,11 +683,8 @@ 683 683 3.0 Beta 1 684 684 )))|((( 685 685 **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders 686 -)))|(% colspan="1" %)(% colspan="1" %) 687 -((( 688 - 689 689 ))) 690 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)679 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 691 691 ((( 692 692 //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.// 693 693 ))) ... ... @@ -700,11 +700,8 @@ 700 700 )))|(% colspan="1" %)(% colspan="1" %) 701 701 ((( 702 702 **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor 703 -)))|(% colspan="1" %)(% colspan="1" %) 704 -((( 705 - 706 706 ))) 707 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)693 +|(% 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 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,11 +717,8 @@ 717 717 )))|(% colspan="1" %)(% colspan="1" %) 718 718 ((( 719 719 **$ware.illegal** updated 720 -)))|(% colspan="1" %)(% colspan="1" %) 721 -((( 722 - 723 723 ))) 724 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)707 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 725 725 ((( 726 726 //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.// 727 727 //It now returns true if $ware is illegal to any faction in the game.// ... ... @@ -735,11 +735,8 @@ 735 735 )))|(% colspan="1" %)(% colspan="1" %) 736 736 ((( 737 737 MD script **RML_Flight_Along_Path** removed 738 -)))|(% colspan="1" %)(% colspan="1" %) 739 -((( 740 - 741 741 ))) 742 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)722 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 743 743 ((( 744 744 //The MD script RML_Flight_Along_Path was not referened and was removed.// 745 745 ))) ... ... @@ -752,11 +752,8 @@ 752 752 )))|(% colspan="1" %)(% colspan="1" %) 753 753 ((( 754 754 parameters of **<event_venture_mission_completed/>** changed 755 -)))|(% colspan="1" %)(% colspan="1" %) 756 -((( 757 - 758 758 ))) 759 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)736 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 760 760 ((( 761 761 //old params: param = venture details, param2 = ships involved, param3 = duration// 762 762 //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration// ... ... @@ -768,11 +768,8 @@ 768 768 )))|((( 769 769 **<set_object_wing_name/>** removed, 770 770 **<set_object_fleet_name/>** added 771 -)))|(% colspan="1" %)(% colspan="1" %) 772 -((( 773 - 774 774 ))) 775 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)749 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 776 776 ((( 777 777 //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>// 778 778 ))) ... ... @@ -783,15 +783,12 @@ 783 783 )))|((( 784 784 **$controllable.wing.*** removed, 785 785 **$controllable.fleet.*** added 786 -)))|(% colspan="1" %)(% colspan="1" %) 787 -((( 788 - 789 789 ))) 790 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)761 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 791 791 ((( 792 792 $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander 793 793 ))) 794 -|(% colspan=" 4" %)(% colspan="4" %)765 +|(% colspan="3" %)(% colspan="3" %) 795 795 ((( 796 796 == 2.60 == 797 797 ))) ... ... @@ -801,11 +801,8 @@ 801 801 2.60 Beta 1 802 802 )))|((( 803 803 '**checkoperational**' filter behaviour changed 804 -)))|(% colspan="1" %)(% colspan="1" %) 805 -((( 806 - 807 807 ))) 808 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)776 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 809 809 ((( 810 810 //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.// 811 811 ... ... @@ -817,15 +817,12 @@ 817 817 2.60 Beta 1 818 818 )))|((( 819 819 $container.**supplyresources** behavior changed 820 -)))|(% colspan="1" %)(% colspan="1" %) 821 -((( 822 - 823 823 ))) 824 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)789 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 825 825 ((( 826 826 //The script keyword $container.supplyresources now includes reserved wares.// 827 827 ))) 828 -|(% colspan=" 4" %)(% colspan="4" %)793 +|(% colspan="3" %)(% colspan="3" %) 829 829 ((( 830 830 == 2.20 == 831 831 ))) ... ... @@ -838,11 +838,8 @@ 838 838 )))|(% colspan="1" %)(% colspan="1" %) 839 839 ((( 840 840 **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined. 841 -)))|(% colspan="1" %)(% colspan="1" %) 842 -((( 843 - 844 844 ))) 845 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)807 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 846 846 ((( 847 847 //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. 848 848 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.// ... ... @@ -859,15 +859,12 @@ 859 859 )))|(% colspan="1" %)(% colspan="1" %) 860 860 ((( 861 861 Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor' 862 -)))|(% colspan="1" %)(% colspan="1" %) 863 -((( 864 - 865 865 ))) 866 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)825 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 867 867 ((( 868 868 //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.// 869 869 ))) 870 -|(% colspan=" 4" %)(% colspan="4" %)829 +|(% colspan="3" %)(% colspan="3" %) 871 871 ((( 872 872 == 2.00 == 873 873 ))) ... ... @@ -880,11 +880,8 @@ 880 880 )))|(% colspan="1" %)(% colspan="1" %) 881 881 ((( 882 882 **<event_build_finished/> **param2 now returns null instead of a construction sequence 883 -)))|(% colspan="1" %)(% colspan="1" %) 884 -((( 885 - 886 886 ))) 887 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)843 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 888 888 ((( 889 889 //The construction sequence which was finished should now be accessed via the buildtask provided via param3.// 890 890 ))) ... ... @@ -897,11 +897,8 @@ 897 897 )))|(% colspan="1" %)(% colspan="1" %) 898 898 ((( 899 899 **param.boarding.{...}** strength parameters removed 900 -)))|(% colspan="1" %)(% colspan="1" %) 901 -((( 902 - 903 903 ))) 904 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)857 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 905 905 ((( 906 906 //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.// 907 907 ))) ... ... @@ -914,11 +914,8 @@ 914 914 )))|(% colspan="1" %)(% colspan="1" %) 915 915 ((( 916 916 **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed 917 -)))|(% colspan="1" %)(% colspan="1" %) 918 -((( 919 - 920 920 ))) 921 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)871 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 922 922 ((( 923 923 //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.// 924 924 ))) ... ... @@ -928,11 +928,8 @@ 928 928 2.00 Beta 1 929 929 )))|((( 930 930 **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals 931 -)))|(% colspan="1" %)(% colspan="1" %) 932 -((( 933 - 934 934 ))) 935 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)882 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 936 936 ((( 937 937 //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.// 938 938 ))) ... ... @@ -942,11 +942,8 @@ 942 942 2.00 Beta 1 943 943 )))|((( 944 944 **FFI: SetFormationShape()** no longer indicates an error upon certain error cases 945 -)))|(% colspan="1" %)(% colspan="1" %) 946 -((( 947 - 948 948 ))) 949 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)893 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 950 950 ((( 951 951 //Before 2.0 Beta 1 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.// 952 952 //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.// ... ... @@ -957,11 +957,8 @@ 957 957 2.00 Beta 1 958 958 )))|((( 959 959 **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated. 960 -)))|(% colspan="1" %)(% colspan="1" %) 961 -((( 962 - 963 963 ))) 964 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)905 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 965 965 ((( 966 966 //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.// 967 967 ))) ... ... @@ -971,11 +971,8 @@ 971 971 2.00 Beta 1 972 972 )))|((( 973 973 **<event_player_changed_target/>** now fires and returns null if the player deselects a target. 974 -)))|(% colspan="1" %)(% colspan="1" %) 975 -((( 976 - 977 977 ))) 978 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)916 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 979 979 ((( 980 980 //For prior behavior, check for event.param being non-null.// 981 981 ))) ... ... @@ -985,11 +985,8 @@ 985 985 2.00 Beta 1 986 986 )))|((( 987 987 **<shoot/>/<shoot_at/>** attribute changes. 988 -)))|(% colspan="1" %)(% colspan="1" %) 989 -((( 990 - 991 991 ))) 992 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)927 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 993 993 ((( 994 994 //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.// 995 995 //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.// ... ... @@ -1002,12 +1002,9 @@ 1002 1002 )))|((( 1003 1003 2.00 Beta 1 1004 1004 )))|((( 1005 -**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% class="confluenceTd" %) 1006 -)))|(% colspan="1" %)(% colspan="1" %) 1007 -((( 1008 - 940 +**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter. 1009 1009 ))) 1010 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)942 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1011 1011 ((( 1012 1012 //Added possibility to query build tasks of a certain buildmodule.// 1013 1013 ))) ... ... @@ -1017,11 +1017,8 @@ 1017 1017 2.00 Beta 1 1018 1018 )))|((( 1019 1019 **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field. 1020 -)))|(% colspan="1" %)(% colspan="1" %) 1021 -((( 1022 - 1023 1023 ))) 1024 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)953 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1025 1025 ((( 1026 1026 //Added list of resources a buildmodule needs to build.// 1027 1027 ))) ... ... @@ -1031,11 +1031,8 @@ 1031 1031 2.00 Beta 1 1032 1032 )))|((( 1033 1033 (% 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 - 1037 1037 ))) 1038 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)964 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1039 1039 ((( 1040 1040 //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.// 1041 1041 ))) ... ... @@ -1044,16 +1044,13 @@ 1044 1044 )))|((( 1045 1045 2.00 Beta 1 1046 1046 )))|((( 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 - 973 +**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. 1051 1051 ))) 1052 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)975 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1053 1053 ((( 1054 1054 //Changed return value type to const char* to better identify failure reasons in Lua script.// 1055 1055 ))) 1056 -|(% colspan=" 4" %)(% colspan="4" %)979 +|(% colspan="3" %)(% colspan="3" %) 1057 1057 ((( 1058 1058 == 1.50 == 1059 1059 ))) ... ... @@ -1062,12 +1062,9 @@ 1062 1062 )))|((( 1063 1063 1.50 Beta 3 1064 1064 )))|((( 1065 -**Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %) 1066 -)))|(% colspan="1" %)(% colspan="1" %) 1067 -((( 1068 - 988 +**Lua: GetComponentData() **changed behavior of "docksizes" property. 1069 1069 ))) 1070 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)990 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1071 1071 ((( 1072 1072 //The "docksizes" property no longer includes internal ship storage docks.// 1073 1073 ))) ... ... @@ -1077,11 +1077,8 @@ 1077 1077 1.50 Beta 2 1078 1078 )))|((( 1079 1079 **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 - 1083 1083 ))) 1084 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)1001 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1085 1085 ((( 1086 1086 //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".// 1087 1087 ... ... @@ -1094,12 +1094,9 @@ 1094 1094 )))|((( 1095 1095 1.50 Beta 2 1096 1096 )))|((( 1097 -**FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %) 1098 -)))|(% colspan="1" %)(% colspan="1" %) 1099 -((( 1100 - 1014 +**FFI: UpgradeGroupInfo **datatype was changed. 1101 1101 ))) 1102 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)1016 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1103 1103 ((( 1104 1104 //Added new "operational" field to retrieve information about number of operational upgrades in a group.// 1105 1105 ))) ... ... @@ -1112,11 +1112,8 @@ 1112 1112 )))|(% colspan="1" %)(% colspan="1" %) 1113 1113 ((( 1114 1114 **FFI: SetGuidance()** removed useinfopoint argument. 1115 -)))|(% colspan="1" %)(% colspan="1" %) 1116 -((( 1117 - 1118 1118 ))) 1119 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)1030 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1120 1120 ((( 1121 1121 //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. 1122 1122 // ... ... @@ -1128,16 +1128,13 @@ 1128 1128 )))|((( 1129 1129 1.50 Beta 1 1130 1130 )))|((( 1131 -**FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %) 1132 -)))|(% colspan="1" %)(% colspan="1" %) 1133 -((( 1134 - 1042 +**FFI: CancelConstruction() **changed its return value. 1135 1135 ))) 1136 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)1044 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1137 1137 ((( 1138 1138 (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. // 1139 1139 ))) 1140 -|(% colspan=" 4" %)(% colspan="4" %)1048 +|(% colspan="3" %)(% colspan="3" %) 1141 1141 ((( 1142 1142 == 1.32 == 1143 1143 ))) ... ... @@ -1147,15 +1147,12 @@ 1147 1147 1.32 1148 1148 )))|((( 1149 1149 **Lua: GetComponentData() **removed the "nextdestname" property. 1150 -)))|(% colspan="1" %)(% colspan="1" %) 1151 -((( 1152 - 1153 1153 ))) 1154 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)1059 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1155 1155 ((( 1156 1156 //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.// 1157 1157 ))) 1158 -|(% colspan=" 4" %)(% colspan="4" %)1063 +|(% colspan="3" %)(% colspan="3" %) 1159 1159 ((( 1160 1160 == 1.20 == 1161 1161 ))) ... ... @@ -1164,12 +1164,9 @@ 1164 1164 )))|((( 1165 1165 1.20 1166 1166 )))|((( 1167 -**FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %) 1168 -)))|(% colspan="1" %)(% colspan="1" %) 1169 -((( 1170 - 1072 +**FFI: GetAAOption()** got a new "useconfig" parameter. 1171 1171 ))) 1172 -|(% class="highlight-grey" colspan=" 4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)1074 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1173 1173 ((( 1174 1174 //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.// 1175 1175 )))
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 -1 068905671 +141329146 - url
-
... ... @@ -1,1 +1,1 @@ 1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/1 06890567/Breaking Changes1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/141329146/Breaking Changes