Getting a full list of systems visited (a bit techie)

[andyl]

I am interested in seeing my entire journey since starting, seeing how many systems I have jumped in to etc.

Now having seen that some of the 3rd party trading tools (EliteOCR, Slopey etc) seem to be able know what system we are in I guessed this must be logged somewhere.

So after a bit of poking around I discovered it was in the net*.log files found in C:\Users\andyl\AppData\Local\Frontier_Developments\Products\FORC-FDEV-D-1010\Logs (change the user as appropriate).

So I copied them over to my Linux box. Then it was simply a matter of

grep System net*.log | cut -c46- | cut -d\) -f1 | uniq | cut -d\( -f2 | uniq

will print out a full list of all the systems (not stations) you have visited (in the order you visited them).

You can obviously redirect that output and put it into a file for later perusal.

That makes it easy to get a full list of your travels.

You can count how many systems you have been to. Pipe it through wc -l.

You can sort it and then throw it through uniq again to get a list of the unique systems.

For me so far 422 systems visited and 367 unique systems. I guess I'm not one to ply a standard trading route, or have a home base for bounty hunting.

Now you may not have a handy Linux box, but they are available on the Mac (in Terminal), and there are third party shells and tools that provide them on Windows.

Hopefully this has been of use to someone.

 

[dioogio]

The Guy who wrote Elite copilot, which does a way better job of providing a route than inside ED, recently added a Jump Log function which does exactly what you are doing. Interrogates the logs and opens the list of systems visited in your default txt editor in windows.

Edit: actually, Just checked and that prog is only shown jumps since Dec 23rd where as my logs go back to Gamma launch.
I will have to post a question on his thread.

 

[WO-One]

Interesting method of getting at the stored data, +1 for your efforts.