Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03

From version 50.1
edited by nick
on 2020/01/08 16:26
Change comment: There is no comment for this version
To version 40.1
edited by stefan
on 2019/09/19 13:06
Change comment: added GetLocalizedInteractiveNotificationKey() for 3.0 Beta 1

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.nick
1 +xwiki:XWiki.stefan
Content
... ... @@ -31,85 +31,17 @@
31 31  )))
32 32  |(% colspan="1" %)(% colspan="1" %)
33 33  (((
34 -Global
35 -)))|(% colspan="1" %)(% colspan="1" %)
36 -(((
37 -3.0 Beta 2
38 -)))|(% colspan="1" %)(% colspan="1" %)
39 -(((
40 -Support for entity flag "**skillsvisible**" dropped
41 -)))
42 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
43 -(((
44 -//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().//
45 -)))
46 -|(% colspan="1" %)(% colspan="1" %)
47 -(((
48 48  Scripts
49 49  )))|(% colspan="1" %)(% colspan="1" %)
50 50  (((
51 -3.0 Beta 5
52 -)))|(% colspan="1" %)(% colspan="1" %)
53 -(((
54 -Changes to $dockingbay.todockpos and $dockingbay.launchpos
55 -)))
56 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
57 -(((
58 -//Before the change, positions are relative to $dockingbay.parent.
59 -After the change, positions are relative to $dockingbay as specified in the documentation.//
60 -)))
61 -|(((
62 -Scripts
63 -)))|(((
64 -3.0 Beta 2
65 -)))|(((
66 -Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**.
67 -)))
68 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
69 -(((
70 -//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.
71 -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.
72 -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.
73 -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).
74 -)))
75 -|(% colspan="1" %)(% colspan="1" %)
76 -(((
77 -Global
78 -)))|(% colspan="1" %)(% colspan="1" %)
79 -(((
80 80  3.0 Beta 1
81 81  )))|(% colspan="1" %)(% colspan="1" %)
82 82  (((
83 -MissionBoard support dropped
84 -)))
85 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
86 -(((
87 -//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.//
88 -)))
89 -|(((
90 -Job/God
91 -)))|(((
92 -3.0 Beta 1
93 -)))|(((
94 -By default, job/god entries now only spawn objects in space added by the extension in which they are defined
95 -)))
96 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
97 -(((
98 -//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.//
99 -)))
100 -|(% colspan="1" %)(% colspan="1" %)
101 -(((
102 -Scripts
103 -)))|(% colspan="1" %)(% colspan="1" %)
104 -(((
105 -3.0 Beta 1
106 -)))|(% colspan="1" %)(% colspan="1" %)
107 -(((
108 108  Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'**
109 109  )))
110 110  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
111 111  (((
112 -//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.//
44 +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.
113 113  )))
114 114  |(% colspan="1" %)(% colspan="1" %)
115 115  (((
... ... @@ -222,20 +222,6 @@
222 222  )))
223 223  |(% colspan="1" %)(% colspan="1" %)
224 224  (((
225 -UI extensions
226 -)))|(% colspan="1" %)(% colspan="1" %)
227 -(((
228 -3.0 Beta 1
229 -)))|(% colspan="1" %)(% colspan="1" %)
230 -(((
231 -**FFI: **UIWeaponMod returned by GetInstalledWeaponMod() now includes property SurfaceElementFactor
232 -)))
233 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
234 -(((
235 -//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.//
236 -)))
237 -|(% colspan="1" %)(% colspan="1" %)
238 -(((
239 239  Scripts
240 240  )))|(% colspan="1" %)(% colspan="1" %)
241 241  (((
... ... @@ -278,30 +278,6 @@
278 278  //old params: param = venture details, param2 = ships involved, param3 = duration//
279 279  //new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration//
280 280  )))
281 -|(((
282 -Scripts
283 -)))|(((
284 -3.0 Beta 1
285 -)))|(((
286 -**<set_object_wing_name/>** removed,
287 -**<set_object_fleet_name/>** added
288 -)))
289 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
290 -(((
291 -//The common action <set_object_wing_name/> has been replaced with <set_object_fleet_name/>//
292 -)))
293 -|(((
294 -Scripts
295 -)))|(((
296 -3.0 Beta 1
297 -)))|(((
298 -**$controllable.wing.*** removed,
299 -**$controllable.fleet.*** added
300 -)))
301 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
302 -(((
303 -$controllable.wing.name, $controllable.wing.iscommander, and $controllable.wing.commander have been replaced with $controllable.fleet.name, $controllable.fleet.iscommander, and $controllable.fleet.commander
304 -)))
305 305  |(% colspan="3" %)(% colspan="3" %)
306 306  (((
307 307  == 2.60 ==
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -89144012
1 +86835243
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/89144012/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/86835243/Breaking Changes