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. owen1 +xwiki:XWiki.stefan - Content
-
... ... @@ -18,7 +18,6 @@ 18 18 19 19 = Breaking Changes = 20 20 21 -(% class="wrapped" %) 22 22 |=((( 23 23 Type 24 24 )))|=((( ... ... @@ -28,390 +28,10 @@ 28 28 ))) 29 29 |(% colspan="3" %)(% colspan="3" %) 30 30 ((( 31 -== 6.00 == 32 -))) 33 -|(% colspan="1" %)(% colspan="1" %) 34 -((( 35 -Scripts 36 -)))|(% colspan="1" %)(% colspan="1" %) 37 -((( 38 -6.00 Beta 1 39 -)))|(% colspan="1" %)(% colspan="1" %) 40 -((( 41 -Changed result attribute location for **<get_attackstrength>** 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 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.// 46 -))) 47 -|((( 48 -Assets 49 -)))|((( 50 -6.00 Beta 1 51 -)))|((( 52 -Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons 53 -))) 54 -|(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %) 55 -((( 56 -//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. 57 -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.// 58 -))) 59 -|(% colspan="1" %)(% colspan="1" %) 60 -((( 61 -Scripts 62 -)))|(% colspan="1" %)(% colspan="1" %) 63 -((( 64 -6.00 Beta 1 65 -)))|(% colspan="1" %)(% colspan="1" %) 66 -((( 67 -Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects 68 -))) 69 -|(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %) 70 -((( 71 -//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.// 72 -))) 73 -|((( 74 -Scripts 75 -)))|((( 76 -6.00 Beta 1 77 -)))|((( 78 -**<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards. 79 -))) 80 -|(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %) 81 -((( 82 -//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.// 83 -))) 84 -|((( 85 -Cutscenes 86 -)))|((( 87 -6.00 Beta 1 88 -)))|((( 89 -Changed behaviour of **<angles>** in cutscenes 90 -))) 91 -|(% colspan="3" %)(% colspan="3" %) 92 -((( 93 -The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees. 94 -))) 95 -|(% colspan="3" %)(% colspan="3" %) 96 -((( 97 -== 5.00 == 98 -))) 99 -|((( 100 -Parameters 101 -)))|((( 102 -5.00 Beta 1 103 -)))|((( 104 -**<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration 105 -))) 106 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 107 -((( 108 -//'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.// 109 -))) 110 -|(% colspan="3" %)(% colspan="3" %) 111 -((( 112 -== 4.10 == 113 -))) 114 -|(% colspan="1" %)(% colspan="1" %) 115 -((( 116 -UI extensions 117 -)))|(% colspan="1" %)(% colspan="1" %) 118 -((( 119 -4.10 Beta 7 120 -)))|(% colspan="1" %)(% colspan="1" %) 121 -((( 122 -**FFI**: (% style="color: rgb(0,0,0);" %)SetMapRenderCargoContents(%%)(), (% style="color: rgb(0,0,0);" %)SetMapRenderWorkForceInfo(), (% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)SetMapRenderCrewInfo() and (% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)SetMapRenderDockedShipInfos()(%%) deprecated 123 -))) 124 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 125 -((( 126 -//The functionality represented by (% style="color: rgb(0,0,0);" %)SetMapRenderCargoContents(%%)(), (% style="color: rgb(0,0,0);" %)SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos()(%%) has been removed and the function was therefore stubbed.// 127 -))) 128 -|(% colspan="1" %)(% colspan="1" %) 129 -((( 130 -UI extensions 131 -)))|(% colspan="1" %)(% colspan="1" %) 132 -((( 133 -4.10 Beta 6 134 -)))|(% colspan="1" %)(% colspan="1" %) 135 -((( 136 -**FFI**: CustomGameStartPlayerProperty2 changed 137 -))) 138 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 139 -((( 140 -//This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.// 141 -))) 142 -|(% colspan="1" %)(% colspan="1" %) 143 -((( 144 -Parameters 145 -)))|(% colspan="1" %)(% colspan="1" %) 146 -((( 147 -4.10 Beta 3 148 -)))|(% colspan="1" %)(% colspan="1" %) 149 -((( 150 -Renamed **<stationinfobox>** to **<infobox>** 151 -))) 152 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 153 -((( 154 -//Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.// 155 -))) 156 -|(% colspan="1" %)(% colspan="1" %) 157 -((( 158 -UI extensions 159 -)))|(% colspan="1" %)(% colspan="1" %) 160 -((( 161 -4.10 Beta 2 162 -)))|(% colspan="1" %)(% colspan="1" %) 163 -((( 164 -**FFI**: SetMacroMapPlayerSectorOffset() deprecated 165 -))) 166 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 167 -((( 168 -//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.// 169 -))) 170 -|((( 171 -UI extensions 172 -)))|((( 173 -4.10 Beta 2 174 -)))|((( 175 -**FFI**: (% style="color: rgb(0,0,0);" %)FilterComponentForMapMode(%%)() and (% style="color: rgb(0,0,0);" %)SetMapObjectFilter() changed 176 -))) 177 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 178 -((( 179 -//These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.// 180 -))) 181 -|((( 182 -Scripts 183 -)))|((( 184 -4.10 Beta 1 185 -)))|((( 186 -People related attributes of mission** <delivery> **node moved 187 -))) 188 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 189 -((( 190 -//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.// 191 -))) 192 -|(% colspan="1" %)(% colspan="1" %) 193 -((( 194 -Scripts 195 -)))|(% colspan="1" %)(% colspan="1" %) 196 -((( 197 -4.10 Beta 1 198 -)))|(% colspan="1" %)(% colspan="1" %) 199 -((( 200 -**$destructible.productions** replaced with $defensible.productions 201 -))) 202 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 203 -((( 204 -//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.// 205 -))) 206 -|((( 207 -Scripts 208 -)))|((( 209 -4.10 Beta 1 210 -)))|((( 211 -Removed script property **$object.spawnsourceseed** 212 -))) 213 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 214 -((( 215 -//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.// 216 -))) 217 -|(% colspan="3" %)(% colspan="3" %) 218 -((( 219 -== 4.00 == 220 -))) 221 -|(% colspan="1" %)(% colspan="1" %) 222 -((( 223 -UI core 224 -)))|(% colspan="1" %)(% colspan="1" %) 225 -((( 226 -4.00 Beta 10 227 -)))|(% colspan="1" %)(% colspan="1" %) 228 -((( 229 -Controlled ship can change without a **gameplanchange-event** occurring. 230 -))) 231 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 232 -((( 233 -//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). 234 -In order to support the new emergency eject feature which was added in 4.00 Beta 7, this assurance was dropped. As of 4.00 Beta 10 it is now possible that the ship the player controls can swap without the gameplanchange-event being risen which one could rely upon in previous versions. If your addon relied on the fact that the ship would not change without first going into first person mode, you will have to adjust your addon accordingly. 235 -// 236 -))) 237 -|((( 238 -Scripts 239 -)))|((( 240 -4.00 Beta 7 241 -)))|((( 242 -Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed 243 -))) 244 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 245 -((( 246 -//Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects? 247 -New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits 248 -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// 249 -))) 250 -|(% colspan="1" %)(% colspan="1" %) 251 -((( 252 -UI core 253 -)))|(% colspan="1" %)(% colspan="1" %) 254 -((( 255 -4.00 Beta 6 256 -)))|(% colspan="1" %)(% colspan="1" %) 257 -((( 258 -**FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed 259 -))) 260 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 261 -((( 262 -//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. 263 -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).// 264 - 265 -//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead. 266 -// 267 -))) 268 -|(% colspan="1" %)(% colspan="1" %) 269 -((( 270 -UI core 271 -)))|(% colspan="1" %)(% colspan="1" %) 272 -((( 273 -4.00 Beta 5 274 -)))|(% colspan="1" %)(% colspan="1" %) 275 -((( 276 -**FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed 277 -))) 278 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 279 -((( 280 -//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.// 281 - 282 -//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). 283 -))) 284 -|((( 285 -Parameters 286 -)))|((( 287 -4.00 Beta 1 288 -)))|((( 289 -**requiresconstructionvessel** parameter moved 290 -))) 291 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 292 -((( 293 -//The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.// 294 -))) 295 -|((( 296 -Scripts 297 -)))|((( 298 -4.00 Beta 1 299 -)))|((( 300 -Changed behaviour of **gatedistance** script property 301 -))) 302 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 303 -((( 304 -//The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.// 305 -))) 306 -|(% colspan="3" %)(% colspan="3" %) 307 -((( 308 -== 3.30 == 309 -))) 310 -|((( 311 -UI extensions 312 -)))|((( 313 -3.30 Beta 3 314 -)))|((( 315 -**FFI: **Removed** (% style="color: rgb(0,0,0);" %)GetMissionLimit() (%%)**(% style="color: rgb(0,0,0);" %)and** **(% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)**IsMissionLimit**(%%)**Enabled()** 316 -))) 317 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 318 -((( 319 -//These mission limit-related functions (added in 3.30 Beta 1 and 2) are replaced with FFI (% style="color: rgb(0,0,0);" %)IsMissionLimit(%%)Reach(% style="color: rgb(0,0,0);" %)ed()// 320 -))) 321 -|(% colspan="3" %)(% colspan="3" %) 322 -((( 323 -== 3.20 == 324 -))) 325 -|((( 326 -Scripts 327 -)))|((( 328 -3.20 Beta 1 329 -)))|((( 330 -Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed 331 -))) 332 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 333 -((( 334 -//Old params: param = attacked object, param2 = attack method, param3 = attacked component// 335 -//New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon] 336 -Note that this also means the component attribute to the events is no longer available, so scripts checking the attacked component need to use event.param3.{1} instead// 337 -))) 338 -|(% colspan="1" %)(% colspan="1" %) 339 -((( 340 -Scripts 341 -)))|(% colspan="1" %)(% colspan="1" %) 342 -((( 343 -3.20 Beta 1 344 -)))|(% colspan="1" %)(% colspan="1" %) 345 -((( 346 -Removed script property $trade.**restriction.faction** 347 -))) 348 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 349 -((( 350 -//$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.// 351 -))) 352 -|((( 353 -UI extensions 354 -)))|((( 355 -3.20 Beta 1 356 -)))|((( 357 -**Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete! 358 -))) 359 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 360 -((( 361 -//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.// 362 -))) 363 -|(% colspan="3" %)(% colspan="3" %) 364 -((( 365 -== 3.10 == 366 -))) 367 -|(% colspan="1" %)(% colspan="1" %) 368 -((( 369 -Scripts 370 -)))|(% colspan="1" %)(% colspan="1" %) 371 -((( 372 -3.10 Beta 1 373 -)))|(% colspan="1" %)(% colspan="1" %) 374 -((( 375 -Removed script action **<add_build/>** 376 -))) 377 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 378 -((( 379 -//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.// 380 -))) 381 -|(% colspan="3" %)(% colspan="3" %) 382 -((( 383 383 == 3.00 == 384 384 ))) 385 385 |(% colspan="1" %)(% colspan="1" %) 386 386 ((( 387 -Scripts 388 -)))|(% colspan="1" %)(% colspan="1" %) 389 -((( 390 -3.0 Beta 6 391 -)))|(% colspan="1" %)(% colspan="1" %) 392 -((( 393 -Changed behaviour of script action **<get_suitable_job/>** 394 -))) 395 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 396 -((( 397 -//<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.// 398 -))) 399 -|(% colspan="1" %)(% colspan="1" %) 400 -((( 401 -Scripts 402 -)))|(% colspan="1" %)(% colspan="1" %) 403 -((( 404 -3.0 Beta 6 405 -)))|(% colspan="1" %)(% colspan="1" %) 406 -((( 407 -Changed behaviour of script action **<get_ware_definition/>** 408 -))) 409 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 410 -((( 411 -//<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.// 412 -))) 413 -|(% colspan="1" %)(% colspan="1" %) 414 -((( 415 415 Global 416 416 )))|(% colspan="1" %)(% colspan="1" %) 417 417 ((( ... ... @@ -888,7 +888,7 @@ 888 888 )))|((( 889 889 2.00 Beta 1 890 890 )))|((( 891 -**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter. 510 +**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% class="confluenceTd" %) 892 892 ))) 893 893 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 894 894 ((( ... ... @@ -921,7 +921,7 @@ 921 921 )))|((( 922 922 2.00 Beta 1 923 923 )))|((( 924 -**FFI: (% style="color: rgb(0,0,0);" %)RequestDockAtReason()/(% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)UndockPlayerShip()(%%) **changed their return values. 543 +**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" %) 925 925 ))) 926 926 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 927 927 ((( ... ... @@ -936,7 +936,7 @@ 936 936 )))|((( 937 937 1.50 Beta 3 938 938 )))|((( 939 -**Lua: GetComponentData() **changed behavior of "docksizes" property. 558 +**Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %) 940 940 ))) 941 941 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 942 942 ((( ... ... @@ -962,7 +962,7 @@ 962 962 )))|((( 963 963 1.50 Beta 2 964 964 )))|((( 965 -**FFI: UpgradeGroupInfo **datatype was changed. 584 +**FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %) 966 966 ))) 967 967 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 968 968 ((( ... ... @@ -990,7 +990,7 @@ 990 990 )))|((( 991 991 1.50 Beta 1 992 992 )))|((( 993 -**FFI: CancelConstruction() **changed its return value. 612 +**FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %) 994 994 ))) 995 995 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 996 996 ((( ... ... @@ -1020,7 +1020,7 @@ 1020 1020 )))|((( 1021 1021 1.20 1022 1022 )))|((( 1023 -**FFI: GetAAOption()** got a new "useconfig" parameter. 642 +**FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %) 1024 1024 ))) 1025 1025 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1026 1026 (((
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 - 1358620121 +89825104 - url
-
... ... @@ -1,1 +1,1 @@ 1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/ 135862012/Breaking Changes1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/89825104/Breaking Changes