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.owen - Content
-
... ... @@ -18,6 +18,7 @@ 18 18 19 19 = Breaking Changes = 20 20 21 +(% class="wrapped" %) 21 21 |=((( 22 22 Type 23 23 )))|=((( ... ... @@ -27,6 +27,316 @@ 27 27 ))) 28 28 |(% colspan="3" %)(% colspan="3" %) 29 29 ((( 31 +== 6.00 == 32 +))) 33 +|(% colspan="1" %)(% colspan="1" %) 34 +((( 35 +Scripts 36 +)))|(% colspan="1" %)(% colspan="1" %) 37 +((( 38 +6.00 Beta 3 39 +)))|(% colspan="1" %)(% colspan="1" %) 40 +((( 41 +Changed result of **<find_object_surface>** action in the case of a failure 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 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.// 46 + 47 +//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.// 48 + 49 +//The action itself has been improved to increase the chance of finding suitable surface positions.// 50 +))) 51 +|(% colspan="1" %)(% colspan="1" %) 52 +((( 53 +Scripts 54 +)))|(% colspan="1" %)(% colspan="1" %) 55 +((( 56 +6.00 Beta 1 57 +)))|(% colspan="1" %)(% colspan="1" %) 58 +((( 59 +Behaviour change for **<match_dock>** script component filter 60 +))) 61 +|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %) 62 +((( 63 +//<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes. 64 +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.// 65 +))) 66 +|(% colspan="1" %)(% colspan="1" %) 67 +((( 68 +Scripts 69 +)))|(% colspan="1" %)(% colspan="1" %) 70 +((( 71 +6.00 Beta 1 72 +)))|(% colspan="1" %)(% colspan="1" %) 73 +((( 74 +Changed result attribute location for **<get_attackstrength>** 75 +))) 76 +|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %) 77 +((( 78 +//The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.// 79 +))) 80 +|((( 81 +Assets 82 +)))|((( 83 +6.00 Beta 1 84 +)))|((( 85 +Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons 86 +))) 87 +|(% 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" %) 88 +((( 89 +//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. 90 +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.// 91 +))) 92 +|(% colspan="1" %)(% colspan="1" %) 93 +((( 94 +Scripts 95 +)))|(% colspan="1" %)(% colspan="1" %) 96 +((( 97 +6.00 Beta 1 98 +)))|(% colspan="1" %)(% colspan="1" %) 99 +((( 100 +Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects 101 +))) 102 +|(% 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" %) 103 +((( 104 +//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.// 105 +))) 106 +|((( 107 +Scripts 108 +)))|((( 109 +6.00 Beta 1 110 +)))|((( 111 +**<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards. 112 +))) 113 +|(% 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" %) 114 +((( 115 +//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.// 116 +))) 117 +|((( 118 +Cutscenes 119 +)))|((( 120 +6.00 Beta 1 121 +)))|((( 122 +Changed behaviour of **<angles>** in cutscenes 123 +))) 124 +|(% 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" %) 125 +((( 126 +//The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.// 127 +))) 128 +|(% colspan="3" %)(% colspan="3" %) 129 +((( 130 +== 5.00 == 131 +))) 132 +|((( 133 +Parameters 134 +)))|((( 135 +5.00 Beta 1 136 +)))|((( 137 +**<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration 138 +))) 139 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 140 +((( 141 +//'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.// 142 +))) 143 +|(% colspan="3" %)(% colspan="3" %) 144 +((( 145 +== 4.10 == 146 +))) 147 +|(% colspan="1" %)(% colspan="1" %) 148 +((( 149 +UI extensions 150 +)))|(% colspan="1" %)(% colspan="1" %) 151 +((( 152 +4.10 Beta 7 153 +)))|(% colspan="1" %)(% colspan="1" %) 154 +((( 155 +**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 156 +))) 157 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 158 +((( 159 +//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.// 160 +))) 161 +|(% colspan="1" %)(% colspan="1" %) 162 +((( 163 +UI extensions 164 +)))|(% colspan="1" %)(% colspan="1" %) 165 +((( 166 +4.10 Beta 6 167 +)))|(% colspan="1" %)(% colspan="1" %) 168 +((( 169 +**FFI**: CustomGameStartPlayerProperty2 changed 170 +))) 171 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 172 +((( 173 +//This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.// 174 +))) 175 +|(% colspan="1" %)(% colspan="1" %) 176 +((( 177 +Parameters 178 +)))|(% colspan="1" %)(% colspan="1" %) 179 +((( 180 +4.10 Beta 3 181 +)))|(% colspan="1" %)(% colspan="1" %) 182 +((( 183 +Renamed **<stationinfobox>** to **<infobox>** 184 +))) 185 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 186 +((( 187 +//Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.// 188 +))) 189 +|(% colspan="1" %)(% colspan="1" %) 190 +((( 191 +UI extensions 192 +)))|(% colspan="1" %)(% colspan="1" %) 193 +((( 194 +4.10 Beta 2 195 +)))|(% colspan="1" %)(% colspan="1" %) 196 +((( 197 +**FFI**: SetMacroMapPlayerSectorOffset() deprecated 198 +))) 199 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 200 +((( 201 +//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.// 202 +))) 203 +|((( 204 +UI extensions 205 +)))|((( 206 +4.10 Beta 2 207 +)))|((( 208 +**FFI**: (% style="color: rgb(0,0,0);" %)FilterComponentForMapMode(%%)() and (% style="color: rgb(0,0,0);" %)SetMapObjectFilter() changed 209 +))) 210 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 211 +((( 212 +//These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.// 213 +))) 214 +|((( 215 +Scripts 216 +)))|((( 217 +4.10 Beta 1 218 +)))|((( 219 +People related attributes of mission** <delivery> **node moved 220 +))) 221 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 222 +((( 223 +//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.// 224 +))) 225 +|(% colspan="1" %)(% colspan="1" %) 226 +((( 227 +Scripts 228 +)))|(% colspan="1" %)(% colspan="1" %) 229 +((( 230 +4.10 Beta 1 231 +)))|(% colspan="1" %)(% colspan="1" %) 232 +((( 233 +**$destructible.productions** replaced with $defensible.productions 234 +))) 235 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 236 +((( 237 +//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.// 238 +))) 239 +|((( 240 +Scripts 241 +)))|((( 242 +4.10 Beta 1 243 +)))|((( 244 +Removed script property **$object.spawnsourceseed** 245 +))) 246 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 247 +((( 248 +//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.// 249 +))) 250 +|(% colspan="3" %)(% colspan="3" %) 251 +((( 252 +== 4.00 == 253 +))) 254 +|(% colspan="1" %)(% colspan="1" %) 255 +((( 256 +UI core 257 +)))|(% colspan="1" %)(% colspan="1" %) 258 +((( 259 +4.00 Beta 10 260 +)))|(% colspan="1" %)(% colspan="1" %) 261 +((( 262 +Controlled ship can change without a **gameplanchange-event** occurring. 263 +))) 264 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 265 +((( 266 +//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). 267 +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. 268 +// 269 +))) 270 +|((( 271 +Scripts 272 +)))|((( 273 +4.00 Beta 7 274 +)))|((( 275 +Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed 276 +))) 277 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 278 +((( 279 +//Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects? 280 +New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits 281 +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// 282 +))) 283 +|(% colspan="1" %)(% colspan="1" %) 284 +((( 285 +UI core 286 +)))|(% colspan="1" %)(% colspan="1" %) 287 +((( 288 +4.00 Beta 6 289 +)))|(% colspan="1" %)(% colspan="1" %) 290 +((( 291 +**FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed 292 +))) 293 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 294 +((( 295 +//In order to keep consistency with regards to the new behvior 'hostile' relation state and the older (deprecated) UI functions, the behavior of the deprecated GetFactionRelationStatus() function was changed according to the behavior of the GetRelationStatus()/GetRelationStatus2() functions which was done in the previous beta. 296 +Factions with a relation rating between -20 and -10 will now report a relation status of 'neutral' (aka: 1) instead of 'hostile'/'enemy' (aka: 0).// 297 + 298 +//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead. 299 +// 300 +))) 301 +|(% colspan="1" %)(% colspan="1" %) 302 +((( 303 +UI core 304 +)))|(% colspan="1" %)(% colspan="1" %) 305 +((( 306 +4.00 Beta 5 307 +)))|(% colspan="1" %)(% colspan="1" %) 308 +((( 309 +**FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed 310 +))) 311 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 312 +((( 313 +//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.// 314 + 315 +//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). 316 +))) 317 +|((( 318 +Parameters 319 +)))|((( 320 +4.00 Beta 1 321 +)))|((( 322 +**requiresconstructionvessel** parameter moved 323 +))) 324 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 325 +((( 326 +//The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.// 327 +))) 328 +|((( 329 +Scripts 330 +)))|((( 331 +4.00 Beta 1 332 +)))|((( 333 +Changed behaviour of **gatedistance** script property 334 +))) 335 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 336 +((( 337 +//The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.// 338 +))) 339 +|(% colspan="3" %)(% colspan="3" %) 340 +((( 30 30 == 3.30 == 31 31 ))) 32 32 |((( ... ... @@ -38,7 +38,7 @@ 38 38 ))) 39 39 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 40 40 ((( 41 -//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()//352 +//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()// 42 42 ))) 43 43 |(% colspan="3" %)(% colspan="3" %) 44 44 ((( ... ... @@ -610,7 +610,7 @@ 610 610 )))|((( 611 611 2.00 Beta 1 612 612 )))|((( 613 -**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter. (% class="confluenceTd" %)924 +**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter. 614 614 ))) 615 615 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 616 616 ((( ... ... @@ -643,7 +643,7 @@ 643 643 )))|((( 644 644 2.00 Beta 1 645 645 )))|((( 646 -**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" %)957 +**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. 647 647 ))) 648 648 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 649 649 ((( ... ... @@ -658,7 +658,7 @@ 658 658 )))|((( 659 659 1.50 Beta 3 660 660 )))|((( 661 -**Lua: GetComponentData() **changed behavior of "docksizes" propert ly.(% class="confluenceTd" %)972 +**Lua: GetComponentData() **changed behavior of "docksizes" property. 662 662 ))) 663 663 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 664 664 ((( ... ... @@ -684,7 +684,7 @@ 684 684 )))|((( 685 685 1.50 Beta 2 686 686 )))|((( 687 -**FFI: UpgradeGroupInfo **datatype was changed. (% class="confluenceTd" %)998 +**FFI: UpgradeGroupInfo **datatype was changed. 688 688 ))) 689 689 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 690 690 ((( ... ... @@ -712,7 +712,7 @@ 712 712 )))|((( 713 713 1.50 Beta 1 714 714 )))|((( 715 -**FFI: CancelConstruction() **changed its return value. (% class="confluenceTd" %)1026 +**FFI: CancelConstruction() **changed its return value. 716 716 ))) 717 717 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 718 718 ((( ... ... @@ -742,7 +742,7 @@ 742 742 )))|((( 743 743 1.20 744 744 )))|((( 745 -**FFI: GetAAOption()** got a new "useconfig" parameter. (% class="confluenceTd" %)1056 +**FFI: GetAAOption()** got a new "useconfig" parameter. 746 746 ))) 747 747 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 748 748 (((
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 - 935532691 +138872528 - url
-
... ... @@ -1,1 +1,1 @@ 1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/ 93553269/Breaking Changes1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/138872528/Breaking Changes