Changes for page Breaking Changes

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

From version 41.1
edited by stefan
on 2019/10/07 18:29
Change comment: added mission board case
To version 31.1
edited by stefan
on 2019/06/25 13:43
Change comment: added breaking change for GetMiniGameCursorPosition()

Summary

Details

Page properties
Content
... ... @@ -25,23 +25,19 @@
25 25  )))|=(((
26 26  Summary
27 27  )))
28 -|(% colspan="3" %)(% colspan="3" %)
29 -(((
30 -== 3.00 ==
31 -)))
32 32  |(% colspan="1" %)(% colspan="1" %)
33 33  (((
34 -Global
30 +UI core
35 35  )))|(% colspan="1" %)(% colspan="1" %)
36 36  (((
37 37  3.0 Beta 1
38 38  )))|(% colspan="1" %)(% colspan="1" %)
39 39  (((
40 -MissionBoard support dropped.
36 +**Lua: **GetMiniGameCursorPosition() removed
41 41  )))
42 42  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
43 43  (((
44 -//MissionBoards was a dummy asset type which was only used during early development and never meant to be shipped in the released version. If any mod tried to make use of this asset type, undefined behavior would occur. Therefore we cleaned things up in 3.0 Beta 1 including deprecating/removing any related UI/script function.//
40 +GetMiniGameCursorPosition() was a left over from the XR era and never supposed to be shipped with X4. The function practically always returned 0 and hence we don't expect the removal of this obsolete function causing any actual mod to break.
45 45  )))
46 46  |(% colspan="1" %)(% colspan="1" %)
47 47  (((
... ... @@ -51,11 +51,12 @@
51 51  3.0 Beta 1
52 52  )))|(% colspan="1" %)(% colspan="1" %)
53 53  (((
54 -Script action **<add_actor_to_room/> **attribute **'room'** renamed to **'object'**
50 +$ware.illegal updated
55 55  )))
56 56  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
57 57  (((
58 -//Due to engine changes, script action <add_actor_to_room/> has had the attribute 'room' changed to 'object', which is more accurate. Most likely requires a 'position' if a slot is not provided.//
54 +$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.
55 +\\It now returns true if $ware is illegal to any faction in the game.
59 59  )))
60 60  |(% colspan="1" %)(% colspan="1" %)
61 61  (((
... ... @@ -65,11 +65,13 @@
65 65  3.0 Beta 1
66 66  )))|(% colspan="1" %)(% colspan="1" %)
67 67  (((
68 -Script action **<set_doors_locked/>** attribute **'group'** changed
65 +'checkoperational' filter behaviour changed
69 69  )))
70 70  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
71 71  (((
72 -//The 'group' attribute of <set_doors_locked/> can no longer be a list. It must be a single tag value. Previously, a list containing one tag was accepted, which was redundant.//
69 +//Actions and conditions which use the 'checkoperational' filter now behave differently. Instead of changing how 'class' and 'exactclass' behave, checkoperational == true adds an additional filter for the components being of state operational, equivalent to state="componentstate.operational". This is implicitly enabled in action elements (e.g. <find_.../>) or condition elements (e.g. <count_...>), meaning that find_ship will only find operational ships. Using such actions/conditions with checkoperational="false" will include non-operational components such as wrecked and constructions. Existing uses may find that results now exclude non-operational components.//
70 +
71 +//Sub nodes such as match_child will have checkoperational default to false. Existing uses may find that results now include non-operational components.//
73 73  )))
74 74  |(% colspan="1" %)(% colspan="1" %)
75 75  (((
... ... @@ -79,116 +79,6 @@
79 79  3.0 Beta 1
80 80  )))|(% colspan="1" %)(% colspan="1" %)
81 81  (((
82 -Script conditions **<event_hack_*/>** and **<event_controlpanel_hack_*/>** removed
83 -)))
84 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
85 -(((
86 -//These events were never triggered, with the exception of <event_hack_started/> on the player entity for instant control panel hacks. Use <event_player_hacked_object> instead.//
87 -)))
88 -|(% colspan="1" %)(% colspan="1" %)
89 -(((
90 -Scripts
91 -)))|(% colspan="1" %)(% colspan="1" %)
92 -(((
93 -3.0 Beta 1
94 -)))|(% colspan="1" %)(% colspan="1" %)
95 -(((
96 -Script actions **<set_hack_target/>** and **<abort_hack/>** removed
97 -)))
98 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
99 -(((
100 -//These actions had no effect and were removed.//
101 -)))
102 -|(% colspan="1" %)(% colspan="1" %)
103 -(((
104 -Scripts
105 -)))|(% colspan="1" %)(% colspan="1" %)
106 -(((
107 -3.0 Beta 1
108 -)))|(% colspan="1" %)(% colspan="1" %)
109 -(((
110 -**<setup_conversation_minigame/>** script action removed
111 -)))
112 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
113 -(((
114 -//The script action was a leftover from the XR era and was never supported in X4 and couldn't be used in a meaningful way. It was therefore decided to better drop it altogether as it's not expected having been used by any mods.//
115 -)))
116 -|(% colspan="1" %)(% colspan="1" %)
117 -(((
118 -Scripts
119 -)))|(% colspan="1" %)(% colspan="1" %)
120 -(((
121 -3.0 Beta 1
122 -)))|(% colspan="1" %)(% colspan="1" %)
123 -(((
124 -<add_player_choice_*> **confidence** attribute removed
125 -)))
126 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
127 -(((
128 -//The default confidence of player options is another leftover from the XR era and had no effect in X4.//
129 -)))
130 -|(% colspan="1" %)(% colspan="1" %)
131 -(((
132 -Scripts
133 -)))|(% colspan="1" %)(% colspan="1" %)
134 -(((
135 -3.0 Beta 1
136 -)))|(% colspan="1" %)(% colspan="1" %)
137 -(((
138 -**<hack_via_control_panel/>** script action removed
139 -)))
140 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
141 -(((
142 -//Unused script action <hack_via_control_panel/> was removed.//
143 -)))
144 -|(% colspan="1" %)(% colspan="1" %)
145 -(((
146 -UI core
147 -)))|(% colspan="1" %)(% colspan="1" %)
148 -(((
149 -3.0 Beta 1
150 -)))|(% colspan="1" %)(% colspan="1" %)
151 -(((
152 -**Lua: **GetMiniGameCursorPosition() removed
153 -)))
154 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
155 -(((
156 -//GetMiniGameCursorPosition() was a left over from the XR era and never supposed to be shipped with X4. The function practically always returned 0 and hence we don't expect the removal of this obsolete function causing any actual mod to break.//
157 -)))
158 -|(((
159 -UI core
160 -)))|(((
161 -3.0 Beta 1
162 -)))|(((
163 -**FFI: **GetLocalizedInteractiveNotificationKey can return icon placeholders
164 -)))
165 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
166 -(((
167 -//In 3.0 Beta 1 we added support to display icons for keyboard bindings, if an icon is available for the specified keys. This results in GetLocalizedInteractiveNotificationKey() potentially returning a different text now if such an icon is assigned to the mapped key/button.//
168 -)))
169 -|(% colspan="1" %)(% colspan="1" %)
170 -(((
171 -Scripts
172 -)))|(% colspan="1" %)(% colspan="1" %)
173 -(((
174 -3.0 Beta 1
175 -)))|(% colspan="1" %)(% colspan="1" %)
176 -(((
177 -**$ware.illegal** updated
178 -)))
179 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
180 -(((
181 -//$ware.illegal used to return true if the specified ware has the 'illegal' tag which is no longer used.//
182 -//It now returns true if $ware is illegal to any faction in the game.//
183 -)))
184 -|(% colspan="1" %)(% colspan="1" %)
185 -(((
186 -Scripts
187 -)))|(% colspan="1" %)(% colspan="1" %)
188 -(((
189 -3.0 Beta 1
190 -)))|(% colspan="1" %)(% colspan="1" %)
191 -(((
192 192  MD script **RML_Flight_Along_Path** removed
193 193  )))
194 194  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
... ... @@ -197,53 +197,6 @@
197 197  )))
198 198  |(% colspan="1" %)(% colspan="1" %)
199 199  (((
200 -Scripts
201 -)))|(% colspan="1" %)(% colspan="1" %)
202 -(((
203 -3.0 Beta 1
204 -)))|(% colspan="1" %)(% colspan="1" %)
205 -(((
206 -parameters of **<event_venture_mission_completed/>** changed
207 -)))
208 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
209 -(((
210 -//old params: param = venture details, param2 = ships involved, param3 = duration//
211 -//new params: param = venture detail list: [mission name, mission type], param2 = list of ships involved, param3 = duration//
212 -)))
213 -|(% colspan="3" %)(% colspan="3" %)
214 -(((
215 -== 2.60 ==
216 -)))
217 -|(((
218 -Scripts
219 -)))|(((
220 -2.60 Beta 1
221 -)))|(((
222 -'**checkoperational**' filter behaviour changed
223 -)))
224 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
225 -(((
226 -//Actions and conditions which use the 'checkoperational' filter now behave differently. Instead of changing how 'class' and 'exactclass' behave, checkoperational == true adds an additional filter for the components being of state operational, equivalent to state="componentstate.operational". This is implicitly enabled in action elements (e.g. <find_.../>) or condition elements (e.g. <count_...>), meaning that find_ship will only find operational ships. Using such actions/conditions with checkoperational="false" will include non-operational components such as wrecked and constructions. Existing uses may find that results now exclude non-operational components.//
227 -
228 -//Sub nodes such as match_child will have checkoperational default to false. Existing uses may find that results now include non-operational components.//
229 -)))
230 -|(((
231 -Scripts
232 -)))|(((
233 -2.60 Beta 1
234 -)))|(((
235 -$container.**supplyresources** behavior changed
236 -)))
237 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
238 -(((
239 -//The script keyword $container.supplyresources now includes reserved wares.//
240 -)))
241 -|(% colspan="3" %)(% colspan="3" %)
242 -(((
243 -== 2.20 ==
244 -)))
245 -|(% colspan="1" %)(% colspan="1" %)
246 -(((
247 247  UI core
248 248  )))|(% colspan="1" %)(% colspan="1" %)
249 249  (((
... ... @@ -274,10 +274,6 @@
274 274  (((
275 275  //The underlying behaviour remains the same in that it involves the buildprocessor, not the buildmodule. The attribute name has simply been corrected.//
276 276  )))
277 -|(% colspan="3" %)(% colspan="3" %)
278 -(((
279 -== 2.00 ==
280 -)))
281 281  |(% colspan="1" %)(% colspan="1" %)
282 282  (((
283 283  Scripts
... ... @@ -424,10 +424,6 @@
424 424  (((
425 425  //Changed return value type to const char* to better identify failure reasons in Lua script.//
426 426  )))
427 -|(% colspan="3" %)(% colspan="3" %)
428 -(((
429 -== 1.50 ==
430 -)))
431 431  |(((
432 432  UI extensions
433 433  )))|(((
... ... @@ -493,10 +493,6 @@
493 493  (((
494 494  (% style="color: rgb(0,0,0);" %)//CancelConstruction() now returns if the cancellation was successful. //
495 495  )))
496 -|(% colspan="3" %)(% colspan="3" %)
497 -(((
498 -== 1.32 ==
499 -)))
500 500  |(((
501 501  UI extensions
502 502  )))|(((
... ... @@ -508,10 +508,6 @@
508 508  (((
509 509  //Instead of "nextdestname", use the properties "destination" or "destinationsector" to retrieve a destination component, then retrieve its "name" property.//
510 510  )))
511 -|(% colspan="3" %)(% colspan="3" %)
512 -(((
513 -== 1.20 ==
514 -)))
515 515  |(((
516 516  UI extensions
517 517  )))|(((
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -87916742
1 +83460733
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/87916742/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/83460733/Breaking Changes