Skip to Content

Changes for page Breaking Changes

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