Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 69.1
edited by owen
on 2020/10/19 17:55
Change comment: added change of location for requiresconstructionvessel recycling parameter
To version 82.1
edited by owen
on 2021/04/26 13:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -30,9 +30,112 @@
30 30  )))
31 31  |(% colspan="4" %)(% colspan="4" %)
32 32  (((
33 +== 4.10 ==
34 +)))
35 +|(((
36 +Scripts
37 +)))|(((
38 +4.10 Beta 1
39 +)))|(((
40 +Removed script property $object.spawnsourceseed
41 +)))|(((
42 +
43 +)))
44 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
45 +(((
46 +The spawnsource seed is no longer directly accessable 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 return a result that differs between objects of the same macro, meaning it can now reliably be used for player property or job ships.
47 +)))
48 +|(% colspan="4" %)(% colspan="4" %)
49 +(((
33 33  == 4.00 ==
34 34  )))
52 +|(% colspan="1" %)(% colspan="1" %)
53 +(((
54 +UI core
55 +)))|(% colspan="1" %)(% colspan="1" %)
56 +(((
57 +4.00 Beta 10
58 +)))|(% colspan="1" %)(% colspan="1" %)
59 +(((
60 +Controlled ship can change without a **gameplanchange-event** occurring.
61 +)))|(% colspan="1" %)(% colspan="1" %)
62 +(((
63 +
64 +)))
65 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
66 +(((
67 +//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).
68 +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.
69 +//
70 +)))|(% colspan="1" %)(% colspan="1" %)
71 +(((
72 +
73 +)))
35 35  |(((
75 +Scripts
76 +)))|(((
77 +4.00 Beta 7
78 +)))|(((
79 +Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed
80 +)))|(((
81 +
82 +)))
83 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
84 +(((
85 +//Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects?
86 +New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits
87 +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//
88 +)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %)
89 +(((
90 +
91 +)))
92 +|(% colspan="1" %)(% colspan="1" %)
93 +(((
94 +UI core
95 +)))|(% colspan="1" %)(% colspan="1" %)
96 +(((
97 +4.00 Beta 6
98 +)))|(% colspan="1" %)(% colspan="1" %)
99 +(((
100 +**FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed
101 +)))|(% colspan="1" %)(% colspan="1" %)
102 +(((
103 +
104 +)))
105 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
106 +(((
107 +//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.
108 +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).//
109 +
110 +//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.
111 +//
112 +)))|(% colspan="1" %)(% colspan="1" %)
113 +(((
114 +
115 +)))
116 +|(% colspan="1" %)(% colspan="1" %)
117 +(((
118 +UI core
119 +)))|(% colspan="1" %)(% colspan="1" %)
120 +(((
121 +4.00 Beta 5
122 +)))|(% colspan="1" %)(% colspan="1" %)
123 +(((
124 +**FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25,-10] changed
125 +)))|(% colspan="1" %)(% colspan="1" %)
126 +(((
127 +
128 +)))
129 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
130 +(((
131 +//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.//
132 +
133 +//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).
134 +)))|(% colspan="1" %)(% colspan="1" %)
135 +(((
136 +
137 +)))
138 +|(((
36 36  Parameters
37 37  )))|(((
38 38  4.00 Beta 1
... ... @@ -45,6 +45,22 @@
45 45  (((
46 46  //The 'requiresconstructionvessel' attribute has been moved from the 'recycling' node itself, to the new 'station' subnode.//
47 47  )))
151 +|(((
152 +Scripts
153 +)))|(((
154 +4.00 Beta 1
155 +)))|(((
156 +Changed behaviour of **gatedistance** script property
157 +)))|(((
158 +
159 +)))
160 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
161 +(((
162 +//The 'gatedistance' script property now minimizes the number of gate jumps instead of counting the number gate jumps in the fastest route.//
163 +)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %)
164 +(((
165 +
166 +)))
48 48  |(% colspan="4" %)(% colspan="4" %)
49 49  (((
50 50  == 3.30 ==
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -100040871
1 +102924739
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/100040871/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/102924739/Breaking Changes