Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 104.6
edited by Ketraar
on 2023/08/15 12:13
Change comment: There is no comment for this version
To version 108.1
edited by Florian Lütkecosmann
on 2023/11/22 13:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.Ketraar
1 +xwiki:XWiki.Florian
Content
... ... @@ -4,6 +4,14 @@
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.
9 +
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 +
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}}
14 +
7 7  {{warning title="UI modding considered unstable until further notice..."}}
8 8  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.
9 9  {{/warning}}
... ... @@ -15,11 +15,28 @@
15 15  Type
16 16  )))|=(((
17 17  Version
18 -)))|=(((
26 +)))|=(% colspan="2" %)(((
19 19  Summary
20 20  )))
21 -|(% colspan="3" %)(% colspan="3" %)
29 +|(% colspan="4" %)(((
30 +== 7.00 ==
31 +)))
32 +|(% colspan="1" %)(% colspan="1" %)
22 22  (((
34 +UI extensions
35 +)))|(% colspan="1" %)(% colspan="1" %)
36 +(((
37 +7.00 Beta 1
38 +)))|(% colspan="2" %)(% colspan="1" %)
39 +(((
40 +**FFI**: RemoveBuildPlot() changed
41 +)))
42 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
43 +(((
44 +// 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.
45 +)))
46 +|(% colspan="4" %)(% colspan="3" %)
47 +(((
23 23  == 6.00 ==
24 24  )))
25 25  |(((
... ... @@ -26,10 +26,10 @@
26 26  Libraries
27 27  )))|(((
28 28  6.00 Beta 7
29 -)))|(((
54 +)))|(% colspan="2" %)(((
30 30  Updated weights for ship groups in shipgroups.xml libraries of base game and all DLCs.
31 31  )))
32 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
57 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
33 33  (((
34 34  //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.//
35 35  
... ... @@ -41,11 +41,11 @@
41 41  )))|(% colspan="1" %)(% colspan="1" %)
42 42  (((
43 43  6.00 Beta 4
44 -)))|(% colspan="1" %)(% colspan="1" %)
69 +)))|(% colspan="2" %)(% colspan="1" %)
45 45  (((
46 46  Changed conditions for **<event_player_travelmode_started> <event_player_travelmode_stopped> <event_player_travelmode_charge_started> <event_player_travelmode_charge_aborted>** to be raised.
47 47  )))
48 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
73 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
49 49  (((
50 50  //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. //
51 51  
... ... @@ -57,11 +57,11 @@
57 57  )))|(% colspan="1" %)(% colspan="1" %)
58 58  (((
59 59  6.00 Beta 3
60 -)))|(% colspan="1" %)(% colspan="1" %)
85 +)))|(% colspan="2" %)(% colspan="1" %)
61 61  (((
62 62  Changed result of **<find_object_surface>** action in the case of a failure
63 63  )))
64 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
89 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
65 65  (((
66 66  //The 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.//
67 67  
... ... @@ -75,11 +75,11 @@
75 75  )))|(% colspan="1" %)(% colspan="1" %)
76 76  (((
77 77  6.00 Beta 1
78 -)))|(% colspan="1" %)(% colspan="1" %)
103 +)))|(% colspan="2" %)(% colspan="1" %)
79 79  (((
80 80  Behaviour change for **<match_dock>** script component filter
81 81  )))
82 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
107 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
83 83  (((
84 84  //<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes.
85 85  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.//
... ... @@ -90,11 +90,11 @@
90 90  )))|(% colspan="1" %)(% colspan="1" %)
91 91  (((
92 92  6.00 Beta 1
93 -)))|(% colspan="1" %)(% colspan="1" %)
118 +)))|(% colspan="2" %)(% colspan="1" %)
94 94  (((
95 95  Changed result attribute location for **<get_attackstrength>**
96 96  )))
97 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
122 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" title="Background colour :" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" title="Background colour :" %)
98 98  (((
99 99  //The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.//
100 100  )))
... ... @@ -102,10 +102,10 @@
102 102  Assets
103 103  )))|(((
104 104  6.00 Beta 1
105 -)))|(((
130 +)))|(% colspan="2" %)(((
106 106  Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons
107 107  )))
108 -|(% class="highlight-#f4f5f7" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% class="highlight-#f4f5f7" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
133 +|(% 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%" %)
109 109  (((
110 110  //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.
111 111  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.//
... ... @@ -116,11 +116,11 @@
116 116  )))|(% colspan="1" %)(% colspan="1" %)
117 117  (((
118 118  6.00 Beta 1
119 -)))|(% colspan="1" %)(% colspan="1" %)
144 +)))|(% colspan="2" %)(% colspan="1" %)
120 120  (((
121 121  Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects
122 122  )))
123 -|(% class="highlight-#f4f5f7" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% class="highlight-#f4f5f7" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
148 +|(% 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%" %)
124 124  (((
125 125  //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.//
126 126  )))
... ... @@ -128,10 +128,10 @@
128 128  Scripts
129 129  )))|(((
130 130  6.00 Beta 1
131 -)))|(((
156 +)))|(% colspan="2" %)(((
132 132  **<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards.
133 133  )))
134 -|(% class="highlight-#f4f5f7" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% class="highlight-#f4f5f7" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
159 +|(% 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%" %)
135 135  (((
136 136  //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.//
137 137  )))
... ... @@ -139,14 +139,14 @@
139 139  Cutscenes
140 140  )))|(((
141 141  6.00 Beta 1
142 -)))|(((
167 +)))|(% colspan="2" %)(((
143 143  Changed behaviour of **<angles>** in cutscenes
144 144  )))
145 -|(% class="highlight-#f4f5f7" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)(% class="highlight-#f4f5f7" colspan="3" data-highlight-colour="#f4f5f7" title="Background color : Light grey 100%" %)
170 +|(% 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%" %)
146 146  (((
147 147  //The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.//
148 148  )))
149 -|(% colspan="3" %)(% colspan="3" %)
174 +|(% colspan="4" %)(% colspan="3" %)
150 150  (((
151 151  == 5.00 ==
152 152  )))
... ... @@ -154,14 +154,14 @@
154 154  Parameters
155 155  )))|(((
156 156  5.00 Beta 1
157 -)))|(((
182 +)))|(% colspan="2" %)(((
158 158  **<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration
159 159  )))
160 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
185 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
161 161  (((
162 162  //'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.//
163 163  )))
164 -|(% colspan="3" %)(% colspan="3" %)
189 +|(% colspan="4" %)(% colspan="3" %)
165 165  (((
166 166  == 4.10 ==
167 167  )))
... ... @@ -171,13 +171,13 @@
171 171  )))|(% colspan="1" %)(% colspan="1" %)
172 172  (((
173 173  4.10 Beta 7
174 -)))|(% colspan="1" %)(% colspan="1" %)
199 +)))|(% colspan="2" %)(% colspan="1" %)
175 175  (((
176 -**FFI**: (% style="color:#000000" %)SetMapRenderCargoContents(%%)(), (% style="color:#000000" %)SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos()(%%) deprecated
201 +**FFI**: SetMapRenderCargoContents(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos() deprecated
177 177  )))
178 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
203 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
179 179  (((
180 -//The functionality represented by (% style="color:#000000" %)SetMapRenderCargoContents(%%)(), (% style="color:#000000" %)SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos()(%%) has been removed and the function was therefore stubbed.//
205 +//The functionality represented by SetMapRenderCargoContents(), SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos() has been removed and the function was therefore stubbed.//
181 181  )))
182 182  |(% colspan="1" %)(% colspan="1" %)
183 183  (((
... ... @@ -185,11 +185,11 @@
185 185  )))|(% colspan="1" %)(% colspan="1" %)
186 186  (((
187 187  4.10 Beta 6
188 -)))|(% colspan="1" %)(% colspan="1" %)
213 +)))|(% colspan="2" %)(% colspan="1" %)
189 189  (((
190 190  **FFI**: CustomGameStartPlayerProperty2 changed
191 191  )))
192 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
217 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
193 193  (((
194 194  //This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.//
195 195  )))
... ... @@ -199,11 +199,11 @@
199 199  )))|(% colspan="1" %)(% colspan="1" %)
200 200  (((
201 201  4.10 Beta 3
202 -)))|(% colspan="1" %)(% colspan="1" %)
227 +)))|(% colspan="2" %)(% colspan="1" %)
203 203  (((
204 204  Renamed **<stationinfobox>** to **<infobox>**
205 205  )))
206 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
231 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
207 207  (((
208 208  //Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.//
209 209  )))
... ... @@ -213,11 +213,11 @@
213 213  )))|(% colspan="1" %)(% colspan="1" %)
214 214  (((
215 215  4.10 Beta 2
216 -)))|(% colspan="1" %)(% colspan="1" %)
241 +)))|(% colspan="2" %)(% colspan="1" %)
217 217  (((
218 218  **FFI**: SetMacroMapPlayerSectorOffset() deprecated
219 219  )))
220 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
245 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
221 221  (((
222 222  //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.//
223 223  )))
... ... @@ -225,10 +225,10 @@
225 225  UI extensions
226 226  )))|(((
227 227  4.10 Beta 2
228 -)))|(((
229 -**FFI**: (% style="color:#000000" %)FilterComponentForMapMode(%%)() and (% style="color:#000000" %)SetMapObjectFilter() changed
253 +)))|(% colspan="2" %)(((
254 +**FFI**: FilterComponentForMapMode() and SetMapObjectFilter() changed
230 230  )))
231 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
256 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
232 232  (((
233 233  //These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.//
234 234  )))
... ... @@ -236,10 +236,10 @@
236 236  Scripts
237 237  )))|(((
238 238  4.10 Beta 1
239 -)))|(((
264 +)))|(% colspan="2" %)(((
240 240  People related attributes of mission** <delivery> **node moved
241 241  )))
242 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
267 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
243 243  (((
244 244  //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.//
245 245  )))
... ... @@ -249,11 +249,11 @@
249 249  )))|(% colspan="1" %)(% colspan="1" %)
250 250  (((
251 251  4.10 Beta 1
252 -)))|(% colspan="1" %)(% colspan="1" %)
277 +)))|(% colspan="2" %)(% colspan="1" %)
253 253  (((
254 254  **$destructible.productions** replaced with $defensible.productions
255 255  )))
256 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
281 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
257 257  (((
258 258  //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.//
259 259  )))
... ... @@ -261,14 +261,14 @@
261 261  Scripts
262 262  )))|(((
263 263  4.10 Beta 1
264 -)))|(((
289 +)))|(% colspan="2" %)(((
265 265  Removed script property **$object.spawnsourceseed**
266 266  )))
267 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
292 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
268 268  (((
269 269  //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.//
270 270  )))
271 -|(% colspan="3" %)(% colspan="3" %)
296 +|(% colspan="4" %)(% colspan="3" %)
272 272  (((
273 273  == 4.00 ==
274 274  )))
... ... @@ -278,11 +278,11 @@
278 278  )))|(% colspan="1" %)(% colspan="1" %)
279 279  (((
280 280  4.00 Beta 10
281 -)))|(% colspan="1" %)(% colspan="1" %)
306 +)))|(% colspan="2" %)(% colspan="1" %)
282 282  (((
283 283  Controlled ship can change without a **gameplanchange-event** occurring.
284 284  )))
285 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
310 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
286 286  (((
287 287  //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).
288 288  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.//
... ... @@ -291,10 +291,10 @@
291 291  Scripts
292 292  )))|(((
293 293  4.00 Beta 7
294 -)))|(((
319 +)))|(% colspan="2" %)(((
295 295  Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed
296 296  )))
297 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
322 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
298 298  (((
299 299  //Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects?
300 300  New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits
... ... @@ -306,11 +306,11 @@
306 306  )))|(% colspan="1" %)(% colspan="1" %)
307 307  (((
308 308  4.00 Beta 6
309 -)))|(% colspan="1" %)(% colspan="1" %)
334 +)))|(% colspan="2" %)(% colspan="1" %)
310 310  (((
311 311  **FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed
312 312  )))
313 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
338 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
314 314  (((
315 315  //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.
316 316  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).//
... ... @@ -323,11 +323,11 @@
323 323  )))|(% colspan="1" %)(% colspan="1" %)
324 324  (((
325 325  4.00 Beta 5
326 -)))|(% colspan="1" %)(% colspan="1" %)
351 +)))|(% colspan="2" %)(% colspan="1" %)
327 327  (((
328 328  **FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed
329 329  )))
330 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
355 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
331 331  (((
332 332  //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.//
333 333  
... ... @@ -337,10 +337,10 @@
337 337  Parameters
338 338  )))|(((
339 339  4.00 Beta 1
340 -)))|(((
365 +)))|(% colspan="2" %)(((
341 341  **requiresconstructionvessel** parameter moved
342 342  )))
343 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
368 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
344 344  (((
345 345  //The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.//
346 346  )))
... ... @@ -348,14 +348,14 @@
348 348  Scripts
349 349  )))|(((
350 350  4.00 Beta 1
351 -)))|(((
376 +)))|(% colspan="2" %)(((
352 352  Changed behaviour of **gatedistance** script property
353 353  )))
354 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
379 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
355 355  (((
356 356  //The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.//
357 357  )))
358 -|(% colspan="3" %)(% colspan="3" %)
383 +|(% colspan="4" %)(% colspan="3" %)
359 359  (((
360 360  == 3.30 ==
361 361  )))
... ... @@ -363,14 +363,14 @@
363 363  UI extensions
364 364  )))|(((
365 365  3.30 Beta 3
366 -)))|(((
367 -**FFI: **Removed** (% style="color:#000000" %)GetMissionLimit() (%%)**(% style="color:#000000" %)and** IsMissionLimit**(%%)**Enabled()**
391 +)))|(% colspan="2" %)(((
392 +**FFI: **Removed** GetMissionLimit() **and** IsMissionLimitEnabled()**
368 368  )))
369 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
394 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
370 370  (((
371 -//These mission limit-related functions (added in 3.30 Beta 1 and 2) are replaced with FFI (% style="color:#000000" %)IsMissionLimit(%%)Reach(% style="color:#000000" %)ed()//
396 +//These mission limit-related functions (added in 3.30 Beta 1 and 2) are replaced with FFI IsMissionLimitReached()//
372 372  )))
373 -|(% colspan="3" %)(% colspan="3" %)
398 +|(% colspan="4" %)(% colspan="3" %)
374 374  (((
375 375  == 3.20 ==
376 376  )))
... ... @@ -378,10 +378,10 @@
378 378  Scripts
379 379  )))|(((
380 380  3.20 Beta 1
381 -)))|(((
406 +)))|(% colspan="2" %)(((
382 382  Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed
383 383  )))
384 -|(% class="highlight-grey" colspan="3" 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="3" data-highlight-colour="grey" %)
385 385  (((
386 386  //Old params: param = attacked object, param2 = attack method, param3 = attacked component//
387 387  //New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon]
... ... @@ -393,11 +393,11 @@
393 393  )))|(% colspan="1" %)(% colspan="1" %)
394 394  (((
395 395  3.20 Beta 1
396 -)))|(% colspan="1" %)(% colspan="1" %)
421 +)))|(% colspan="2" %)(% colspan="1" %)
397 397  (((
398 398  Removed script property $trade.**restriction.faction**
399 399  )))
400 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
425 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
401 401  (((
402 402  //$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.//
403 403  )))
... ... @@ -405,14 +405,14 @@
405 405  UI extensions
406 406  )))|(((
407 407  3.20 Beta 1
408 -)))|(((
433 +)))|(% colspan="2" %)(((
409 409  **Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete!
410 410  )))
411 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
436 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
412 412  (((
413 413  //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.//
414 414  )))
415 -|(% colspan="3" %)(% colspan="3" %)
440 +|(% colspan="4" %)(% colspan="3" %)
416 416  (((
417 417  == 3.10 ==
418 418  )))
... ... @@ -422,15 +422,15 @@
422 422  )))|(% colspan="1" %)(% colspan="1" %)
423 423  (((
424 424  3.10 Beta 1
425 -)))|(% colspan="1" %)(% colspan="1" %)
450 +)))|(% colspan="2" %)(% colspan="1" %)
426 426  (((
427 427  Removed script action **<add_build/>**
428 428  )))
429 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
454 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
430 430  (((
431 431  //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.//
432 432  )))
433 -|(% colspan="3" %)(% colspan="3" %)
458 +|(% colspan="4" %)(% colspan="3" %)
434 434  (((
435 435  == 3.00 ==
436 436  )))
... ... @@ -440,11 +440,11 @@
440 440  )))|(% colspan="1" %)(% colspan="1" %)
441 441  (((
442 442  3.0 Beta 6
443 -)))|(% colspan="1" %)(% colspan="1" %)
468 +)))|(% colspan="2" %)(% colspan="1" %)
444 444  (((
445 445  Changed behaviour of script action **<get_suitable_job/>**
446 446  )))
447 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
472 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
448 448  (((
449 449  //<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.//
450 450  )))
... ... @@ -454,11 +454,11 @@
454 454  )))|(% colspan="1" %)(% colspan="1" %)
455 455  (((
456 456  3.0 Beta 6
457 -)))|(% colspan="1" %)(% colspan="1" %)
482 +)))|(% colspan="2" %)(% colspan="1" %)
458 458  (((
459 459  Changed behaviour of script action **<get_ware_definition/>**
460 460  )))
461 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
486 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
462 462  (((
463 463  //<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.//
464 464  )))
... ... @@ -468,11 +468,11 @@
468 468  )))|(% colspan="1" %)(% colspan="1" %)
469 469  (((
470 470  3.0 Beta 5
471 -)))|(% colspan="1" %)(% colspan="1" %)
496 +)))|(% colspan="2" %)(% colspan="1" %)
472 472  (((
473 473  Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case
474 474  )))
475 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
500 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
476 476  (((
477 477  //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.)
478 478  
... ... @@ -484,11 +484,11 @@
484 484  )))|(% colspan="1" %)(% colspan="1" %)
485 485  (((
486 486  3.0 Beta 5
487 -)))|(% colspan="1" %)(% colspan="1" %)
512 +)))|(% colspan="2" %)(% colspan="1" %)
488 488  (((
489 489  Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions>
490 490  )))
491 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
516 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
492 492  (((
493 493  //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.//
494 494  )))
... ... @@ -498,11 +498,11 @@
498 498  )))|(% colspan="1" %)(% colspan="1" %)
499 499  (((
500 500  3.0 Beta 5
501 -)))|(% colspan="1" %)(% colspan="1" %)
526 +)))|(% colspan="2" %)(% colspan="1" %)
502 502  (((
503 503  Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos**
504 504  )))
505 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
530 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
506 506  (((
507 507  //Before the change, positions are relative to $dockingbay.parent.
508 508  After the change, positions are relative to $dockingbay as specified in the documentation.//
... ... @@ -513,11 +513,11 @@
513 513  )))|(% colspan="1" %)(% colspan="1" %)
514 514  (((
515 515  3.0 Beta 2
516 -)))|(% colspan="1" %)(% colspan="1" %)
541 +)))|(% colspan="2" %)(% colspan="1" %)
517 517  (((
518 518  Support for entity flag "**skillsvisible**" dropped
519 519  )))
520 -|(% class="highlight-grey" colspan="3" 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="3" data-highlight-colour="grey" %)
521 521  (((
522 522  //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().//
523 523  )))
... ... @@ -525,10 +525,10 @@
525 525  Scripts
526 526  )))|(((
527 527  3.0 Beta 2
528 -)))|(((
553 +)))|(% colspan="2" %)(((
529 529  Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**.
530 530  )))
531 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
556 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
532 532  (((
533 533  //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.
534 534  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.
... ... @@ -541,11 +541,11 @@
541 541  )))|(% colspan="1" %)(% colspan="1" %)
542 542  (((
543 543  3.0 Beta 1
544 -)))|(% colspan="1" %)(% colspan="1" %)
569 +)))|(% colspan="2" %)(% colspan="1" %)
545 545  (((
546 546  **MissionBoard** support dropped
547 547  )))
548 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
573 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
549 549  (((
550 550  //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.//
551 551  )))
... ... @@ -553,10 +553,10 @@
553 553  Job/God
554 554  )))|(((
555 555  3.0 Beta 1
556 -)))|(((
581 +)))|(% colspan="2" %)(((
557 557  By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined
558 558  )))
559 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
584 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
560 560  (((
561 561  //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.//
562 562  )))
... ... @@ -566,11 +566,11 @@
566 566  )))|(% colspan="1" %)(% colspan="1" %)
567 567  (((
568 568  3.0 Beta 1
569 -)))|(% colspan="1" %)(% colspan="1" %)
594 +)))|(% colspan="2" %)(% colspan="1" %)
570 570  (((
571 571  Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'**
572 572  )))
573 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
598 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
574 574  (((
575 575  //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.//
576 576  )))
... ... @@ -580,11 +580,11 @@
580 580  )))|(% colspan="1" %)(% colspan="1" %)
581 581  (((
582 582  3.0 Beta 1
583 -)))|(% colspan="1" %)(% colspan="1" %)
608 +)))|(% colspan="2" %)(% colspan="1" %)
584 584  (((
585 585  Script action **<set_doors_locked/>** attribute **'group'** changed
586 586  )))
587 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
612 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
588 588  (((
589 589  //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.//
590 590  )))
... ... @@ -594,11 +594,11 @@
594 594  )))|(% colspan="1" %)(% colspan="1" %)
595 595  (((
596 596  3.0 Beta 1
597 -)))|(% colspan="1" %)(% colspan="1" %)
622 +)))|(% colspan="2" %)(% colspan="1" %)
598 598  (((
599 599  Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed
600 600  )))
601 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
626 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
602 602  (((
603 603  //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.//
604 604  )))
... ... @@ -608,11 +608,11 @@
608 608  )))|(% colspan="1" %)(% colspan="1" %)
609 609  (((
610 610  3.0 Beta 1
611 -)))|(% colspan="1" %)(% colspan="1" %)
636 +)))|(% colspan="2" %)(% colspan="1" %)
612 612  (((
613 613  Script actions **<set_hack_target/>** and **<abort_hack/>** removed
614 614  )))
615 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
640 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
616 616  (((
617 617  //These actions had no effect and were removed.//
618 618  )))
... ... @@ -622,11 +622,11 @@
622 622  )))|(% colspan="1" %)(% colspan="1" %)
623 623  (((
624 624  3.0 Beta 1
625 -)))|(% colspan="1" %)(% colspan="1" %)
650 +)))|(% colspan="2" %)(% colspan="1" %)
626 626  (((
627 627  **<setup_conversation_minigame/>** script action removed
628 628  )))
629 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
654 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
630 630  (((
631 631  //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.//
632 632  )))
... ... @@ -636,11 +636,11 @@
636 636  )))|(% colspan="1" %)(% colspan="1" %)
637 637  (((
638 638  3.0 Beta 1
639 -)))|(% colspan="1" %)(% colspan="1" %)
664 +)))|(% colspan="2" %)(% colspan="1" %)
640 640  (((
641 641  <add_player_choice_*> **confidence** attribute removed
642 642  )))
643 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
668 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
644 644  (((
645 645  //The default confidence of player options is another leftover from the XR era and had no effect in X4.//
646 646  )))
... ... @@ -650,11 +650,11 @@
650 650  )))|(% colspan="1" %)(% colspan="1" %)
651 651  (((
652 652  3.0 Beta 1
653 -)))|(% colspan="1" %)(% colspan="1" %)
678 +)))|(% colspan="2" %)(% colspan="1" %)
654 654  (((
655 655  **<hack_via_control_panel/>** script action removed
656 656  )))
657 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
682 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
658 658  (((
659 659  //Unused script action <hack_via_control_panel/> was removed.//
660 660  )))
... ... @@ -664,11 +664,11 @@
664 664  )))|(% colspan="1" %)(% colspan="1" %)
665 665  (((
666 666  3.0 Beta 1
667 -)))|(% colspan="1" %)(% colspan="1" %)
692 +)))|(% colspan="2" %)(% colspan="1" %)
668 668  (((
669 669  **Lua: **GetMiniGameCursorPosition() removed
670 670  )))
671 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
696 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
672 672  (((
673 673  //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.//
674 674  )))
... ... @@ -676,10 +676,10 @@
676 676  UI core
677 677  )))|(((
678 678  3.0 Beta 1
679 -)))|(((
704 +)))|(% colspan="2" %)(((
680 680  **FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders
681 681  )))
682 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
707 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
683 683  (((
684 684  //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.//
685 685  )))
... ... @@ -689,11 +689,11 @@
689 689  )))|(% colspan="1" %)(% colspan="1" %)
690 690  (((
691 691  3.0 Beta 1
692 -)))|(% colspan="1" %)(% colspan="1" %)
717 +)))|(% colspan="2" %)(% colspan="1" %)
693 693  (((
694 694  **FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor
695 695  )))
696 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
721 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
697 697  (((
698 698  //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.//
699 699  )))
... ... @@ -703,11 +703,11 @@
703 703  )))|(% colspan="1" %)(% colspan="1" %)
704 704  (((
705 705  3.0 Beta 1
706 -)))|(% colspan="1" %)(% colspan="1" %)
731 +)))|(% colspan="2" %)(% colspan="1" %)
707 707  (((
708 708  **$ware.illegal** updated
709 709  )))
710 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
735 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
711 711  (((
712 712  //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.//
713 713  //It now returns true if $ware is illegal to any faction in the game.//
... ... @@ -718,11 +718,11 @@
718 718  )))|(% colspan="1" %)(% colspan="1" %)
719 719  (((
720 720  3.0 Beta 1
721 -)))|(% colspan="1" %)(% colspan="1" %)
746 +)))|(% colspan="2" %)(% colspan="1" %)
722 722  (((
723 723  MD script **RML_Flight_Along_Path** removed
724 724  )))
725 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
750 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
726 726  (((
727 727  //The MD script RML_Flight_Along_Path was not referened and was removed.//
728 728  )))
... ... @@ -732,11 +732,11 @@
732 732  )))|(% colspan="1" %)(% colspan="1" %)
733 733  (((
734 734  3.0 Beta 1
735 -)))|(% colspan="1" %)(% colspan="1" %)
760 +)))|(% colspan="2" %)(% colspan="1" %)
736 736  (((
737 737  parameters of **<event_venture_mission_completed/>** changed
738 738  )))
739 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
764 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
740 740  (((
741 741  //old params: param = venture details, param2 = ships involved, param3 = duration//
742 742  //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration//
... ... @@ -745,11 +745,11 @@
745 745  Scripts
746 746  )))|(((
747 747  3.0 Beta 1
748 -)))|(((
773 +)))|(% colspan="2" %)(((
749 749  **<set_object_wing_name/>** removed,
750 750  **<set_object_fleet_name/>** added
751 751  )))
752 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
777 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
753 753  (((
754 754  //The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>//
755 755  )))
... ... @@ -757,15 +757,15 @@
757 757  Scripts
758 758  )))|(((
759 759  3.0 Beta 1
760 -)))|(((
785 +)))|(% colspan="2" %)(((
761 761  **$controllable.wing.*** removed,
762 762  **$controllable.fleet.*** added
763 763  )))
764 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
789 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
765 765  (((
766 766  $controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander
767 767  )))
768 -|(% colspan="3" %)(% colspan="3" %)
793 +|(% colspan="4" %)(% colspan="3" %)
769 769  (((
770 770  == 2.60 ==
771 771  )))
... ... @@ -773,10 +773,10 @@
773 773  Scripts
774 774  )))|(((
775 775  2.60 Beta 1
776 -)))|(((
801 +)))|(% colspan="2" %)(((
777 777  '**checkoperational**' filter behaviour changed
778 778  )))
779 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
804 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
780 780  (((
781 781  //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.//
782 782  
... ... @@ -786,14 +786,14 @@
786 786  Scripts
787 787  )))|(((
788 788  2.60 Beta 1
789 -)))|(((
814 +)))|(% colspan="2" %)(((
790 790  $container.**supplyresources** behavior changed
791 791  )))
792 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
817 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
793 793  (((
794 794  //The script keyword $container.supplyresources now includes reserved wares.//
795 795  )))
796 -|(% colspan="3" %)(% colspan="3" %)
821 +|(% colspan="4" %)(% colspan="3" %)
797 797  (((
798 798  == 2.20 ==
799 799  )))
... ... @@ -803,11 +803,11 @@
803 803  )))|(% colspan="1" %)(% colspan="1" %)
804 804  (((
805 805  2.20 Beta 3/4
806 -)))|(% colspan="1" %)(% colspan="1" %)
831 +)))|(% colspan="2" %)(% colspan="1" %)
807 807  (((
808 808  **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined.
809 809  )))
810 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
835 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
811 811  (((
812 812  //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.
813 813  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.//
... ... @@ -820,15 +820,15 @@
820 820  )))|(% colspan="1" %)(% colspan="1" %)
821 821  (((
822 822  2.20 Beta 3
823 -)))|(% colspan="1" %)(% colspan="1" %)
848 +)))|(% colspan="2" %)(% colspan="1" %)
824 824  (((
825 825  Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor'
826 826  )))
827 -|(% class="highlight-grey" colspan="3" 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="3" data-highlight-colour="grey" %)
828 828  (((
829 829  //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.//
830 830  )))
831 -|(% colspan="3" %)(% colspan="3" %)
856 +|(% colspan="4" %)(% colspan="3" %)
832 832  (((
833 833  == 2.00 ==
834 834  )))
... ... @@ -838,11 +838,11 @@
838 838  )))|(% colspan="1" %)(% colspan="1" %)
839 839  (((
840 840  2.00 Beta 1
841 -)))|(% colspan="1" %)(% colspan="1" %)
866 +)))|(% colspan="2" %)(% colspan="1" %)
842 842  (((
843 843  **<event_build_finished/> **param2 now returns null instead of a construction sequence
844 844  )))
845 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
870 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
846 846  (((
847 847  //The construction sequence which was finished should now be accessed via the buildtask provided via param3.//
848 848  )))
... ... @@ -852,11 +852,11 @@
852 852  )))|(% colspan="1" %)(% colspan="1" %)
853 853  (((
854 854  2.00 Beta 1
855 -)))|(% colspan="1" %)(% colspan="1" %)
880 +)))|(% colspan="2" %)(% colspan="1" %)
856 856  (((
857 857  **param.boarding.{...}** strength parameters removed
858 858  )))
859 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
884 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
860 860  (((
861 861  //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.//
862 862  )))
... ... @@ -866,11 +866,11 @@
866 866  )))|(% colspan="1" %)(% colspan="1" %)
867 867  (((
868 868  2.00 Beta 1
869 -)))|(% colspan="1" %)(% colspan="1" %)
894 +)))|(% colspan="2" %)(% colspan="1" %)
870 870  (((
871 871  **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed
872 872  )))
873 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
898 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
874 874  (((
875 875  //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.//
876 876  )))
... ... @@ -878,10 +878,10 @@
878 878  UI extensions
879 879  )))|(((
880 880  2.00 Beta 1
881 -)))|(((
906 +)))|(% colspan="2" %)(((
882 882  **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals
883 883  )))
884 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
909 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
885 885  (((
886 886  //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.//
887 887  )))
... ... @@ -889,10 +889,10 @@
889 889  UI extensions
890 890  )))|(((
891 891  2.00 Beta 1
892 -)))|(((
917 +)))|(% colspan="2" %)(((
893 893  **FFI: SetFormationShape()** no longer indicates an error upon certain error cases
894 894  )))
895 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
920 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
896 896  (((
897 897  //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.//
898 898  //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.//
... ... @@ -901,10 +901,10 @@
901 901  Scripts
902 902  )))|(((
903 903  2.00 Beta 1
904 -)))|(((
929 +)))|(% colspan="2" %)(((
905 905  **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated.
906 906  )))
907 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
932 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
908 908  (((
909 909  //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.//
910 910  )))
... ... @@ -912,10 +912,10 @@
912 912  Scripts
913 913  )))|(((
914 914  2.00 Beta 1
915 -)))|(((
940 +)))|(% colspan="2" %)(((
916 916  **<event_player_changed_target/>** now fires and returns null if the player deselects a target.
917 917  )))
918 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
943 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
919 919  (((
920 920  //For prior behavior, check for event.param being non-null.//
921 921  )))
... ... @@ -923,10 +923,10 @@
923 923  AI Scripts
924 924  )))|(((
925 925  2.00 Beta 1
926 -)))|(((
951 +)))|(% colspan="2" %)(((
927 927  **<shoot/>/<shoot_at/>** attribute changes.
928 928  )))
929 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
954 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
930 930  (((
931 931  //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.//
932 932  //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.//
... ... @@ -938,10 +938,10 @@
938 938  UI extensions
939 939  )))|(((
940 940  2.00 Beta 1
941 -)))|(((
966 +)))|(% colspan="2" %)(((
942 942  **FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.
943 943  )))
944 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
969 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
945 945  (((
946 946  //Added possibility to query build tasks of a certain buildmodule.//
947 947  )))
... ... @@ -949,10 +949,10 @@
949 949  UI extensions
950 950  )))|(((
951 951  2.00 Beta 1
952 -)))|(((
977 +)))|(% colspan="2" %)(((
953 953  **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field.
954 954  )))
955 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
980 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
956 956  (((
957 957  //Added list of resources a buildmodule needs to build.//
958 958  )))
... ... @@ -960,10 +960,10 @@
960 960  UI extensions
961 961  )))|(((
962 962  2.00 Beta 1
963 -)))|(((
964 -(% style="color:#000000" %)**Lua: CalculateTotalHullFraction() **(%%)was removed.(% style="color:#000000" %)
988 +)))|(% colspan="2" %)(((
989 +**Lua: CalculateTotalHullFraction() **was removed.
965 965  )))
966 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
991 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
967 967  (((
968 968  //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.//
969 969  )))
... ... @@ -971,14 +971,14 @@
971 971  UI extensions
972 972  )))|(((
973 973  2.00 Beta 1
974 -)))|(((
975 -**FFI: (% style="color:#000000" %)RequestDockAtReason()/UndockPlayerShip()(%%) **changed their return values.
999 +)))|(% colspan="2" %)(((
1000 +**FFI: RequestDockAtReason()/UndockPlayerShip() **changed their return values.
976 976  )))
977 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1002 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
978 978  (((
979 979  //Changed return value type to const char* to better identify failure reasons in Lua script.//
980 980  )))
981 -|(% colspan="3" %)(% colspan="3" %)
1006 +|(% colspan="4" %)(% colspan="3" %)
982 982  (((
983 983  == 1.50 ==
984 984  )))
... ... @@ -986,10 +986,10 @@
986 986  UI extensions
987 987  )))|(((
988 988  1.50 Beta 3
989 -)))|(((
1014 +)))|(% colspan="2" %)(((
990 990  **Lua: GetComponentData() **changed behavior of "docksizes" property.
991 991  )))
992 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1017 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
993 993  (((
994 994  //The "docksizes" property no longer includes internal ship storage docks.//
995 995  )))
... ... @@ -997,10 +997,10 @@
997 997  All
998 998  )))|(((
999 999  1.50 Beta 2
1000 -)))|(((
1025 +)))|(% colspan="2" %)(((
1001 1001  **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR).
1002 1002  )))
1003 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1028 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1004 1004  (((
1005 1005  //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".//
1006 1006  
... ... @@ -1012,10 +1012,10 @@
1012 1012  UI extensions
1013 1013  )))|(((
1014 1014  1.50 Beta 2
1015 -)))|(((
1040 +)))|(% colspan="2" %)(((
1016 1016  **FFI: UpgradeGroupInfo **datatype was changed.
1017 1017  )))
1018 -|(% 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" %)
1019 1019  (((
1020 1020  //Added new "operational" field to retrieve information about number of operational upgrades in a group.//
1021 1021  )))
... ... @@ -1025,11 +1025,11 @@
1025 1025  )))|(% colspan="1" %)(% colspan="1" %)
1026 1026  (((
1027 1027  1.50 Beta 1
1028 -)))|(% colspan="1" %)(% colspan="1" %)
1053 +)))|(% colspan="2" %)(% colspan="1" %)
1029 1029  (((
1030 1030  **FFI: SetGuidance()** removed useinfopoint argument.
1031 1031  )))
1032 -|(% class="highlight-grey" colspan="3" 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="3" data-highlight-colour="grey" %)
1033 1033  (((
1034 1034  //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.//
1035 1035  
... ... @@ -1039,14 +1039,14 @@
1039 1039  UI extensions
1040 1040  )))|(((
1041 1041  1.50 Beta 1
1042 -)))|(((
1067 +)))|(% colspan="2" %)(((
1043 1043  **FFI: CancelConstruction() **changed its return value.
1044 1044  )))
1045 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1070 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1046 1046  (((
1047 -(% style="color:#000000" %)//CancelConstruction() now returns if the cancellation was successful. //
1072 +//CancelConstruction() now returns if the cancellation was successful. //
1048 1048  )))
1049 -|(% colspan="3" %)(% colspan="3" %)
1074 +|(% colspan="4" %)(% colspan="3" %)
1050 1050  (((
1051 1051  == 1.32 ==
1052 1052  )))
... ... @@ -1054,14 +1054,14 @@
1054 1054  UI extensions
1055 1055  )))|(((
1056 1056  1.32
1057 -)))|(((
1082 +)))|(% colspan="2" %)(((
1058 1058  **Lua: GetComponentData() **removed the "nextdestname" property.
1059 1059  )))
1060 -|(% 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" %)
1061 1061  (((
1062 1062  //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.//
1063 1063  )))
1064 -|(% colspan="3" %)(% colspan="3" %)
1089 +|(% colspan="4" %)(% colspan="3" %)
1065 1065  (((
1066 1066  == 1.20 ==
1067 1067  )))
... ... @@ -1069,10 +1069,10 @@
1069 1069  UI extensions
1070 1070  )))|(((
1071 1071  1.20
1072 -)))|(((
1097 +)))|(% colspan="2" %)(((
1073 1073  **FFI: GetAAOption()** got a new "useconfig" parameter.
1074 1074  )))
1075 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1100 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1076 1076  (((
1077 -//The AA setting was changed to check the new setting with the user. In order to restore the old setting (% style="color:#000000" %)GetAAOption() gets the option to retrieve the config settings.//
1102 +//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.//
1078 1078  )))