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 56.1
edited by owen
on 2020/01/29 16:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.nick
1 +xwiki:XWiki.owen
Content
... ... @@ -31,17 +31,33 @@
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_ware_definition/>
41 +)))
42 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
43 +(((
44 +//<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.//
45 +)))
46 +|(% colspan="1" %)(% colspan="1" %)
47 +(((
34 34  Global
35 35  )))|(% colspan="1" %)(% colspan="1" %)
36 36  (((
37 -3.0 Beta 2
51 +3.0 Beta 5
38 38  )))|(% colspan="1" %)(% colspan="1" %)
39 39  (((
40 -Support for entity flag "**skillsvisible**" dropped
54 +Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case
41 41  )))
42 42  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
43 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().//
58 +//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.)\\
59 +
60 +//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).//
45 45  )))
46 46  |(% colspan="1" %)(% colspan="1" %)
47 47  (((
... ... @@ -51,13 +51,41 @@
51 51  3.0 Beta 5
52 52  )))|(% colspan="1" %)(% colspan="1" %)
53 53  (((
54 -Changes to $dockingbay.todockpos and $dockingbay.launchpos
70 +Adjustments of some MD library cues in the base game to change their usage from **<include_actions>** to <run_actions>
55 55  )))
56 56  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
57 57  (((
74 +//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.//
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 +Changes to $dockingbay.**todockpos** and $dockingbay.**launchpos**
85 +)))
86 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
87 +(((
58 58  //Before the change, positions are relative to $dockingbay.parent.
59 59  After the change, positions are relative to $dockingbay as specified in the documentation.//
60 60  )))
91 +|(% colspan="1" %)(% colspan="1" %)
92 +(((
93 +Global
94 +)))|(% colspan="1" %)(% colspan="1" %)
95 +(((
96 +3.0 Beta 2
97 +)))|(% colspan="1" %)(% colspan="1" %)
98 +(((
99 +Support for entity flag "**skillsvisible**" dropped
100 +)))
101 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
102 +(((
103 +//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().//
104 +)))
61 61  |(((
62 62  Scripts
63 63  )))|(((
... ... @@ -80,7 +80,7 @@
80 80  3.0 Beta 1
81 81  )))|(% colspan="1" %)(% colspan="1" %)
82 82  (((
83 -MissionBoard support dropped
127 +**MissionBoard** support dropped
84 84  )))
85 85  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
86 86  (((
... ... @@ -91,7 +91,7 @@
91 91  )))|(((
92 92  3.0 Beta 1
93 93  )))|(((
94 -By default, job/god entries now only spawn objects in space added by the extension in which they are defined
138 +By default, **job/god entries** now only spawn objects in space added by the extension in which they are defined
95 95  )))
96 96  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
97 97  (((
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -89144012
1 +90539273
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/90539273/Breaking Changes