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. klaus1 +xwiki:XWiki.cbj - Content
-
... ... @@ -18,7 +18,6 @@ 18 18 19 19 = Breaking Changes = 20 20 21 -(% class="wrapped" %) 22 22 |=((( 23 23 Type 24 24 )))|=((( ... ... @@ -28,424 +28,13 @@ 28 28 ))) 29 29 |(% colspan="3" %)(% colspan="3" %) 30 30 ((( 31 -== 6.00 == 32 -))) 33 -|((( 34 -Assets 35 -)))|((( 36 -6.00 Beta 1 37 -)))|((( 38 -Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons 39 -))) 40 -|(% 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" %) 41 -((( 42 -//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. 43 -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.// 44 -))) 45 -|(% colspan="1" %)(% colspan="1" %) 46 -((( 47 -Scripts 48 -)))|(% colspan="1" %)(% colspan="1" %) 49 -((( 50 -6.00 Beta 1 51 -)))|(% colspan="1" %)(% colspan="1" %) 52 -((( 53 -Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects 54 -))) 55 -|(% 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" %) 56 -((( 57 -//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.// 58 -))) 59 -|((( 60 -Scripts 61 -)))|((( 62 -6.00 Beta 1 63 -)))|((( 64 -**<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards. 65 -))) 66 -|(% 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" %) 67 -((( 68 -//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.// 69 -))) 70 -|((( 71 -Cutscenes 72 -)))|((( 73 -6.00 Beta 1 74 -)))|((( 75 -Changed behaviour of **<angles>** in cutscenes 76 -))) 77 -|(% colspan="3" %)(% colspan="3" %) 78 -((( 79 -The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees. 80 -))) 81 -|(% colspan="3" %)(% colspan="3" %) 82 -((( 83 -== 5.00 == 84 -))) 85 -|((( 86 -Parameters 87 -)))|((( 88 -5.00 Beta 1 89 -)))|((( 90 -**<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration 91 -))) 92 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 93 -((( 94 -//'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.// 95 -))) 96 -|(% colspan="3" %)(% colspan="3" %) 97 -((( 98 -== 4.10 == 99 -))) 100 -|(% colspan="1" %)(% colspan="1" %) 101 -((( 102 -UI extensions 103 -)))|(% colspan="1" %)(% colspan="1" %) 104 -((( 105 -4.10 Beta 7 106 -)))|(% colspan="1" %)(% colspan="1" %) 107 -((( 108 -**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 109 -))) 110 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 111 -((( 112 -//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.// 113 -))) 114 -|(% colspan="1" %)(% colspan="1" %) 115 -((( 116 -UI extensions 117 -)))|(% colspan="1" %)(% colspan="1" %) 118 -((( 119 -4.10 Beta 6 120 -)))|(% colspan="1" %)(% colspan="1" %) 121 -((( 122 -**FFI**: CustomGameStartPlayerProperty2 changed 123 -))) 124 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 125 -((( 126 -//This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.// 127 -))) 128 -|(% colspan="1" %)(% colspan="1" %) 129 -((( 130 -Parameters 131 -)))|(% colspan="1" %)(% colspan="1" %) 132 -((( 133 -4.10 Beta 3 134 -)))|(% colspan="1" %)(% colspan="1" %) 135 -((( 136 -Renamed **<stationinfobox>** to **<infobox>** 137 -))) 138 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 139 -((( 140 -//Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.// 141 -))) 142 -|(% colspan="1" %)(% colspan="1" %) 143 -((( 144 -UI extensions 145 -)))|(% colspan="1" %)(% colspan="1" %) 146 -((( 147 -4.10 Beta 2 148 -)))|(% colspan="1" %)(% colspan="1" %) 149 -((( 150 -**FFI**: SetMacroMapPlayerSectorOffset() deprecated 151 -))) 152 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 153 -((( 154 -//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.// 155 -))) 156 -|((( 157 -UI extensions 158 -)))|((( 159 -4.10 Beta 2 160 -)))|((( 161 -**FFI**: (% style="color: rgb(0,0,0);" %)FilterComponentForMapMode(%%)() and (% style="color: rgb(0,0,0);" %)SetMapObjectFilter() changed 162 -))) 163 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 164 -((( 165 -//These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.// 166 -))) 167 -|((( 168 -Scripts 169 -)))|((( 170 -4.10 Beta 1 171 -)))|((( 172 -People related attributes of mission** <delivery> **node moved 173 -))) 174 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 175 -((( 176 -//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.// 177 -))) 178 -|(% colspan="1" %)(% colspan="1" %) 179 -((( 180 -Scripts 181 -)))|(% colspan="1" %)(% colspan="1" %) 182 -((( 183 -4.10 Beta 1 184 -)))|(% colspan="1" %)(% colspan="1" %) 185 -((( 186 -**$destructible.productions** replaced with $defensible.productions 187 -))) 188 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 189 -((( 190 -//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.// 191 -))) 192 -|((( 193 -Scripts 194 -)))|((( 195 -4.10 Beta 1 196 -)))|((( 197 -Removed script property **$object.spawnsourceseed** 198 -))) 199 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 200 -((( 201 -//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.// 202 -))) 203 -|(% colspan="3" %)(% colspan="3" %) 204 -((( 205 -== 4.00 == 206 -))) 207 -|(% colspan="1" %)(% colspan="1" %) 208 -((( 209 -UI core 210 -)))|(% colspan="1" %)(% colspan="1" %) 211 -((( 212 -4.00 Beta 10 213 -)))|(% colspan="1" %)(% colspan="1" %) 214 -((( 215 -Controlled ship can change without a **gameplanchange-event** occurring. 216 -))) 217 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 218 -((( 219 -//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). 220 -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. 221 -// 222 -))) 223 -|((( 224 -Scripts 225 -)))|((( 226 -4.00 Beta 7 227 -)))|((( 228 -Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed 229 -))) 230 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 231 -((( 232 -//Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects? 233 -New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits 234 -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// 235 -))) 236 -|(% colspan="1" %)(% colspan="1" %) 237 -((( 238 -UI core 239 -)))|(% colspan="1" %)(% colspan="1" %) 240 -((( 241 -4.00 Beta 6 242 -)))|(% colspan="1" %)(% colspan="1" %) 243 -((( 244 -**FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed 245 -))) 246 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 247 -((( 248 -//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. 249 -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).// 250 - 251 -//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead. 252 -// 253 -))) 254 -|(% colspan="1" %)(% colspan="1" %) 255 -((( 256 -UI core 257 -)))|(% colspan="1" %)(% colspan="1" %) 258 -((( 259 -4.00 Beta 5 260 -)))|(% colspan="1" %)(% colspan="1" %) 261 -((( 262 -**FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed 263 -))) 264 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 265 -((( 266 -//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.// 267 - 268 -//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). 269 -))) 270 -|((( 271 -Parameters 272 -)))|((( 273 -4.00 Beta 1 274 -)))|((( 275 -**requiresconstructionvessel** parameter moved 276 -))) 277 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 278 -((( 279 -//The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.// 280 -))) 281 -|((( 282 -Scripts 283 -)))|((( 284 -4.00 Beta 1 285 -)))|((( 286 -Changed behaviour of **gatedistance** script property 287 -))) 288 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 289 -((( 290 -//The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.// 291 -))) 292 -|(% colspan="3" %)(% colspan="3" %) 293 -((( 294 -== 3.30 == 295 -))) 296 -|((( 297 -UI extensions 298 -)))|((( 299 -3.30 Beta 3 300 -)))|((( 301 -**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()** 302 -))) 303 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 304 -((( 305 -//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()// 306 -))) 307 -|(% colspan="3" %)(% colspan="3" %) 308 -((( 309 -== 3.20 == 310 -))) 311 -|((( 312 -Scripts 313 -)))|((( 314 -3.20 Beta 1 315 -)))|((( 316 -Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed 317 -))) 318 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 319 -((( 320 -//Old params: param = attacked object, param2 = attack method, param3 = attacked component// 321 -//New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon] 322 -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// 323 -))) 324 -|(% colspan="1" %)(% colspan="1" %) 325 -((( 326 -Scripts 327 -)))|(% colspan="1" %)(% colspan="1" %) 328 -((( 329 -3.20 Beta 1 330 -)))|(% colspan="1" %)(% colspan="1" %) 331 -((( 332 -Removed script property $trade.**restriction.faction** 333 -))) 334 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 335 -((( 336 -//$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.// 337 -))) 338 -|((( 339 -UI extensions 340 -)))|((( 341 -3.20 Beta 1 342 -)))|((( 343 -**Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete! 344 -))) 345 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 346 -((( 347 -//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.// 348 -))) 349 -|(% colspan="3" %)(% colspan="3" %) 350 -((( 351 -== 3.10 == 352 -))) 353 -|(% colspan="1" %)(% colspan="1" %) 354 -((( 355 -Scripts 356 -)))|(% colspan="1" %)(% colspan="1" %) 357 -((( 358 -3.10 Beta 1 359 -)))|(% colspan="1" %)(% colspan="1" %) 360 -((( 361 -Removed script action **<add_build/>** 362 -))) 363 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 364 -((( 365 -//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.// 366 -))) 367 -|(% colspan="3" %)(% colspan="3" %) 368 -((( 369 369 == 3.00 == 370 370 ))) 371 371 |(% colspan="1" %)(% colspan="1" %) 372 372 ((( 373 -Scripts 374 -)))|(% colspan="1" %)(% colspan="1" %) 375 -((( 376 -3.0 Beta 6 377 -)))|(% colspan="1" %)(% colspan="1" %) 378 -((( 379 -Changed behaviour of script action **<get_suitable_job/>** 380 -))) 381 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 382 -((( 383 -//<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.// 384 -))) 385 -|(% colspan="1" %)(% colspan="1" %) 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_ware_definition/>** 394 -))) 395 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 396 -((( 397 -//<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.// 398 -))) 399 -|(% colspan="1" %)(% colspan="1" %) 400 -((( 401 401 Global 402 402 )))|(% colspan="1" %)(% colspan="1" %) 403 403 ((( 404 -3.0 Beta 5 405 -)))|(% colspan="1" %)(% colspan="1" %) 406 -((( 407 -Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case 408 -))) 409 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 410 -((( 411 -//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.)\\ 412 - 413 -//Note that this change has no effect on the actual content of scripts or cutscenes. The MD script/cutscene names are stored in the files, regardless of the filenames, so that references to them remain unchanged (e.g., "md.Setup.Start" references a cue in setup.xml).// 414 -))) 415 -|(% colspan="1" %)(% colspan="1" %) 416 -((( 417 -Scripts 418 -)))|(% colspan="1" %)(% colspan="1" %) 419 -((( 420 -3.0 Beta 5 421 -)))|(% colspan="1" %)(% colspan="1" %) 422 -((( 423 -Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions> 424 -))) 425 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 426 -((( 427 -//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.// 428 -))) 429 -|(% colspan="1" %)(% colspan="1" %) 430 -((( 431 -Scripts 432 -)))|(% colspan="1" %)(% colspan="1" %) 433 -((( 434 -3.0 Beta 5 435 -)))|(% colspan="1" %)(% colspan="1" %) 436 -((( 437 -Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos** 438 -))) 439 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 440 -((( 441 -//Before the change, positions are relative to $dockingbay.parent. 442 -After the change, positions are relative to $dockingbay as specified in the documentation.// 443 -))) 444 -|(% colspan="1" %)(% colspan="1" %) 445 -((( 446 -Global 447 -)))|(% colspan="1" %)(% colspan="1" %) 448 -((( 449 449 3.0 Beta 2 450 450 )))|(% colspan="1" %)(% colspan="1" %) 451 451 ((( ... ... @@ -477,7 +477,7 @@ 477 477 3.0 Beta 1 478 478 )))|(% colspan="1" %)(% colspan="1" %) 479 479 ((( 480 - **MissionBoard**support dropped68 +MissionBoard support dropped 481 481 ))) 482 482 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 483 483 ((( ... ... @@ -488,7 +488,7 @@ 488 488 )))|((( 489 489 3.0 Beta 1 490 490 )))|((( 491 -By default, **job/god entries**now only spawn objects in space added by the extension in which they are defined79 +By default, job/god entries now only spawn objects in space added by the extension in which they are defined 492 492 ))) 493 493 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 494 494 ((( ... ... @@ -874,7 +874,7 @@ 874 874 )))|((( 875 875 2.00 Beta 1 876 876 )))|((( 877 -**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter. 465 +**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% class="confluenceTd" %) 878 878 ))) 879 879 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 880 880 ((( ... ... @@ -907,7 +907,7 @@ 907 907 )))|((( 908 908 2.00 Beta 1 909 909 )))|((( 910 -**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. 498 +**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" %) 911 911 ))) 912 912 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 913 913 ((( ... ... @@ -922,7 +922,7 @@ 922 922 )))|((( 923 923 1.50 Beta 3 924 924 )))|((( 925 -**Lua: GetComponentData() **changed behavior of "docksizes" property. 513 +**Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %) 926 926 ))) 927 927 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 928 928 ((( ... ... @@ -948,7 +948,7 @@ 948 948 )))|((( 949 949 1.50 Beta 2 950 950 )))|((( 951 -**FFI: UpgradeGroupInfo **datatype was changed. 539 +**FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %) 952 952 ))) 953 953 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 954 954 ((( ... ... @@ -976,7 +976,7 @@ 976 976 )))|((( 977 977 1.50 Beta 1 978 978 )))|((( 979 -**FFI: CancelConstruction() **changed its return value. 567 +**FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %) 980 980 ))) 981 981 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 982 982 ((( ... ... @@ -1006,7 +1006,7 @@ 1006 1006 )))|((( 1007 1007 1.20 1008 1008 )))|((( 1009 -**FFI: GetAAOption()** got a new "useconfig" parameter. 597 +**FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %) 1010 1010 ))) 1011 1011 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 1012 1012 (((
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 -13 58620091 +89143986 - url
-
... ... @@ -1,1 +1,1 @@ 1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/13 5862009/Breaking Changes1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/89143986/Breaking Changes