I guess because my commander name will be logged in the code which is captured to update the codex.
Only for Codex discoveries. I have an awful lot of visited systems which don't include any Codex discoveries.
Worse still though, as an illustration of Varonica's point, when you get the Codex notification, the game fires off some logic which notes
directly in the Codex how your name is relevant. Next time you look up that entry in the Codex - say for a nitrogen geyser - you will see your own name there if you are the confirmation in that sector. That's all it knows. It doesn't know which system you visited before. Or after. It doesn't even
directly store the fact that you visited that system at all. You, the human, can infer the fact you visited from the fact you achieved a Codex entry, but "the game" - more accurately a "system of systems" doesn't care.
A search for my commander name would bring up every visited and mapped system.
I guess it must store a list of
your mapping server-side otherwise you could claim a discovery twice. But that's entirely centred on your data, nobody else can look up whether you're flying around with a map of Phobos in your console. But you'll note none of that is permanently stored
until you hand in the carto data. The list of systems you have visited but not handed in is most likely kept with the commander data somehow until it's handed in, but at that point it determines how many credits you are due, works out Firsts that need to be stored
in the Firsts data and then anything else will go down the memory hole.
Even if they charge for the option I’m sure there’s people who would pay to retrieve the data.
I think that's fair. It wouldn't be too hard to add a breadcrumbs feature so you could authenticate yourself as your Cmdr's identity and keep a history. But the point is, that has to be designed in, and things have to happen at the time of the system visit to allow that to work. What's annoying is the client and the GalMap already support most of that, it's just the data is in the wrong place.
It's not designed-in as a feature and looking it up "backwards" is extremely hard across 400 billion entries (and that's before you remember you have to multiply that 400 billion by the average number of bodies in the system).
So they could add it as a feature in Update 22 and it would work for systems you visit
after Update 22. But a retrofit ain't gonna happen.
If you're after a feature which shows you what systems another Cmdr visited, you could do that with a call-centre type "impersonation" feature where you look up that Cmdr's breadcrumbs by accessing their breadcrumbs data; you wouldn't do it by searching galactic data in general.
You still won't be able to get a list of all Cmdrs that visited a system because that really does get you into the territory Varonica is talking about.
I’m flying around the bubble to systems it says unvisited and the codex doesn’t increase meaning I’ve already been there.
Sure, but the Codex is managed separately for a narrow purpose, as above.
I do agree the Exploration game needs a bit of love - especially since the PP 2.0 team apparently aren't allowed to spend the time to make it make sense in that context - and it does seem stupid not to just move the Visited cache to somewhere it can be retrieved after a reinstall.
But to me it also seems stupid to not simply change some wording in the PP 2.0 documentation and cut out 90% of complaints, so clearly FDev are on some higher-dimensional chess game we don't understand.