Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 146.1
edited by Matthias Haan
on 2026/02/17 13:08
Change comment: There is no comment for this version
To version 124.8
edited by Klaus Meyer
on 2025/01/07 16:43
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.Matthias
1 +xwiki:XWiki.Klaus
Content
... ... @@ -20,57 +20,11 @@
20 20  
21 21  {{toc scope="LOCAL" start="3"/}}
22 22  
23 -=== Version 9.00 ===
24 -
25 -(% class="table-striped" %)
26 -|(% colspan="1" style="width:117px" %)Assets|(% colspan="1" style="width:119px" %)9.00 Beta 1|(% colspan="4" style="width:1625px" %)Added **overheatcooldelay** property to **<heat>** of weapons, changed functionality of **cooldelay**
27 -|(% colspan="6" style="width:117px" %)**cooldelay** now optionally defines a delay between firing a non-overheating shot and the cooldown starting, **overheatcooldelay** is an additional penalty delay when the weapon overheats.
28 -|(% 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>**
29 -|(% colspan="6" style="width:117px" %)A new property that can be used in its place is **$sector.bestyieldrating.{$ware}**.
30 -|(% 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>**
31 -|(% colspan="6" style="width:117px" %)**<find_asteroid_with_yield_in_sector>** and **<find_recyclable_with_yield_in_sector>** should now be used instead.
32 -|(% colspan="1" style="width:117px" %)Parameters|(% colspan="1" style="width:119px" %)9.00 Beta 1|(% colspan="4" style="width:1625px" %)Removed **<yielddensities>** from **<miningparams>**
33 -|(% colspan="6" style="width:117px" %)It has been replaced with the new **<resources>** node.
34 -|(% 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
35 -|(% 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>**.
36 -|(% 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
37 -|(% colspan="6" style="width:117px" %)It now contains definitions of resource areas referenced by sector properties (see **mapdefaults.xml**).
38 -|(% 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**
39 -|(% 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.
40 -|(% 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>**
41 -|(% colspan="6" style="width:117px" %)(((
42 -The flags attribute is no longer available in the MD action <add_blueprints>
43 -)))
44 -|(% style="width:117px" %)Scripts|(% style="width:117px" %)9.00 Beta 1|(% colspan="3" style="width:117px" %)Construction sequence param removed from build_started events
45 -|(% 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.
46 -|(% style="width:117px" %)Scripts|(% style="width:117px" %)9.00 Beta 1|(% colspan="3" style="width:117px" %)Script properties removed from macro
47 -|(% colspan="6" style="width:117px" %)**.purposemacro** and **.purposename **have been removed from the **macro **script properties
48 -|(% 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>**
49 -|(% 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.
50 -
51 -=== Version 8.00 ===
52 -
53 -(% class="table-striped" %)
54 -|(% 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>**
55 -|(% colspan="6" style="width:117px" %)(((
56 -The deprecated MD action <populate_platforms> has been removed. The previously referenced character quotas in quotas.xml have also been removed.
57 -)))
58 -|(% 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**
59 -|(% 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.
60 -|(% 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**
61 -|(% 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).
62 -|(% 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**
63 -|(% 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.
64 -|(% 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
65 -|(% 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.
66 -
67 67  === Version 7.50 ===
68 68  
69 69  (% class="table-striped" %)
70 -|(% 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)
71 -|(% colspan="4" style="width:117px" %)(((
72 -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.
73 -)))
26 +|(% 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)**
27 +|(% colspan="4" style="width:117px" %)
74 74  |(% 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**
75 75  |(% colspan="7" style="width:117px" %)(((
76 76  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.
... ... @@ -81,20 +81,20 @@
81 81  
82 82  (% class="table-striped" %)
83 83  |(% colspan="1" style="width:117px" %)Gamestarts|(% colspan="1" style="width:119px" %)7.00 Beta 8|(% colspan="2" style="width:1625px" %)**Text references**
84 -|(% 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.
38 +|(% 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.//
85 85  |(% 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**
86 86  |(% colspan="4" style="width:117px" %)highway_fx_electric_02 is still available in "legacy" folder if needed
87 87  |(% 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
88 88  |(% colspan="4" style="width:117px" %)(((
89 -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.
43 +//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.//
90 90  )))
91 91  |(% 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.
92 92  |(% colspan="4" style="width:117px" %)(((
93 -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.**
47 +//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.**//
94 94  )))
95 95  |(% 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.
96 96  |(% colspan="4" style="width:117px" %)(((
97 -Some material names and texture paths were changed. Please DIFF the materiallibrary.xml from 6.20 with 7.0 to see the difference
51 +(% 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//
98 98  )))
99 99  |(% colspan="1" style="width:117px" %)(% colspan="1" %)
100 100  (((
... ... @@ -106,7 +106,7 @@
106 106  )))
107 107  |(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
108 108  (((
109 - Previously it was possible to set normal clusters to be persistent presentation clusters which was an invalid state.
63 +// Previously it was possible to set normal clusters to be persistent presentation clusters which was an invalid state.//
110 110  )))
111 111  |(% colspan="1" style="width:117px" %)(% colspan="1" %)
112 112  (((
... ... @@ -118,7 +118,7 @@
118 118  )))
119 119  |(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
120 120  (((
121 - 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.
75 +// 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.//
122 122  )))
123 123  |(% colspan="1" style="width:117px" %)(% colspan="1" %)
124 124  (((
... ... @@ -145,9 +145,9 @@
145 145  )))
146 146  |(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
147 147  (((
148 -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.
102 +//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.//
149 149  
150 -All groups should now have "weight" parameter added and old "weights" were updated to not have single-digit numbers.
104 +//All groups should now have "weight" parameter added and old "weights" were updated to not have single-digit numbers.//
151 151  )))
152 152  |(% colspan="1" %)(% colspan="1" %)
153 153  (((
... ... @@ -161,9 +161,9 @@
161 161  )))
162 162  |(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
163 163  (((
164 -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.
118 +//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. //
165 165  
166 -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.
120 +//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.//
167 167  )))
168 168  |(% colspan="1" %)(% colspan="1" %)
169 169  (((
... ... @@ -177,11 +177,11 @@
177 177  )))
178 178  |(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
179 179  (((
180 -The 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.
134 +//The 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.//
181 181  
182 -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.
136 +//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.//
183 183  
184 -The action itself has been improved to increase the chance of finding suitable surface positions.
138 +//The action itself has been improved to increase the chance of finding suitable surface positions.//
185 185  )))
186 186  |(% colspan="1" %)(% colspan="1" %)
187 187  (((
... ... @@ -195,8 +195,8 @@
195 195  )))
196 196  |(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
197 197  (((
198 -<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes.
199 -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.
152 +//<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes.
153 +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.//
200 200  )))
201 201  |(% colspan="1" %)(% colspan="1" %)
202 202  (((
... ... @@ -210,7 +210,7 @@
210 210  )))
211 211  |(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
212 212  (((
213 -The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.
167 +//The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.//
214 214  )))
215 215  |(((
216 216  Assets
... ... @@ -221,8 +221,8 @@
221 221  )))
222 222  |(% colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
223 223  (((
224 -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.
225 -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.
178 +//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.
179 +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.//
226 226  )))
227 227  |(% colspan="1" %)(% colspan="1" %)
228 228  (((
... ... @@ -236,7 +236,7 @@
236 236  )))
237 237  |(% colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
238 238  (((
239 -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.
193 +//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.//
240 240  )))
241 241  |(((
242 242  Scripts