Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 61.1
edited by florian
on 2020/04/30 09:16
Change comment: There is no comment for this version
To version 54.1
edited by klaus
on 2020/01/14 19:05
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.klaus
Content
... ... @@ -27,108 +27,23 @@
27 27  )))
28 28  |(% colspan="3" %)(% colspan="3" %)
29 29  (((
30 -== 3.20 ==
31 -)))
32 -|(((
33 -Scripts
34 -)))|(((
35 -3.20 Beta 1
36 -)))|(((
37 -Parameters of **<event_player_attacked_object/>** and **<event_object_attacked_object/>** changed
38 -)))
39 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
40 -(((
41 -//Old params: param = attacked object, param2 = attack method, param3 = attacked component//
42 -//New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon]
43 -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//
44 -)))
45 -|(((
46 -UI extensions
47 -)))|(((
48 -3.20 Beta 1
49 -)))|(((
50 -**FFI**: Deprecated the following functions: **GetContainerAllowedBuildFactions()**, **GetNumContainerAllowedBuildFactions()**, **IsContainerFactionBuildRescricted()**, **IsContainerFactionTradeRescricted()**, **SetContainerBuildAllowedFactions()**, **SetContainerFactionBuildRescricted()**
51 -)))
52 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
53 -(((
54 -With the addition of the Trade Rule feature the given functions are considered deprecated and should not be used anymore. Consider GetAllTradeRules(), GetContainerTradeRuleID(), SetContainerTradeRule() and similar trade rule functions for replacement.
55 -)))
56 -|(((
57 -UI extensions
58 -)))|(((
59 -3.20 Beta 1
60 -)))|(((
61 -**Lua**: **GetTradeRestrictions()**, **ToggleFactionTradeRestriction()** and **ToggleFactionTradeWareOverride()** are now obsolete!
62 -)))
63 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
64 -(((
65 -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.
66 -)))
67 -|(% colspan="3" %)(% colspan="3" %)
68 -(((
69 -== 3.10 ==
70 -)))
71 -|(% colspan="1" %)(% colspan="1" %)
72 -(((
73 -Scripts
74 -)))|(% colspan="1" %)(% colspan="1" %)
75 -(((
76 -3.10 Beta 1
77 -)))|(% colspan="1" %)(% colspan="1" %)
78 -(((
79 -Removed script action **<add_build/>**
80 -)))
81 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
82 -(((
83 -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.
84 -)))
85 -|(% colspan="3" %)(% colspan="3" %)
86 -(((
87 87  == 3.00 ==
88 88  )))
89 89  |(% colspan="1" %)(% colspan="1" %)
90 90  (((
91 -Scripts
34 +MD Scripts, Cutscenes
92 92  )))|(% colspan="1" %)(% colspan="1" %)
93 93  (((
94 -3.0 Beta 6
95 -)))|(% colspan="1" %)(% colspan="1" %)
96 -(((
97 -Changed behaviour of script action **<get_suitable_job/>**
98 -)))
99 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
100 -(((
101 -<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.
102 -)))
103 -|(% colspan="1" %)(% colspan="1" %)
104 -(((
105 -Scripts
106 -)))|(% colspan="1" %)(% colspan="1" %)
107 -(((
108 -3.0 Beta 6
109 -)))|(% colspan="1" %)(% colspan="1" %)
110 -(((
111 -Changed behaviour of script action **<get_ware_definition/>**
112 -)))
113 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
114 -(((
115 -//<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.//
116 -)))
117 -|(% colspan="1" %)(% colspan="1" %)
118 -(((
119 -Global
120 -)))|(% colspan="1" %)(% colspan="1" %)
121 -(((
122 122  3.0 Beta 5
123 123  )))|(% colspan="1" %)(% colspan="1" %)
124 124  (((
125 -Renamed all files in the **md**, ui, and **cutscenes** folders to lower-case
40 +Renamed all files in the **md** and **cutscenes** folders to lower-case
126 126  )))
127 127  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
128 128  (((
129 -//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.)\\
44 +//All MD 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.)\\
130 130  
131 -//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).//
46 +//Note that this change has no effect on the actual content of scripts or cutscenes. The 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).//
132 132  )))
133 133  |(% colspan="1" %)(% colspan="1" %)
134 134  (((
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -91947560
1 +89818026
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/91947560/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/89818026/Breaking Changes