Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 84.1
edited by owen
on 2021/04/30 12:54
Change comment: There is no comment for this version
To version 78.1
edited by matthias
on 2021/02/05 17:00
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.matthias
Content
... ... @@ -30,43 +30,6 @@
30 30  )))
31 31  |(% colspan="4" %)(% colspan="4" %)
32 32  (((
33 -== 4.10 ==
34 -)))
35 -|(% colspan="1" %)(% colspan="1" %)
36 -(((
37 -Scripts
38 -)))|(% colspan="1" %)(% colspan="1" %)
39 -(((
40 -4.10 Beta 1
41 -)))|(% colspan="1" %)(% colspan="1" %)
42 -(((
43 -$destructible.productions replaced with $defensible.productions
44 -)))|(% colspan="1" %)(% colspan="1" %)
45 -(((
46 -
47 -)))
48 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
49 -(((
50 -//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.//
51 -)))|(% colspan="1" %)(% colspan="1" %)
52 -(((
53 -
54 -)))
55 -|(((
56 -Scripts
57 -)))|(((
58 -4.10 Beta 1
59 -)))|(((
60 -Removed script property $object.spawnsourceseed
61 -)))|(((
62 -
63 -)))
64 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)
65 -(((
66 -//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.//
67 -)))
68 -|(% colspan="4" %)(% colspan="4" %)
69 -(((
70 70  == 4.00 ==
71 71  )))
72 72  |(% colspan="1" %)(% colspan="1" %)
... ... @@ -74,46 +74,6 @@
74 74  UI core
75 75  )))|(% colspan="1" %)(% colspan="1" %)
76 76  (((
77 -4.00 Beta 10
78 -)))|(% colspan="1" %)(% colspan="1" %)
79 -(((
80 -Controlled ship can change without a **gameplanchange-event** occurring.
81 -)))|(% colspan="1" %)(% colspan="1" %)
82 -(((
83 -
84 -)))
85 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
86 -(((
87 -//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).
88 -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.
89 -//
90 -)))|(% colspan="1" %)(% colspan="1" %)
91 -(((
92 -
93 -)))
94 -|(((
95 -Scripts
96 -)))|(((
97 -4.00 Beta 7
98 -)))|(((
99 -Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed
100 -)))|(((
101 -
102 -)))
103 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
104 -(((
105 -//Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects?
106 -New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits
107 -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//
108 -)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %)
109 -(((
110 -
111 -)))
112 -|(% colspan="1" %)(% colspan="1" %)
113 -(((
114 -UI core
115 -)))|(% colspan="1" %)(% colspan="1" %)
116 -(((
117 117  4.00 Beta 6
118 118  )))|(% colspan="1" %)(% colspan="1" %)
119 119  (((
... ... @@ -184,6 +184,24 @@
184 184  (((
185 185  
186 186  )))
110 +|(((
111 +Scripts
112 +)))|(((
113 +4.00 Beta 7
114 +)))|(((
115 +Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed
116 +)))|(((
117 +
118 +)))
119 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
120 +(((
121 +//Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects?
122 +New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits
123 +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//
124 +)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %)
125 +(((
126 +
127 +)))
187 187  |(% colspan="4" %)(% colspan="4" %)
188 188  (((
189 189  == 3.30 ==
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -102924788
1 +101548222
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/102924788/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/101548222/Breaking Changes