Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03

From version 102.1
edited by owen
on 2023/02/07 12:57
Change comment: Added documentation for <find_object_surface> changes
To version 99.1
edited by owen
on 2023/01/19 19:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -35,42 +35,9 @@
35 35  Scripts
36 36  )))|(% colspan="1" %)(% colspan="1" %)
37 37  (((
38 -6.00 Beta 3
39 -)))|(% colspan="1" %)(% colspan="1" %)
40 -(((
41 -Changed result of **<find_object_surface>** action in the case of a failure
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 'posname' and 'rotname' result attributes of <find_object_surface> will now return null in the case of no valid surface position being found.//
46 -
47 -//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.//
48 -
49 -//The action itself has been improved to increase the chance of finding suitable surface positions.//
50 -)))
51 -|(% colspan="1" %)(% colspan="1" %)
52 -(((
53 -Scripts
54 -)))|(% colspan="1" %)(% colspan="1" %)
55 -(((
56 56  6.00 Beta 1
57 57  )))|(% colspan="1" %)(% colspan="1" %)
58 58  (((
59 -Behaviour change for **<match_dock>** script component filter
60 -)))
61 -|(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
62 -(((
63 -//<match_dock> nodes can now be used on container and walkablemodule classes without wrapping them in <match_content> nodes.
64 -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.//
65 -)))
66 -|(% colspan="1" %)(% colspan="1" %)
67 -(((
68 -Scripts
69 -)))|(% colspan="1" %)(% colspan="1" %)
70 -(((
71 -6.00 Beta 1
72 -)))|(% colspan="1" %)(% colspan="1" %)
73 -(((
74 74  Changed result attribute location for **<get_attackstrength>**
75 75  )))
76 76  |(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" title="Background colour : " colspan="3" data-highlight-colour="grey" %)
... ... @@ -121,9 +121,9 @@
121 121  )))|(((
122 122  Changed behaviour of **<angles>** in cutscenes
123 123  )))
124 -|(% 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" %)
91 +|(% colspan="3" %)(% colspan="3" %)
125 125  (((
126 -//The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.//
93 +The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.
127 127  )))
128 128  |(% colspan="3" %)(% colspan="3" %)
129 129  (((
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -138872528
1 +135862012
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/138872528/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/135862012/Breaking Changes