Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 57.1
edited by owen
on 2020/02/14 14:30
Change comment: There is no comment for this version
To version 45.1
edited by stefan
on 2019/11/19 20:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.owen
1 +xwiki:XWiki.stefan
Content
... ... @@ -31,82 +31,9 @@
31 31  )))
32 32  |(% colspan="1" %)(% colspan="1" %)
33 33  (((
34 -Scripts
35 -)))|(% colspan="1" %)(% colspan="1" %)
36 -(((
37 -3.0 Beta 6
38 -)))|(% colspan="1" %)(% colspan="1" %)
39 -(((
40 -Changed behaviour of script action <get_suitable_job/>
41 -)))
42 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
43 -(((
44 -<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.
45 -)))
46 -|(% colspan="1" %)(% colspan="1" %)
47 -(((
48 -Scripts
49 -)))|(% colspan="1" %)(% colspan="1" %)
50 -(((
51 -3.0 Beta 6
52 -)))|(% colspan="1" %)(% colspan="1" %)
53 -(((
54 -Changed behaviour of script action <get_ware_definition/>
55 -)))
56 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
57 -(((
58 -//<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.//
59 -)))
60 -|(% colspan="1" %)(% colspan="1" %)
61 -(((
62 62  Global
63 63  )))|(% colspan="1" %)(% colspan="1" %)
64 64  (((
65 -3.0 Beta 5
66 -)))|(% colspan="1" %)(% colspan="1" %)
67 -(((
68 -Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case
69 -)))
70 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
71 -(((
72 -//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.)\\
73 -
74 -//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).//
75 -)))
76 -|(% colspan="1" %)(% colspan="1" %)
77 -(((
78 -Scripts
79 -)))|(% colspan="1" %)(% colspan="1" %)
80 -(((
81 -3.0 Beta 5
82 -)))|(% colspan="1" %)(% colspan="1" %)
83 -(((
84 -Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions>
85 -)))
86 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
87 -(((
88 -//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.//
89 -)))
90 -|(% colspan="1" %)(% colspan="1" %)
91 -(((
92 -Scripts
93 -)))|(% colspan="1" %)(% colspan="1" %)
94 -(((
95 -3.0 Beta 5
96 -)))|(% colspan="1" %)(% colspan="1" %)
97 -(((
98 -Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos**
99 -)))
100 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
101 -(((
102 -//Before the change, positions are relative to $dockingbay.parent.
103 -After the change, positions are relative to $dockingbay as specified in the documentation.//
104 -)))
105 -|(% colspan="1" %)(% colspan="1" %)
106 -(((
107 -Global
108 -)))|(% colspan="1" %)(% colspan="1" %)
109 -(((
110 110  3.0 Beta 2
111 111  )))|(% colspan="1" %)(% colspan="1" %)
112 112  (((
... ... @@ -121,14 +121,14 @@
121 121  )))|(((
122 122  3.0 Beta 2
123 123  )))|(((
124 -Changes to **<event_object_changed_owner>** and added **<event_object_changed_true_owner>**.
51 +Changes to **<event_changed_owner>** and added **<event_changed_true_owner>**.
125 125  )))
126 126  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
127 127  (((
128 -//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.
129 -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.
130 -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.
131 -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).
55 +//Before 3.0 Beta 2 there was just a single event_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.
56 +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_changed_true_owner was introduced.
57 +If in your scripts you make use of the event_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.
58 +On top of that the 3rd-parameter of the event_changed_owner (oldtrueowner) 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).//
132 132  )))
133 133  |(% colspan="1" %)(% colspan="1" %)
134 134  (((
... ... @@ -138,23 +138,12 @@
138 138  3.0 Beta 1
139 139  )))|(% colspan="1" %)(% colspan="1" %)
140 140  (((
141 -**MissionBoard** support dropped
68 +MissionBoard support dropped
142 142  )))
143 143  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
144 144  (((
145 -//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.//
72 +//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 behavior would occur. Therefore we cleaned things up in 3.0 Beta 1 including deprecating/removing any related UI/script function.//
146 146  )))
147 -|(((
148 -Job/God
149 -)))|(((
150 -3.0 Beta 1
151 -)))|(((
152 -By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined
153 -)))
154 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
155 -(((
156 -//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.//
157 -)))
158 158  |(% colspan="1" %)(% colspan="1" %)
159 159  (((
160 160  Scripts
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -91030334
1 +88346129
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/91030334/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/88346129/Breaking Changes