Skip to Content

Changes for page Breaking Changes

Last modified by Michael Baumgardt on 2026/04/17 12:03
From version 76.1
edited by stefan
on 2021/02/01 11:51
Change comment: added breaking change for GetFactionRelationStatus()
To version 80.1
edited by stefan
on 2021/03/05 01:24
Change comment: add note on gameplanchange-event change

Summary

Details

Page properties
Content
... ... @@ -37,6 +37,45 @@
37 37  UI core
38 38  )))|(% colspan="1" %)(% colspan="1" %)
39 39  (((
40 +4.00 Beta 10
41 +)))|(% colspan="1" %)(% colspan="1" %)
42 +(((
43 +Controlled ship can change without a **gameplanchange-event** occurring.
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 +//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).
51 +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.//
52 +)))|(% colspan="1" %)(% colspan="1" %)
53 +(((
54 +
55 +)))
56 +|(((
57 +Scripts
58 +)))|(((
59 +4.00 Beta 7
60 +)))|(((
61 +Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed
62 +)))|(((
63 +
64 +)))
65 +|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
66 +(((
67 +//Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects?
68 +New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits
69 +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//
70 +)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %)
71 +(((
72 +
73 +)))
74 +|(% colspan="1" %)(% colspan="1" %)
75 +(((
76 +UI core
77 +)))|(% colspan="1" %)(% colspan="1" %)
78 +(((
40 40  4.00 Beta 6
41 41  )))|(% colspan="1" %)(% colspan="1" %)
42 42  (((
... ... @@ -48,7 +48,7 @@
48 48  |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)
49 49  (((
50 50  //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.
51 -Factions with a relation rating between -20 and -10 will now report a relation status of 'neutral' (aka: 0) instead of 'hostile'/'enemy' (aka: 1).//
90 +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).//
52 52  
53 53  //If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead.
54 54  //
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -101548082
1 +101909300
url
... ... @@ -1,1 +1,1 @@
1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/101548082/Breaking Changes
1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/101909300/Breaking Changes