Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 99.1
edited by owen
on 2023/01/19 19:13
Change comment: There is no comment for this version
To version 104.3
edited by Volodymyr Boichuk
on 2023/07/10 16:52
Change comment: Update document after refactoring.

Summary

Details

Page properties
Parent
... ... @@ -1,0 +1,1 @@
1 +X4 Foundations Wiki.Modding Support.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.owen
1 +xwiki:XWiki.Volodymyr
Content
... ... @@ -30,14 +30,77 @@
30 30  (((
31 31  == 6.00 ==
32 32  )))
33 +|(((
34 +Libraries
35 +)))|(((
36 +6.00 Beta 7
37 +)))|(((
38 +Updated weights for ship groups in shipgroups.xml libraries of base game and all DLCs.
39 +)))
40 +|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
41 +(((
42 +//Previously some entries were lacking "weight" parameter, causing it to default to "1", which prevent adding new ships to the group with appropriate/configurable granularity.
43 +//
44 +
45 +//All groups should now have "weight" parameter added and old "weights" were updated to not have single-digit numbers.//
46 +)))
33 33  |(% colspan="1" %)(% colspan="1" %)
34 34  (((
35 35  Scripts
36 36  )))|(% colspan="1" %)(% colspan="1" %)
37 37  (((
52 +6.00 Beta 4
53 +)))|(% colspan="1" %)(% colspan="1" %)
54 +(((
55 +Changed conditions for **<event_player_travelmode_started> <event_player_travelmode_stopped> <event_player_travelmode_charge_started> <event_player_travelmode_charge_aborted>** to be raised.
56 +)))
57 +|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
58 +(((
59 +//The <event_player_travelmode_started>, <event_player_travelmode_stopped>, <event_player_travelmode_charge_started> and <event_player_travelmode_charge_aborted> events will no longer be raised if the player is a passenger on board a ship which enters or leaves travel mode. Previously these events would be raised whether the player was the pilot or a passenger. //
60 +
61 +//Scripts that need to check whether the player exits travel mode may also need to consider checking whether the player leaves the control seat using <event_player_stopped_control> since this will also result in travel mode stopping.//
62 +)))
63 +|(% colspan="1" %)(% colspan="1" %)
64 +(((
65 +Scripts
66 +)))|(% colspan="1" %)(% colspan="1" %)
67 +(((
68 +6.00 Beta 3
69 +)))|(% colspan="1" %)(% colspan="1" %)
70 +(((
71 +Changed result of **<find_object_surface>** action in the case of a failure
72 +)))
73 +|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
74 +(((
75 +//The 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.//
76 +
77 +//Previously, it returned null only if there was a physics error. It however returned a valid, somewhat-random, position if physics were fine but it was still unable to find a suitable surface position. This position was often unsuitable to use for gameplay purposes so it is now null so the caller can handle the situation.//
78 +
79 +//The action itself has been improved to increase the chance of finding suitable surface positions.//
80 +)))
81 +|(% colspan="1" %)(% colspan="1" %)
82 +(((
83 +Scripts
84 +)))|(% colspan="1" %)(% colspan="1" %)
85 +(((
38 38  6.00 Beta 1
39 39  )))|(% colspan="1" %)(% colspan="1" %)
40 40  (((
89 +Behaviour change for **<match_dock>** script component filter
90 +)))
91 +|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
92 +(((
93 +//<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes.
94 +This has introduced a new potential pitfall: If finding or counting contained components be wary that there may be multiple positive results, even if there is only one dockingbay. e.g. matching contents for a station will include the dockingbay but also its containing walkable module as that also contains the dockingbay. To only account for docking bays, also filter by dockingbay class.//
95 +)))
96 +|(% colspan="1" %)(% colspan="1" %)
97 +(((
98 +Scripts
99 +)))|(% colspan="1" %)(% colspan="1" %)
100 +(((
101 +6.00 Beta 1
102 +)))|(% colspan="1" %)(% colspan="1" %)
103 +(((
41 41  Changed result attribute location for **<get_attackstrength>**
42 42  )))
43 43  |(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
... ... @@ -88,9 +88,9 @@
88 88  )))|(((
89 89  Changed behaviour of **<angles>** in cutscenes
90 90  )))
91 -|(% colspan="3" %)(% colspan="3" %)
154 +|(% 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" %)
92 92  (((
93 -The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.
156 +//The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.//
94 94  )))
95 95  |(% colspan="3" %)(% colspan="3" %)
96 96  (((
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -135862012
1 +78577854
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/135862012/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/78577854/Breaking Changes