Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 104.4
edited by Volodymyr Boichuk
on 2023/07/12 12:51
Change comment: Update document after refactoring.
To version 111.1
edited by Ketraar
on 2023/11/29 19:11
Change comment: There is no comment for this version

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,1 @@
1 -X4 Foundations Wiki (OLD).Modding Support.WebHome
1 +X4 Foundations Wiki.Modding Support.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.Volodymyr
1 +xwiki:XWiki.Ketraar
Content
... ... @@ -4,13 +4,13 @@
4 4  The following table provides an overview about all breaking changes. This should help you to make any necessary changes to restore compatibility of older mods with new versions of X4.
5 5  Feel free to drop a note if a certain breaking change is breaking your mod and you have difficulties finding a way to work around the issue.
6 6  
7 -{{note}}
8 -The list of breaking changes does **NOT** cover changes in the provided/shipped scripts (for instance UI scripts like the ones located under ui/addons/XXX or ui/core/Lua). These scripts can change anytime without explicit notice. If you hook into one of these scripts or provide replacements for these, please check the script for possible breaking changes yourself.
7 +{{info}}
8 +⚠ The list of breaking changes does **NOT** cover changes in the provided/shipped scripts (for instance UI scripts like the ones located under ui/addons/XXX or ui/core/Lua). These scripts can change anytime without explicit notice. If you hook into one of these scripts or provide replacements for these, please check the script for possible breaking changes yourself.
9 9  
10 10  Further note that the list provides information about breaking changes which are in the pipeline of being released. This is meant merely as an informational heads up. Neither do mistake this as an announcement of that version becoming available soon nor take it for granted that such a change will go live. Any information provided for not yet released versions can change (and even be removed) prior to such version having seen the light of day.
11 11  
12 12  As a final note, please be aware that issues introduced during the beta phase might not be explicitly mentioned in the list below, if things would only be broken in-between two beta versions. While we still aim to document any (potential) breaking change here, there might be circumstances for which we divert from that procedure (especially in case of only minor issues which are considered merely bugfixes rather than an intended behavior change).
13 -{{/note}}
13 +{{/info}}
14 14  
15 15  {{warning title="UI modding considered unstable until further notice..."}}
16 16  Please note that UI modding must be considered **unstable** in the current version. While we are working hard to get the UI modding integration into a stable state, we might have to introduce larger backwards incompatibilities in the following patches. This means that you might have to modify any mod using UI modding capabilities to a larger extend to keep it compatible with certain patches. Still, we are doing our best not to unnecessarily break things for modders and certainly will announce such changes on this page here.
... ... @@ -18,29 +18,38 @@
18 18  
19 19  = Breaking Changes =
20 20  
21 +{{toc scope="LOCAL" start="3"/}}
22 +
23 +=== Version 7.00 ===
24 +
21 21  (% class="wrapped" %)
22 22  |=(((
23 23  Type
24 -)))|=(((
25 -Version
26 -)))|=(((
27 -Summary
28 28  )))
29 -|(% colspan="3" %)(% colspan="3" %)
29 +|(% colspan="1" %)(% colspan="1" %)
30 30  (((
31 -== 6.00 ==
31 +UI extensions
32 32  )))
33 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
34 +(((
35 +// 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.//
36 +)))
37 +
38 +----
39 +
40 +=== Version 6.00 ===
41 +
42 +(% class="wrapped" %)
33 33  |(((
34 34  Libraries
35 35  )))|(((
36 36  6.00 Beta 7
37 -)))|(((
47 +)))|(% colspan="2" %)(((
38 38  Updated weights for ship groups in shipgroups.xml libraries of base game and all DLCs.
39 39  )))
40 -|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
50 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
41 41  (((
42 -//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.
43 -//
52 +//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.//
44 44  
45 45  //All groups should now have "weight" parameter added and old "weights" were updated to not have single-digit numbers.//
46 46  )))
... ... @@ -50,11 +50,11 @@
50 50  )))|(% colspan="1" %)(% colspan="1" %)
51 51  (((
52 52  6.00 Beta 4
53 -)))|(% colspan="1" %)(% colspan="1" %)
62 +)))|(% colspan="2" %)(% colspan="1" %)
54 54  (((
55 55  Changed conditions for **<event_player_travelmode_started> <event_player_travelmode_stopped> <event_player_travelmode_charge_started> <event_player_travelmode_charge_aborted>** to be raised.
56 56  )))
57 -|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
66 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
58 58  (((
59 59  //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. //
60 60  
... ... @@ -66,11 +66,11 @@
66 66  )))|(% colspan="1" %)(% colspan="1" %)
67 67  (((
68 68  6.00 Beta 3
69 -)))|(% colspan="1" %)(% colspan="1" %)
78 +)))|(% colspan="2" %)(% colspan="1" %)
70 70  (((
71 71  Changed result of **<find_object_surface>** action in the case of a failure
72 72  )))
73 -|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
82 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
74 74  (((
75 75  //The 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.//
76 76  
... ... @@ -84,11 +84,11 @@
84 84  )))|(% colspan="1" %)(% colspan="1" %)
85 85  (((
86 86  6.00 Beta 1
87 -)))|(% colspan="1" %)(% colspan="1" %)
96 +)))|(% colspan="2" %)(% colspan="1" %)
88 88  (((
89 89  Behaviour change for **<match_dock>** script component filter
90 90  )))
91 -|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
100 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
92 92  (((
93 93  //<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes.
94 94  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.//
... ... @@ -99,11 +99,11 @@
99 99  )))|(% colspan="1" %)(% colspan="1" %)
100 100  (((
101 101  6.00 Beta 1
102 -)))|(% colspan="1" %)(% colspan="1" %)
111 +)))|(% colspan="2" %)(% colspan="1" %)
103 103  (((
104 104  Changed result attribute location for **<get_attackstrength>**
105 105  )))
106 -|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
115 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
107 107  (((
108 108  //The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.//
109 109  )))
... ... @@ -111,10 +111,10 @@
111 111  Assets
112 112  )))|(((
113 113  6.00 Beta 1
114 -)))|(((
123 +)))|(% colspan="2" %)(((
115 115  Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons
116 116  )))
117 -|(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)
126 +|(% class="highlight-grey" colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% class="highlight-grey" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
118 118  (((
119 119  //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.
120 120  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.//
... ... @@ -125,11 +125,11 @@
125 125  )))|(% colspan="1" %)(% colspan="1" %)
126 126  (((
127 127  6.00 Beta 1
128 -)))|(% colspan="1" %)(% colspan="1" %)
137 +)))|(% colspan="2" %)(% colspan="1" %)
129 129  (((
130 130  Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects
131 131  )))
132 -|(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)
141 +|(% class="highlight-grey" colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% class="highlight-grey" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
133 133  (((
134 134  //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.//
135 135  )))
... ... @@ -137,10 +137,10 @@
137 137  Scripts
138 138  )))|(((
139 139  6.00 Beta 1
140 -)))|(((
149 +)))|(% colspan="2" %)(((
141 141  **<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards.
142 142  )))
143 -|(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)
152 +|(% class="highlight-grey" colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% class="highlight-grey" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
144 144  (((
145 145  //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.//
146 146  )))
... ... @@ -148,32 +148,36 @@
148 148  Cutscenes
149 149  )))|(((
150 150  6.00 Beta 1
151 -)))|(((
160 +)))|(% colspan="2" %)(((
152 152  Changed behaviour of **<angles>** in cutscenes
153 153  )))
154 -|(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)
163 +|(% class="highlight-grey" colspan="4" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% class="highlight-grey" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
155 155  (((
156 156  //The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.//
157 157  )))
158 -|(% colspan="3" %)(% colspan="3" %)
159 -(((
160 -== 5.00 ==
161 -)))
167 +
168 +----
169 +
170 +=== Version 5.00 ===
171 +
172 +(% class="wrapped" %)
162 162  |(((
163 163  Parameters
164 164  )))|(((
165 165  5.00 Beta 1
166 -)))|(((
177 +)))|(% colspan="2" %)(((
167 167  **<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration
168 168  )))
169 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
180 +|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
170 170  (((
171 171  //'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.//
172 172  )))
173 -|(% colspan="3" %)(% colspan="3" %)
174 -(((
175 -== 4.10 ==
176 -)))
184 +
185 +----
186 +
187 +=== Version 4.10 ===
188 +
189 +(% class="wrapped" %)
177 177  |(% colspan="1" %)(% colspan="1" %)
178 178  (((
179 179  UI extensions
... ... @@ -180,13 +180,13 @@
180 180  )))|(% colspan="1" %)(% colspan="1" %)
181 181  (((
182 182  4.10 Beta 7
183 -)))|(% colspan="1" %)(% colspan="1" %)
196 +)))|(% colspan="2" %)(% colspan="1" %)
184 184  (((
185 -**FFI**: (% style="color: rgb(0,0,0);" %)SetMapRenderCargoContents(%%)(), (% style="color: rgb(0,0,0);" %)SetMapRenderWorkForceInfo(), (% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)SetMapRenderCrewInfo() and (% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)SetMapRenderDockedShipInfos()(%%) deprecated
198 +**FFI**: SetMapRenderCargoContents(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos() deprecated
186 186  )))
187 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
200 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
188 188  (((
189 -//The functionality represented by (% style="color: rgb(0,0,0);" %)SetMapRenderCargoContents(%%)(), (% style="color: rgb(0,0,0);" %)SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos()(%%) has been removed and the function was therefore stubbed.//
202 +//The functionality represented by SetMapRenderCargoContents(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos() has been removed and the function was therefore stubbed.//
190 190  )))
191 191  |(% colspan="1" %)(% colspan="1" %)
192 192  (((
... ... @@ -194,11 +194,11 @@
194 194  )))|(% colspan="1" %)(% colspan="1" %)
195 195  (((
196 196  4.10 Beta 6
197 -)))|(% colspan="1" %)(% colspan="1" %)
210 +)))|(% colspan="2" %)(% colspan="1" %)
198 198  (((
199 199  **FFI**: CustomGameStartPlayerProperty2 changed
200 200  )))
201 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
214 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
202 202  (((
203 203  //This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.//
204 204  )))
... ... @@ -208,11 +208,11 @@
208 208  )))|(% colspan="1" %)(% colspan="1" %)
209 209  (((
210 210  4.10 Beta 3
211 -)))|(% colspan="1" %)(% colspan="1" %)
224 +)))|(% colspan="2" %)(% colspan="1" %)
212 212  (((
213 213  Renamed **<stationinfobox>** to **<infobox>**
214 214  )))
215 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
228 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
216 216  (((
217 217  //Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.//
218 218  )))
... ... @@ -222,11 +222,11 @@
222 222  )))|(% colspan="1" %)(% colspan="1" %)
223 223  (((
224 224  4.10 Beta 2
225 -)))|(% colspan="1" %)(% colspan="1" %)
238 +)))|(% colspan="2" %)(% colspan="1" %)
226 226  (((
227 227  **FFI**: SetMacroMapPlayerSectorOffset() deprecated
228 228  )))
229 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
242 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
230 230  (((
231 231  //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.//
232 232  )))
... ... @@ -234,10 +234,10 @@
234 234  UI extensions
235 235  )))|(((
236 236  4.10 Beta 2
237 -)))|(((
238 -**FFI**: (% style="color: rgb(0,0,0);" %)FilterComponentForMapMode(%%)() and (% style="color: rgb(0,0,0);" %)SetMapObjectFilter() changed
250 +)))|(% colspan="2" %)(((
251 +**FFI**: FilterComponentForMapMode() and SetMapObjectFilter() changed
239 239  )))
240 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
253 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
241 241  (((
242 242  //These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.//
243 243  )))
... ... @@ -245,10 +245,10 @@
245 245  Scripts
246 246  )))|(((
247 247  4.10 Beta 1
248 -)))|(((
249 -People related attributes of mission** <delivery> **node moved
261 +)))|(% colspan="2" %)(((
262 +People related attributes of mission** <delivery> **node moved
250 250  )))
251 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
264 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
252 252  (((
253 253  //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.//
254 254  )))
... ... @@ -258,11 +258,11 @@
258 258  )))|(% colspan="1" %)(% colspan="1" %)
259 259  (((
260 260  4.10 Beta 1
261 -)))|(% colspan="1" %)(% colspan="1" %)
274 +)))|(% colspan="2" %)(% colspan="1" %)
262 262  (((
263 263  **$destructible.productions** replaced with $defensible.productions
264 264  )))
265 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
278 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
266 266  (((
267 267  //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.//
268 268  )))
... ... @@ -270,17 +270,19 @@
270 270  Scripts
271 271  )))|(((
272 272  4.10 Beta 1
273 -)))|(((
286 +)))|(% colspan="2" %)(((
274 274  Removed script property **$object.spawnsourceseed**
275 275  )))
276 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
289 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
277 277  (((
278 278  //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.//
279 279  )))
280 -|(% colspan="3" %)(% colspan="3" %)
281 -(((
282 -== 4.00 ==
283 -)))
293 +
294 +----
295 +
296 +=== Version 4.00 ===
297 +
298 +(% class="wrapped" %)
284 284  |(% colspan="1" %)(% colspan="1" %)
285 285  (((
286 286  UI core
... ... @@ -287,24 +287,23 @@
287 287  )))|(% colspan="1" %)(% colspan="1" %)
288 288  (((
289 289  4.00 Beta 10
290 -)))|(% colspan="1" %)(% colspan="1" %)
305 +)))|(% colspan="2" %)(% colspan="1" %)
291 291  (((
292 292  Controlled ship can change without a **gameplanchange-event** occurring.
293 293  )))
294 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
309 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
295 295  (((
296 296  //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).
297 -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.
298 -//
312 +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.//
299 299  )))
300 300  |(((
301 301  Scripts
302 302  )))|(((
303 303  4.00 Beta 7
304 -)))|(((
318 +)))|(% colspan="2" %)(((
305 305  Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed
306 306  )))
307 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
321 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
308 308  (((
309 309  //Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects?
310 310  New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits
... ... @@ -316,17 +316,16 @@
316 316  )))|(% colspan="1" %)(% colspan="1" %)
317 317  (((
318 318  4.00 Beta 6
319 -)))|(% colspan="1" %)(% colspan="1" %)
333 +)))|(% colspan="2" %)(% colspan="1" %)
320 320  (((
321 321  **FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed
322 322  )))
323 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
337 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
324 324  (((
325 325  //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.
326 326  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).//
327 327  
328 -//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.
329 -//
342 +//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.//
330 330  )))
331 331  |(% colspan="1" %)(% colspan="1" %)
332 332  (((
... ... @@ -334,11 +334,11 @@
334 334  )))|(% colspan="1" %)(% colspan="1" %)
335 335  (((
336 336  4.00 Beta 5
337 -)))|(% colspan="1" %)(% colspan="1" %)
350 +)))|(% colspan="2" %)(% colspan="1" %)
338 338  (((
339 339  **FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed
340 340  )))
341 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
354 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
342 342  (((
343 343  //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.//
344 344  
... ... @@ -348,10 +348,10 @@
348 348  Parameters
349 349  )))|(((
350 350  4.00 Beta 1
351 -)))|(((
364 +)))|(% colspan="2" %)(((
352 352  **requiresconstructionvessel** parameter moved
353 353  )))
354 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
367 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
355 355  (((
356 356  //The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.//
357 357  )))
... ... @@ -359,40 +359,44 @@
359 359  Scripts
360 360  )))|(((
361 361  4.00 Beta 1
362 -)))|(((
375 +)))|(% colspan="2" %)(((
363 363  Changed behaviour of **gatedistance** script property
364 364  )))
365 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
378 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
366 366  (((
367 367  //The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.//
368 368  )))
369 -|(% colspan="3" %)(% colspan="3" %)
370 -(((
371 -== 3.30 ==
372 -)))
382 +
383 +----
384 +
385 +=== Version 3.30 ===
386 +
387 +(% class="wrapped" %)
373 373  |(((
374 374  UI extensions
375 375  )))|(((
376 376  3.30 Beta 3
377 -)))|(((
378 -**FFI: **Removed** (% style="color: rgb(0,0,0);" %)GetMissionLimit() (%%)**(% style="color: rgb(0,0,0);" %)and** **(% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)**IsMissionLimit**(%%)**Enabled()**
392 +)))|(% colspan="2" %)(((
393 +**FFI: **Removed** GetMissionLimit() **and** IsMissionLimitEnabled()**
379 379  )))
380 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
395 +|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
381 381  (((
382 -//These mission limit-related functions (added in 3.30 Beta 1 and 2) are replaced with FFI (% style="color: rgb(0,0,0);" %)IsMissionLimit(%%)Reach(% style="color: rgb(0,0,0);" %)ed()//
397 +//These mission limit-related functions (added in 3.30 Beta 1 and 2) are replaced with FFI IsMissionLimitReached()//
383 383  )))
384 -|(% colspan="3" %)(% colspan="3" %)
385 -(((
386 -== 3.20 ==
387 -)))
399 +
400 +----
401 +
402 +=== Version 3.20 ===
403 +
404 +(% class="wrapped" %)
388 388  |(((
389 389  Scripts
390 390  )))|(((
391 391  3.20 Beta 1
392 -)))|(((
409 +)))|(% colspan="2" %)(((
393 393  Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed
394 394  )))
395 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
412 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
396 396  (((
397 397  //Old params: param = attacked object, param2 = attack method, param3 = attacked component//
398 398  //New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon]
... ... @@ -404,11 +404,11 @@
404 404  )))|(% colspan="1" %)(% colspan="1" %)
405 405  (((
406 406  3.20 Beta 1
407 -)))|(% colspan="1" %)(% colspan="1" %)
424 +)))|(% colspan="2" %)(% colspan="1" %)
408 408  (((
409 409  Removed script property $trade.**restriction.faction**
410 410  )))
411 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
428 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
412 412  (((
413 413  //$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.//
414 414  )))
... ... @@ -416,17 +416,19 @@
416 416  UI extensions
417 417  )))|(((
418 418  3.20 Beta 1
419 -)))|(((
436 +)))|(% colspan="2" %)(((
420 420  **Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete!
421 421  )))
422 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
439 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
423 423  (((
424 424  //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.//
425 425  )))
426 -|(% colspan="3" %)(% colspan="3" %)
427 -(((
428 -== 3.10 ==
429 -)))
443 +
444 +----
445 +
446 +=== Version 3.10 ===
447 +
448 +(% class="wrapped" %)
430 430  |(% colspan="1" %)(% colspan="1" %)
431 431  (((
432 432  Scripts
... ... @@ -433,18 +433,20 @@
433 433  )))|(% colspan="1" %)(% colspan="1" %)
434 434  (((
435 435  3.10 Beta 1
436 -)))|(% colspan="1" %)(% colspan="1" %)
455 +)))|(% colspan="2" %)(% colspan="1" %)
437 437  (((
438 438  Removed script action **<add_build/>**
439 439  )))
440 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
459 +|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
441 441  (((
442 442  //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.//
443 443  )))
444 -|(% colspan="3" %)(% colspan="3" %)
445 -(((
446 -== 3.00 ==
447 -)))
463 +
464 +----
465 +
466 +=== Version 3.00 ===
467 +
468 +(% class="wrapped" %)
448 448  |(% colspan="1" %)(% colspan="1" %)
449 449  (((
450 450  Scripts
... ... @@ -451,11 +451,11 @@
451 451  )))|(% colspan="1" %)(% colspan="1" %)
452 452  (((
453 453  3.0 Beta 6
454 -)))|(% colspan="1" %)(% colspan="1" %)
475 +)))|(% colspan="2" %)(% colspan="1" %)
455 455  (((
456 456  Changed behaviour of script action **<get_suitable_job/>**
457 457  )))
458 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
479 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
459 459  (((
460 460  //<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.//
461 461  )))
... ... @@ -465,11 +465,11 @@
465 465  )))|(% colspan="1" %)(% colspan="1" %)
466 466  (((
467 467  3.0 Beta 6
468 -)))|(% colspan="1" %)(% colspan="1" %)
489 +)))|(% colspan="2" %)(% colspan="1" %)
469 469  (((
470 470  Changed behaviour of script action **<get_ware_definition/>**
471 471  )))
472 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
493 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
473 473  (((
474 474  //<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.//
475 475  )))
... ... @@ -479,13 +479,13 @@
479 479  )))|(% colspan="1" %)(% colspan="1" %)
480 480  (((
481 481  3.0 Beta 5
482 -)))|(% colspan="1" %)(% colspan="1" %)
503 +)))|(% colspan="2" %)(% colspan="1" %)
483 483  (((
484 484  Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case
485 485  )))
486 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
507 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
487 487  (((
488 -//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.)\\
509 +//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.)
489 489  
490 490  //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).//
491 491  )))
... ... @@ -495,11 +495,11 @@
495 495  )))|(% colspan="1" %)(% colspan="1" %)
496 496  (((
497 497  3.0 Beta 5
498 -)))|(% colspan="1" %)(% colspan="1" %)
519 +)))|(% colspan="2" %)(% colspan="1" %)
499 499  (((
500 500  Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions>
501 501  )))
502 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
523 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
503 503  (((
504 504  //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.//
505 505  )))
... ... @@ -509,11 +509,11 @@
509 509  )))|(% colspan="1" %)(% colspan="1" %)
510 510  (((
511 511  3.0 Beta 5
512 -)))|(% colspan="1" %)(% colspan="1" %)
533 +)))|(% colspan="2" %)(% colspan="1" %)
513 513  (((
514 514  Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos**
515 515  )))
516 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
537 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
517 517  (((
518 518  //Before the change, positions are relative to $dockingbay.parent.
519 519  After the change, positions are relative to $dockingbay as specified in the documentation.//
... ... @@ -524,11 +524,11 @@
524 524  )))|(% colspan="1" %)(% colspan="1" %)
525 525  (((
526 526  3.0 Beta 2
527 -)))|(% colspan="1" %)(% colspan="1" %)
548 +)))|(% colspan="2" %)(% colspan="1" %)
528 528  (((
529 529  Support for entity flag "**skillsvisible**" dropped
530 530  )))
531 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
552 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
532 532  (((
533 533  //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().//
534 534  )))
... ... @@ -536,10 +536,10 @@
536 536  Scripts
537 537  )))|(((
538 538  3.0 Beta 2
539 -)))|(((
560 +)))|(% colspan="2" %)(((
540 540  Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**.
541 541  )))
542 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
563 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
543 543  (((
544 544  //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.
545 545  3.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.
... ... @@ -552,11 +552,11 @@
552 552  )))|(% colspan="1" %)(% colspan="1" %)
553 553  (((
554 554  3.0 Beta 1
555 -)))|(% colspan="1" %)(% colspan="1" %)
576 +)))|(% colspan="2" %)(% colspan="1" %)
556 556  (((
557 557  **MissionBoard** support dropped
558 558  )))
559 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
580 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
560 560  (((
561 561  //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.//
562 562  )))
... ... @@ -564,10 +564,10 @@
564 564  Job/God
565 565  )))|(((
566 566  3.0 Beta 1
567 -)))|(((
588 +)))|(% colspan="2" %)(((
568 568  By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined
569 569  )))
570 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
591 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
571 571  (((
572 572  //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.//
573 573  )))
... ... @@ -577,11 +577,11 @@
577 577  )))|(% colspan="1" %)(% colspan="1" %)
578 578  (((
579 579  3.0 Beta 1
580 -)))|(% colspan="1" %)(% colspan="1" %)
601 +)))|(% colspan="2" %)(% colspan="1" %)
581 581  (((
582 582  Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'**
583 583  )))
584 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
605 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
585 585  (((
586 586  //Due to engine changes, script action <add_actor_to_room/> has had the attribute 'room' changed to 'object', which is more accurate. Most likely requires a 'position' if a slot is not provided.//
587 587  )))
... ... @@ -591,11 +591,11 @@
591 591  )))|(% colspan="1" %)(% colspan="1" %)
592 592  (((
593 593  3.0 Beta 1
594 -)))|(% colspan="1" %)(% colspan="1" %)
615 +)))|(% colspan="2" %)(% colspan="1" %)
595 595  (((
596 596  Script action **<set_doors_locked/>** attribute **'group'** changed
597 597  )))
598 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
619 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
599 599  (((
600 600  //The 'group' attribute of <set_doors_locked/> can no longer be a list. It must be a single tag value. Previously, a list containing one tag was accepted, which was redundant.//
601 601  )))
... ... @@ -605,11 +605,11 @@
605 605  )))|(% colspan="1" %)(% colspan="1" %)
606 606  (((
607 607  3.0 Beta 1
608 -)))|(% colspan="1" %)(% colspan="1" %)
629 +)))|(% colspan="2" %)(% colspan="1" %)
609 609  (((
610 610  Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed
611 611  )))
612 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
633 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
613 613  (((
614 614  //These events were never triggered, with the exception of <event_hack_started/> on the player entity for instant control panel hacks. Use <event_player_hacked_object> instead.//
615 615  )))
... ... @@ -619,11 +619,11 @@
619 619  )))|(% colspan="1" %)(% colspan="1" %)
620 620  (((
621 621  3.0 Beta 1
622 -)))|(% colspan="1" %)(% colspan="1" %)
643 +)))|(% colspan="2" %)(% colspan="1" %)
623 623  (((
624 624  Script actions **<set_hack_target/>** and **<abort_hack/>** removed
625 625  )))
626 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
647 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
627 627  (((
628 628  //These actions had no effect and were removed.//
629 629  )))
... ... @@ -633,11 +633,11 @@
633 633  )))|(% colspan="1" %)(% colspan="1" %)
634 634  (((
635 635  3.0 Beta 1
636 -)))|(% colspan="1" %)(% colspan="1" %)
657 +)))|(% colspan="2" %)(% colspan="1" %)
637 637  (((
638 638  **<setup_conversation_minigame/>** script action removed
639 639  )))
640 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
661 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
641 641  (((
642 642  //The script action was a leftover from the XR era and was never supported in X4 and couldn't be used in a meaningful way. It was therefore decided to better drop it altogether as it's not expected having been used by any mods.//
643 643  )))
... ... @@ -647,11 +647,11 @@
647 647  )))|(% colspan="1" %)(% colspan="1" %)
648 648  (((
649 649  3.0 Beta 1
650 -)))|(% colspan="1" %)(% colspan="1" %)
671 +)))|(% colspan="2" %)(% colspan="1" %)
651 651  (((
652 652  <add_player_choice_*> **confidence** attribute removed
653 653  )))
654 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
675 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
655 655  (((
656 656  //The default confidence of player options is another leftover from the XR era and had no effect in X4.//
657 657  )))
... ... @@ -661,11 +661,11 @@
661 661  )))|(% colspan="1" %)(% colspan="1" %)
662 662  (((
663 663  3.0 Beta 1
664 -)))|(% colspan="1" %)(% colspan="1" %)
685 +)))|(% colspan="2" %)(% colspan="1" %)
665 665  (((
666 666  **<hack_via_control_panel/>** script action removed
667 667  )))
668 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
689 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
669 669  (((
670 670  //Unused script action <hack_via_control_panel/> was removed.//
671 671  )))
... ... @@ -675,11 +675,11 @@
675 675  )))|(% colspan="1" %)(% colspan="1" %)
676 676  (((
677 677  3.0 Beta 1
678 -)))|(% colspan="1" %)(% colspan="1" %)
699 +)))|(% colspan="2" %)(% colspan="1" %)
679 679  (((
680 680  **Lua: **GetMiniGameCursorPosition() removed
681 681  )))
682 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
703 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
683 683  (((
684 684  //GetMiniGameCursorPosition() was a left over from the XR era and never supposed to be shipped with X4. The function practically always returned 0 and hence we don't expect the removal of this obsolete function causing any actual mod to break.//
685 685  )))
... ... @@ -687,10 +687,10 @@
687 687  UI core
688 688  )))|(((
689 689  3.0 Beta 1
690 -)))|(((
711 +)))|(% colspan="2" %)(((
691 691  **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders
692 692  )))
693 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
714 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
694 694  (((
695 695  //In 3.0 Beta 1 we added support to display icons for keyboard bindings, if an icon is available for the specified keys. This results in GetLocalizedInteractiveNotificationKey() potentially returning a different text now if such an icon is assigned to the mapped key/button.//
696 696  )))
... ... @@ -700,11 +700,11 @@
700 700  )))|(% colspan="1" %)(% colspan="1" %)
701 701  (((
702 702  3.0 Beta 1
703 -)))|(% colspan="1" %)(% colspan="1" %)
724 +)))|(% colspan="2" %)(% colspan="1" %)
704 704  (((
705 705  **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor
706 706  )))
707 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
728 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
708 708  (((
709 709  //In 3.0 Beta 1 we added support for a new weapon mod property "SurfaceElementFactor" to allow weapons to deal increased damage to surface elements such as Shield Generators, Turrets or Engines.//
710 710  )))
... ... @@ -714,11 +714,11 @@
714 714  )))|(% colspan="1" %)(% colspan="1" %)
715 715  (((
716 716  3.0 Beta 1
717 -)))|(% colspan="1" %)(% colspan="1" %)
738 +)))|(% colspan="2" %)(% colspan="1" %)
718 718  (((
719 719  **$ware.illegal** updated
720 720  )))
721 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
742 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
722 722  (((
723 723  //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.//
724 724  //It now returns true if $ware is illegal to any faction in the game.//
... ... @@ -729,11 +729,11 @@
729 729  )))|(% colspan="1" %)(% colspan="1" %)
730 730  (((
731 731  3.0 Beta 1
732 -)))|(% colspan="1" %)(% colspan="1" %)
753 +)))|(% colspan="2" %)(% colspan="1" %)
733 733  (((
734 734  MD script **RML_Flight_Along_Path** removed
735 735  )))
736 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
757 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
737 737  (((
738 738  //The MD script RML_Flight_Along_Path was not referened and was removed.//
739 739  )))
... ... @@ -743,11 +743,11 @@
743 743  )))|(% colspan="1" %)(% colspan="1" %)
744 744  (((
745 745  3.0 Beta 1
746 -)))|(% colspan="1" %)(% colspan="1" %)
767 +)))|(% colspan="2" %)(% colspan="1" %)
747 747  (((
748 748  parameters of **<event_venture_mission_completed/>** changed
749 749  )))
750 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
771 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
751 751  (((
752 752  //old params: param = venture details, param2 = ships involved, param3 = duration//
753 753  //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration//
... ... @@ -756,11 +756,11 @@
756 756  Scripts
757 757  )))|(((
758 758  3.0 Beta 1
759 -)))|(((
780 +)))|(% colspan="2" %)(((
760 760  **<set_object_wing_name/>** removed,
761 761  **<set_object_fleet_name/>** added
762 762  )))
763 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
784 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
764 764  (((
765 765  //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>//
766 766  )))
... ... @@ -768,26 +768,28 @@
768 768  Scripts
769 769  )))|(((
770 770  3.0 Beta 1
771 -)))|(((
792 +)))|(% colspan="2" %)(((
772 772  **$controllable.wing.*** removed,
773 773  **$controllable.fleet.*** added
774 774  )))
775 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
796 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
776 776  (((
777 777  $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander
778 778  )))
779 -|(% colspan="3" %)(% colspan="3" %)
780 -(((
781 -== 2.60 ==
782 -)))
800 +
801 +----
802 +
803 +=== Version 2.60 ===
804 +
805 +(% class="wrapped" %)
783 783  |(((
784 784  Scripts
785 785  )))|(((
786 786  2.60 Beta 1
787 -)))|(((
810 +)))|(% colspan="2" %)(((
788 788  '**checkoperational**' filter behaviour changed
789 789  )))
790 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
813 +|(% class="highlight-grey" colspan="10" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
791 791  (((
792 792  //Actions and conditions which use the 'checkoperational' filter now behave differently. Instead of changing how 'class' and 'exactclass' behave, checkoperational == true adds an additional filter for the components being of state operational, equivalent to state="componentstate.operational". This is implicitly enabled in action elements (e.g. <find_.../>) or condition elements (e.g. <count_...>), meaning that find_ship will only find operational ships. Using such actions/conditions with checkoperational="false" will include non-operational components such as wrecked and constructions. Existing uses may find that results now exclude non-operational components.//
793 793  
... ... @@ -797,17 +797,19 @@
797 797  Scripts
798 798  )))|(((
799 799  2.60 Beta 1
800 -)))|(((
823 +)))|(% colspan="2" %)(((
801 801  $container.**supplyresources** behavior changed
802 -)))
803 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
825 +)))| | |
826 +|(% class="highlight-grey" colspan="10" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
804 804  (((
805 805  //The script keyword $container.supplyresources now includes reserved wares.//
806 806  )))
807 -|(% colspan="3" %)(% colspan="3" %)
808 -(((
809 -== 2.20 ==
810 -)))
830 +
831 +----
832 +
833 +=== Version 2.20 ===
834 +
835 +(% class="wrapped" %)
811 811  |(% colspan="1" %)(% colspan="1" %)
812 812  (((
813 813  UI core
... ... @@ -814,17 +814,16 @@
814 814  )))|(% colspan="1" %)(% colspan="1" %)
815 815  (((
816 816  2.20 Beta 3/4
817 -)))|(% colspan="1" %)(% colspan="1" %)
842 +)))|(% colspan="2" %)(% colspan="1" %)
818 818  (((
819 819  **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined.
820 820  )))
821 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
846 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
822 822  (((
823 823  //2.20 Beta 3 introduced the new direct mouse steering mode. The mode was however not integrated as a first level mode and hence GetControllerInfo() returned the "gamepad" mode while direct mouse steering was active.
824 824  In 2.20 Beta 4 we improved the situation slightly so that a call to GetControllerInfo() will return either "mouseCursor" or "mouseSteering" in any of the 3 mouse modes.//
825 825  
826 -//It's a pending change to ensure that the returned mode is more reasonable in an upcoming patch. So be aware that another breaking change might be introduced at some point.
827 -//
851 +//It's a pending change to ensure that the returned mode is more reasonable in an upcoming patch. So be aware that another breaking change might be introduced at some point.//
828 828  )))
829 829  |(% colspan="1" %)(% colspan="1" %)
830 830  (((
... ... @@ -832,18 +832,20 @@
832 832  )))|(% colspan="1" %)(% colspan="1" %)
833 833  (((
834 834  2.20 Beta 3
835 -)))|(% colspan="1" %)(% colspan="1" %)
859 +)))|(% colspan="2" %)(% colspan="1" %)
836 836  (((
837 837  Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor'
838 838  )))
839 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
863 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
840 840  (((
841 841  //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.//
842 842  )))
843 -|(% colspan="3" %)(% colspan="3" %)
844 -(((
845 -== 2.00 ==
846 -)))
867 +
868 +----
869 +
870 +=== Version 2.00 ===
871 +
872 +(% class="wrapped" %)
847 847  |(% colspan="1" %)(% colspan="1" %)
848 848  (((
849 849  Scripts
... ... @@ -850,11 +850,11 @@
850 850  )))|(% colspan="1" %)(% colspan="1" %)
851 851  (((
852 852  2.00 Beta 1
853 -)))|(% colspan="1" %)(% colspan="1" %)
879 +)))|(% colspan="2" %)(% colspan="1" %)
854 854  (((
855 855  **<event_build_finished/> **param2 now returns null instead of a construction sequence
856 856  )))
857 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
883 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
858 858  (((
859 859  //The construction sequence which was finished should now be accessed via the buildtask provided via param3.//
860 860  )))
... ... @@ -864,11 +864,11 @@
864 864  )))|(% colspan="1" %)(% colspan="1" %)
865 865  (((
866 866  2.00 Beta 1
867 -)))|(% colspan="1" %)(% colspan="1" %)
893 +)))|(% colspan="2" %)(% colspan="1" %)
868 868  (((
869 869  **param.boarding.{...}** strength parameters removed
870 870  )))
871 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
897 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
872 872  (((
873 873  //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.//
874 874  )))
... ... @@ -878,11 +878,11 @@
878 878  )))|(% colspan="1" %)(% colspan="1" %)
879 879  (((
880 880  2.00 Beta 1
881 -)))|(% colspan="1" %)(% colspan="1" %)
907 +)))|(% colspan="2" %)(% colspan="1" %)
882 882  (((
883 883  **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed
884 884  )))
885 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
911 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
886 886  (((
887 887  //Due to changes to boarding in X4, the boarding connections accessed by these script properties and actions became redundent and thus, removed. Any connections set by these actions in a savegame will not survive loading.//
888 888  )))
... ... @@ -890,10 +890,10 @@
890 890  UI extensions
891 891  )))|(((
892 892  2.00 Beta 1
893 -)))|(((
919 +)))|(% colspan="2" %)(((
894 894  **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals
895 895  )))
896 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
922 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
897 897  (((
898 898  //Before 2.0 Beta 1 using GetUpgradeSlotCurrentComponent() or GetUpgradeSlotGroup() only performed on operational objects (i.e. not wrecked objects or objects under construction). Since this is inconsistent with the rest of the UI functions, this was considered a bug and fixed in 2.0 Beta 1. If you require the old behavior, use the FFI function: IsComponentOperational() to check the passed object's state before making the call.//
899 899  )))
... ... @@ -901,10 +901,10 @@
901 901  UI extensions
902 902  )))|(((
903 903  2.00 Beta 1
904 -)))|(((
930 +)))|(% colspan="2" %)(((
905 905  **FFI: SetFormationShape()** no longer indicates an error upon certain error cases
906 906  )))
907 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
933 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
908 908  (((
909 909  //Before 2.0 Beta 1 a call to SetFormationShape() indicated an error state to the caller in certain cases where setting a formation shape (potentially) failed. Due to a design flaw in the handling of formations, this however doesn't do any good, since the function by itself doesn't really set the formation shape in all cases. On top of that the call can fail at random. Hence, at the moment an indication of an error case that setting a formation potentially fails is no good to the caller and he has no means to distinguish that case from a real error case.//
910 910  //Therefore, in 2.0 Beta 1 we drop the error indication in case of an attempt to set the formation fails. We are currently working on a better solution to the underlying problem and hope to have it ready as part of a following beta.//
... ... @@ -913,10 +913,10 @@
913 913  Scripts
914 914  )))|(((
915 915  2.00 Beta 1
916 -)))|(((
942 +)))|(% colspan="2" %)(((
917 917  **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated.
918 918  )))
919 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
945 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
920 920  (((
921 921  //This now enforces a leader and at least one follower in order to create or change a formation.  Former implementation made it possible to create formations without any followers which led to issues.//
922 922  )))
... ... @@ -924,10 +924,10 @@
924 924  Scripts
925 925  )))|(((
926 926  2.00 Beta 1
927 -)))|(((
953 +)))|(% colspan="2" %)(((
928 928  **<event_player_changed_target/>** now fires and returns null if the player deselects a target.
929 929  )))
930 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
956 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
931 931  (((
932 932  //For prior behavior, check for event.param being non-null.//
933 933  )))
... ... @@ -935,10 +935,10 @@
935 935  AI Scripts
936 936  )))|(((
937 937  2.00 Beta 1
938 -)))|(((
964 +)))|(% colspan="2" %)(((
939 939  **<shoot/>/<shoot_at/>** attribute changes.
940 940  )))
941 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
967 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
942 942  (((
943 943  //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.//
944 944  //New attribute: "secondary" is an optional attribute that defines whether weapons from the ship's active secondary weapon group will be fired. Defaults to true.//
... ... @@ -950,10 +950,10 @@
950 950  UI extensions
951 951  )))|(((
952 952  2.00 Beta 1
953 -)))|(((
979 +)))|(% colspan="2" %)(((
954 954  **FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.
955 955  )))
956 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
982 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
957 957  (((
958 958  //Added possibility to query build tasks of a certain buildmodule.//
959 959  )))
... ... @@ -961,10 +961,10 @@
961 961  UI extensions
962 962  )))|(((
963 963  2.00 Beta 1
964 -)))|(((
990 +)))|(% colspan="2" %)(((
965 965  **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field.
966 966  )))
967 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
993 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
968 968  (((
969 969  //Added list of resources a buildmodule needs to build.//
970 970  )))
... ... @@ -972,10 +972,10 @@
972 972  UI extensions
973 973  )))|(((
974 974  2.00 Beta 1
975 -)))|(((
976 -(% style="color: rgb(0,0,0);" %)**Lua:**(% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)** CalculateTotalHullFraction()**(% style="color: rgb(0,0,0);" %)** **(%%)was removed.(% style="color: rgb(0,0,0);" %)
1001 +)))|(% colspan="2" %)(((
1002 +**Lua: CalculateTotalHullFraction() **was removed.
977 977  )))
978 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1004 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
979 979  (((
980 980  //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.//
981 981  )))
... ... @@ -983,25 +983,27 @@
983 983  UI extensions
984 984  )))|(((
985 985  2.00 Beta 1
986 -)))|(((
987 -**FFI: (% style="color: rgb(0,0,0);" %)RequestDockAtReason()/(% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)UndockPlayerShip()(%%) **changed their return values.
1012 +)))|(% colspan="2" %)(((
1013 +**FFI: RequestDockAtReason()/UndockPlayerShip() **changed their return values.
988 988  )))
989 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1015 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
990 990  (((
991 991  //Changed return value type to const char* to better identify failure reasons in Lua script.//
992 992  )))
993 -|(% colspan="3" %)(% colspan="3" %)
994 -(((
995 -== 1.50 ==
996 -)))
1019 +
1020 +----
1021 +
1022 +=== Version 1.50 ===
1023 +
1024 +(% class="wrapped" %)
997 997  |(((
998 998  UI extensions
999 999  )))|(((
1000 1000  1.50 Beta 3
1001 -)))|(((
1029 +)))|(% colspan="2" %)(((
1002 1002  **Lua: GetComponentData() **changed behavior of "docksizes" property.
1003 1003  )))
1004 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1032 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1005 1005  (((
1006 1006  //The "docksizes" property no longer includes internal ship storage docks.//
1007 1007  )))
... ... @@ -1009,10 +1009,10 @@
1009 1009  All
1010 1010  )))|(((
1011 1011  1.50 Beta 2
1012 -)))|(((
1040 +)))|(% colspan="2" %)(((
1013 1013  **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR).
1014 1014  )))
1015 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1043 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1016 1016  (((
1017 1017  //Shipyards (formerly also known as Capital Shipyards) can build capital ships, while Wharfs only build non-capital ships. To check whether a station is a Shipyard or a Wharf, check whether the station "can build ships".//
1018 1018  
... ... @@ -1024,10 +1024,10 @@
1024 1024  UI extensions
1025 1025  )))|(((
1026 1026  1.50 Beta 2
1027 -)))|(((
1055 +)))|(% colspan="2" %)(((
1028 1028  **FFI: UpgradeGroupInfo **datatype was changed.
1029 1029  )))
1030 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1058 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1031 1031  (((
1032 1032  //Added new "operational" field to retrieve information about number of operational upgrades in a group.//
1033 1033  )))
... ... @@ -1037,14 +1037,13 @@
1037 1037  )))|(% colspan="1" %)(% colspan="1" %)
1038 1038  (((
1039 1039  1.50 Beta 1
1040 -)))|(% colspan="1" %)(% colspan="1" %)
1068 +)))|(% colspan="2" %)(% colspan="1" %)
1041 1041  (((
1042 1042  **FFI: SetGuidance()** removed useinfopoint argument.
1043 1043  )))
1044 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1072 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1045 1045  (((
1046 -//In X Rebirth "info points" existed (which were mainly used as interaction points to scan stations/access information about modules). These were removed in X4 but this left-over property here was missed to be removed in-time for release. It was therefore removed now in order to move towards a stable/clean UI API.
1047 -//
1074 +//In X Rebirth "info points" existed (which were mainly used as interaction points to scan stations/access information about modules). These were removed in X4 but this left-over property here was missed to be removed in-time for release. It was therefore removed now in order to move towards a stable/clean UI API.//
1048 1048  
1049 1049  //The new function declaration is: void SetGuidance(UniverseID componentid, UIPosRot offset)//
1050 1050  )))
... ... @@ -1052,40 +1052,44 @@
1052 1052  UI extensions
1053 1053  )))|(((
1054 1054  1.50 Beta 1
1055 -)))|(((
1082 +)))|(% colspan="2" %)(((
1056 1056  **FFI: CancelConstruction() **changed its return value.
1057 1057  )))
1058 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1085 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1059 1059  (((
1060 -(% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. //
1087 +//CancelConstruction() now returns if the cancellation was successful. //
1061 1061  )))
1062 -|(% colspan="3" %)(% colspan="3" %)
1063 -(((
1064 -== 1.32 ==
1065 -)))
1089 +
1090 +----
1091 +
1092 +=== Version 1.32 ===
1093 +
1094 +(% class="wrapped" %)
1066 1066  |(((
1067 1067  UI extensions
1068 1068  )))|(((
1069 1069  1.32
1070 -)))|(((
1099 +)))|(% colspan="2" %)(((
1071 1071  **Lua: GetComponentData() **removed the "nextdestname" property.
1072 1072  )))
1073 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1102 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1074 1074  (((
1075 1075  //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.//
1076 1076  )))
1077 -|(% colspan="3" %)(% colspan="3" %)
1078 -(((
1079 -== 1.20 ==
1080 -)))
1106 +
1107 +----
1108 +
1109 +=== Version 1.20 ===
1110 +
1111 +(% class="wrapped" %)
1081 1081  |(((
1082 1082  UI extensions
1083 1083  )))|(((
1084 1084  1.20
1085 -)))|(((
1116 +)))|(% colspan="2" %)(((
1086 1086  **FFI: GetAAOption()** got a new "useconfig" parameter.
1087 1087  )))
1088 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1119 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1089 1089  (((
1090 -//The AA setting was changed to check the new setting with the user. In order to restore the old setting (% style="color: rgb(0,0,0);" %)GetAAOption() gets the option to retrieve the config settings.//
1121 +//The AA setting was changed to check the new setting with the user. In order to restore the old setting GetAAOption() gets the option to retrieve the config settings.//
1091 1091  )))