Changes for page Breaking Changes
Last modified by Michael Baumgardt on 2026/04/17 12:03
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -xwiki:XWiki. klaus1 +xwiki:XWiki.owen - Content
-
... ... @@ -30,6 +30,53 @@ 30 30 ((( 31 31 == 6.00 == 32 32 ))) 33 +|(% colspan="1" %)(% colspan="1" %) 34 +((( 35 +Scripts 36 +)))|(% colspan="1" %)(% colspan="1" %) 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 +6.00 Beta 1 57 +)))|(% colspan="1" %)(% colspan="1" %) 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 +Changed result attribute location for **<get_attackstrength>** 75 +))) 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" %) 77 +((( 78 +//The 'result' attribute of get_attackstrength has been moved into the new <result> subnode and renamed to 'total'.// 79 +))) 33 33 |((( 34 34 Assets 35 35 )))|((( ... ... @@ -74,9 +74,9 @@ 74 74 )))|((( 75 75 Changed behaviour of **<angles>** in cutscenes 76 76 ))) 77 -|(% colspan="3" %)(% colspan="3" %) 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" %) 78 78 ((( 79 -The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees. 126 +//The yaw and pitch nodes in <angles> are now correctly interpreted as values in degrees.// 80 80 ))) 81 81 |(% colspan="3" %)(% colspan="3" %) 82 82 (((
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 -13 58620091 +138872528 - url
-
... ... @@ -1,1 +1,1 @@ 1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/13 5862009/Breaking Changes1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/138872528/Breaking Changes