Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Including FSSSignalDiscovered event to list of allowed events to send over EDDN

See original GitHub issue

It will allow EDDN listeners to:

  1. Track FCs movements
  2. Track combat zones
  3. Track Resources extraction points (not quite useful since body info isn’t included)
  4. Track NonHuman signals
  5. Track high grade emissions signals
  6. Track installations
  7. Match FCs IDs and names

In order to decide which fields have to be removed I analyzed all keys in all my own journals record for FSSSignalDiscovered event, here is the list with some comments:

TimeRemaining - on USS, I don't think it can be useful for anybody but I also don't think it is private information
SpawningFaction_Localised - candidate to removing
SignalName_Localised - candidate to removing
USSType_Localised - candidate to removing
SpawningState_Localised - candidate to removing

There is also an event type that can be considered as personal information, it is missions related signals

{ "timestamp":"2021-10-27T20:33:30Z", "event":"FSSSignalDiscovered", "SystemAddress":3107509342922, "SignalName":"$USS; ", "USSType":"$USS_Type_MissionTarget;", "USSType_Localised":"Mission target", "SpawningState":"$FactionState_None;", "SpawningState_Localised":"None", "SpawningFaction":"$faction_none;", "SpawningFaction_Localised":"None", "ThreatLevel":4 }

Also please note that every jump for single player can generate more than 100 FSSSignalDiscovered events.

Additional values: horizons odyssey StarSystem StarPos With appropriate values as in journal-v1.0.json schema.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:1
  • Comments:15 (10 by maintainers)

github_iconTop GitHub Comments

Athanasiuscommented, Aug 4, 2022

The new schema has been live for many weeks now without anyone bringing up an issue, so closing this.

clonedArtiecommented, Nov 4, 2021

It’s easy to parse though. I certainly recommend for the specs that senders MUST NOT alter the SignalName any way.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Wow! signal
The Wow! signal was a strong narrowband radio signal detected on August 15, 1977, by Ohio State University's Big Ear radio telescope in...
Read more >
Mysterious Radio Signal Discovered in Milky Way Center
Ziteng (Andy) Wang is a PhD student at the University of Sydney. He recently discovered an unusual radio signal coming from the direction...
Read more >
SETI Talks: Mysterious Radio Signals in the Milky Way
These mysterious signals, which seem natural, were discovered ... more about the SETI Institute and stay up-to-date on awesome science: ...
Read more >
DHS Acronyms, Abbreviations, and Terms (DAAT) List
The DHS Acronyms, Abbreviations, and Terms (DAAT) list contains homeland security related acronyms, abbreviations, and terms.
Read more >
Acting Manager, Transport Airplane Directorate, Aircraft ...
The TR provides procedures for the flightcrew to follow in the event of the loss of all LCD units on airplanes equipped with...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found