Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 74.1
edited by stefan
on 2021/01/14 02:41
Change comment: There is no comment for this version
To version 87.1
edited by owen
on 2021/06/10 13:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -xwiki:XWiki.stefan
1 +xwiki:XWiki.owen
Content
... ... @@ -30,6 +30,56 @@
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 +People related attributes of mission** <delivery> **node moved
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 <delivery> node of <create_mission> and <update_mission> has been changed to support a new <wares> subnode. The people related attributes: 'people' and 'skills' have been moved from the <delivery> node itself to a <people> subnode.//
47 +)))
48 +|(% colspan="1" %)(% colspan="1" %)
49 +(((
50 +Scripts
51 +)))|(% colspan="1" %)(% colspan="1" %)
52 +(((
53 +4.10 Beta 1
54 +)))|(% colspan="1" %)(% colspan="1" %)
55 +(((
56 +**$destructible.productions** replaced with $defensible.productions
57 +)))|(% colspan="1" %)(% colspan="1" %)
58 +(((
59 +
60 +)))
61 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
62 +(((
63 +//The $destructible.productions script property was removed and reimplemented as $defensible.productions meaning some old uses may no longer work unless the destructible is also a defensible. The old implementation functioned by finding the containing object of the destructible (including itself) to query for the production modules.//
64 +)))|(% colspan="1" %)(% colspan="1" %)
65 +(((
66 +
67 +)))
68 +|(((
69 +Scripts
70 +)))|(((
71 +4.10 Beta 1
72 +)))|(((
73 +Removed script property **$object.spawnsourceseed**
74 +)))|(((
75 +
76 +)))
77 +|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
78 +(((
79 +//The spawnsource seed is no longer directly accessible 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 result in a value that differs between objects of the same macro, meaning it can now reliably be used for player property or job ships.//
80 +)))
81 +|(% colspan="4" %)(% colspan="4" %)
82 +(((
33 33  == 4.00 ==
34 34  )))
35 35  |(% colspan="1" %)(% colspan="1" %)
... ... @@ -37,6 +37,70 @@
37 37  UI core
38 38  )))|(% colspan="1" %)(% colspan="1" %)
39 39  (((
90 +4.00 Beta 10
91 +)))|(% colspan="1" %)(% colspan="1" %)
92 +(((
93 +Controlled ship can change without a **gameplanchange-event** occurring.
94 +)))|(% colspan="1" %)(% colspan="1" %)
95 +(((
96 +
97 +)))
98 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
99 +(((
100 +//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).
101 +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.
102 +//
103 +)))|(% colspan="1" %)(% colspan="1" %)
104 +(((
105 +
106 +)))
107 +|(((
108 +Scripts
109 +)))|(((
110 +4.00 Beta 7
111 +)))|(((
112 +Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed
113 +)))|(((
114 +
115 +)))
116 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
117 +(((
118 +//Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects?
119 +New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits
120 +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//
121 +)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %)
122 +(((
123 +
124 +)))
125 +|(% colspan="1" %)(% colspan="1" %)
126 +(((
127 +UI core
128 +)))|(% colspan="1" %)(% colspan="1" %)
129 +(((
130 +4.00 Beta 6
131 +)))|(% colspan="1" %)(% colspan="1" %)
132 +(((
133 +**FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed
134 +)))|(% colspan="1" %)(% colspan="1" %)
135 +(((
136 +
137 +)))
138 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
139 +(((
140 +//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.
141 +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).//
142 +
143 +//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.
144 +//
145 +)))|(% colspan="1" %)(% colspan="1" %)
146 +(((
147 +
148 +)))
149 +|(% colspan="1" %)(% colspan="1" %)
150 +(((
151 +UI core
152 +)))|(% colspan="1" %)(% colspan="1" %)
153 +(((
40 40  4.00 Beta 5
41 41  )))|(% colspan="1" %)(% colspan="1" %)
42 42  (((
... ... @@ -47,9 +47,9 @@
47 47  )))
48 48  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
49 49  (((
50 -//4.00 Beta 5// //introduces a new 'adversary' relation state. Previously, objects within that relation range were categorized as 'enemy' and GetRelationStatus()/GetRelationStatus2() therefore returned 0 (enemy) for these objects.
51 -Since these 'adversary' objects are now visualized and therefore distinguishable from enemies, several related changes were made for these objects to bring them more in line with how 'neutral' objects are handled (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.
52 -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 'adversary' here with following relations having been shifted up).
164 +//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.//
165 +
166 +//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).
53 53  )))|(% colspan="1" %)(% colspan="1" %)
54 54  (((
55 55  
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -101548076
1 +103612552
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/101548076/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/103612552/Breaking Changes