how to find which systems i've "discovered"?
- Thread starter Niamhy
- Start date
edit:
oh nevermind, you can do it on EDSM via this query:
(as long as you were using EDDI or EDSM or something that reported it to EDSM in the first place)
oh nevermind, you can do it on EDSM via this query:
(as long as you were using EDDI or EDSM or something that reported it to EDSM in the first place)
I went to the page
I went to the above link and do not see any way to enter your commander name and get a list of only your commander's first discovers.
I went to the above link and do not see any way to enter your commander name and get a list of only your commander's first discovers.
Right, it won't work like that.
That link would show you your FDs according to EDSM, not the game, if you were signed up to EDSM and sending data to EDSM.
Today, you could sign in to EDSM then upload all your old journals if you have them, which would probably give you something, but I don't know how it would handle the case where someone else discovered a system after you but told EDSM before you.
Ozric
Volunteer Moderator
Unfortunately there is no way to get a definitive list of first discovered systems. EDSM records the first person to report a system to it. In fact it gets even more confusing if you try to use it to work out who's scanned what.
If you look at Alectrona for example it says that I was the first person to report that into EDSM in 2015. I definitely wasn't the first person in Alectrona, but that was my first visit. If you view the system bodies and then Alectrona 1, it says that it was first scanned for EDSM by: Striker667 and first mapped for EDSM by: Disemboweled Ego
But the system has no first discovered tag, as it was a seeded system, and the person who first mapped planet 1 was Sharkbiscuit.
Unfortunately the best you can do really is to sort through your own journal/netlog files, and the cross reference that with actually checking the system map in game. I use EDDiscovery, which is a stand alone app, to keep track of my journeys. You can set it up to upload to EDDN and EDSM if you want, I don't, but within that you can see which systems you've visited and a whole host of information about that system (depending on how old the log is). But even that doesn't go into first discovered level of detail.
If you look at Alectrona for example it says that I was the first person to report that into EDSM in 2015. I definitely wasn't the first person in Alectrona, but that was my first visit. If you view the system bodies and then Alectrona 1, it says that it was first scanned for EDSM by: Striker667 and first mapped for EDSM by: Disemboweled Ego
But the system has no first discovered tag, as it was a seeded system, and the person who first mapped planet 1 was Sharkbiscuit.
Unfortunately the best you can do really is to sort through your own journal/netlog files, and the cross reference that with actually checking the system map in game. I use EDDiscovery, which is a stand alone app, to keep track of my journeys. You can set it up to upload to EDDN and EDSM if you want, I don't, but within that you can see which systems you've visited and a whole host of information about that system (depending on how old the log is). But even that doesn't go into first discovered level of detail.
Michael Brookes once made a spreadsheet available that listed all the systems visited and who was the first to visit them, but this was back during the first couple of weeks of the games release so there were only several thousand entries. I can't even imagine how big that database will be now, but its a shame frontier don't make it available offline so those want to use it could.
I've been away from the game since 2022, but seeing this colonisation stuff is coming I've been tempted to dust off the old siateks.
I've got some firsts to my name, at least one black hole, which would be a sick system to set up in but I've no way of finding it apart from cross referencing my journey to colonia/SagA* n back. In game is there anyway of searching other than toggling visited and trying to follow the route you took/copy paste each system name manually?
EDSM says' it's only 991 "firsts" to check...
At least they let you export your travel logs back into a text file AND let you pull your reported "firsts" separately.
One of the closest to the bubble I have is a mere 284ly from sol, and is a Green system (mats for a boosted jump) that I'd quite like to grab, but as a solo player, building ~28 claims just to get that one system seems... impossible.
I've got some firsts to my name, at least one black hole, which would be a sick system to set up in but I've no way of finding it apart from cross referencing my journey to colonia/SagA* n back. In game is there anyway of searching other than toggling visited and trying to follow the route you took/copy paste each system name manually?
EDSM says' it's only 991 "firsts" to check...
At least they let you export your travel logs back into a text file AND let you pull your reported "firsts" separately.One of the closest to the bubble I have is a mere 284ly from sol, and is a Green system (mats for a boosted jump) that I'd quite like to grab, but as a solo player, building ~28 claims just to get that one system seems... impossible.
Last edited:
I've been away from the game since 2022, but seeing this colonisation stuff is coming I've been tempted to dust off the old siateks.
I've got some firsts to my name, at least one black hole, which would be a sick system to set up in but I've no way of finding it apart from cross referencing my journey to colonia/SagA* n back. In game is there anyway of searching other than toggling visited and trying to follow the route you took/copy paste each system name manually?
EDSM says' it's only 991 "firsts" to check...
One of the closest to the bubble I have is a mere 284ly from sol, and is a Green system (mats for a boosted jump) that I'd quite like to grab, but as a solo player, building ~28 claims just to get that one system seems... impossible.
Well if you are looking for that black hole system it will be in your journals and a utility to list all the black holes in the journal means you will just need to check those ones, something like EDDiscovery will let you list you black hole systems easily.
You say this, I've been bouncing around EDSM for a few hours and I'm yet to find it. But then that isn't the tool you mentioned, I'm so out of the loop.
I don't know if I've used EDDisco, it rings a bell, but I might be thinking of EDDB. I'll have a goosey and see what's the happy haps, thanks.
Do you still have your journal files though?
You can get an approximation to what you want. Some scripting/grepping/similar tools/skills needed. There's one called jq that eats JSON files, which is what ED log files are. It is good for quick extraction of data, but does require that you know the data and what it contains. I run jq in Windows or Linux environments. (See https://jqlang.github.io/jq/download/ and https://jqlang.github.io/jq/manual/ )
How: Identify all entry stars that were found by autodiscovery and were previously undiscoveredby you. With jq, this is
The select() expression defines what you are looking for, and the '| .StarSystem' prints the system name of the star(s) that match(es). The '-r' option makes jq print strings 'raw' instead of making them into JSON strings with quotes and all ...
This is only an approximation as: 1) if you get a MauveAdder error during jump to a multi-star system, you usually don't get the entry star autoscanned,
2) you may not return alive with the exploration data to Universal Cartopraphics, which is what registers it as discovered by you.
It may be possible to identify 1-situations, and to extract the StarSystem name for those in a separate pass. 2-situations require much more analysis.
It would be simpler to use EDDiscovery, but as I don't have much luck with its search expression, I have personally given up on that. Perhaps someone else can provide suggestions for that.
(Added: You don't invoke jq for each separate file: you concatenate the log files to one single 'all_logs.log', and let jq loose on that.)
(Added more: There may be a 3). I don't know exactly what makes ED regard a system as discovered. If it is scanning the entry star only, there is no 3). But if it is 'all stars in system' corresponding to a honk, multi-star systems will not be detected by the search expression above.)
(Added: 4) The WasDiscovered value was introduced after 2019 and before early 2021. Earlier logs can't be used (as far as known) for 'I discovered this'. ) Similarly, autoscan (AutoDiscovery) was introduced after the game was published: logs from versions that did not have autodiscovery (or 'scan' command) won't be useful either.
How: Identify all entry stars that were found by autodiscovery and were previously undiscovered
The select() expression defines what you are looking for, and the '| .StarSystem' prints the system name of the star(s) that match(es). The '-r' option makes jq print strings 'raw' instead of making them into JSON strings with quotes and all ...
This is only an approximation as: 1) if you get a MauveAdder error during jump to a multi-star system, you usually don't get the entry star autoscanned,
2) you may not return alive with the exploration data to Universal Cartopraphics, which is what registers it as discovered by you.
It may be possible to identify 1-situations, and to extract the StarSystem name for those in a separate pass. 2-situations require much more analysis.
It would be simpler to use EDDiscovery, but as I don't have much luck with its search expression, I have personally given up on that. Perhaps someone else can provide suggestions for that.
(Added: You don't invoke jq for each separate file: you concatenate the log files to one single 'all_logs.log', and let jq loose on that.)
(Added more: There may be a 3). I don't know exactly what makes ED regard a system as discovered. If it is scanning the entry star only, there is no 3). But if it is 'all stars in system' corresponding to a honk, multi-star systems will not be detected by the search expression above.)
(Added: 4) The WasDiscovered value was introduced after 2019 and before early 2021. Earlier logs can't be used (as far as known) for 'I discovered this'. ) Similarly, autoscan (AutoDiscovery) was introduced after the game was published: logs from versions that did not have autodiscovery (or 'scan' command) won't be useful either.
Last edited:
Wow, I hadn't come across jq before - very nice tool!
Did you mean "previously undiscovered by you" or "previously undiscovered" full stop?
I assumed that field would mean the latter.
However... While playing with this (with just plain ol' grep for now, haven't yet downloaded jq) I found what appears to be an annoying limitation of earlier journal files:
The
WasDiscovered field doesn't show up in any of my 2019 journal files (the year I bought the game). It first appears in my February 2021 journals, but since I had a long break from the game between those two dates, I imagine that it was added at some point between those dates.I now wondering if there's any clue in older journal files about first discoveries.
Previously undiscovered full stop. Thanks! Corrected/overstruck in original question.
Grep is often faster than jq, but requires more knowhow (I think) to use well.
I haven't any logs from so far back, so I had not noticed the lack of WasDiscovered. And a check in the format documentation does not show any info that it depends on log dates/client version. The sample log entry (from 2018) does not contain any WasDiscovered ... but then it's a NavBeacon 'scan' which I can't find any in my own logs. That means there's a 4) ... (added)
Last edited: