Changes for page Breaking Changes

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -23,10 +23,8 @@
23	23	=== Version 7.50 ===
24	24
25	25	(% class="table-striped" %)
26		-|(% 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
27		-|(% colspan="4" style="width:117px" %)(((
28		-The mapping of relations (-1.0 to +1.0) to displayed UI values (-30 to +30) is a piecewise logarithmic interpolation between fixed mappings (e.g. +0.32 corresponds to +25 in the UI). The "ally" range is the interval from 0.5 to 1.0, which corresponds to the UI value range of approximately +26.9897 to +30. The mapping within the range from 0.32 and 1.0 has been adjusted so that 0.5 now precisely corresponds to +27.
29		-)))
	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" %)
30	30	|(% 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**
31	31	|(% colspan="7" style="width:117px" %)(((
32	32	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.
...	...	@@ -37,20 +37,20 @@
37	37
38	38	(% class="table-striped" %)
39	39	|(% colspan="1" style="width:117px" %)Gamestarts|(% colspan="1" style="width:119px" %)7.00 Beta 8|(% colspan="2" style="width:1625px" %)**Text references**
40		-|(% 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.//
41	41	|(% 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**
42	42	|(% colspan="4" style="width:117px" %)highway_fx_electric_02 is still available in "legacy" folder if needed
43	43	|(% 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
44	44	|(% colspan="4" style="width:117px" %)(((
45		-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.//
46	46	)))
47	47	|(% 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.
48	48	|(% colspan="4" style="width:117px" %)(((
49		-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.**//
50	50	)))
51	51	|(% 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.
52	52	|(% colspan="4" style="width:117px" %)(((
53		-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//
54	54	)))
55	55	|(% colspan="1" style="width:117px" %)(% colspan="1" %)
56	56	(((
...	...	@@ -62,7 +62,7 @@
62	62	)))
63	63	|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
64	64	(((
65		- 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.//
66	66	)))
67	67	|(% colspan="1" style="width:117px" %)(% colspan="1" %)
68	68	(((
...	...	@@ -74,7 +74,7 @@
74	74	)))
75	75	|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
76	76	(((
77		- 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.//
78	78	)))
79	79	|(% colspan="1" style="width:117px" %)(% colspan="1" %)
80	80	(((
...	...	@@ -101,9 +101,9 @@
101	101	)))
102	102	|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
103	103	(((
104		-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.//
105	105
106		-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.//
107	107	)))
108	108	|(% colspan="1" %)(% colspan="1" %)
109	109	(((
...	...	@@ -117,9 +117,9 @@
117	117	)))
118	118	|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
119	119	(((
120		-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. //
121	121
122		-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.//
123	123	)))
124	124	|(% colspan="1" %)(% colspan="1" %)
125	125	(((
...	...	@@ -133,11 +133,11 @@
133	133	)))
134	134	|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
135	135	(((
136		-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.//
137	137
138		-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.//
139	139
140		-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.//
141	141	)))
142	142	|(% colspan="1" %)(% colspan="1" %)
143	143	(((
...	...	@@ -151,8 +151,8 @@
151	151	)))
152	152	|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
153	153	(((
154		-<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes.
155		-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.//
156	156	)))
157	157	|(% colspan="1" %)(% colspan="1" %)
158	158	(((
...	...	@@ -166,7 +166,7 @@
166	166	)))
167	167	|(% colspan="4" title="Background colour :" %)(% colspan="3" title="Background colour :" %)
168	168	(((
169		-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'.//
170	170	)))
171	171	|(((
172	172	Assets
...	...	@@ -177,8 +177,8 @@
177	177	)))
178	178	|(% colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
179	179	(((
180		-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.
181		-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.//
182	182	)))
183	183	|(% colspan="1" %)(% colspan="1" %)
184	184	(((
...	...	@@ -192,7 +192,7 @@
192	192	)))
193	193	|(% colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
194	194	(((
195		-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.//
196	196	)))
197	197	|(((
198	198	Scripts