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 48.1
edited by cbj
on 2019/12/18 14:42
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.cbj
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  (((
... ... @@ -138,7 +138,7 @@
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  (((
... ... @@ -149,11 +149,11 @@
149 149  )))|(((
150 150  3.0 Beta 1
151 151  )))|(((
152 -By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined
79 +By default, job/god entries now only spawn objects in space added by the extension in which they are defined
153 153  )))
154 154  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
155 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.//
83 +//To better support extensions which extend the 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 157  )))
158 158  |(% colspan="1" %)(% colspan="1" %)
159 159  (((
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -91030334
1 +89132386
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/89132386/Breaking Changes