Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03

Manage
- Copy
Actions
- Export
- Print Preview

From 124.7 to 124.6 From 146.1 to 145.1

From version 145.1

edited by Matthias Haan
on 2026/02/16 13:09

Change comment: There is no comment for this version

To version 124.7

edited by Klaus Meyer
on 2025/01/07 16:42

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

@@ -1,1 +1,1 @@
--xwiki:XWiki.Matthias
++xwiki:XWiki.Klaus

Content

@@ -20,55 +20,11 @@
  {{toc scope="LOCAL" start="3"/}}
--=== Version 9.00 ===
--
--(% class="table-striped" %)
--|(% colspan="1" style="width:117px" %)Scripts|(% colspan="1" style="width:119px" %)9.00 Beta 1|(% colspan="4" style="width:1625px" %)Removed script action **<get_highest_resource_yield>**
--|(% colspan="6" style="width:117px" %)A new property that can be used in its place is **$sector.bestyieldrating.{$ware}**.
--|(% colspan="1" style="width:117px" %)Scripts|(% colspan="1" style="width:119px" %)9.00 Beta 1|(% colspan="4" style="width:1625px" %)Removed **<find_asteroid_in_cluster>** and **<find_recyclable_in_cluster>**
--|(% colspan="6" style="width:117px" %)**<find_asteroid_with_yield_in_sector>** and **<find_recyclable_with_yield_in_sector>** should now be used instead.
--|(% colspan="1" style="width:117px" %)Parameters|(% colspan="1" style="width:119px" %)9.00 Beta 1|(% colspan="4" style="width:1625px" %)Removed **<yielddensities>** from **<miningparams>**
--|(% colspan="6" style="width:117px" %)It has been replaced with the new **<resources>** node.
--|(% colspan="1" style="width:117px" %)Libraries|(% colspan="1" style="width:119px" %)9.00 Beta 1|(% colspan="4" style="width:1625px" %)**region_definitions.xml** no longer contains **<resources>** or **<scaneffect> **nodes
--|(% colspan="6" style="width:117px" %)Instead of defining resources in regions, they're now defined via resource areas in sectors (see **mapdefaults.xml** and **resourceyields.xml**). Regions can still have some control by defining **<allowedyields>**.
--|(% colspan="1" style="width:117px" %)Libraries|(% colspan="1" style="width:119px" %)9.00 Beta 1|(% colspan="4" style="width:1625px" %)**regionyields.xml** has a completely different structure
--|(% colspan="6" style="width:117px" %)It now contains definitions of resource areas referenced by sector properties (see **mapdefaults.xml**).
--|(% colspan="1" style="width:117px" %)Scripts|(% colspan="1" style="width:119px" %)9.00 Beta 1|(% colspan="4" style="width:1625px" %)Removed **$resourceprobe.currentbestyield** and **.maxyield**, **$sector.averagemaxyield**, and **$galaxy.yieldthresholds**
--|(% colspan="6" style="width:117px" %)New properties that can be used are **$resourceprobe.bestyieldrating** and **$sector.yieldrating.{$ware}**. Yields thresholds are no longer a thing in 9.00.
--|(% colspan="1" style="width:117px" %)Scripts|(% colspan="1" style="width:119px" %)9.00 Beta 1|(% colspan="4" style="width:1625px" %)Removed **flags **attribute from action **<add_blueprints>**
--|(% colspan="6" style="width:117px" %)(((
--The flags attribute is no longer available in the MD action <add_blueprints>
--)))
--|(% style="width:117px" %)Scripts|(% style="width:117px" %)9.00 Beta 1|(% colspan="3" style="width:117px" %)Construction sequence param removed from build_started events
--|(% colspan="6" style="width:117px" %)Script events <event_build_started> and <event_player_build_started> no longer receive the construction sequence via param2. param2 will now yield null. Query the sequence via the param3 buildtask instead.
--|(% style="width:117px" %)Scripts|(% style="width:117px" %)9.00 Beta 1|(% colspan="3" style="width:117px" %)Script properties removed from macro
--|(% colspan="6" style="width:117px" %)**.purposemacro** and **.purposename **have been removed from the **macro **script properties
--|(% style="width:117px" %)Scripts|(% style="width:117px" %)9.00 Beta 1|(% colspan="4" rowspan="1" style="width:117px" %)**constructionplan **attribute now required for **<add_build_to_expand_station>**
--|(% colspan="6" style="width:117px" %)The constructionplan attribute for the <add_build_to_expand_station> action is no longer optional. Past behaviour when omitted was for the station to recycle down to nothing. Use new script action <add_build_to_recycle_station> instead.
--
--=== Version 8.00 ===
--
--(% class="table-striped" %)
--|(% colspan="1" style="width:117px" %)Scripts|(% colspan="1" style="width:119px" %)8.00 Beta 1|(% colspan="4" style="width:1625px" %)Removed MD action **<populate_platforms>**
--|(% colspan="6" style="width:117px" %)(((
--The deprecated MD action <populate_platforms> has been removed. The previously referenced character quotas in quotas.xml have also been removed.
--)))
--|(% style="width:117px" %)Assets|(% style="width:117px" %)8.00 Beta 1|(% colspan="4" rowspan="1" style="width:117px" %)**\assets\units\size_m\ship_gen_m_transdrone_container_02** and **\assets\units\size_s\ship_gen_s_transdrone_container_02** moved to **ego_dlc_terran**
--|(% colspan="6" style="width:117px" %)**ship_gen_m_transdrone_container_02** and **ship_gen_s_transdrone_container_02** (templates and macros) have been moved to the **ego_dlc_terran** extension and any reference to these files now requires that the resulting dependency on that extension is taken into account.
--|(% style="width:117px" %)Assets|(% style="width:117px" %)8.00 Beta 1|(% colspan="4" rowspan="1" style="width:117px" %)Icons moved from **assets\fx\textures\gui** to **assets\textures\ui**
--|(% colspan="6" style="width:117px" %)Assets with the exception of the **loadingscreen** folder have been moved and any reference to these files will require updating (mostly affects icons.xml).
--|(% style="width:117px" %)Assets|(% colspan="3" style="width:117px" %)8.00 Beta 1|(% colspan="3" style="width:117px" %)**boron** and **terran** tags for equipment (weapons, engines, ...) changed to **advanced**
--|(% colspan="6" style="width:117px" %)Ships and equipment with **boron **and **terran** (Frontier terran, not CoH terran) tags will no longer work properly as they do not match the new **advanced** tag (for example "small engine boron" has been replaced by "small engine advanced") which has been introduced for a compatibility between boron and Frontier-terran ships/equipment.
--|(% style="width:117px" %)Assets|(% style="width:117px" %)8.00|(% colspan="4" rowspan="1" style="width:117px" %)Terran NPC heads from Terran DLC **extensions/ego_dlc_terran/assets/characters/terran/heads/[...]** have been removed
--|(% colspan="6" style="width:117px" %)All Terran NPC heads are now pointed to **assets/characters/argon/heads/char_arg_f_dyn_blend_head** (female characters) and **assets/characters/argon/heads/char_arg_m_dyn_blend_head** (male characters) instead of using random selection from a list.
--
  === Version 7.50 ===
  (% class="table-striped" %)
--|(% colspan="1" style="width:117px" %)Relations|(% colspan="1" style="width:119px" %)7.50 Beta 4|(% colspan="2" style="width:1625px" %)**Adjusted displayed UI values (25 to 30) for relations between 0.32 and 1.0:** The minimum relation for the "ally" range (0.5) now corresponds to the displayed UI value of precisely +27 (previously rounded down to +26)
--|(% colspan="4" style="width:117px" %)(((
--The "ally" range is the interval from 0.5 to 1.0, which previously corresponded to the UI value range of approximately +26.9897 to +30. The interpolated mapping within the range from 0.32 and 1.0 has been adjusted so that 0.5 now exactly corresponds to +27. As a consequence, certain relations that were previously between 25 and 28 (rounded down) may have gained +1 in the UI, i.e. they are now displayed as 26 instead of 25, etc. For consistency, the negative range between -1.0 and -0.32 has been adjusted analogously (-0.5 is now displayed as -27). This mostly only affects the UI display, not actual gameplay.
--)))
++|(% colspan="1" style="width:117px" %)Relations|(% colspan="1" style="width:119px" %)7.50 Beta 4|(% colspan="2" style="width:1625px" %)**Faction relation UI values: Changed mapping of relations to displayed UI values between 0.5 and 1.0 (UI +25 and +30)**
++|(% colspan="4" style="width:117px" %)
  |(% colspan="1" style="width:117px" %)Parameters|(% colspan="1" style="width:119px" %)7.50 Beta 4|(% colspan="2" style="width:1625px" %)**<holomap><radar>**:** complete change in structure**
  |(% colspan="7" style="width:117px" %)(((
  This section now contains sets of parameters for the different modes it can be in, each in its own <mode> child node. This list can be dynamically expanded to add more modes.
@@ -79,20 +79,20 @@
  (% class="table-striped" %)
  |(% colspan="1" style="width:117px" %)Gamestarts|(% colspan="1" style="width:119px" %)7.00 Beta 8|(% colspan="2" style="width:1625px" %)**Text references**
--|(% colspan="4" style="width:117px" %)Fields containing text references in gamestarts.xml now have full text conversion applied, allowing texts to be constructed from multiple text entries, e.g. {1234,56}\n\n{1234,78}. As a result, raw text placed in the text fields needs to be formatted accordingly, e.g. "Test start (easy)" would need to be changed to "Test start \(easy\)" to avoid the text in brackets being treated as a comment.
++|(% colspan="4" style="width:117px" %)//Fields containing text references in gamestarts.xml now have full text conversion applied, allowing texts to be constructed from multiple text entries, e.g. {1234,56}\n\n{1234,78}. As a result, raw text placed in the text fields needs to be formatted accordingly, e.g. "Test start (easy)" would need to be changed to "Test start \(easy\)" to avoid the text in brackets being treated as a comment.//
  |(% colspan="1" style="width:117px" %)Assets|(% colspan="1" style="width:119px" %)7.00 Beta 7|(% colspan="2" style="width:1625px" %)**\assets\textures\fx\highway_fx_electric_02** was deleted and replaced with **\assets\textures\fx\fx_p2_electric_01**
  |(% colspan="4" style="width:117px" %)highway_fx_electric_02 is still available in "legacy" folder if needed
  |(% colspan="1" style="width:117px" %)Parameters|(% colspan="1" style="width:119px" %)7.00 Beta 7|(% colspan="2" style="width:1625px" %)**<aiflight><skills>**: **strafespeed**, **strafeacc**, **steeringspeed**, **steeringacc** moved to separate nodes; added support for min and max values
  |(% colspan="4" style="width:117px" %)(((
--The four parameters used to represent flat factors applied to ships' properties with respect to their respective pilots' skill levels. Parameters moved to separate nodes with support for min and max values which, if supplied, scales the factor linearly if the affected ship's unmodified property is within min and max. Factor does not affect the ship if that property is below min.
++//The four parameters used to represent flat factors applied to ships' properties with respect to their respective pilots' skill levels. Parameters moved to separate nodes with support for min and max values which, if supplied, scales the factor linearly if the affected ship's unmodified property is within min and max. Factor does not affect the ship if that property is below min.//
  )))
  |(% colspan="1" style="width:117px" %)Scripts|(% colspan="1" style="width:119px" %)7.00 Beta 6|(% colspan="2" style="width:1625px" %)MD action **<set_holomap_target>** parameter change.
  |(% colspan="4" style="width:117px" %)(((
--The **pantime** parameter has never actually done anything beyond turning panning on or making the transition instant. To make this clear it has been** **replaced with the boolean parameter **instant.**
++//The **pantime** parameter has never actually done anything beyond turning panning on or making the transition instant. To make this clear it has been** **replaced with the boolean parameter **instant.**//
  )))
  |(% colspan="1" style="width:117px" %)Assets|(% colspan="1" style="width:119px" %)7.00 Beta 1|(% colspan="2" style="width:1625px" %)Renamed some material names and changed file paths for textures.
  |(% colspan="4" style="width:117px" %)(((
--Some material names and texture paths were changed. Please DIFF the materiallibrary.xml from 6.20 with 7.0 to see the difference
++(% style="color:#ffffff" %)//Some material names and texture paths were changed. Please DIFF the materiallibrary.xml from 6.20 with 7.0 to see the difference//
  )))
  |(% colspan="1" style="width:117px" %)(% colspan="1" %)
  (((
@@ -104,7 +104,7 @@
  )))
  |(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
  (((
-- Previously it was possible to set normal clusters to be persistent presentation clusters which was an invalid state.
++// Previously it was possible to set normal clusters to be persistent presentation clusters which was an invalid state.//
  )))
  |(% colspan="1" style="width:117px" %)(% colspan="1" %)
  (((
@@ -116,7 +116,7 @@
  )))
  |(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
  (((
-- The build plot's buildstorage is no longer removed implicitly. The buildstorage will instead be cleaned-up once it is empty and no ships are docked.
++// The build plot's buildstorage is no longer removed implicitly. The buildstorage will instead be cleaned-up once it is empty and no ships are docked.//
  )))
  |(% colspan="1" style="width:117px" %)(% colspan="1" %)
  (((
@@ -143,9 +143,9 @@
  )))
  |(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
  (((
--Previously some entries were lacking "weight" parameter, causing it to default to "1", which prevent adding new ships to the group with appropriate/configurable granularity.
++//Previously some entries were lacking "weight" parameter, causing it to default to "1", which prevent adding new ships to the group with appropriate/configurable granularity.//
--All groups should now have "weight" parameter added and old "weights" were updated to not have single-digit numbers.
++//All groups should now have "weight" parameter added and old "weights" were updated to not have single-digit numbers.//
  )))
  |(% colspan="1" %)(% colspan="1" %)
  (((
@@ -159,9 +159,9 @@
  )))
  |(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
  (((
--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.
++//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. //
--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.
++//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.//
  )))
  |(% colspan="1" %)(% colspan="1" %)
  (((
@@ -175,11 +175,11 @@
  )))
  |(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
  (((
--The 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.
++//The 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.//
--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.
++//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.//
--The action itself has been improved to increase the chance of finding suitable surface positions.
++//The action itself has been improved to increase the chance of finding suitable surface positions.//
  )))
  |(% colspan="1" %)(% colspan="1" %)
  (((
@@ -193,8 +193,8 @@
  )))
  |(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
  (((
--<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes.
--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.
++//<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes.
++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.//
  )))
  |(% colspan="1" %)(% colspan="1" %)
  (((
@@ -208,7 +208,7 @@
  )))
  |(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
  (((
--The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.
++//The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.//
  )))
  |(((
  Assets
@@ -219,8 +219,8 @@
  )))
  |(% colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
  (((
--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.
--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.
++//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.
++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.//
  )))
  |(% colspan="1" %)(% colspan="1" %)
  (((
@@ -234,7 +234,7 @@
  )))
  |(% colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
  (((
--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.
++//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.//
  )))
  |(((
  Scripts
@@ -245,7 +245,7 @@
  )))
  |(% colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
  (((
--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.
++//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.//
  )))
  |(((
  Cutscenes
@@ -256,7 +256,7 @@
  )))
  |(% colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
  (((
--The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.
++//The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.//
  )))
  ----
@@ -273,7 +273,7 @@
  )))
  |(% colspan="7" %)(% colspan="3" %)
  (((
--'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.
++//'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.//
  )))
  ----
@@ -293,7 +293,7 @@
  )))
  |(% colspan="4" %)(% colspan="3" %)
  (((
--The functionality represented by SetMapRenderCargoContents(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos() has been removed and the function was therefore stubbed.
++//The functionality represented by SetMapRenderCargoContents(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos() has been removed and the function was therefore stubbed.//
  )))
  |(% colspan="1" %)(% colspan="1" %)
  (((
@@ -307,7 +307,7 @@
  )))
  |(% colspan="4" %)(% colspan="3" %)
  (((
--This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.
++//This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.//
  )))
  |(% colspan="1" %)(% colspan="1" %)
  (((
@@ -321,7 +321,7 @@
  )))
  |(% colspan="4" %)(% colspan="3" %)
  (((
--Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.
++//Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.//
  )))
  |(% colspan="1" %)(% colspan="1" %)
  (((
@@ -335,7 +335,7 @@
  )))
  |(% colspan="4" %)(% colspan="3" %)
  (((
--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.
++//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.//
  )))
  |(((
  UI extensions
@@ -346,7 +346,7 @@
  )))
  |(% colspan="4" %)(% colspan="3" %)
  (((
--These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.
++//These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.//
  )))
  |(((
  Scripts
@@ -357,7 +357,7 @@
  )))
  |(% colspan="4" %)(% colspan="3" %)
  (((
--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.
++//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.//
  )))
  |(% colspan="1" %)(% colspan="1" %)
  (((
@@ -371,7 +371,7 @@
  )))
  |(% colspan="4" %)(% colspan="3" %)
  (((
--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.
++//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.//
  )))
  |(((
  Scripts
@@ -382,7 +382,7 @@
  )))
  |(% colspan="4" %)(% colspan="3" %)
  (((
--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.
++//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.//
  )))
  ----
@@ -402,8 +402,8 @@
  )))
  |(% colspan="4" %)(% colspan="3" %)
  (((
--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).
--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.
++//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).
++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.//
  )))
  |(((
  Scripts
@@ -414,9 +414,9 @@
  )))
  |(% colspan="4" %)(% colspan="3" %)
  (((
--Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects?
++//Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects?
  New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits
--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
++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//
  )))
  |(% colspan="1" %)(% colspan="1" %)
  (((
@@ -430,10 +430,10 @@
  )))
  |(% colspan="4" %)(% colspan="3" %)
  (((
--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.
--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).
++//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.
++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).//
--If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.
++//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.//
  )))
  |(% colspan="1" %)(% colspan="1" %)
  (((
@@ -447,9 +447,9 @@
  )))
  |(% colspan="4" %)(% colspan="3" %)
  (((
--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.
++//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.//
--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).
++//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).
  )))
  |(((
  Parameters
@@ -460,7 +460,7 @@
  )))
  |(% colspan="4" %)(% colspan="3" %)
  (((
--The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.
++//The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.//
  )))
  |(((
  Scripts
@@ -471,7 +471,7 @@
  )))
  |(% colspan="4" %)(% colspan="3" %)
  (((
--The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.
++//The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.//
  )))
  ----
@@ -488,7 +488,7 @@
  )))
  |(% colspan="7" %)(% colspan="3" %)
  (((
--These mission limit-related functions (added in 3.30 Beta 1 and 2) are replaced with FFI IsMissionLimitReached()
++//These mission limit-related functions (added in 3.30 Beta 1 and 2) are replaced with FFI IsMissionLimitReached()//
  )))
  ----
@@ -505,9 +505,9 @@
  )))
  |(% colspan="4" %)(% colspan="3" %)
  (((
--Old params: param = attacked object, param2 = attack method, param3 = attacked component
--New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon]
--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
++//Old params: param = attacked object, param2 = attack method, param3 = attacked component//
++//New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon]
++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//
  )))
  |(% colspan="1" %)(% colspan="1" %)
  (((
@@ -521,7 +521,7 @@
  )))
  |(% colspan="4" %)(% colspan="3" %)
  (((
--$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.
++//$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.//
  )))
  |(((
  UI extensions
@@ -532,7 +532,7 @@
  )))
  |(% colspan="4" %)(% colspan="3" %)
  (((
--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.
++//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.//
  )))
  ----
@@ -552,7 +552,7 @@
  )))
  |(% colspan="7" %)(% colspan="3" %)
  (((
--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.
++//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.//
  )))
  ----
@@ -572,7 +572,7 @@
  )))
  |(% colspan="4" %)(% colspan="3" %)
  (((
--<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.
++//<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.//
  )))
  |(% colspan="1" %)(% colspan="1" %)
  (((
@@ -586,7 +586,7 @@
  )))
  |(% colspan="4" %)(% colspan="3" %)
  (((
--<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.
++//<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.//
  )))
  |(% colspan="1" %)(% colspan="1" %)
  (((
@@ -600,9 +600,9 @@
  )))
  |(% colspan="4" %)(% colspan="3" %)
  (((
--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.)
++//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.)
--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).
++//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).//
  )))
  |(% colspan="1" %)(% colspan="1" %)
  (((
@@ -616,7 +616,7 @@
  )))
  |(% colspan="4" %)(% colspan="3" %)
  (((
--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.
++//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.//
  )))
  |(% colspan="1" %)(% colspan="1" %)
  (((
@@ -630,8 +630,8 @@
  )))
  |(% colspan="4" %)(% colspan="3" %)
  (((
--Before the change, positions are relative to $dockingbay.parent.
--After the change, positions are relative to $dockingbay as specified in the documentation.
++//Before the change, positions are relative to $dockingbay.parent.
++After the change, positions are relative to $dockingbay as specified in the documentation.//
  )))
  |(% colspan="1" %)(% colspan="1" %)
  (((
@@ -645,7 +645,7 @@
  )))
  |(% colspan="4" %)(% colspan="3" %)
  (((
--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().
++//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().//
  )))
  |(((
  Scripts
@@ -656,7 +656,7 @@
  )))
  |(% colspan="4" %)(% colspan="3" %)
  (((
--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.
++//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.
 .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.
  If in your scripts you make use of the <event_object_changed_owner> condition you need to verify that you indeed want to work with the "effective" component owner or whether your script code actually should work with the true owner of an object and update your code accordingly.
  On top of that the 3rd parameter of <event_object_changed_owner> (trueprevious) was dropped as the event is no longer triggered upon a change of the true owner alone (i.e. only if the change of the true owner has also an effect on the "effective" component owner).
@@ -673,7 +673,7 @@
  )))
  |(% colspan="4" %)(% colspan="3" %)
  (((
--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.
++//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.//
  )))
  |(((
  Job/God
@@ -684,7 +684,7 @@
  )))
  |(% colspan="4" %)(% colspan="3" %)
  (((
--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.
++//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.//
  )))
  |(% colspan="1" %)(% colspan="1" %)
  (((

Changes for page Breaking Changes

Summary

Details

Navigation

Applications