third-party-mirrors/EDDN
1
0
Fork 0
mirror of https://github.com/EDCD/EDDN.git synced 2025-06-09 11:52:16 +03:00
Code Issues Actions Packages Projects Releases Wiki Activity

schemas/README: Give some hints about odyssey/horizons flags

Browse Source
This commit is contained in:
Athanasius 2022-01-20 11:32:08 +00:00
parent 8d5b03915b
commit 7819eff826
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
schemas/README-EDDN-schemas.md
View File

@ -245,6 +245,17 @@ Each `message` object must have, at bare minimum:
will be much more than this. Consult the will be much more than this. Consult the
[schemas and their documentation](./). [schemas and their documentation](./).
Where the schema allows for them, add the `horizons` and `odyssey`
keys with boolean values. `null` is not allowed in the values, so if
you cannot determine a value do not include that key at all. The best
source of these is the `LoadGame` event from journals. It's present
both in the PC local files and the CAPI journal data. If you're
composing a shipyard or outfitting message from CAPI data then it is
possible to synthesise the `horizons` flag. For now consult the function
`capi_is_horizons()` in
[EDMarketConnector:plugins/eddn.py](https://github.com/EDCD/EDMarketConnector/blob/stable/plugins/eddn.py)
for a method to achieve this.
Because the first versions of some schemas were defined when only the CAPI Because the first versions of some schemas were defined when only the CAPI
data was available, before Journal files existed, many of the key names chosen data was available, before Journal files existed, many of the key names chosen
in the schemas are based on the equivalent in CAPI data, not Journal events. in the schemas are based on the equivalent in CAPI data, not Journal events.