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 103.1
edited by cbj
on 2023/02/20 14:12
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
... ... @@ -35,9 +35,58 @@
35 35  Scripts
36 36  )))|(% colspan="1" %)(% colspan="1" %)
37 37  (((
38 +6.00 Beta 4
39 +)))|(% colspan="1" %)(% colspan="1" %)
40 +(((
41 +Changed conditions for **<event_player_travelmode_started> <event_player_travelmode_stopped> <event_player_travelmode_charge_started> <event_player_travelmode_charge_aborted>** to be raised.
42 +)))
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" %)
44 +(((
45 +//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. //
46 +
47 +//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.//
48 +)))
49 +|(% colspan="1" %)(% colspan="1" %)
50 +(((
51 +Scripts
52 +)))|(% colspan="1" %)(% colspan="1" %)
53 +(((
54 +6.00 Beta 3
55 +)))|(% colspan="1" %)(% colspan="1" %)
56 +(((
57 +Changed result of **<find_object_surface>** action in the case of a failure
58 +)))
59 +|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
60 +(((
61 +//The 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.//
62 +
63 +//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.//
64 +
65 +//The action itself has been improved to increase the chance of finding suitable surface positions.//
66 +)))
67 +|(% colspan="1" %)(% colspan="1" %)
68 +(((
69 +Scripts
70 +)))|(% colspan="1" %)(% colspan="1" %)
71 +(((
38 38  6.00 Beta 1
39 39  )))|(% colspan="1" %)(% colspan="1" %)
40 40  (((
75 +Behaviour change for **<match_dock>** script component filter
76 +)))
77 +|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
78 +(((
79 +//<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes.
80 +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.//
81 +)))
82 +|(% colspan="1" %)(% colspan="1" %)
83 +(((
84 +Scripts
85 +)))|(% colspan="1" %)(% colspan="1" %)
86 +(((
87 +6.00 Beta 1
88 +)))|(% colspan="1" %)(% colspan="1" %)
89 +(((
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" %)
140 +|(% 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.
142 +//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 +141329146
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/141329146/Breaking Changes