Changes for page Breaking Changes
Last modified by Michael Baumgardt on 2026/04/17 12:03
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -xwiki:XWiki.f lorian1 +xwiki:XWiki.stefan - Content
-
... ... @@ -30,133 +30,6 @@ 30 30 ))) 31 31 |(% colspan="4" %)(% colspan="4" %) 32 32 ((( 33 -== 4.10 == 34 -))) 35 -|(% colspan="1" %)(% colspan="1" %) 36 -((( 37 -UI extensions 38 -)))|(% colspan="1" %)(% colspan="1" %) 39 -((( 40 -4.10 Beta 6 41 -)))|(% colspan="1" %)(% colspan="1" %) 42 -((( 43 -**FFI**: CustomGameStartPlayerProperty2 changed 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 -//This struct was added in 4.10 Beta 2 and an additional member count was added in Beta 6.// 51 -)))|(% colspan="1" %)(% colspan="1" %) 52 -((( 53 - 54 -))) 55 -|(% colspan="1" %)(% colspan="1" %) 56 -((( 57 -Parameters 58 -)))|(% colspan="1" %)(% colspan="1" %) 59 -((( 60 -4.10 Beta 3 61 -)))|(% colspan="1" %)(% colspan="1" %) 62 -((( 63 -Renamed **<stationinfobox>** to **<infobox>** 64 -)))|(% colspan="1" %)(% colspan="1" %) 65 -((( 66 - 67 -))) 68 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 69 -((( 70 -//Info box parameters are now shared across stations and ships. The node has a more generic name to reflect that.// 71 -)))|(% colspan="1" %)(% colspan="1" %) 72 -((( 73 - 74 -))) 75 -|(% colspan="1" %)(% colspan="1" %) 76 -((( 77 -UI extensions 78 -)))|(% colspan="1" %)(% colspan="1" %) 79 -((( 80 -4.10 Beta 2 81 -)))|(% colspan="1" %)(% colspan="1" %) 82 -((( 83 -**FFI**: SetMacroMapPlayerSectorOffset() deprecated 84 -)))|(% colspan="1" %)(% colspan="1" %) 85 -((( 86 - 87 -))) 88 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 89 -((( 90 -//The functionality represented by SetMacroMapPlayerSectorOffset() has been removed and the function was therefore stubbed. Setting the gamestart properties "sector" and "offset" will affect the universe macro map instead directly.// 91 -)))|(% colspan="1" %)(% colspan="1" %) 92 -((( 93 - 94 -))) 95 -|((( 96 -UI extensions 97 -)))|((( 98 -4.10 Beta 2 99 -)))|((( 100 -**FFI**: (% style="color: rgb(0,0,0);" %)FilterComponentForMapMode(%%)() and (% style="color: rgb(0,0,0);" %)SetMapObjectFilter() 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 -//These functions were added in 4.10 Beta 1 and an additional boolean parameter allowentitydeliverymissionobject was added in Beta 2.// 108 -)))|(% colspan="1" %)(% colspan="1" %) 109 -((( 110 - 111 -))) 112 -|((( 113 -Scripts 114 -)))|((( 115 -4.10 Beta 1 116 -)))|((( 117 -People related attributes of mission** <delivery> **node moved 118 -)))|((( 119 - 120 -))) 121 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 122 -((( 123 -//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.// 124 -))) 125 -|(% colspan="1" %)(% colspan="1" %) 126 -((( 127 -Scripts 128 -)))|(% colspan="1" %)(% colspan="1" %) 129 -((( 130 -4.10 Beta 1 131 -)))|(% colspan="1" %)(% colspan="1" %) 132 -((( 133 -**$destructible.productions** replaced with $defensible.productions 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 -//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.// 141 -)))|(% colspan="1" %)(% colspan="1" %) 142 -((( 143 - 144 -))) 145 -|((( 146 -Scripts 147 -)))|((( 148 -4.10 Beta 1 149 -)))|((( 150 -Removed script property **$object.spawnsourceseed** 151 -)))|((( 152 - 153 -))) 154 -|(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="4" data-highlight-colour="grey" %) 155 -((( 156 -//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.// 157 -))) 158 -|(% colspan="4" %)(% colspan="4" %) 159 -((( 160 160 == 4.00 == 161 161 ))) 162 162 |(% colspan="1" %)(% colspan="1" %) ... ... @@ -164,74 +164,10 @@ 164 164 UI core 165 165 )))|(% colspan="1" %)(% colspan="1" %) 166 166 ((( 167 -4.00 Beta 10 168 -)))|(% colspan="1" %)(% colspan="1" %) 169 -((( 170 -Controlled ship can change without a **gameplanchange-event** occurring. 171 -)))|(% colspan="1" %)(% colspan="1" %) 172 -((( 173 - 174 -))) 175 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 176 -((( 177 -//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). 178 -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. 179 -// 180 -)))|(% colspan="1" %)(% colspan="1" %) 181 -((( 182 - 183 -))) 184 -|((( 185 -Scripts 186 -)))|((( 187 -4.00 Beta 7 188 -)))|((( 189 -Parameters of **<event_terraforming_project_succeeded>** and **<event_terraforming_project_failed>** changed 190 -)))|((( 191 - 192 -))) 193 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 194 -((( 195 -//Old params: param = project ID, param2 = were there positive side-effects?, param3 = were there negative side-effects? 196 -New params: param = project ID, param2 = [were there positive side-effects?, were there negative side-effects?], param3 = payout in Credits 197 -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// 198 -)))|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %) 199 -((( 200 - 201 -))) 202 -|(% colspan="1" %)(% colspan="1" %) 203 -((( 204 -UI core 205 -)))|(% colspan="1" %)(% colspan="1" %) 206 -((( 207 -4.00 Beta 6 208 -)))|(% colspan="1" %)(% colspan="1" %) 209 -((( 210 -**FFI:** GetFactionRelationStatus() handling for faction relation range [-20,-10] changed 211 -)))|(% colspan="1" %)(% colspan="1" %) 212 -((( 213 - 214 -))) 215 -|(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 216 -((( 217 -//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. 218 -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).// 219 - 220 -//If you rely on a handling where these factions are treated like enemies, please use the new GetFactionRelationStatus2() function instead. 221 -// 222 -)))|(% colspan="1" %)(% colspan="1" %) 223 -((( 224 - 225 -))) 226 -|(% colspan="1" %)(% colspan="1" %) 227 -((( 228 -UI core 229 -)))|(% colspan="1" %)(% colspan="1" %) 230 -((( 231 231 4.00 Beta 5 232 232 )))|(% colspan="1" %)(% colspan="1" %) 233 233 ((( 234 -**FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in relation range [-25 ,-10] changed43 +**FFI:** GetRelationStatus()/GetRelationStatus2() handling for objects in ranges relation range [-25 - -10] changed 235 235 )))|(% colspan="1" %)(% colspan="1" %) 236 236 ((( 237 237 ... ... @@ -238,9 +238,9 @@ 238 238 ))) 239 239 |(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %)(% class="highlight-grey" colspan="3" data-highlight-colour="grey" %) 240 240 ((( 241 -//4.00 Beta 5// //introduces a new ' hostile' relation status and thegamenow distinguishes between hostile and enemyrelation states. Objectsnot yet 'hostile'withthe player are now visualized differentlyandtherefore distinguishablefrom realhostileones.Because of that, several related changesweremade forthese objects to bringthem morein linewith how 'neutral' objectsbehave (f.e.no automaticattackingof these objects by theplayer property anymore,notargetselectionwhentargeting the closest enemy, etc.).To reflectthis, theseobjects arenowreturning1(neutral)astherelationstatus by theGetRelationStatus()/GetRelationStatus2() functions.//242 - 243 - //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 yethostile) here with following relations having been shifted up).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 objects are now visualized and therefore are 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() //FFI function which returns the new range for these objects: 1 (meaning 'adversary' here with following relations having been shifted up). 244 244 )))|(% colspan="1" %)(% colspan="1" %) 245 245 ((( 246 246
- Confluence.Code.ConfluencePageClass[0]
-
- id
-
... ... @@ -1,1 +1,1 @@ 1 -10 49238401 +100860793 - url
-
... ... @@ -1,1 +1,1 @@ 1 -https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/10 4923840/Breaking Changes1 +https://www.egosoft.com:8444/confluence/wiki/spaces/X4WIKI/pages/100860793/Breaking Changes