Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 96.1
edited by klaus
on 2023/01/04 13:23
Change comment: There is no comment for this version
To version 63.1
edited by cbj
on 2020/04/30 11:13
Change comment: Formatting again

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.klaus
1 +xwiki:XWiki.cbj
Content
... ... @@ -18,7 +18,6 @@
18 18  
19 19  = Breaking Changes =
20 20  
21 -(% class="wrapped" %)
22 22  |=(((
23 23  Type
24 24  )))|=(((
... ... @@ -28,273 +28,6 @@
28 28  )))
29 29  |(% colspan="3" %)(% colspan="3" %)
30 30  (((
31 -== 6.00 ==
32 -)))
33 -|(((
34 -Assets
35 -)))|(((
36 -6.00 Beta 1
37 -)))|(((
38 -Surface element **connections** are incompatible by default unless tagged as "**standard**", and also "**combat**" for non-missile, non-mining weapons
39 -)))
40 -|(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)
41 -(((
42 -//Connection tags used to specify compatibilities in component templates between a ship or station module and engines or shields now additionally require the use of the "standard" tag matching weapon or turret logic. For weapons that are neither Missile Launcher nor Mining Laser, the tag "combat" is also required.
43 -//
44 -)))
45 -|(% colspan="1" %)(% colspan="1" %)
46 -(((
47 -Scripts
48 -)))|(% colspan="1" %)(% colspan="1" %)
49 -(((
50 -6.00 Beta 1
51 -)))|(% colspan="1" %)(% colspan="1" %)
52 -(((
53 -Changed behaviour of attribute **sortbygatedistanceto** when finding objects, discarding unreachable objects
54 -)))
55 -|(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)
56 -(((
57 -//When finding components with attribute "sortbygatedistanceto", e.g. in <find_object>, any objects with a negative gatedistance (i.e. unreachable objects) are automatically excluded from the result.//
58 -)))
59 -|(((
60 -Scripts
61 -)))|(((
62 -6.00 Beta 1
63 -)))|(((
64 -**<event_player_owned_killed_object>** and **<event_player_owned_destroyed>** are now triggered before the corresponding **<event_object_destroyed>**, instead of afterwards.
65 -)))
66 -|(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)(% class="highlight-#f4f5f7" title="Background color : Light grey 100%" colspan="3" data-highlight-colour="#f4f5f7" %)
67 -(((
68 -//The order of events was adjusted, allowing handlers of <event_player_owned_killed_object> and <event_player_owned_destroyed> to access commander/subordinate relationship of the destroyed object.//
69 -)))
70 -|(% colspan="3" %)(% colspan="3" %)
71 -(((
72 -== 5.00 ==
73 -)))
74 -|(((
75 -Parameters
76 -)))|(((
77 -5.00 Beta 1
78 -)))|(((
79 -**<controlpanel><entry>: minduration** removed, **maxduration** renamed to duration
80 -)))
81 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
82 -(((
83 -//'minduration' was unused in X4, maxduration was and still is taken as the actual duration of control panel hacks. No functionality change.//
84 -)))
85 -|(% colspan="3" %)(% colspan="3" %)
86 -(((
87 -== 4.10 ==
88 -)))
89 -|(% colspan="1" %)(% colspan="1" %)
90 -(((
91 -UI extensions
92 -)))|(% colspan="1" %)(% colspan="1" %)
93 -(((
94 -4.10 Beta 7
95 -)))|(% colspan="1" %)(% colspan="1" %)
96 -(((
97 -**FFI**: (% style="color: rgb(0,0,0);" %)SetMapRenderCargoContents(%%)(), (% style="color: rgb(0,0,0);" %)SetMapRenderWorkForceInfo(), (% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)SetMapRenderCrewInfo() and (% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)SetMapRenderDockedShipInfos()(%%) deprecated
98 -)))
99 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
100 -(((
101 -//The functionality represented by (% style="color: rgb(0,0,0);" %)SetMapRenderCargoContents(%%)(), (% style="color: rgb(0,0,0);" %)SetMapRenderWorkForceInfo(), SetMapRenderCrewInfo() and SetMapRenderDockedShipInfos()(%%) has been removed and the function was therefore stubbed.//
102 -)))
103 -|(% colspan="1" %)(% colspan="1" %)
104 -(((
105 -UI extensions
106 -)))|(% colspan="1" %)(% colspan="1" %)
107 -(((
108 -4.10 Beta 6
109 -)))|(% colspan="1" %)(% colspan="1" %)
110 -(((
111 -**FFI**: CustomGameStartPlayerProperty2 changed
112 -)))
113 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
114 -(((
115 -//This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.//
116 -)))
117 -|(% colspan="1" %)(% colspan="1" %)
118 -(((
119 -Parameters
120 -)))|(% colspan="1" %)(% colspan="1" %)
121 -(((
122 -4.10 Beta 3
123 -)))|(% colspan="1" %)(% colspan="1" %)
124 -(((
125 -Renamed **<stationinfobox>** to **<infobox>**
126 -)))
127 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
128 -(((
129 -//Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.//
130 -)))
131 -|(% colspan="1" %)(% colspan="1" %)
132 -(((
133 -UI extensions
134 -)))|(% colspan="1" %)(% colspan="1" %)
135 -(((
136 -4.10 Beta 2
137 -)))|(% colspan="1" %)(% colspan="1" %)
138 -(((
139 -**FFI**: SetMacroMapPlayerSectorOffset() deprecated
140 -)))
141 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
142 -(((
143 -//The functionality represented by SetMacroMapPlayerSectorOffset() has been removed and the function was therefore stubbed. Setting the gamestart properties "sector" and "offset" will affect the universe macro map instead directly.//
144 -)))
145 -|(((
146 -UI extensions
147 -)))|(((
148 -4.10 Beta 2
149 -)))|(((
150 -**FFI**: (% style="color: rgb(0,0,0);" %)FilterComponentForMapMode(%%)() and (% style="color: rgb(0,0,0);" %)SetMapObjectFilter() changed
151 -)))
152 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
153 -(((
154 -//These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.//
155 -)))
156 -|(((
157 -Scripts
158 -)))|(((
159 -4.10 Beta 1
160 -)))|(((
161 -People related attributes of mission** <delivery> **node moved
162 -)))
163 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
164 -(((
165 -//The <delivery> node of <create_mission> and <update_mission> has been changed to support a new <wares> subnode. The people related attributes: 'people' and 'skills' have been moved from the <delivery> node itself to a <people> subnode.//
166 -)))
167 -|(% colspan="1" %)(% colspan="1" %)
168 -(((
169 -Scripts
170 -)))|(% colspan="1" %)(% colspan="1" %)
171 -(((
172 -4.10 Beta 1
173 -)))|(% colspan="1" %)(% colspan="1" %)
174 -(((
175 -**$destructible.productions** replaced with $defensible.productions
176 -)))
177 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
178 -(((
179 -//The $destructible.productions script property was removed and reimplemented as $defensible.productions meaning some old uses may no longer work unless the destructible is also a defensible. The old implementation functioned by finding the containing object of the destructible (including itself) to query for the production modules.//
180 -)))
181 -|(((
182 -Scripts
183 -)))|(((
184 -4.10 Beta 1
185 -)))|(((
186 -Removed script property **$object.spawnsourceseed**
187 -)))
188 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
189 -(((
190 -//The spawnsource seed is no longer directly accessible by scripts. Use $component.seed, which will internally use the spawnsource seed if able. Note: An improvement is that .seed on objects without a spawnsource seed will now result in a value that differs between objects of the same macro, meaning it can now reliably be used for player property or job ships.//
191 -)))
192 -|(% colspan="3" %)(% colspan="3" %)
193 -(((
194 -== 4.00 ==
195 -)))
196 -|(% colspan="1" %)(% colspan="1" %)
197 -(((
198 -UI core
199 -)))|(% colspan="1" %)(% colspan="1" %)
200 -(((
201 -4.00 Beta 10
202 -)))|(% colspan="1" %)(% colspan="1" %)
203 -(((
204 -Controlled ship can change without a **gameplanchange-event** occurring.
205 -)))
206 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
207 -(((
208 -//Before 4.00 Beta 10 it was ensured that there is no direct transition between the 'cockpit ui mode' of one ship to another. Instead, it was always ensured that the UI first transitions into the firstperson mode and then back into the cockpit mode (controlling then the other ship).
209 -In order to support the new emergency eject feature which was added in 4.00 Beta 7, this assurance was dropped. As of 4.00 Beta 10 it is now possible that the ship the player controls can swap without the gameplanchange-event being risen which one could rely upon in previous versions. If your addon relied on the fact that the ship would not change without first going into first person mode, you will have to adjust your addon accordingly.
210 -//
211 -)))
212 -|(((
213 -Scripts
214 -)))|(((
215 -4.00 Beta 7
216 -)))|(((
217 -Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed
218 -)))
219 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
220 -(((
221 -//Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects?
222 -New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits
223 -Note: param3 only exists in <event_terraforming_project_succeeded> and not in <event_terraforming_project_failed>, but both now have the booleans in a list for consistency//
224 -)))
225 -|(% colspan="1" %)(% colspan="1" %)
226 -(((
227 -UI core
228 -)))|(% colspan="1" %)(% colspan="1" %)
229 -(((
230 -4.00 Beta 6
231 -)))|(% colspan="1" %)(% colspan="1" %)
232 -(((
233 -**FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed
234 -)))
235 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
236 -(((
237 -//In order to keep consistency with regards to the new behvior 'hostile' relation state and the older (deprecated) UI functions, the behavior of the deprecated GetFactionRelationStatus() function was changed according to the behavior of the GetRelationStatus()/GetRelationStatus2() functions which was done in the previous beta.
238 -Factions with a relation rating between -20 and -10 will now report a relation status of 'neutral' (aka: 1) instead of 'hostile'/'enemy' (aka: 0).//
239 -
240 -//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.
241 -//
242 -)))
243 -|(% colspan="1" %)(% colspan="1" %)
244 -(((
245 -UI core
246 -)))|(% colspan="1" %)(% colspan="1" %)
247 -(((
248 -4.00 Beta 5
249 -)))|(% colspan="1" %)(% colspan="1" %)
250 -(((
251 -**FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed
252 -)))
253 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
254 -(((
255 -//4.00 Beta 5// //introduces a new 'hostile' relation status and the game now distinguishes between hostile and enemy relation states. Objects not yet 'hostile' with the player are now visualized differently and therefore distinguishable from real hostile ones. Because of that, several related changes were made for these objects to bring them more in line with how 'neutral' objects behave (f.e. no automatic attacking of these objects by the player property anymore, no target selection when targeting the closest enemy, etc.). To reflect this, these objects are now returning 1 (neutral) as the relation status by the GetRelationStatus()/GetRelationStatus2() functions.//
256 -
257 -//If you rely on a handling where they are treated like enemies, please use the new GetRelationStatus3() //function which returns the new range for these objects: 1 (meaning 'enemy' (aka: not yet hostile) here with following relations having been shifted up).
258 -)))
259 -|(((
260 -Parameters
261 -)))|(((
262 -4.00 Beta 1
263 -)))|(((
264 -**requiresconstructionvessel** parameter moved
265 -)))
266 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
267 -(((
268 -//The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.//
269 -)))
270 -|(((
271 -Scripts
272 -)))|(((
273 -4.00 Beta 1
274 -)))|(((
275 -Changed behaviour of **gatedistance** script property
276 -)))
277 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
278 -(((
279 -//The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.//
280 -)))
281 -|(% colspan="3" %)(% colspan="3" %)
282 -(((
283 -== 3.30 ==
284 -)))
285 -|(((
286 -UI extensions
287 -)))|(((
288 -3.30 Beta 3
289 -)))|(((
290 -**FFI: **Removed** (% style="color: rgb(0,0,0);" %)GetMissionLimit() (%%)**(% style="color: rgb(0,0,0);" %)and** **(% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)**IsMissionLimit**(%%)**Enabled()**
291 -)))
292 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
293 -(((
294 -//These mission limit-related functions (added in 3.30 Beta 1 and 2) are replaced with FFI (% style="color: rgb(0,0,0);" %)IsMissionLimit(%%)Reach(% style="color: rgb(0,0,0);" %)ed()//
295 -)))
296 -|(% colspan="3" %)(% colspan="3" %)
297 -(((
298 298  == 3.20 ==
299 299  )))
300 300  |(((
... ... @@ -310,19 +310,16 @@
310 310  //New params: param = attacked object, param2 = attack method, param3 = attack component detail list: [attacked component, attacking weapon]
311 311  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//
312 312  )))
313 -|(% colspan="1" %)(% colspan="1" %)
314 -(((
315 -Scripts
316 -)))|(% colspan="1" %)(% colspan="1" %)
317 -(((
45 +|(((
46 +UI extensions
47 +)))|(((
318 318  3.20 Beta 1
319 -)))|(% colspan="1" %)(% colspan="1" %)
320 -(((
321 -Removed script property $trade.**restriction.faction**
49 +)))|(((
50 +**FFI**: Deprecated the following functions: **GetContainerAllowedBuildFactions()**, **GetNumContainerAllowedBuildFactions()**, **IsContainerFactionBuildRescricted()**, **IsContainerFactionTradeRescricted()**, **SetContainerBuildAllowedFactions()**, **SetContainerFactionBuildRescricted()**
322 322  )))
323 323  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
324 324  (((
325 -//$trade.restriction.faction has been replaced with $trade.restriction.factions, which returns a list of factions.//
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.//
326 326  )))
327 327  |(((
328 328  UI extensions
... ... @@ -863,7 +863,7 @@
863 863  )))|(((
864 864  2.00 Beta 1
865 865  )))|(((
866 -**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.
595 +**FFI: GetBuildTask()/GetNumBuildTasks()** got a new "buildmoduleid" parameter.(% class="confluenceTd" %)
867 867  )))
868 868  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
869 869  (((
... ... @@ -896,7 +896,7 @@
896 896  )))|(((
897 897  2.00 Beta 1
898 898  )))|(((
899 -**FFI: (% style="color: rgb(0,0,0);" %)RequestDockAtReason()/(% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)UndockPlayerShip()(%%) **changed their return values.
628 +**FFI: (% style="color: rgb(0,0,0);" %)RequestDockAtReason()/(% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %)UndockPlayerShip()(%%) **changed their return values.(% style="color: rgb(0,0,0);" class="confluenceTd" %)
900 900  )))
901 901  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
902 902  (((
... ... @@ -911,7 +911,7 @@
911 911  )))|(((
912 912  1.50 Beta 3
913 913  )))|(((
914 -**Lua: GetComponentData() **changed behavior of "docksizes" property.
643 +**Lua: GetComponentData() **changed behavior of "docksizes" propertly.(% class="confluenceTd" %)
915 915  )))
916 916  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
917 917  (((
... ... @@ -937,7 +937,7 @@
937 937  )))|(((
938 938  1.50 Beta 2
939 939  )))|(((
940 -**FFI: UpgradeGroupInfo **datatype was changed.
669 +**FFI: UpgradeGroupInfo **datatype was changed.(% class="confluenceTd" %)
941 941  )))
942 942  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
943 943  (((
... ... @@ -965,7 +965,7 @@
965 965  )))|(((
966 966  1.50 Beta 1
967 967  )))|(((
968 -**FFI: CancelConstruction() **changed its return value.
697 +**FFI: CancelConstruction() **changed its return value.(% class="confluenceTd" %)
969 969  )))
970 970  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
971 971  (((
... ... @@ -995,7 +995,7 @@
995 995  )))|(((
996 996  1.20
997 997  )))|(((
998 -**FFI: GetAAOption()** got a new "useconfig" parameter.
727 +**FFI: GetAAOption()** got a new "useconfig" parameter.(% class="confluenceTd" %)
999 999  )))
1000 1000  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
1001 1001  (((
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -135856500
1 +91949219
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/135856500/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/91949219/Breaking Changes