diff --git a/schemas/approachsettlement-README.md b/schemas/approachsettlement-README.md index 61dad84..7845e21 100644 --- a/schemas/approachsettlement-README.md +++ b/schemas/approachsettlement-README.md @@ -58,33 +58,9 @@ Examples: Please read [horizons and odyssey flags](../docs/Developers.md#horizons-and-odyssey-flags) in the Developers' documentation. -#### gameversion -You **MUST** always add this field **to the header object**. - -1. If you are using Journal files directly then you **MUST** use the value - of the `gameversion` element from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `gameversion` is present in the `LoadGame` event, as in 4.0 clients, - use its value. - 3. If `LoadGame` does not have a `gameversion` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gameversion`, but - with the value `"CAPI"`. - -#### gamebuild -You **MUST** always add this field **to the header object**. - -1. If you are using Journal files directly then you **MUST** use the value - of the `build` value from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `build` is present in the `LoadGame` event, as in 4.0 clients, use - its value. - 3. If `LoadGame` does not have a `build` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gamebuild`, but - with the value `"CAPI"`. +#### gameversion and gamebuild +You **MUST** always set these as per [the relevant section](../docs/Developers.md#gameversions-and-gamebuild) +of the Developers' documentation. #### StarSystem diff --git a/schemas/codexentry-README.md b/schemas/codexentry-README.md index dee769d..3495bed 100644 --- a/schemas/codexentry-README.md +++ b/schemas/codexentry-README.md @@ -23,33 +23,9 @@ The primary data source for this schema is the ED Journal event `CodexEntry`. Please read [horizons and odyssey flags](../docs/Developers.md#horizons-and-odyssey-flags) in the Developers' documentation. -#### gameversion -You **MUST** always add this field **to the header object**. - -1. If you are using Journal files directly then you **MUST** use the value - of the `gameversion` element from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `gameversion` is present in the `LoadGame` event, as in 4.0 clients, - use its value. - 3. If `LoadGame` does not have a `gameversion` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gameversion`, but - with the value `"CAPI"`. - -#### gamebuild -You **MUST** always add this field **to the header object**. - -1. If you are using Journal files directly then you **MUST** use the value - of the `build` value from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `build` is present in the `LoadGame` event, as in 4.0 clients, use - its value. - 3. If `LoadGame` does not have a `build` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gamebuild`, but - with the value `"CAPI"`. +#### gameversion and gamebuild +You **MUST** always set these as per [the relevant section](../docs/Developers.md#gameversions-and-gamebuild) +of the Developers' documentation. #### StarPos You MUST add a `StarPos` array containing the system co-ordinates from the diff --git a/schemas/commodity-README.md b/schemas/commodity-README.md index 3ceb378..220363a 100644 --- a/schemas/commodity-README.md +++ b/schemas/commodity-README.md @@ -60,33 +60,9 @@ Remove not only the `Category_Localised` key:values, but also the Please read [horizons and odyssey flags](../docs/Developers.md#horizons-and-odyssey-flags) in the Developers' documentation. -#### gameversion -You **MUST** always add this field **to the header object**. - -1. If you are using Journal files directly then you **MUST** use the value - of the `gameversion` element from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `gameversion` is present in the `LoadGame` event, as in 4.0 clients, - use its value. - 3. If `LoadGame` does not have a `gameversion` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gameversion`, but - with the value `"CAPI"`. - -#### gamebuild -You **MUST** always add this field **to the header object**. - -1. If you are using Journal files directly then you **MUST** use the value - of the `build` value from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `build` is present in the `LoadGame` event, as in 4.0 clients, use - its value. - 3. If `LoadGame` does not have a `build` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gamebuild`, but - with the value `"CAPI"`. +#### gameversion and gamebuild +You **MUST** always set these as per [the relevant section](../docs/Developers.md#gameversions-and-gamebuild) +of the Developers' documentation. ### Using CAPI data It is *not* recommended to use CAPI data as the source as it's fraught with diff --git a/schemas/fcmaterials_capi-README.md b/schemas/fcmaterials_capi-README.md index a76f136..da2b040 100644 --- a/schemas/fcmaterials_capi-README.md +++ b/schemas/fcmaterials_capi-README.md @@ -57,6 +57,10 @@ You **MUST NOT** set them otherwise, as e.g. the player could be active in the game on another computer, using a different game mode and the CAPI data will be for that game mode. +#### gameversion and gamebuild +You **MUST** always set these as per [the relevant section](../docs/Developers.md#gameversions-and-gamebuild) +of the Developers' documentation. + ## Listeners The advice above for [Senders](#senders), combined with the actual Schema file *should* provide all the information you need to process these events. diff --git a/schemas/fcmaterials_journal-README.md b/schemas/fcmaterials_journal-README.md index fbcc04c..bf14d02 100644 --- a/schemas/fcmaterials_journal-README.md +++ b/schemas/fcmaterials_journal-README.md @@ -33,33 +33,9 @@ of any augmentations, as noted below. Please read [horizons and odyssey flags](../docs/Developers.md#horizons-and-odyssey-flags) in the Developers' documentation. -#### gameversion -You **MUST** always add this field **to the header object**. - -1. If you are using Journal files directly then you **MUST** use the value - of the `gameversion` element from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `gameversion` is present in the `LoadGame` event, as in 4.0 clients, - use its value. - 3. If `LoadGame` does not have a `gameversion` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gameversion`, but - with the value `"CAPI"`. - -#### gamebuild -You **MUST** always add this field **to the header object**. - -1. If you are using Journal files directly then you **MUST** use the value - of the `build` value from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `build` is present in the `LoadGame` event, as in 4.0 clients, use - its value. - 3. If `LoadGame` does not have a `build` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gamebuild`, but - with the value `"CAPI"`. +#### gameversion and gamebuild +You **MUST** always set these as per [the relevant section](../docs/Developers.md#gameversions-and-gamebuild) +of the Developers' documentation. ## Listeners The advice above for [Senders](#senders), combined with the actual Schema file diff --git a/schemas/fssallbodiesfound-README.md b/schemas/fssallbodiesfound-README.md index 35a883a..8c186c3 100644 --- a/schemas/fssallbodiesfound-README.md +++ b/schemas/fssallbodiesfound-README.md @@ -24,33 +24,9 @@ The primary data source for this schema is the ED Journal event Please read [horizons and odyssey flags](../docs/Developers.md#horizons-and-odyssey-flags) in the Developers' documentation. -#### gameversion -You **MUST** always add this field **to the header object**. - -1. If you are using Journal files directly then you **MUST** use the value - of the `gameversion` element from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `gameversion` is present in the `LoadGame` event, as in 4.0 clients, - use its value. - 3. If `LoadGame` does not have a `gameversion` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gameversion`, but - with the value `"CAPI"`. - -#### gamebuild -You **MUST** always add this field **to the header object**. - -1. If you are using Journal files directly then you **MUST** use the value - of the `build` value from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `build` is present in the `LoadGame` event, as in 4.0 clients, use - its value. - 3. If `LoadGame` does not have a `build` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gamebuild`, but - with the value `"CAPI"`. +#### gameversion and gamebuild +You **MUST** always set these as per [the relevant section](../docs/Developers.md#gameversions-and-gamebuild) +of the Developers' documentation. #### StarPos You MUST add a `StarPos` array containing the system co-ordinates from the diff --git a/schemas/fssbodysignals-README.md b/schemas/fssbodysignals-README.md index b2110d9..7582514 100644 --- a/schemas/fssbodysignals-README.md +++ b/schemas/fssbodysignals-README.md @@ -24,33 +24,9 @@ The primary data source for this schema is the ED Journal event Please read [horizons and odyssey flags](../docs/Developers.md#horizons-and-odyssey-flags) in the Developers' documentation. -#### gameversion -You **MUST** always add this field **to the header object**. - -1. If you are using Journal files directly then you **MUST** use the value - of the `gameversion` element from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `gameversion` is present in the `LoadGame` event, as in 4.0 clients, - use its value. - 3. If `LoadGame` does not have a `gameversion` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gameversion`, but - with the value `"CAPI"`. - -#### gamebuild -You **MUST** always add this field **to the header object**. - -1. If you are using Journal files directly then you **MUST** use the value - of the `build` value from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `build` is present in the `LoadGame` event, as in 4.0 clients, use - its value. - 3. If `LoadGame` does not have a `build` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gamebuild`, but - with the value `"CAPI"`. +#### gameversion and gamebuild +You **MUST** always set these as per [the relevant section](../docs/Developers.md#gameversions-and-gamebuild) +of the Developers' documentation. #### StarSystem You MUST add a `StarSystem` string containing the name of the system from the diff --git a/schemas/fssdiscoveryscan-README.md b/schemas/fssdiscoveryscan-README.md index 014d44d..8e3e1f9 100644 --- a/schemas/fssdiscoveryscan-README.md +++ b/schemas/fssdiscoveryscan-README.md @@ -24,33 +24,9 @@ The primary data source for this schema is the ED Journal event Please read [horizons and odyssey flags](../docs/Developers.md#horizons-and-odyssey-flags) in the Developers' documentation. -#### gameversion -You **MUST** always add this field **to the header object**. - -1. If you are using Journal files directly then you **MUST** use the value - of the `gameversion` element from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `gameversion` is present in the `LoadGame` event, as in 4.0 clients, - use its value. - 3. If `LoadGame` does not have a `gameversion` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gameversion`, but - with the value `"CAPI"`. - -#### gamebuild -You **MUST** always add this field **to the header object**. - -1. If you are using Journal files directly then you **MUST** use the value - of the `build` value from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `build` is present in the `LoadGame` event, as in 4.0 clients, use - its value. - 3. If `LoadGame` does not have a `build` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gamebuild`, but - with the value `"CAPI"`. +#### gameversion and gamebuild +You **MUST** always set these as per [the relevant section](../docs/Developers.md#gameversions-and-gamebuild) +of the Developers' documentation. #### StarPos You MUST add a `StarPos` array containing the system co-ordinates from the diff --git a/schemas/fsssignaldiscovered-README.md b/schemas/fsssignaldiscovered-README.md index 6aab328..6889dbc 100644 --- a/schemas/fsssignaldiscovered-README.md +++ b/schemas/fsssignaldiscovered-README.md @@ -87,33 +87,9 @@ You SHOULD add this key/value pair, using the value from the `LoadGame` event. #### odyssey flag You SHOULD add this key/value pair, using the value from the `LoadGame` event. -#### gameversion -You **MUST** always add this field **to the header object**. - -1. If you are using Journal files directly then you **MUST** use the value - of the `gameversion` element from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `gameversion` is present in the `LoadGame` event, as in 4.0 clients, - use its value. - 3. If `LoadGame` does not have a `gameversion` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gameversion`, but - with the value `"CAPI"`. - -#### gamebuild -You **MUST** always add this field **to the header object**. - -1. If you are using Journal files directly then you **MUST** use the value - of the `build` value from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `build` is present in the `LoadGame` event, as in 4.0 clients, use - its value. - 3. If `LoadGame` does not have a `build` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gamebuild`, but - with the value `"CAPI"`. +#### gameversion and gamebuild +You **MUST** always set these as per [the relevant section](../docs/Developers.md#gameversions-and-gamebuild) +of the Developers' documentation. #### StarSystem You **MUST** add a `StarSystem` string containing the system name from the last diff --git a/schemas/journal-README.md b/schemas/journal-README.md index a28d17b..a59865b 100644 --- a/schemas/journal-README.md +++ b/schemas/journal-README.md @@ -65,33 +65,9 @@ The following keys+values should be removed from `Location` event data: - `SquadronFaction` from within the list of `Factions`. ### Augmentations -#### gameversion -You **MUST** always add this field **to the header object**. - -1. If you are using Journal files directly then you **MUST** use the value - of the `gameversion` element from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `gameversion` is present in the `LoadGame` event, as in 4.0 clients, - use its value. - 3. If `LoadGame` does not have a `gameversion` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gameversion`, but - with the value `"CAPI"`. - -#### gamebuild -You **MUST** always add this field **to the header object**. - -1. If you are using Journal files directly then you **MUST** use the value - of the `build` value from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `build` is present in the `LoadGame` event, as in 4.0 clients, use - its value. - 3. If `LoadGame` does not have a `build` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gamebuild`, but - with the value `"CAPI"`. +#### gameversion and gamebuild +You **MUST** always set these as per [the relevant section](../docs/Developers.md#gameversions-and-gamebuild) +of the Developers' documentation. #### horizons flag You **MUST** add this key/value pair, using the value from the `LoadGame` event. diff --git a/schemas/navbeaconscan-README.md b/schemas/navbeaconscan-README.md index 75818eb..de14f12 100644 --- a/schemas/navbeaconscan-README.md +++ b/schemas/navbeaconscan-README.md @@ -24,33 +24,9 @@ The primary data source for this schema is the ED Journal event Please read [horizons and odyssey flags](../docs/Developers.md#horizons-and-odyssey-flags) in the Developers' documentation. -#### gameversion -You **MUST** always add this field **to the header object**. - -1. If you are using Journal files directly then you **MUST** use the value - of the `gameversion` element from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `gameversion` is present in the `LoadGame` event, as in 4.0 clients, - use its value. - 3. If `LoadGame` does not have a `gameversion` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gameversion`, but - with the value `"CAPI"`. - -#### gamebuild -You **MUST** always add this field **to the header object**. - -1. If you are using Journal files directly then you **MUST** use the value - of the `build` value from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `build` is present in the `LoadGame` event, as in 4.0 clients, use - its value. - 3. If `LoadGame` does not have a `build` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gamebuild`, but - with the value `"CAPI"`. +#### gameversion and gamebuild +You **MUST** always set these as per [the relevant section](../docs/Developers.md#gameversions-and-gamebuild) +of the Developers' documentation. #### StarSystem You MUST add a `StarSystem` key/value pair representing the name of the diff --git a/schemas/navroute-README.md b/schemas/navroute-README.md index 7315e39..5358df8 100644 --- a/schemas/navroute-README.md +++ b/schemas/navroute-README.md @@ -31,30 +31,7 @@ separate file. Please read [horizons and odyssey flags](../docs/Developers.md#horizons-and-odyssey-flags) in the Developers' documentation. -#### gameversion -You **MUST** always add this field **to the header object**. +#### gameversion and gamebuild +You **MUST** always set these as per [the relevant section](../docs/Developers.md#gameversions-and-gamebuild) +of the Developers' documentation. -1. If you are using Journal files directly then you **MUST** use the value - of the `gameversion` element from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `gameversion` is present in the `LoadGame` event, as in 4.0 clients, - use its value. - 3. If `LoadGame` does not have a `gameversion` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gameversion`, but - with the value `"CAPI"`. - -#### gamebuild -You **MUST** always add this field **to the header object**. - -1. If you are using Journal files directly then you **MUST** use the value - of the `build` value from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `build` is present in the `LoadGame` event, as in 4.0 clients, use - its value. - 3. If `LoadGame` does not have a `build` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gamebuild`, but - with the value `"CAPI"`. diff --git a/schemas/outfitting-README.md b/schemas/outfitting-README.md index 6440bff..f9a405c 100644 --- a/schemas/outfitting-README.md +++ b/schemas/outfitting-README.md @@ -54,30 +54,7 @@ station. Namely: Please read [horizons and odyssey flags](../docs/Developers.md#horizons-and-odyssey-flags) in the Developers' documentation. -#### gameversion -You **MUST** always add this field **to the header object**. +#### gameversion and gamebuild +You **MUST** always set these as per [the relevant section](../docs/Developers.md#gameversions-and-gamebuild) +of the Developers' documentation. -1. If you are using Journal files directly then you **MUST** use the value - of the `gameversion` element from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `gameversion` is present in the `LoadGame` event, as in 4.0 clients, - use its value. - 3. If `LoadGame` does not have a `gameversion` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gameversion`, but - with the value `"CAPI"`. - -#### gamebuild -You **MUST** always add this field **to the header object**. - -1. If you are using Journal files directly then you **MUST** use the value - of the `build` value from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `build` is present in the `LoadGame` event, as in 4.0 clients, use - its value. - 3. If `LoadGame` does not have a `build` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gamebuild`, but - with the value `"CAPI"`. diff --git a/schemas/scanbarycentre-README.md b/schemas/scanbarycentre-README.md index 9cea06e..11353bb 100644 --- a/schemas/scanbarycentre-README.md +++ b/schemas/scanbarycentre-README.md @@ -27,33 +27,9 @@ senders SHOULD include any defined in the schema if it's in the source data. Please read [horizons and odyssey flags](../docs/Developers.md#horizons-and-odyssey-flags) in the Developers' documentation. -#### gameversion -You **MUST** always add this field **to the header object**. - -1. If you are using Journal files directly then you **MUST** use the value - of the `gameversion` element from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `gameversion` is present in the `LoadGame` event, as in 4.0 clients, - use its value. - 3. If `LoadGame` does not have a `gameversion` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gameversion`, but - with the value `"CAPI"`. - -#### gamebuild -You **MUST** always add this field **to the header object**. - -1. If you are using Journal files directly then you **MUST** use the value - of the `build` value from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `build` is present in the `LoadGame` event, as in 4.0 clients, use - its value. - 3. If `LoadGame` does not have a `build` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gamebuild`, but - with the value `"CAPI"`. +#### gameversion and gamebuild +You **MUST** always set these as per [the relevant section](../docs/Developers.md#gameversions-and-gamebuild) +of the Developers' documentation. #### StarPos You MUST add a `StarPos` array containing the system co-ordinates from the diff --git a/schemas/shipyard-README.md b/schemas/shipyard-README.md index 8492651..0b3ac58 100644 --- a/schemas/shipyard-README.md +++ b/schemas/shipyard-README.md @@ -41,30 +41,7 @@ value is what the name would have been in the source Journal data. Please read [horizons and odyssey flags](../docs/Developers.md#horizons-and-odyssey-flags) in the Developers' documentation. -#### gameversion -You **MUST** always add this field **to the header object**. +#### gameversion and gamebuild +You **MUST** always set these as per [the relevant section](../docs/Developers.md#gameversions-and-gamebuild) +of the Developers' documentation. -1. If you are using Journal files directly then you **MUST** use the value - of the `gameversion` element from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `gameversion` is present in the `LoadGame` event, as in 4.0 clients, - use its value. - 3. If `LoadGame` does not have a `gameversion` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gameversion`, but - with the value `"CAPI"`. - -#### gamebuild -You **MUST** always add this field **to the header object**. - -1. If you are using Journal files directly then you **MUST** use the value - of the `build` value from the`Fileheader` event. -2. If you are using the CAPI `/journal` endpoint to retrieve and process - Journal events then: - 1. You will not have `Fileheader` available. - 2. If `build` is present in the `LoadGame` event, as in 4.0 clients, use - its value. - 3. If `LoadGame` does not have a `build` element, as with 3.8 Horizons - clients (up to at least `3.8.0.407`), you **MUST** set `gamebuild`, but - with the value `"CAPI"`.