schemas/template: Update template for StarSystem default & cross-checks

* New schemas will need to use `StarSystem`, not `SystemName` or `System`, if
  applicable, so have that example here.
* Any such augmentations need the cross-check mandating.
This commit is contained in:
Athanasius 2022-05-31 13:21:49 +01:00
parent c3149f06bc
commit 85031ba2b0
No known key found for this signature in database
GPG Key ID: AE3E527847057C7D

View File

@ -106,10 +106,20 @@ 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.
#### StarSystem
You MUST add a `StarSystem` string containing the name of the system from the
last `FSDJump`, `CarrierJump`, or `Location` event.
**You MUST apply a location cross-check, as per
[Other data augmentations](../docs/Developers.md#other-data-augmentations).**
#### StarPos
You MUST add a `StarPos` array containing the system co-ordinates from the
last `FSDJump`, `CarrierJump`, or `Location` event.
**You MUST apply a location cross-check, as per
[Other data augmentations](../docs/Developers.md#other-data-augmentations).**
## Listeners
The advice above for [Senders](#senders), combined with the actual Schema file
*should* provide all the information you need to process these events.