Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 127.1
edited by Klaus Meyer
on 2025/06/03 16:37
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
Content
... ... @@ -20,21 +20,11 @@
20 20  
21 21  {{toc scope="LOCAL" start="3"/}}
22 22  
23 -=== Version 8.00 ===
24 -
25 -(% class="table-striped" %)
26 -|(% colspan="1" style="width:117px" %)Scripts|(% colspan="1" style="width:119px" %)8.00 Beta 1|(% colspan="2" style="width:1625px" %)Removed MD action **<populate_platforms>**
27 -|(% colspan="4" style="width:117px" %)(((
28 -The deprecated MD action <populate_platforms> has been removed. The previously referenced character quotas in quotas.xml have also been removed.
29 -)))
30 -
31 31  === Version 7.50 ===
32 32  
33 33  (% class="table-striped" %)
34 -|(% 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)
35 -|(% colspan="4" style="width:117px" %)(((
36 -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.
37 -)))
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" %)
38 38  |(% 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**
39 39  |(% colspan="7" style="width:117px" %)(((
40 40  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.
... ... @@ -45,20 +45,20 @@
45 45  
46 46  (% class="table-striped" %)
47 47  |(% colspan="1" style="width:117px" %)Gamestarts|(% colspan="1" style="width:119px" %)7.00 Beta 8|(% colspan="2" style="width:1625px" %)**Text references**
48 -|(% 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.//
49 49  |(% 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**
50 50  |(% colspan="4" style="width:117px" %)highway_fx_electric_02 is still available in "legacy" folder if needed
51 51  |(% 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
52 52  |(% colspan="4" style="width:117px" %)(((
53 -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.//
54 54  )))
55 55  |(% 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.
56 56  |(% colspan="4" style="width:117px" %)(((
57 -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.**//
58 58  )))
59 59  |(% 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.
60 60  |(% colspan="4" style="width:117px" %)(((
61 -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//
62 62  )))
63 63  |(% colspan="1" style="width:117px" %)(% colspan="1" %)
64 64  (((
... ... @@ -70,7 +70,7 @@
70 70  )))
71 71  |(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
72 72  (((
73 - 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.//
74 74  )))
75 75  |(% colspan="1" style="width:117px" %)(% colspan="1" %)
76 76  (((
... ... @@ -82,7 +82,7 @@
82 82  )))
83 83  |(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
84 84  (((
85 - 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.//
86 86  )))
87 87  |(% colspan="1" style="width:117px" %)(% colspan="1" %)
88 88  (((
... ... @@ -109,9 +109,9 @@
109 109  )))
110 110  |(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
111 111  (((
112 -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.//
113 113  
114 -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.//
115 115  )))
116 116  |(% colspan="1" %)(% colspan="1" %)
117 117  (((
... ... @@ -125,9 +125,9 @@
125 125  )))
126 126  |(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
127 127  (((
128 -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. //
129 129  
130 -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.//
131 131  )))
132 132  |(% colspan="1" %)(% colspan="1" %)
133 133  (((
... ... @@ -141,11 +141,11 @@
141 141  )))
142 142  |(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
143 143  (((
144 -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.//
145 145  
146 -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.//
147 147  
148 -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.//
149 149  )))
150 150  |(% colspan="1" %)(% colspan="1" %)
151 151  (((
... ... @@ -159,8 +159,8 @@
159 159  )))
160 160  |(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
161 161  (((
162 -<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes.
163 -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.//
164 164  )))
165 165  |(% colspan="1" %)(% colspan="1" %)
166 166  (((
... ... @@ -174,7 +174,7 @@
174 174  )))
175 175  |(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
176 176  (((
177 -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'.//
178 178  )))
179 179  |(((
180 180  Assets
... ... @@ -185,8 +185,8 @@
185 185  )))
186 186  |(% colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
187 187  (((
188 -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.
189 -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.//
190 190  )))
191 191  |(% colspan="1" %)(% colspan="1" %)
192 192  (((
... ... @@ -200,7 +200,7 @@
200 200  )))
201 201  |(% colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
202 202  (((
203 -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.//
204 204  )))
205 205  |(((
206 206  Scripts