Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 114.1
edited by Owen Lake
on 2024/01/31 12:40
Change comment: There is no comment for this version
To version 87.1
edited by owen
on 2021/06/10 13:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,0 @@
1 -X4 Foundations Wiki.Modding Support.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.Owen
1 +xwiki:XWiki.owen
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 -{{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.
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.
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 -{{/info}}
13 +{{/note}}
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,310 +18,70 @@
18 18  
19 19  = Breaking Changes =
20 20  
21 -{{toc scope="LOCAL" start="3"/}}
22 -
23 -=== Version 7.00 ===
24 -
25 -
26 -(% class="wrapped" %)
27 -|(% colspan="1" style="width:117px" %)(% colspan="1" %)
21 +|=(((
22 +Type
23 +)))|=(((
24 +Version
25 +)))|=(((
26 +Summary
27 +)))|=(% colspan="1" %)(% colspan="1" %)
28 28  (((
29 -Scripts
30 -)))|(% colspan="1" style="width:119px" %)(((
31 -7.00 Beta 1
32 -)))|(% colspan="2" style="width:1625px" %)(((
33 -MD action **<set_presentation_cluster_persistence/>** now requires the cluster to be a presentation cluster.
29 +
34 34  )))
35 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
31 +|(% colspan="4" %)(% colspan="4" %)
36 36  (((
37 -// Previously it was possible to set normal clusters to be persistent presentation clusters which was an invalid state.//
33 +== 4.10 ==
38 38  )))
39 -|(% colspan="1" style="width:117px" %)(% colspan="1" %)
40 -(((
41 -UI extensions
42 -)))|(% colspan="1" style="width:119px" %)(((
43 -7.00 Beta 1
44 -)))|(% colspan="2" style="width:1625px" %)(((
45 -**FFI**: RemoveBuildPlot() changed
46 -)))
47 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
48 -(((
49 -// 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.//
50 -)))
51 -|(% colspan="1" style="width:117px" %)(% colspan="1" %)
52 -(((
53 -Assets
54 -)))|(% colspan="1" style="width:119px" %)(((
55 -7.00 Beta 1
56 -)))|(% colspan="2" style="width:1625px" %)(((
57 -**Some Split DLC materials moved to base game**
58 -)))
59 -|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
60 -(((
61 -// //"spl_p1_fx" AND "split_p1_hulltexture_01" were moved from Split DLC to base game
62 -)))
63 -
64 -----
65 -
66 -=== Version 6.00 ===
67 -
68 -(% class="wrapped" %)
69 69  |(((
70 -Libraries
71 -)))|(((
72 -6.00 Beta 7
73 -)))|(% colspan="2" %)(((
74 -Updated weights for ship groups in shipgroups.xml libraries of base game and all DLCs.
75 -)))
76 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
77 -(((
78 -//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.//
79 -
80 -//All groups should now have "weight" parameter added and old "weights" were updated to not have single-digit numbers.//
81 -)))
82 -|(% colspan="1" %)(% colspan="1" %)
83 -(((
84 84  Scripts
85 -)))|(% colspan="1" %)(% colspan="1" %)
86 -(((
87 -6.00 Beta 4
88 -)))|(% colspan="2" %)(% colspan="1" %)
89 -(((
90 -Changed conditions for **<event_player_travelmode_started> <event_player_travelmode_stopped> <event_player_travelmode_charge_started> <event_player_travelmode_charge_aborted>** to be raised.
91 -)))
92 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
93 -(((
94 -//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. //
95 -
96 -//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.//
97 -)))
98 -|(% colspan="1" %)(% colspan="1" %)
99 -(((
100 -Scripts
101 -)))|(% colspan="1" %)(% colspan="1" %)
102 -(((
103 -6.00 Beta 3
104 -)))|(% colspan="2" %)(% colspan="1" %)
105 -(((
106 -Changed result of **<find_object_surface>** action in the case of a failure
107 -)))
108 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
109 -(((
110 -//The 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.//
111 -
112 -//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.//
113 -
114 -//The action itself has been improved to increase the chance of finding suitable surface positions.//
115 -)))
116 -|(% colspan="1" %)(% colspan="1" %)
117 -(((
118 -Scripts
119 -)))|(% colspan="1" %)(% colspan="1" %)
120 -(((
121 -6.00 Beta 1
122 -)))|(% colspan="2" %)(% colspan="1" %)
123 -(((
124 -Behaviour change for **<match_dock>** script component filter
125 -)))
126 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
127 -(((
128 -//<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes.
129 -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.//
130 -)))
131 -|(% colspan="1" %)(% colspan="1" %)
132 -(((
133 -Scripts
134 -)))|(% colspan="1" %)(% colspan="1" %)
135 -(((
136 -6.00 Beta 1
137 -)))|(% colspan="2" %)(% colspan="1" %)
138 -(((
139 -Changed result attribute location for **<get_attackstrength>**
140 -)))
141 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
142 -(((
143 -//The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.//
144 -)))
145 -|(((
146 -Assets
147 147  )))|(((
148 -6.00 Beta 1
149 -)))|(% colspan="2" %)(((
150 -Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons
151 -)))
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%" %)
153 -(((
154 -//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.
155 -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.//
156 -)))
157 -|(% colspan="1" %)(% colspan="1" %)
158 -(((
159 -Scripts
160 -)))|(% colspan="1" %)(% colspan="1" %)
161 -(((
162 -6.00 Beta 1
163 -)))|(% colspan="2" %)(% colspan="1" %)
164 -(((
165 -Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects
166 -)))
167 -|(% 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%" %)
168 -(((
169 -//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.//
170 -)))
171 -|(((
172 -Scripts
38 +4.10 Beta 1
173 173  )))|(((
174 -6.00 Beta 1
175 -)))|(% colspan="2" %)(((
176 -**<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards.
177 -)))
178 -|(% 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%" %)
179 -(((
180 -//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.//
181 -)))
182 -|(((
183 -Cutscenes
40 +People related attributes of mission** <delivery> **node moved
184 184  )))|(((
185 -6.00 Beta 1
186 -)))|(% colspan="2" %)(((
187 -Changed behaviour of **<angles>** in cutscenes
42 +
188 188  )))
189 -|(% 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%" %)
44 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
190 190  (((
191 -//The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.//
46 +//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.//
192 192  )))
193 -
194 -----
195 -
196 -=== Version 5.00 ===
197 -
198 -(% class="wrapped" %)
199 -|(((
200 -Parameters
201 -)))|(((
202 -5.00 Beta 1
203 -)))|(% colspan="2" %)(((
204 -**<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration
205 -)))
206 -|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
207 -(((
208 -//'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.//
209 -)))
210 -
211 -----
212 -
213 -=== Version 4.10 ===
214 -
215 -(% class="wrapped" %)
216 216  |(% colspan="1" %)(% colspan="1" %)
217 217  (((
218 -UI extensions
50 +Scripts
219 219  )))|(% colspan="1" %)(% colspan="1" %)
220 220  (((
221 -4.10 Beta 7
222 -)))|(% colspan="2" %)(% colspan="1" %)
223 -(((
224 -**FFI**: SetMapRenderCargoContents(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos() deprecated
225 -)))
226 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
227 -(((
228 -//The functionality represented by SetMapRenderCargoContents(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos() has been removed and the function was therefore stubbed.//
229 -)))
230 -|(% colspan="1" %)(% colspan="1" %)
231 -(((
232 -UI extensions
53 +4.10 Beta 1
233 233  )))|(% colspan="1" %)(% colspan="1" %)
234 234  (((
235 -4.10 Beta 6
236 -)))|(% colspan="2" %)(% colspan="1" %)
237 -(((
238 -**FFI**: CustomGameStartPlayerProperty2 changed
239 -)))
240 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
241 -(((
242 -//This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.//
243 -)))
244 -|(% colspan="1" %)(% colspan="1" %)
245 -(((
246 -Parameters
56 +**$destructible.productions** replaced with $defensible.productions
247 247  )))|(% colspan="1" %)(% colspan="1" %)
248 248  (((
249 -4.10 Beta 3
250 -)))|(% colspan="2" %)(% colspan="1" %)
251 -(((
252 -Renamed **<stationinfobox>** to **<infobox>**
59 +
253 253  )))
254 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
61 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
255 255  (((
256 -//Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.//
257 -)))
258 -|(% colspan="1" %)(% colspan="1" %)
259 -(((
260 -UI extensions
63 +//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.//
261 261  )))|(% colspan="1" %)(% colspan="1" %)
262 262  (((
263 -4.10 Beta 2
264 -)))|(% colspan="2" %)(% colspan="1" %)
265 -(((
266 -**FFI**: SetMacroMapPlayerSectorOffset() deprecated
66 +
267 267  )))
268 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
269 -(((
270 -//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.//
271 -)))
272 272  |(((
273 -UI extensions
274 -)))|(((
275 -4.10 Beta 2
276 -)))|(% colspan="2" %)(((
277 -**FFI**: FilterComponentForMapMode() and SetMapObjectFilter() changed
278 -)))
279 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
280 -(((
281 -//These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.//
282 -)))
283 -|(((
284 284  Scripts
285 285  )))|(((
286 286  4.10 Beta 1
287 -)))|(% colspan="2" %)(((
288 -People related attributes of mission** <delivery> **node moved
289 -)))
290 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
291 -(((
292 -//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.//
293 -)))
294 -|(% colspan="1" %)(% colspan="1" %)
295 -(((
296 -Scripts
297 -)))|(% colspan="1" %)(% colspan="1" %)
298 -(((
299 -4.10 Beta 1
300 -)))|(% colspan="2" %)(% colspan="1" %)
301 -(((
302 -**$destructible.productions** replaced with $defensible.productions
303 -)))
304 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
305 -(((
306 -//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.//
307 -)))
308 -|(((
309 -Scripts
310 310  )))|(((
311 -4.10 Beta 1
312 -)))|(% colspan="2" %)(((
313 313  Removed script property **$object.spawnsourceseed**
74 +)))|(((
75 +
314 314  )))
315 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
77 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
316 316  (((
317 317  //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.//
318 318  )))
319 -
320 -----
321 -
322 -=== Version 4.00 ===
323 -
324 -(% class="wrapped" %)
81 +|(% colspan="4" %)(% colspan="4" %)
82 +(((
83 +== 4.00 ==
84 +)))
325 325  |(% colspan="1" %)(% colspan="1" %)
326 326  (((
327 327  UI core
... ... @@ -328,27 +328,39 @@
328 328  )))|(% colspan="1" %)(% colspan="1" %)
329 329  (((
330 330  4.00 Beta 10
331 -)))|(% colspan="2" %)(% colspan="1" %)
91 +)))|(% colspan="1" %)(% colspan="1" %)
332 332  (((
333 333  Controlled ship can change without a **gameplanchange-event** occurring.
94 +)))|(% colspan="1" %)(% colspan="1" %)
95 +(((
96 +
334 334  )))
335 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
98 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
336 336  (((
337 337  //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).
338 -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.//
101 +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.
102 +//
103 +)))|(% colspan="1" %)(% colspan="1" %)
104 +(((
105 +
339 339  )))
340 340  |(((
341 341  Scripts
342 342  )))|(((
343 343  4.00 Beta 7
344 -)))|(% colspan="2" %)(((
111 +)))|(((
345 345  Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed
113 +)))|(((
114 +
346 346  )))
347 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
116 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
348 348  (((
349 349  //Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects?
350 350  New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits
351 351  Note: param3 only exists in <event_terraforming_project_succeeded> and not in <event_terraforming_project_failed>, but both now have the booleans in a list for consistency//
121 +)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %)
122 +(((
123 +
352 352  )))
353 353  |(% colspan="1" %)(% colspan="1" %)
354 354  (((
... ... @@ -356,16 +356,23 @@
356 356  )))|(% colspan="1" %)(% colspan="1" %)
357 357  (((
358 358  4.00 Beta 6
359 -)))|(% colspan="2" %)(% colspan="1" %)
131 +)))|(% colspan="1" %)(% colspan="1" %)
360 360  (((
361 361  **FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed
134 +)))|(% colspan="1" %)(% colspan="1" %)
135 +(((
136 +
362 362  )))
363 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
138 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
364 364  (((
365 365  //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.
366 366  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).//
367 367  
368 -//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.//
143 +//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.
144 +//
145 +)))|(% colspan="1" %)(% colspan="1" %)
146 +(((
147 +
369 369  )))
370 370  |(% colspan="1" %)(% colspan="1" %)
371 371  (((
... ... @@ -373,24 +373,32 @@
373 373  )))|(% colspan="1" %)(% colspan="1" %)
374 374  (((
375 375  4.00 Beta 5
376 -)))|(% colspan="2" %)(% colspan="1" %)
155 +)))|(% colspan="1" %)(% colspan="1" %)
377 377  (((
378 378  **FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed
158 +)))|(% colspan="1" %)(% colspan="1" %)
159 +(((
160 +
379 379  )))
380 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
162 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
381 381  (((
382 382  //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.//
383 383  
384 384  //If you rely on a handling where they are treated like enemies, please use the new GetRelationStatus3() //function which returns the new range for these objects: 1 (meaning 'enemy' (aka: not yet hostile) here with following relations having been shifted up).
167 +)))|(% colspan="1" %)(% colspan="1" %)
168 +(((
169 +
385 385  )))
386 386  |(((
387 387  Parameters
388 388  )))|(((
389 389  4.00 Beta 1
390 -)))|(% colspan="2" %)(((
175 +)))|(((
391 391  **requiresconstructionvessel** parameter moved
177 +)))|(((
178 +
392 392  )))
393 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
180 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
394 394  (((
395 395  //The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.//
396 396  )))
... ... @@ -398,44 +398,51 @@
398 398  Scripts
399 399  )))|(((
400 400  4.00 Beta 1
401 -)))|(% colspan="2" %)(((
188 +)))|(((
402 402  Changed behaviour of **gatedistance** script property
190 +)))|(((
191 +
403 403  )))
404 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
193 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
405 405  (((
406 406  //The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.//
196 +)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %)
197 +(((
198 +
407 407  )))
408 -
409 -----
410 -
411 -=== Version 3.30 ===
412 -
413 -(% class="wrapped" %)
200 +|(% colspan="4" %)(% colspan="4" %)
201 +(((
202 +== 3.30 ==
203 +)))
414 414  |(((
415 415  UI extensions
416 416  )))|(((
417 417  3.30 Beta 3
418 -)))|(% colspan="2" %)(((
419 -**FFI: **Removed** GetMissionLimit() **and** IsMissionLimitEnabled()**
208 +)))|(((
209 +**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()**
210 +)))|(% colspan="1" %)(% colspan="1" %)
211 +(((
212 +
420 420  )))
421 -|(% class="highlight-grey" colspan="7" 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="4" data-highlight-colour="grey" %)
422 422  (((
423 -//These mission limit-related functions (added in 3.30 Beta 1 and 2) are replaced with FFI IsMissionLimitReached()//
216 +//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()//
424 424  )))
425 -
426 -----
427 -
428 -=== Version 3.20 ===
429 -
430 -(% class="wrapped" %)
218 +|(% colspan="4" %)(% colspan="4" %)
219 +(((
220 +== 3.20 ==
221 +)))
431 431  |(((
432 432  Scripts
433 433  )))|(((
434 434  3.20 Beta 1
435 -)))|(% colspan="2" %)(((
226 +)))|(((
436 436  Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed
228 +)))|(% colspan="1" %)(% colspan="1" %)
229 +(((
230 +
437 437  )))
438 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
232 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
439 439  (((
440 440  //Old params: param = attacked object, param2 = attack method, param3 = attacked component//
441 441  //New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon]
... ... @@ -447,11 +447,14 @@
447 447  )))|(% colspan="1" %)(% colspan="1" %)
448 448  (((
449 449  3.20 Beta 1
450 -)))|(% colspan="2" %)(% colspan="1" %)
244 +)))|(% colspan="1" %)(% colspan="1" %)
451 451  (((
452 452  Removed script property $trade.**restriction.faction**
247 +)))|(% colspan="1" %)(% colspan="1" %)
248 +(((
249 +
453 453  )))
454 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
251 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
455 455  (((
456 456  //$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.//
457 457  )))
... ... @@ -459,19 +459,20 @@
459 459  UI extensions
460 460  )))|(((
461 461  3.20 Beta 1
462 -)))|(% colspan="2" %)(((
259 +)))|(((
463 463  **Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete!
261 +)))|(% colspan="1" %)(% colspan="1" %)
262 +(((
263 +
464 464  )))
465 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
265 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
466 466  (((
467 467  //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.//
468 468  )))
469 -
470 -----
471 -
472 -=== Version 3.10 ===
473 -
474 -(% class="wrapped" %)
269 +|(% colspan="4" %)(% colspan="4" %)
270 +(((
271 +== 3.10 ==
272 +)))
475 475  |(% colspan="1" %)(% colspan="1" %)
476 476  (((
477 477  Scripts
... ... @@ -478,20 +478,21 @@
478 478  )))|(% colspan="1" %)(% colspan="1" %)
479 479  (((
480 480  3.10 Beta 1
481 -)))|(% colspan="2" %)(% colspan="1" %)
279 +)))|(% colspan="1" %)(% colspan="1" %)
482 482  (((
483 483  Removed script action **<add_build/>**
282 +)))|(% colspan="1" %)(% colspan="1" %)
283 +(((
284 +
484 484  )))
485 -|(% class="highlight-grey" colspan="7" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
286 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
486 486  (((
487 487  //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.//
488 488  )))
489 -
490 -----
491 -
492 -=== Version 3.00 ===
493 -
494 -(% class="wrapped" %)
290 +|(% colspan="4" %)(% colspan="4" %)
291 +(((
292 +== 3.00 ==
293 +)))
495 495  |(% colspan="1" %)(% colspan="1" %)
496 496  (((
497 497  Scripts
... ... @@ -498,11 +498,14 @@
498 498  )))|(% colspan="1" %)(% colspan="1" %)
499 499  (((
500 500  3.0 Beta 6
501 -)))|(% colspan="2" %)(% colspan="1" %)
300 +)))|(% colspan="1" %)(% colspan="1" %)
502 502  (((
503 503  Changed behaviour of script action **<get_suitable_job/>**
303 +)))|(% colspan="1" %)(% colspan="1" %)
304 +(((
305 +
504 504  )))
505 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
307 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
506 506  (((
507 507  //<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.//
508 508  )))
... ... @@ -512,11 +512,14 @@
512 512  )))|(% colspan="1" %)(% colspan="1" %)
513 513  (((
514 514  3.0 Beta 6
515 -)))|(% colspan="2" %)(% colspan="1" %)
317 +)))|(% colspan="1" %)(% colspan="1" %)
516 516  (((
517 517  Changed behaviour of script action **<get_ware_definition/>**
320 +)))|(% colspan="1" %)(% colspan="1" %)
321 +(((
322 +
518 518  )))
519 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
324 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
520 520  (((
521 521  //<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.//
522 522  )))
... ... @@ -526,13 +526,16 @@
526 526  )))|(% colspan="1" %)(% colspan="1" %)
527 527  (((
528 528  3.0 Beta 5
529 -)))|(% colspan="2" %)(% colspan="1" %)
334 +)))|(% colspan="1" %)(% colspan="1" %)
530 530  (((
531 531  Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case
337 +)))|(% colspan="1" %)(% colspan="1" %)
338 +(((
339 +
532 532  )))
533 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
341 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
534 534  (((
535 -//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.)
343 +//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.)\\
536 536  
537 537  //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).//
538 538  )))
... ... @@ -542,11 +542,14 @@
542 542  )))|(% colspan="1" %)(% colspan="1" %)
543 543  (((
544 544  3.0 Beta 5
545 -)))|(% colspan="2" %)(% colspan="1" %)
353 +)))|(% colspan="1" %)(% colspan="1" %)
546 546  (((
547 547  Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions>
356 +)))|(% colspan="1" %)(% colspan="1" %)
357 +(((
358 +
548 548  )))
549 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
360 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
550 550  (((
551 551  //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.//
552 552  )))
... ... @@ -556,11 +556,14 @@
556 556  )))|(% colspan="1" %)(% colspan="1" %)
557 557  (((
558 558  3.0 Beta 5
559 -)))|(% colspan="2" %)(% colspan="1" %)
370 +)))|(% colspan="1" %)(% colspan="1" %)
560 560  (((
561 561  Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos**
373 +)))|(% colspan="1" %)(% colspan="1" %)
374 +(((
375 +
562 562  )))
563 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
377 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
564 564  (((
565 565  //Before the change, positions are relative to $dockingbay.parent.
566 566  After the change, positions are relative to $dockingbay as specified in the documentation.//
... ... @@ -571,11 +571,14 @@
571 571  )))|(% colspan="1" %)(% colspan="1" %)
572 572  (((
573 573  3.0 Beta 2
574 -)))|(% colspan="2" %)(% colspan="1" %)
388 +)))|(% colspan="1" %)(% colspan="1" %)
575 575  (((
576 576  Support for entity flag "**skillsvisible**" dropped
391 +)))|(% colspan="1" %)(% colspan="1" %)
392 +(((
393 +
577 577  )))
578 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
395 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
579 579  (((
580 580  //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().//
581 581  )))
... ... @@ -583,10 +583,13 @@
583 583  Scripts
584 584  )))|(((
585 585  3.0 Beta 2
586 -)))|(% colspan="2" %)(((
403 +)))|(((
587 587  Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**.
405 +)))|(% colspan="1" %)(% colspan="1" %)
406 +(((
407 +
588 588  )))
589 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
409 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
590 590  (((
591 591  //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.
592 592  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.
... ... @@ -599,11 +599,14 @@
599 599  )))|(% colspan="1" %)(% colspan="1" %)
600 600  (((
601 601  3.0 Beta 1
602 -)))|(% colspan="2" %)(% colspan="1" %)
422 +)))|(% colspan="1" %)(% colspan="1" %)
603 603  (((
604 604  **MissionBoard** support dropped
425 +)))|(% colspan="1" %)(% colspan="1" %)
426 +(((
427 +
605 605  )))
606 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
429 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
607 607  (((
608 608  //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.//
609 609  )))
... ... @@ -611,10 +611,13 @@
611 611  Job/God
612 612  )))|(((
613 613  3.0 Beta 1
614 -)))|(% colspan="2" %)(((
437 +)))|(((
615 615  By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined
439 +)))|(% colspan="1" %)(% colspan="1" %)
440 +(((
441 +
616 616  )))
617 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
443 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
618 618  (((
619 619  //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.//
620 620  )))
... ... @@ -624,11 +624,14 @@
624 624  )))|(% colspan="1" %)(% colspan="1" %)
625 625  (((
626 626  3.0 Beta 1
627 -)))|(% colspan="2" %)(% colspan="1" %)
453 +)))|(% colspan="1" %)(% colspan="1" %)
628 628  (((
629 629  Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'**
456 +)))|(% colspan="1" %)(% colspan="1" %)
457 +(((
458 +
630 630  )))
631 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
460 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
632 632  (((
633 633  //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.//
634 634  )))
... ... @@ -638,11 +638,14 @@
638 638  )))|(% colspan="1" %)(% colspan="1" %)
639 639  (((
640 640  3.0 Beta 1
641 -)))|(% colspan="2" %)(% colspan="1" %)
470 +)))|(% colspan="1" %)(% colspan="1" %)
642 642  (((
643 643  Script action **<set_doors_locked/>** attribute **'group'** changed
473 +)))|(% colspan="1" %)(% colspan="1" %)
474 +(((
475 +
644 644  )))
645 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
477 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
646 646  (((
647 647  //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.//
648 648  )))
... ... @@ -652,11 +652,14 @@
652 652  )))|(% colspan="1" %)(% colspan="1" %)
653 653  (((
654 654  3.0 Beta 1
655 -)))|(% colspan="2" %)(% colspan="1" %)
487 +)))|(% colspan="1" %)(% colspan="1" %)
656 656  (((
657 657  Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed
490 +)))|(% colspan="1" %)(% colspan="1" %)
491 +(((
492 +
658 658  )))
659 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
494 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
660 660  (((
661 661  //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.//
662 662  )))
... ... @@ -666,11 +666,14 @@
666 666  )))|(% colspan="1" %)(% colspan="1" %)
667 667  (((
668 668  3.0 Beta 1
669 -)))|(% colspan="2" %)(% colspan="1" %)
504 +)))|(% colspan="1" %)(% colspan="1" %)
670 670  (((
671 671  Script actions **<set_hack_target/>** and **<abort_hack/>** removed
507 +)))|(% colspan="1" %)(% colspan="1" %)
508 +(((
509 +
672 672  )))
673 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
511 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
674 674  (((
675 675  //These actions had no effect and were removed.//
676 676  )))
... ... @@ -680,11 +680,14 @@
680 680  )))|(% colspan="1" %)(% colspan="1" %)
681 681  (((
682 682  3.0 Beta 1
683 -)))|(% colspan="2" %)(% colspan="1" %)
521 +)))|(% colspan="1" %)(% colspan="1" %)
684 684  (((
685 685  **<setup_conversation_minigame/>** script action removed
524 +)))|(% colspan="1" %)(% colspan="1" %)
525 +(((
526 +
686 686  )))
687 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
528 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
688 688  (((
689 689  //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.//
690 690  )))
... ... @@ -694,11 +694,14 @@
694 694  )))|(% colspan="1" %)(% colspan="1" %)
695 695  (((
696 696  3.0 Beta 1
697 -)))|(% colspan="2" %)(% colspan="1" %)
538 +)))|(% colspan="1" %)(% colspan="1" %)
698 698  (((
699 699  <add_player_choice_*> **confidence** attribute removed
541 +)))|(% colspan="1" %)(% colspan="1" %)
542 +(((
543 +
700 700  )))
701 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
545 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
702 702  (((
703 703  //The default confidence of player options is another leftover from the XR era and had no effect in X4.//
704 704  )))
... ... @@ -708,11 +708,14 @@
708 708  )))|(% colspan="1" %)(% colspan="1" %)
709 709  (((
710 710  3.0 Beta 1
711 -)))|(% colspan="2" %)(% colspan="1" %)
555 +)))|(% colspan="1" %)(% colspan="1" %)
712 712  (((
713 713  **<hack_via_control_panel/>** script action removed
558 +)))|(% colspan="1" %)(% colspan="1" %)
559 +(((
560 +
714 714  )))
715 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
562 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
716 716  (((
717 717  //Unused script action <hack_via_control_panel/> was removed.//
718 718  )))
... ... @@ -722,11 +722,14 @@
722 722  )))|(% colspan="1" %)(% colspan="1" %)
723 723  (((
724 724  3.0 Beta 1
725 -)))|(% colspan="2" %)(% colspan="1" %)
572 +)))|(% colspan="1" %)(% colspan="1" %)
726 726  (((
727 727  **Lua: **GetMiniGameCursorPosition() removed
575 +)))|(% colspan="1" %)(% colspan="1" %)
576 +(((
577 +
728 728  )))
729 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
579 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
730 730  (((
731 731  //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.//
732 732  )))
... ... @@ -734,10 +734,13 @@
734 734  UI core
735 735  )))|(((
736 736  3.0 Beta 1
737 -)))|(% colspan="2" %)(((
587 +)))|(((
738 738  **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders
589 +)))|(% colspan="1" %)(% colspan="1" %)
590 +(((
591 +
739 739  )))
740 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
593 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
741 741  (((
742 742  //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.//
743 743  )))
... ... @@ -747,11 +747,14 @@
747 747  )))|(% colspan="1" %)(% colspan="1" %)
748 748  (((
749 749  3.0 Beta 1
750 -)))|(% colspan="2" %)(% colspan="1" %)
603 +)))|(% colspan="1" %)(% colspan="1" %)
751 751  (((
752 752  **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor
606 +)))|(% colspan="1" %)(% colspan="1" %)
607 +(((
608 +
753 753  )))
754 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
610 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
755 755  (((
756 756  //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.//
757 757  )))
... ... @@ -761,11 +761,14 @@
761 761  )))|(% colspan="1" %)(% colspan="1" %)
762 762  (((
763 763  3.0 Beta 1
764 -)))|(% colspan="2" %)(% colspan="1" %)
620 +)))|(% colspan="1" %)(% colspan="1" %)
765 765  (((
766 766  **$ware.illegal** updated
623 +)))|(% colspan="1" %)(% colspan="1" %)
624 +(((
625 +
767 767  )))
768 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
627 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
769 769  (((
770 770  //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.//
771 771  //It now returns true if $ware is illegal to any faction in the game.//
... ... @@ -776,11 +776,14 @@
776 776  )))|(% colspan="1" %)(% colspan="1" %)
777 777  (((
778 778  3.0 Beta 1
779 -)))|(% colspan="2" %)(% colspan="1" %)
638 +)))|(% colspan="1" %)(% colspan="1" %)
780 780  (((
781 781  MD script **RML_Flight_Along_Path** removed
641 +)))|(% colspan="1" %)(% colspan="1" %)
642 +(((
643 +
782 782  )))
783 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
645 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
784 784  (((
785 785  //The MD script RML_Flight_Along_Path was not referened and was removed.//
786 786  )))
... ... @@ -790,11 +790,14 @@
790 790  )))|(% colspan="1" %)(% colspan="1" %)
791 791  (((
792 792  3.0 Beta 1
793 -)))|(% colspan="2" %)(% colspan="1" %)
655 +)))|(% colspan="1" %)(% colspan="1" %)
794 794  (((
795 795  parameters of **<event_venture_mission_completed/>** changed
658 +)))|(% colspan="1" %)(% colspan="1" %)
659 +(((
660 +
796 796  )))
797 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
662 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
798 798  (((
799 799  //old params: param = venture details, param2 = ships involved, param3 = duration//
800 800  //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration//
... ... @@ -803,11 +803,14 @@
803 803  Scripts
804 804  )))|(((
805 805  3.0 Beta 1
806 -)))|(% colspan="2" %)(((
671 +)))|(((
807 807  **<set_object_wing_name/>** removed,
808 808  **<set_object_fleet_name/>** added
674 +)))|(% colspan="1" %)(% colspan="1" %)
675 +(((
676 +
809 809  )))
810 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
678 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
811 811  (((
812 812  //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>//
813 813  )))
... ... @@ -815,28 +815,32 @@
815 815  Scripts
816 816  )))|(((
817 817  3.0 Beta 1
818 -)))|(% colspan="2" %)(((
686 +)))|(((
819 819  **$controllable.wing.*** removed,
820 820  **$controllable.fleet.*** added
689 +)))|(% colspan="1" %)(% colspan="1" %)
690 +(((
691 +
821 821  )))
822 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
693 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
823 823  (((
824 824  $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander
825 825  )))
826 -
827 -----
828 -
829 -=== Version 2.60 ===
830 -
831 -(% class="wrapped" %)
697 +|(% colspan="4" %)(% colspan="4" %)
698 +(((
699 +== 2.60 ==
700 +)))
832 832  |(((
833 833  Scripts
834 834  )))|(((
835 835  2.60 Beta 1
836 -)))|(% colspan="2" %)(((
705 +)))|(((
837 837  '**checkoperational**' filter behaviour changed
707 +)))|(% colspan="1" %)(% colspan="1" %)
708 +(((
709 +
838 838  )))
839 -|(% class="highlight-grey" colspan="10" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
711 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
840 840  (((
841 841  //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.//
842 842  
... ... @@ -846,19 +846,20 @@
846 846  Scripts
847 847  )))|(((
848 848  2.60 Beta 1
849 -)))|(% colspan="2" %)(((
721 +)))|(((
850 850  $container.**supplyresources** behavior changed
851 -)))| | |
852 -|(% class="highlight-grey" colspan="10" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
723 +)))|(% colspan="1" %)(% colspan="1" %)
853 853  (((
725 +
726 +)))
727 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
728 +(((
854 854  //The script keyword $container.supplyresources now includes reserved wares.//
855 855  )))
856 -
857 -----
858 -
859 -=== Version 2.20 ===
860 -
861 -(% class="wrapped" %)
731 +|(% colspan="4" %)(% colspan="4" %)
732 +(((
733 +== 2.20 ==
734 +)))
862 862  |(% colspan="1" %)(% colspan="1" %)
863 863  (((
864 864  UI core
... ... @@ -865,16 +865,20 @@
865 865  )))|(% colspan="1" %)(% colspan="1" %)
866 866  (((
867 867  2.20 Beta 3/4
868 -)))|(% colspan="2" %)(% colspan="1" %)
741 +)))|(% colspan="1" %)(% colspan="1" %)
869 869  (((
870 870  **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined.
744 +)))|(% colspan="1" %)(% colspan="1" %)
745 +(((
746 +
871 871  )))
872 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
748 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
873 873  (((
874 874  //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.
875 875  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.//
876 876  
877 -//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.//
753 +//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.
754 +//
878 878  )))
879 879  |(% colspan="1" %)(% colspan="1" %)
880 880  (((
... ... @@ -882,20 +882,21 @@
882 882  )))|(% colspan="1" %)(% colspan="1" %)
883 883  (((
884 884  2.20 Beta 3
885 -)))|(% colspan="2" %)(% colspan="1" %)
762 +)))|(% colspan="1" %)(% colspan="1" %)
886 886  (((
887 887  Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor'
765 +)))|(% colspan="1" %)(% colspan="1" %)
766 +(((
767 +
888 888  )))
889 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
769 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
890 890  (((
891 891  //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.//
892 892  )))
893 -
894 -----
895 -
896 -=== Version 2.00 ===
897 -
898 -(% class="wrapped" %)
773 +|(% colspan="4" %)(% colspan="4" %)
774 +(((
775 +== 2.00 ==
776 +)))
899 899  |(% colspan="1" %)(% colspan="1" %)
900 900  (((
901 901  Scripts
... ... @@ -902,11 +902,14 @@
902 902  )))|(% colspan="1" %)(% colspan="1" %)
903 903  (((
904 904  2.00 Beta 1
905 -)))|(% colspan="2" %)(% colspan="1" %)
783 +)))|(% colspan="1" %)(% colspan="1" %)
906 906  (((
907 907  **<event_build_finished/> **param2 now returns null instead of a construction sequence
786 +)))|(% colspan="1" %)(% colspan="1" %)
787 +(((
788 +
908 908  )))
909 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
790 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
910 910  (((
911 911  //The construction sequence which was finished should now be accessed via the buildtask provided via param3.//
912 912  )))
... ... @@ -916,11 +916,14 @@
916 916  )))|(% colspan="1" %)(% colspan="1" %)
917 917  (((
918 918  2.00 Beta 1
919 -)))|(% colspan="2" %)(% colspan="1" %)
800 +)))|(% colspan="1" %)(% colspan="1" %)
920 920  (((
921 921  **param.boarding.{...}** strength parameters removed
803 +)))|(% colspan="1" %)(% colspan="1" %)
804 +(((
805 +
922 922  )))
923 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
807 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
924 924  (((
925 925  //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.//
926 926  )))
... ... @@ -930,11 +930,14 @@
930 930  )))|(% colspan="1" %)(% colspan="1" %)
931 931  (((
932 932  2.00 Beta 1
933 -)))|(% colspan="2" %)(% colspan="1" %)
817 +)))|(% colspan="1" %)(% colspan="1" %)
934 934  (((
935 935  **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed
820 +)))|(% colspan="1" %)(% colspan="1" %)
821 +(((
822 +
936 936  )))
937 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
824 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
938 938  (((
939 939  //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.//
940 940  )))
... ... @@ -942,10 +942,13 @@
942 942  UI extensions
943 943  )))|(((
944 944  2.00 Beta 1
945 -)))|(% colspan="2" %)(((
832 +)))|(((
946 946  **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals
834 +)))|(% colspan="1" %)(% colspan="1" %)
835 +(((
836 +
947 947  )))
948 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
838 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
949 949  (((
950 950  //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.//
951 951  )))
... ... @@ -953,10 +953,13 @@
953 953  UI extensions
954 954  )))|(((
955 955  2.00 Beta 1
956 -)))|(% colspan="2" %)(((
846 +)))|(((
957 957  **FFI: SetFormationShape()** no longer indicates an error upon certain error cases
848 +)))|(% colspan="1" %)(% colspan="1" %)
849 +(((
850 +
958 958  )))
959 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
852 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
960 960  (((
961 961  //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.//
962 962  //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.//
... ... @@ -965,10 +965,13 @@
965 965  Scripts
966 966  )))|(((
967 967  2.00 Beta 1
968 -)))|(% colspan="2" %)(((
861 +)))|(((
969 969  **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated.
863 +)))|(% colspan="1" %)(% colspan="1" %)
864 +(((
865 +
970 970  )))
971 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
867 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
972 972  (((
973 973  //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.//
974 974  )))
... ... @@ -976,10 +976,13 @@
976 976  Scripts
977 977  )))|(((
978 978  2.00 Beta 1
979 -)))|(% colspan="2" %)(((
875 +)))|(((
980 980  **<event_player_changed_target/>** now fires and returns null if the player deselects a target.
877 +)))|(% colspan="1" %)(% colspan="1" %)
878 +(((
879 +
981 981  )))
982 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
881 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
983 983  (((
984 984  //For prior behavior, check for event.param being non-null.//
985 985  )))
... ... @@ -987,10 +987,13 @@
987 987  AI Scripts
988 988  )))|(((
989 989  2.00 Beta 1
990 -)))|(% colspan="2" %)(((
889 +)))|(((
991 991  **<shoot/>/<shoot_at/>** attribute changes.
891 +)))|(% colspan="1" %)(% colspan="1" %)
892 +(((
893 +
992 992  )))
993 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
895 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
994 994  (((
995 995  //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.//
996 996  //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.//
... ... @@ -1002,10 +1002,13 @@
1002 1002  UI extensions
1003 1003  )))|(((
1004 1004  2.00 Beta 1
1005 -)))|(% colspan="2" %)(((
1006 -**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.
907 +)))|(((
908 +**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% class="confluenceTd" %)
909 +)))|(% colspan="1" %)(% colspan="1" %)
910 +(((
911 +
1007 1007  )))
1008 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
913 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1009 1009  (((
1010 1010  //Added possibility to query build tasks of a certain buildmodule.//
1011 1011  )))
... ... @@ -1013,10 +1013,13 @@
1013 1013  UI extensions
1014 1014  )))|(((
1015 1015  2.00 Beta 1
1016 -)))|(% colspan="2" %)(((
921 +)))|(((
1017 1017  **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field.
923 +)))|(% colspan="1" %)(% colspan="1" %)
924 +(((
925 +
1018 1018  )))
1019 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
927 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1020 1020  (((
1021 1021  //Added list of resources a buildmodule needs to build.//
1022 1022  )))
... ... @@ -1024,10 +1024,13 @@
1024 1024  UI extensions
1025 1025  )))|(((
1026 1026  2.00 Beta 1
1027 -)))|(% colspan="2" %)(((
1028 -**Lua: CalculateTotalHullFraction() **was removed.
935 +)))|(((
936 +(% 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);" %)
937 +)))|(% colspan="1" %)(% colspan="1" %)
938 +(((
939 +
1029 1029  )))
1030 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
941 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1031 1031  (((
1032 1032  //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.//
1033 1033  )))
... ... @@ -1035,27 +1035,31 @@
1035 1035  UI extensions
1036 1036  )))|(((
1037 1037  2.00 Beta 1
1038 -)))|(% colspan="2" %)(((
1039 -**FFI: RequestDockAtReason()/UndockPlayerShip() **changed their return values.
949 +)))|(((
950 +**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.(% style="color: rgb(0,0,0);" class="confluenceTd" %)
951 +)))|(% colspan="1" %)(% colspan="1" %)
952 +(((
953 +
1040 1040  )))
1041 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
955 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1042 1042  (((
1043 1043  //Changed return value type to const char* to better identify failure reasons in Lua script.//
1044 1044  )))
1045 -
1046 -----
1047 -
1048 -=== Version 1.50 ===
1049 -
1050 -(% class="wrapped" %)
959 +|(% colspan="4" %)(% colspan="4" %)
960 +(((
961 +== 1.50 ==
962 +)))
1051 1051  |(((
1052 1052  UI extensions
1053 1053  )))|(((
1054 1054  1.50 Beta 3
1055 -)))|(% colspan="2" %)(((
1056 -**Lua: GetComponentData() **changed behavior of "docksizes" property.
967 +)))|(((
968 +**Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %)
969 +)))|(% colspan="1" %)(% colspan="1" %)
970 +(((
971 +
1057 1057  )))
1058 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
973 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1059 1059  (((
1060 1060  //The "docksizes" property no longer includes internal ship storage docks.//
1061 1061  )))
... ... @@ -1063,10 +1063,13 @@
1063 1063  All
1064 1064  )))|(((
1065 1065  1.50 Beta 2
1066 -)))|(% colspan="2" %)(((
981 +)))|(((
1067 1067  **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR).
983 +)))|(% colspan="1" %)(% colspan="1" %)
984 +(((
985 +
1068 1068  )))
1069 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
987 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1070 1070  (((
1071 1071  //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".//
1072 1072  
... ... @@ -1078,10 +1078,13 @@
1078 1078  UI extensions
1079 1079  )))|(((
1080 1080  1.50 Beta 2
1081 -)))|(% colspan="2" %)(((
1082 -**FFI: UpgradeGroupInfo **datatype was changed.
999 +)))|(((
1000 +**FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %)
1001 +)))|(% colspan="1" %)(% colspan="1" %)
1002 +(((
1003 +
1083 1083  )))
1084 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1005 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1085 1085  (((
1086 1086  //Added new "operational" field to retrieve information about number of operational upgrades in a group.//
1087 1087  )))
... ... @@ -1091,13 +1091,17 @@
1091 1091  )))|(% colspan="1" %)(% colspan="1" %)
1092 1092  (((
1093 1093  1.50 Beta 1
1094 -)))|(% colspan="2" %)(% colspan="1" %)
1015 +)))|(% colspan="1" %)(% colspan="1" %)
1095 1095  (((
1096 1096  **FFI: SetGuidance()** removed useinfopoint argument.
1018 +)))|(% colspan="1" %)(% colspan="1" %)
1019 +(((
1020 +
1097 1097  )))
1098 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1022 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1099 1099  (((
1100 -//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.//
1024 +//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.
1025 +//
1101 1101  
1102 1102  //The new function declaration is: void SetGuidance(UniverseID componentid, UIPosRot offset)//
1103 1103  )))
... ... @@ -1105,44 +1105,49 @@
1105 1105  UI extensions
1106 1106  )))|(((
1107 1107  1.50 Beta 1
1108 -)))|(% colspan="2" %)(((
1109 -**FFI: CancelConstruction() **changed its return value.
1033 +)))|(((
1034 +**FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %)
1035 +)))|(% colspan="1" %)(% colspan="1" %)
1036 +(((
1037 +
1110 1110  )))
1111 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1039 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1112 1112  (((
1113 -//CancelConstruction() now returns if the cancellation was successful. //
1041 +(% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. //
1114 1114  )))
1115 -
1116 -----
1117 -
1118 -=== Version 1.32 ===
1119 -
1120 -(% class="wrapped" %)
1043 +|(% colspan="4" %)(% colspan="4" %)
1044 +(((
1045 +== 1.32 ==
1046 +)))
1121 1121  |(((
1122 1122  UI extensions
1123 1123  )))|(((
1124 1124  1.32
1125 -)))|(% colspan="2" %)(((
1051 +)))|(((
1126 1126  **Lua: GetComponentData() **removed the "nextdestname" property.
1053 +)))|(% colspan="1" %)(% colspan="1" %)
1054 +(((
1055 +
1127 1127  )))
1128 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1057 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1129 1129  (((
1130 1130  //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.//
1131 1131  )))
1132 -
1133 -----
1134 -
1135 -=== Version 1.20 ===
1136 -
1137 -(% class="wrapped" %)
1061 +|(% colspan="4" %)(% colspan="4" %)
1062 +(((
1063 +== 1.20 ==
1064 +)))
1138 1138  |(((
1139 1139  UI extensions
1140 1140  )))|(((
1141 1141  1.20
1142 -)))|(% colspan="2" %)(((
1143 -**FFI: GetAAOption()** got a new "useconfig" parameter.
1069 +)))|(((
1070 +**FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %)
1071 +)))|(% colspan="1" %)(% colspan="1" %)
1072 +(((
1073 +
1144 1144  )))
1145 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1075 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
1146 1146  (((
1147 -//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.//
1077 +//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.//
1148 1148  )))
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -78577854
1 +103612552
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/78577854/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/103612552/Breaking Changes