You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The NavRoute.json file, written when a journal NavRoute event occurs, contains:
System Name
System co-ordinates
SystemAddress (id64)
Main star's class
for each step in the plotted route. It would be simple to take the route array out of the file and insert it into the journal event before sending that over EDDN. Then any listeners could choose to utilise it to potentially gain co-ordinates and systemaddress for extra systems.
As the provided data in the route array is what is currently required as the bare minimum in a journal schema message this shouldn't actually require any changes to the schema other than adding the event type to the allowed list. This issue mostly for reference and any further discussion. It would require a small update to the documentation to explicitly state that the route array needs adding from the file.
The text was updated successfully, but these errors were encountered:
The
NavRoute.json
file, written when a journalNavRoute
event occurs, contains:for each step in the plotted route. It would be simple to take the
route
array out of the file and insert it into the journal event before sending that over EDDN. Then any listeners could choose to utilise it to potentially gain co-ordinates and systemaddress for extra systems.As the provided data in the route array is what is currently required as the bare minimum in a journal schema message this shouldn't actually require any changes to the schema other than adding the event type to the allowed list. This issue mostly for reference and any further discussion. It would require a small update to the documentation to explicitly state that the route array needs adding from the file.
The text was updated successfully, but these errors were encountered: