Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 91.1
edited by florian
on 2021/06/24 11:25
Change comment: There is no comment for this version
To version 37.1
edited by nick
on 2019/09/02 12:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.florian
1 +xwiki:XWiki.nick
Content
... ... @@ -24,479 +24,20 @@
24 24  Version
25 25  )))|=(((
26 26  Summary
27 -)))|=(% colspan="1" %)(% colspan="1" %)
28 -(((
29 -
30 30  )))
31 -|(% colspan="4" %)(% colspan="4" %)
32 -(((
33 -== 4.10 ==
34 -)))
35 35  |(% colspan="1" %)(% colspan="1" %)
36 36  (((
37 -UI extensions
38 -)))|(% colspan="1" %)(% colspan="1" %)
39 -(((
40 -4.10 Beta 2
41 -)))|(% colspan="1" %)(% colspan="1" %)
42 -(((
43 -**FFI**: SetMacroMapPlayerSectorOffset() deprecated
44 -)))|(% colspan="1" %)(% colspan="1" %)
45 -(((
46 -
47 -)))
48 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
49 -(((
50 -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.
51 -)))|(% colspan="1" %)(% colspan="1" %)
52 -(((
53 -
54 -)))
55 -|(((
56 -UI extensions
57 -)))|(((
58 -4.10 Beta 2
59 -)))|(((
60 -**FFI**: (% style="color: rgb(0,0,0);" %)FilterComponentForMapMode(%%)() and (% style="color: rgb(0,0,0);" %)SetMapObjectFilter() changed
61 -)))|(% colspan="1" %)(% colspan="1" %)
62 -(((
63 -
64 -)))
65 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
66 -(((
67 -//These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.//
68 -)))|(% colspan="1" %)(% colspan="1" %)
69 -(((
70 -
71 -)))
72 -|(((
73 73  Scripts
74 -)))|(((
75 -4.10 Beta 1
76 -)))|(((
77 -People related attributes of mission** <delivery> **node moved
78 -)))|(((
79 -
80 -)))
81 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
82 -(((
83 -//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.//
84 -)))
85 -|(% colspan="1" %)(% colspan="1" %)
86 -(((
87 -Scripts
88 88  )))|(% colspan="1" %)(% colspan="1" %)
89 89  (((
90 -4.10 Beta 1
91 -)))|(% colspan="1" %)(% colspan="1" %)
92 -(((
93 -**$destructible.productions** replaced with $defensible.productions
94 -)))|(% colspan="1" %)(% colspan="1" %)
95 -(((
96 -
97 -)))
98 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
99 -(((
100 -//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.//
101 -)))|(% colspan="1" %)(% colspan="1" %)
102 -(((
103 -
104 -)))
105 -|(((
106 -Scripts
107 -)))|(((
108 -4.10 Beta 1
109 -)))|(((
110 -Removed script property **$object.spawnsourceseed**
111 -)))|(((
112 -
113 -)))
114 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
115 -(((
116 -//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.//
117 -)))
118 -|(% colspan="4" %)(% colspan="4" %)
119 -(((
120 -== 4.00 ==
121 -)))
122 -|(% colspan="1" %)(% colspan="1" %)
123 -(((
124 -UI core
125 -)))|(% colspan="1" %)(% colspan="1" %)
126 -(((
127 -4.00 Beta 10
128 -)))|(% colspan="1" %)(% colspan="1" %)
129 -(((
130 -Controlled ship can change without a **gameplanchange-event** occurring.
131 -)))|(% colspan="1" %)(% colspan="1" %)
132 -(((
133 -
134 -)))
135 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
136 -(((
137 -//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).
138 -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.
139 -//
140 -)))|(% colspan="1" %)(% colspan="1" %)
141 -(((
142 -
143 -)))
144 -|(((
145 -Scripts
146 -)))|(((
147 -4.00 Beta 7
148 -)))|(((
149 -Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed
150 -)))|(((
151 -
152 -)))
153 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
154 -(((
155 -//Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects?
156 -New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits
157 -Note: param3 only exists in <event_terraforming_project_succeeded> and not in <event_terraforming_project_failed>, but both now have the booleans in a list for consistency//
158 -)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %)
159 -(((
160 -
161 -)))
162 -|(% colspan="1" %)(% colspan="1" %)
163 -(((
164 -UI core
165 -)))|(% colspan="1" %)(% colspan="1" %)
166 -(((
167 -4.00 Beta 6
168 -)))|(% colspan="1" %)(% colspan="1" %)
169 -(((
170 -**FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed
171 -)))|(% colspan="1" %)(% colspan="1" %)
172 -(((
173 -
174 -)))
175 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
176 -(((
177 -//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.
178 -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).//
179 -
180 -//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.
181 -//
182 -)))|(% colspan="1" %)(% colspan="1" %)
183 -(((
184 -
185 -)))
186 -|(% colspan="1" %)(% colspan="1" %)
187 -(((
188 -UI core
189 -)))|(% colspan="1" %)(% colspan="1" %)
190 -(((
191 -4.00 Beta 5
192 -)))|(% colspan="1" %)(% colspan="1" %)
193 -(((
194 -**FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed
195 -)))|(% colspan="1" %)(% colspan="1" %)
196 -(((
197 -
198 -)))
199 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
200 -(((
201 -//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.//
202 -
203 -//If you rely on a handling where they are treated like enemies, please use the new GetRelationStatus3() //function which returns the new range for these objects: 1 (meaning 'enemy' (aka: not yet hostile) here with following relations having been shifted up).
204 -)))|(% colspan="1" %)(% colspan="1" %)
205 -(((
206 -
207 -)))
208 -|(((
209 -Parameters
210 -)))|(((
211 -4.00 Beta 1
212 -)))|(((
213 -**requiresconstructionvessel** parameter moved
214 -)))|(((
215 -
216 -)))
217 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
218 -(((
219 -//The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.//
220 -)))
221 -|(((
222 -Scripts
223 -)))|(((
224 -4.00 Beta 1
225 -)))|(((
226 -Changed behaviour of **gatedistance** script property
227 -)))|(((
228 -
229 -)))
230 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
231 -(((
232 -//The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.//
233 -)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %)
234 -(((
235 -
236 -)))
237 -|(% colspan="4" %)(% colspan="4" %)
238 -(((
239 -== 3.30 ==
240 -)))
241 -|(((
242 -UI extensions
243 -)))|(((
244 -3.30 Beta 3
245 -)))|(((
246 -**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()**
247 -)))|(% colspan="1" %)(% colspan="1" %)
248 -(((
249 -
250 -)))
251 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
252 -(((
253 -//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()//
254 -)))
255 -|(% colspan="4" %)(% colspan="4" %)
256 -(((
257 -== 3.20 ==
258 -)))
259 -|(((
260 -Scripts
261 -)))|(((
262 -3.20 Beta 1
263 -)))|(((
264 -Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed
265 -)))|(% colspan="1" %)(% colspan="1" %)
266 -(((
267 -
268 -)))
269 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
270 -(((
271 -//Old params: param = attacked object, param2 = attack method, param3 = attacked component//
272 -//New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon]
273 -Note that this also means the component attribute to the events is no longer available, so scripts checking the attacked component need to use event.param3.{1} instead//
274 -)))
275 -|(% colspan="1" %)(% colspan="1" %)
276 -(((
277 -Scripts
278 -)))|(% colspan="1" %)(% colspan="1" %)
279 -(((
280 -3.20 Beta 1
281 -)))|(% colspan="1" %)(% colspan="1" %)
282 -(((
283 -Removed script property $trade.**restriction.faction**
284 -)))|(% colspan="1" %)(% colspan="1" %)
285 -(((
286 -
287 -)))
288 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
289 -(((
290 -//$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.//
291 -)))
292 -|(((
293 -UI extensions
294 -)))|(((
295 -3.20 Beta 1
296 -)))|(((
297 -**Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete!
298 -)))|(% colspan="1" %)(% colspan="1" %)
299 -(((
300 -
301 -)))
302 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
303 -(((
304 -//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.//
305 -)))
306 -|(% colspan="4" %)(% colspan="4" %)
307 -(((
308 -== 3.10 ==
309 -)))
310 -|(% colspan="1" %)(% colspan="1" %)
311 -(((
312 -Scripts
313 -)))|(% colspan="1" %)(% colspan="1" %)
314 -(((
315 -3.10 Beta 1
316 -)))|(% colspan="1" %)(% colspan="1" %)
317 -(((
318 -Removed script action **<add_build/>**
319 -)))|(% colspan="1" %)(% colspan="1" %)
320 -(((
321 -
322 -)))
323 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
324 -(((
325 -//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.//
326 -)))
327 -|(% colspan="4" %)(% colspan="4" %)
328 -(((
329 -== 3.00 ==
330 -)))
331 -|(% colspan="1" %)(% colspan="1" %)
332 -(((
333 -Scripts
334 -)))|(% colspan="1" %)(% colspan="1" %)
335 -(((
336 -3.0 Beta 6
337 -)))|(% colspan="1" %)(% colspan="1" %)
338 -(((
339 -Changed behaviour of script action **<get_suitable_job/>**
340 -)))|(% colspan="1" %)(% colspan="1" %)
341 -(((
342 -
343 -)))
344 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
345 -(((
346 -//<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.//
347 -)))
348 -|(% colspan="1" %)(% colspan="1" %)
349 -(((
350 -Scripts
351 -)))|(% colspan="1" %)(% colspan="1" %)
352 -(((
353 -3.0 Beta 6
354 -)))|(% colspan="1" %)(% colspan="1" %)
355 -(((
356 -Changed behaviour of script action **<get_ware_definition/>**
357 -)))|(% colspan="1" %)(% colspan="1" %)
358 -(((
359 -
360 -)))
361 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
362 -(((
363 -//<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.//
364 -)))
365 -|(% colspan="1" %)(% colspan="1" %)
366 -(((
367 -Global
368 -)))|(% colspan="1" %)(% colspan="1" %)
369 -(((
370 -3.0 Beta 5
371 -)))|(% colspan="1" %)(% colspan="1" %)
372 -(((
373 -Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case
374 -)))|(% colspan="1" %)(% colspan="1" %)
375 -(((
376 -
377 -)))
378 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
379 -(((
380 -//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.)\\
381 -
382 -//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).//
383 -)))
384 -|(% colspan="1" %)(% colspan="1" %)
385 -(((
386 -Scripts
387 -)))|(% colspan="1" %)(% colspan="1" %)
388 -(((
389 -3.0 Beta 5
390 -)))|(% colspan="1" %)(% colspan="1" %)
391 -(((
392 -Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions>
393 -)))|(% colspan="1" %)(% colspan="1" %)
394 -(((
395 -
396 -)))
397 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
398 -(((
399 -//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.//
400 -)))
401 -|(% colspan="1" %)(% colspan="1" %)
402 -(((
403 -Scripts
404 -)))|(% colspan="1" %)(% colspan="1" %)
405 -(((
406 -3.0 Beta 5
407 -)))|(% colspan="1" %)(% colspan="1" %)
408 -(((
409 -Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos**
410 -)))|(% colspan="1" %)(% colspan="1" %)
411 -(((
412 -
413 -)))
414 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
415 -(((
416 -//Before the change, positions are relative to $dockingbay.parent.
417 -After the change, positions are relative to $dockingbay as specified in the documentation.//
418 -)))
419 -|(% colspan="1" %)(% colspan="1" %)
420 -(((
421 -Global
422 -)))|(% colspan="1" %)(% colspan="1" %)
423 -(((
424 -3.0 Beta 2
425 -)))|(% colspan="1" %)(% colspan="1" %)
426 -(((
427 -Support for entity flag "**skillsvisible**" dropped
428 -)))|(% colspan="1" %)(% colspan="1" %)
429 -(((
430 -
431 -)))
432 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
433 -(((
434 -//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().//
435 -)))
436 -|(((
437 -Scripts
438 -)))|(((
439 -3.0 Beta 2
440 -)))|(((
441 -Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**.
442 -)))|(% colspan="1" %)(% colspan="1" %)
443 -(((
444 -
445 -)))
446 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
447 -(((
448 -//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.
449 -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.
450 -If in your scripts you make use of the <event_object_changed_owner> condition you need to verify that you indeed want to work with the "effective" component owner or whether your script code actually should work with the true owner of an object and update your code accordingly.
451 -On top of that the 3rd parameter of <event_object_changed_owner> (trueprevious) was dropped as the event is no longer triggered upon a change of the true owner alone (i.e. only if the change of the true owner has also an effect on the "effective" component owner).
452 -)))
453 -|(% colspan="1" %)(% colspan="1" %)
454 -(((
455 -Global
456 -)))|(% colspan="1" %)(% colspan="1" %)
457 -(((
458 458  3.0 Beta 1
459 459  )))|(% colspan="1" %)(% colspan="1" %)
460 460  (((
461 -**MissionBoard** support dropped
462 -)))|(% colspan="1" %)(% colspan="1" %)
463 -(((
464 -
465 -)))
466 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
467 -(((
468 -//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.//
469 -)))
470 -|(((
471 -Job/God
472 -)))|(((
473 -3.0 Beta 1
474 -)))|(((
475 -By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined
476 -)))|(% colspan="1" %)(% colspan="1" %)
477 -(((
478 -
479 -)))
480 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
481 -(((
482 -//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.//
483 -)))
484 -|(% colspan="1" %)(% colspan="1" %)
485 -(((
486 -Scripts
487 -)))|(% colspan="1" %)(% colspan="1" %)
488 -(((
489 -3.0 Beta 1
490 -)))|(% colspan="1" %)(% colspan="1" %)
491 -(((
492 492  Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'**
493 -)))|(% colspan="1" %)(% colspan="1" %)
494 -(((
495 -
496 496  )))
497 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
38 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
498 498  (((
499 -//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.//
40 +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.
500 500  )))
501 501  |(% colspan="1" %)(% colspan="1" %)
502 502  (((
... ... @@ -507,11 +507,8 @@
507 507  )))|(% colspan="1" %)(% colspan="1" %)
508 508  (((
509 509  Script action **<set_doors_locked/>** attribute **'group'** changed
510 -)))|(% colspan="1" %)(% colspan="1" %)
511 -(((
512 -
513 513  )))
514 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
52 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
515 515  (((
516 516  //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.//
517 517  )))
... ... @@ -524,11 +524,8 @@
524 524  )))|(% colspan="1" %)(% colspan="1" %)
525 525  (((
526 526  Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed
527 -)))|(% colspan="1" %)(% colspan="1" %)
528 -(((
529 -
530 530  )))
531 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
66 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
532 532  (((
533 533  //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.//
534 534  )))
... ... @@ -541,11 +541,8 @@
541 541  )))|(% colspan="1" %)(% colspan="1" %)
542 542  (((
543 543  Script actions **<set_hack_target/>** and **<abort_hack/>** removed
544 -)))|(% colspan="1" %)(% colspan="1" %)
545 -(((
546 -
547 547  )))
548 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
80 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
549 549  (((
550 550  //These actions had no effect and were removed.//
551 551  )))
... ... @@ -558,11 +558,8 @@
558 558  )))|(% colspan="1" %)(% colspan="1" %)
559 559  (((
560 560  **<setup_conversation_minigame/>** script action removed
561 -)))|(% colspan="1" %)(% colspan="1" %)
562 -(((
563 -
564 564  )))
565 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
94 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
566 566  (((
567 567  //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.//
568 568  )))
... ... @@ -575,11 +575,8 @@
575 575  )))|(% colspan="1" %)(% colspan="1" %)
576 576  (((
577 577  <add_player_choice_*> **confidence** attribute removed
578 -)))|(% colspan="1" %)(% colspan="1" %)
579 -(((
580 -
581 581  )))
582 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
108 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
583 583  (((
584 584  //The default confidence of player options is another leftover from the XR era and had no effect in X4.//
585 585  )))
... ... @@ -592,11 +592,8 @@
592 592  )))|(% colspan="1" %)(% colspan="1" %)
593 593  (((
594 594  **<hack_via_control_panel/>** script action removed
595 -)))|(% colspan="1" %)(% colspan="1" %)
596 -(((
597 -
598 598  )))
599 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
122 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
600 600  (((
601 601  //Unused script action <hack_via_control_panel/> was removed.//
602 602  )))
... ... @@ -609,47 +609,13 @@
609 609  )))|(% colspan="1" %)(% colspan="1" %)
610 610  (((
611 611  **Lua: **GetMiniGameCursorPosition() removed
612 -)))|(% colspan="1" %)(% colspan="1" %)
613 -(((
614 -
615 615  )))
616 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
136 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
617 617  (((
618 618  //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.//
619 619  )))
620 -|(((
621 -UI core
622 -)))|(((
623 -3.0 Beta 1
624 -)))|(((
625 -**FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders
626 -)))|(% colspan="1" %)(% colspan="1" %)
627 -(((
628 -
629 -)))
630 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
631 -(((
632 -//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.//
633 -)))
634 634  |(% colspan="1" %)(% colspan="1" %)
635 635  (((
636 -UI extensions
637 -)))|(% colspan="1" %)(% colspan="1" %)
638 -(((
639 -3.0 Beta 1
640 -)))|(% colspan="1" %)(% colspan="1" %)
641 -(((
642 -**FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor
643 -)))|(% colspan="1" %)(% colspan="1" %)
644 -(((
645 -
646 -)))
647 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
648 -(((
649 -//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.//
650 -)))
651 -|(% colspan="1" %)(% colspan="1" %)
652 -(((
653 653  Scripts
654 654  )))|(% colspan="1" %)(% colspan="1" %)
655 655  (((
... ... @@ -657,14 +657,11 @@
657 657  )))|(% colspan="1" %)(% colspan="1" %)
658 658  (((
659 659  **$ware.illegal** updated
660 -)))|(% colspan="1" %)(% colspan="1" %)
661 -(((
662 -
663 663  )))
664 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
150 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
665 665  (((
666 666  //$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.//
667 -//It now returns true if $ware is illegal to any faction in the game.//
153 +\\//It now returns true if $ware is illegal to any faction in the game.//
668 668  )))
669 669  |(% colspan="1" %)(% colspan="1" %)
670 670  (((
... ... @@ -674,14 +674,13 @@
674 674  3.0 Beta 1
675 675  )))|(% colspan="1" %)(% colspan="1" %)
676 676  (((
677 -MD script **RML_Flight_Along_Path** removed
678 -)))|(% colspan="1" %)(% colspan="1" %)
679 -(((
680 -
163 +'**checkoperational**' filter behaviour changed
681 681  )))
682 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
165 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
683 683  (((
684 -//The MD script RML_Flight_Along_Path was not referened and was removed.//
167 +//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.//
168 +
169 +//Sub nodes such as match_child will have checkoperational default to false. Existing uses may find that results now include non-operational components.//
685 685  )))
686 686  |(% colspan="1" %)(% colspan="1" %)
687 687  (((
... ... @@ -691,84 +691,23 @@
691 691  3.0 Beta 1
692 692  )))|(% colspan="1" %)(% colspan="1" %)
693 693  (((
694 -parameters of **<event_venture_mission_completed/>** changed
695 -)))|(% colspan="1" %)(% colspan="1" %)
696 -(((
697 -
179 +MD script **RML_Flight_Along_Path** removed
698 698  )))
699 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
181 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
700 700  (((
701 -//old params: param = venture details, param2 = ships involved, param3 = duration//
702 -//new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration//
183 +//The MD script RML_Flight_Along_Path was not referened and was removed.//
703 703  )))
704 704  |(((
705 705  Scripts
706 706  )))|(((
707 -3.0 Beta 1
708 -)))|(((
709 -**<set_object_wing_name/>** removed,
710 -**<set_object_fleet_name/>** added
711 -)))|(% colspan="1" %)(% colspan="1" %)
712 -(((
713 -
714 -)))
715 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
716 -(((
717 -//The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>//
718 -)))
719 -|(((
720 -Scripts
721 -)))|(((
722 -3.0 Beta 1
723 -)))|(((
724 -**$controllable.wing.*** removed,
725 -**$controllable.fleet.*** added
726 -)))|(% colspan="1" %)(% colspan="1" %)
727 -(((
728 -
729 -)))
730 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
731 -(((
732 -$controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander
733 -)))
734 -|(% colspan="4" %)(% colspan="4" %)
735 -(((
736 -== 2.60 ==
737 -)))
738 -|(((
739 -Scripts
740 -)))|(((
741 741  2.60 Beta 1
742 742  )))|(((
743 -'**checkoperational**' filter behaviour changed
744 -)))|(% colspan="1" %)(% colspan="1" %)
745 -(((
746 -
190 +$container.supplyresources behavior changed
747 747  )))
748 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
192 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
749 749  (((
750 -//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.//
751 -
752 -//Sub nodes such as match_child will have checkoperational default to false. Existing uses may find that results now include non-operational components.//
753 -)))
754 -|(((
755 -Scripts
756 -)))|(((
757 -2.60 Beta 1
758 -)))|(((
759 -$container.**supplyresources** behavior changed
760 -)))|(% colspan="1" %)(% colspan="1" %)
761 -(((
762 -
763 -)))
764 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
765 -(((
766 766  //The script keyword $container.supplyresources now includes reserved wares.//
767 767  )))
768 -|(% colspan="4" %)(% colspan="4" %)
769 -(((
770 -== 2.20 ==
771 -)))
772 772  |(% colspan="1" %)(% colspan="1" %)
773 773  (((
774 774  UI core
... ... @@ -778,11 +778,8 @@
778 778  )))|(% colspan="1" %)(% colspan="1" %)
779 779  (((
780 780  **Lua: GetControllerInfo()** returned mouseSteering/mouseCursor values are undefined.
781 -)))|(% colspan="1" %)(% colspan="1" %)
782 -(((
783 -
784 784  )))
785 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
206 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
786 786  (((
787 787  //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.
788 788  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.//
... ... @@ -799,18 +799,11 @@
799 799  )))|(% colspan="1" %)(% colspan="1" %)
800 800  (((
801 801  Attribute for build related conditions e.g. **<event_build_finished/>** renamed from 'buildmodule' to 'buildprocessor'
802 -)))|(% colspan="1" %)(% colspan="1" %)
803 -(((
804 -
805 805  )))
806 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
224 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
807 807  (((
808 808  //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.//
809 809  )))
810 -|(% colspan="4" %)(% colspan="4" %)
811 -(((
812 -== 2.00 ==
813 -)))
814 814  |(% colspan="1" %)(% colspan="1" %)
815 815  (((
816 816  Scripts
... ... @@ -820,11 +820,8 @@
820 820  )))|(% colspan="1" %)(% colspan="1" %)
821 821  (((
822 822  **<event_build_finished/> **param2 now returns null instead of a construction sequence
823 -)))|(% colspan="1" %)(% colspan="1" %)
824 -(((
825 -
826 826  )))
827 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
238 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
828 828  (((
829 829  //The construction sequence which was finished should now be accessed via the buildtask provided via param3.//
830 830  )))
... ... @@ -837,11 +837,8 @@
837 837  )))|(% colspan="1" %)(% colspan="1" %)
838 838  (((
839 839  **param.boarding.{...}** strength parameters removed
840 -)))|(% colspan="1" %)(% colspan="1" %)
841 -(((
842 -
843 843  )))
844 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
252 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
845 845  (((
846 846  //The 'recruitstrength', 'veteranstrength' and 'elitestrength' script parameters were no longer required for balancing the boarding gameplay, and were removed.//
847 847  )))
... ... @@ -854,11 +854,8 @@
854 854  )))|(% colspan="1" %)(% colspan="1" %)
855 855  (((
856 856  **$defensible.boardee/$defensible.boarder** and **<set_object_boarder/>/<remove_object_boarder/>** removed
857 -)))|(% colspan="1" %)(% colspan="1" %)
858 -(((
859 -
860 860  )))
861 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
266 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
862 862  (((
863 863  //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.//
864 864  )))
... ... @@ -868,11 +868,8 @@
868 868  2.00 Beta 1
869 869  )))|(((
870 870  **FFI: GetUpgradeSlotCurrentComponent()/GetUpgradeSlotGroup()** works on non-operationals
871 -)))|(% colspan="1" %)(% colspan="1" %)
872 -(((
873 -
874 874  )))
875 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
277 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
876 876  (((
877 877  //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.//
878 878  )))
... ... @@ -882,11 +882,8 @@
882 882  2.00 Beta 1
883 883  )))|(((
884 884  **FFI: SetFormationShape()** no longer indicates an error upon certain error cases
885 -)))|(% colspan="1" %)(% colspan="1" %)
886 -(((
887 -
888 888  )))
889 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
288 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
890 890  (((
891 891  //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.//
892 892  //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.//
... ... @@ -897,11 +897,8 @@
897 897  2.00 Beta 1
898 898  )))|(((
899 899  **<create_formation/>** now requires the attributes: 'leader' and 'follower'. Attribute 'object' is now deprecated.
900 -)))|(% colspan="1" %)(% colspan="1" %)
901 -(((
902 -
903 903  )))
904 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
300 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
905 905  (((
906 906  //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.//
907 907  )))
... ... @@ -911,11 +911,8 @@
911 911  2.00 Beta 1
912 912  )))|(((
913 913  **<event_player_changed_target/>** now fires and returns null if the player deselects a target.
914 -)))|(% colspan="1" %)(% colspan="1" %)
915 -(((
916 -
917 917  )))
918 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
311 +|(% class="highlight-grey" colspan="3" 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  )))
... ... @@ -925,11 +925,8 @@
925 925  2.00 Beta 1
926 926  )))|(((
927 927  **<shoot/>/<shoot_at/>** attribute changes.
928 -)))|(% colspan="1" %)(% colspan="1" %)
929 -(((
930 -
931 931  )))
932 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
322 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
933 933  (((
934 934  //Changed: Attribute "primary" is now optional and defines whether weapons from the ship's active primary weapon group will be fired. Defaults to true.//
935 935  //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.//
... ... @@ -943,11 +943,8 @@
943 943  2.00 Beta 1
944 944  )))|(((
945 945  **FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% class="confluenceTd" %)
946 -)))|(% colspan="1" %)(% colspan="1" %)
947 -(((
948 -
949 949  )))
950 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
337 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
951 951  (((
952 952  //Added possibility to query build tasks of a certain buildmodule.//
953 953  )))
... ... @@ -957,11 +957,8 @@
957 957  2.00 Beta 1
958 958  )))|(((
959 959  **Lua:** **GetLibraryEntry()** retrieved a new "buildresources" field.
960 -)))|(% colspan="1" %)(% colspan="1" %)
961 -(((
962 -
963 963  )))
964 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
348 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
965 965  (((
966 966  //Added list of resources a buildmodule needs to build.//
967 967  )))
... ... @@ -971,11 +971,8 @@
971 971  2.00 Beta 1
972 972  )))|(((
973 973  (% 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);" %)
974 -)))|(% colspan="1" %)(% colspan="1" %)
975 -(((
976 -
977 977  )))
978 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
359 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
979 979  (((
980 980  //Unused, derelict function from XR - use GetComponentData(..., "hullpercent") instead.//
981 981  )))
... ... @@ -985,18 +985,11 @@
985 985  2.00 Beta 1
986 986  )))|(((
987 987  **FFI: (% style="color: rgb(0,0,0);" %)RequestDockAtReason()/(% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)UndockPlayerShip()(%%) **changed their return values.(% style="color: rgb(0,0,0);" class="confluenceTd" %)
988 -)))|(% colspan="1" %)(% colspan="1" %)
989 -(((
990 -
991 991  )))
992 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
370 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
993 993  (((
994 994  //Changed return value type to const char* to better identify failure reasons in Lua script.//
995 995  )))
996 -|(% colspan="4" %)(% colspan="4" %)
997 -(((
998 -== 1.50 ==
999 -)))
1000 1000  |(((
1001 1001  UI extensions
1002 1002  )))|(((
... ... @@ -1003,11 +1003,8 @@
1003 1003  1.50 Beta 3
1004 1004  )))|(((
1005 1005  **Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %)
1006 -)))|(% colspan="1" %)(% colspan="1" %)
1007 -(((
1008 -
1009 1009  )))
1010 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
381 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1011 1011  (((
1012 1012  //The "docksizes" property no longer includes internal ship storage docks.//
1013 1013  )))
... ... @@ -1017,11 +1017,8 @@
1017 1017  1.50 Beta 2
1018 1018  )))|(((
1019 1019  **Meaning of "Shipyard"** was corrected throughout Lua/MD/AI scripts, so that Wharfs are not Shipyards (unlike in XR).
1020 -)))|(% colspan="1" %)(% colspan="1" %)
1021 -(((
1022 -
1023 1023  )))
1024 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
392 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1025 1025  (((
1026 1026  //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".//
1027 1027  
... ... @@ -1035,11 +1035,8 @@
1035 1035  1.50 Beta 2
1036 1036  )))|(((
1037 1037  **FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %)
1038 -)))|(% colspan="1" %)(% colspan="1" %)
1039 -(((
1040 -
1041 1041  )))
1042 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
407 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1043 1043  (((
1044 1044  //Added new "operational" field to retrieve information about number of operational upgrades in a group.//
1045 1045  )))
... ... @@ -1052,11 +1052,8 @@
1052 1052  )))|(% colspan="1" %)(% colspan="1" %)
1053 1053  (((
1054 1054  **FFI: SetGuidance()** removed useinfopoint argument.
1055 -)))|(% colspan="1" %)(% colspan="1" %)
1056 -(((
1057 -
1058 1058  )))
1059 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
421 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1060 1060  (((
1061 1061  //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.
1062 1062  //
... ... @@ -1069,18 +1069,11 @@
1069 1069  1.50 Beta 1
1070 1070  )))|(((
1071 1071  **FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %)
1072 -)))|(% colspan="1" %)(% colspan="1" %)
1073 -(((
1074 -
1075 1075  )))
1076 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
435 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1077 1077  (((
1078 1078  (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. //
1079 1079  )))
1080 -|(% colspan="4" %)(% colspan="4" %)
1081 -(((
1082 -== 1.32 ==
1083 -)))
1084 1084  |(((
1085 1085  UI extensions
1086 1086  )))|(((
... ... @@ -1087,18 +1087,11 @@
1087 1087  1.32
1088 1088  )))|(((
1089 1089  **Lua: GetComponentData() **removed the "nextdestname" property.
1090 -)))|(% colspan="1" %)(% colspan="1" %)
1091 -(((
1092 -
1093 1093  )))
1094 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
446 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1095 1095  (((
1096 1096  //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.//
1097 1097  )))
1098 -|(% colspan="4" %)(% colspan="4" %)
1099 -(((
1100 -== 1.20 ==
1101 -)))
1102 1102  |(((
1103 1103  UI extensions
1104 1104  )))|(((
... ... @@ -1105,11 +1105,8 @@
1105 1105  1.20
1106 1106  )))|(((
1107 1107  **FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %)
1108 -)))|(% colspan="1" %)(% colspan="1" %)
1109 -(((
1110 -
1111 1111  )))
1112 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
457 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1113 1113  (((
1114 1114  //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.//
1115 1115  )))
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -103940142
1 +85132000
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/103940142/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/85132000/Breaking Changes