Misrepresented Codex Entries when using a Carrier to Explore.

[Marxanthius]

Hello, each week I scan the in game codex by hand looking for new discoveries.
A few weeks ago, Solid Mineral Spheres, Prasinum Metallic Crystals, and Flavum Metallic Crystals where found in the OUTOTZ YX-N C21-0 system and recorded in the codex as first discovered for that region. When I went to that system there was no Notable Stellar Phenomenon and none of those items in the system. There were systems within a 500 ly range that did have those items.

I believed this to be a carrier jump issue. I was able to replicate this scenario, by jumping my carrier from a non NSP system into a system in a different region with an NSP. When I scanned the items they showed up in the codex in the region that I had jumped from, not where I currently was. I was able to get a first discover entry, even though they don't exist in that system: RUBEUM Metallic Crystals in the Sanguineous Rim region in OUTOTZ YX-N C21-0

I have logged the issue here with replication steps I used. https://issues.frontierstore.net/issue-detail/49216

I think the key thing was to be in your ship during the jump, not in the carrier on foot, or else I always seem to get the black adder message when going to super cruise after the carrier jump.

Today when scanning the codex, this entry came up:
CMDR BARBA NEGRA 82 found a Viride Lagrange Storm Cloud in the Odin's Hold region in AGNAIRY LK-S C6-6833 on April 21 3308 (2 days ago)
But when the system was visited, there was no NSP within the system.

There is a Viride Lagrange Storm Cloud in Agnairy JH-U e3-2113, in the Empyrean Straits, about 900 ly away.
Unfortunately I don't know how to contact this CMDR and find out if they are perhaps exploring with the aid of a fleet carrier.
If indeed the problem persists over multiple jumps, one could conceivably get codex entries into some funky locations with enough time and tritium.

If anyone else is able to replicate I would greatly appreciate the info for the support ticket. Or keep an eye out for it a least if you are using a carrier to explore.

I just feel that these incorrect entries could ruin a CMDR's trip, if they go all that way where the game itself tells you that something exists, and it isn't there.

o7

 

[marx]

Wow, that's messy. It could even be used to pollute the Codex, although that would take a fair amount of effort.
Well, another Codex bug to add to the pile. Quite a bad one, at that. Thanks for posting this, and in detail too!

 

[Mooing]

Even if they do fix this, like terraformable ammonia worlds, I doubt they'll remove the false entries. Hopefully, this gets fixed before the whole galaxy is covered with false reports!

 

[varonica]

Hello, each week I scan the in game codex by hand looking for new discoveries.
A few weeks ago, Solid Mineral Spheres, Prasinum Metallic Crystals, and Flavum Metallic Crystals where found in the OUTOTZ YX-N C21-0 system and recorded in the codex as first discovered for that region. When I went to that system there was no Notable Stellar Phenomenon and none of those items in the system. There were systems within a 500 ly range that did have those items.

This is highly unlikely and looks like a codex error, Outotz YX-N c21-0 has been visited over 1,600 times, I doubt that was all in the last few weeks. There are multiple entries in EDSM for these items in that region so it sounds like a false codex entry of some sort, this has happened before where it reported the incorrect data to CMDR about first regional discoveries.

 

[Marxanthius]

This is highly unlikely and looks like a codex error, Outotz YX-N c21-0 has been visited over 1,600 times, I doubt that was all in the last few weeks. There are multiple entries in EDSM for these items in that region so it sounds like a false codex entry of some sort, this has happened before where it reported the incorrect data to CMDR about first regional discoveries.

The additions to the in game codex were definitely in the last few weeks, the entries have timestamps in game as to when they were added.

Searching for Prasnium Metallic Crystals, and Flavum Metallic Crystals and Solid mineral Spheres in the Sanguineous Rim in EDSM, there ae 12 systems that have one of these items, and when you look at them in the galaxy map they are all on the border of the region. There is another known issue where the interface of the game, including the entries that go into the codex, are different than what appear in the logs that are parsed for tools like EDSM and EDMC. It means that EDSM, EDMC and the other tools are recording a different region than what gets sent to the codex entries. It occurs for systems that are right on the border, I have also been able to reproduce this separate issue as well. At least in those situations the items are actually in those systems so people can find them, even if they recorded for the wrong region. I have been looking into this specific issue, because of a discrepancy between entries from the codex, and entries being recorded by the logs.

For example these are the regions that Aleoida Laminiae - Emerald are found based on the in game codex, and they appear to be locked to "arms" of the galaxy

However, when we look at the reports that come from the logs, you will notice an entry for Sanguineous Rim.

That small discrepancy causing them to bleed over into other regions could ruin potential patterns for some bios like Aleoida Spica - Teal which almost seem to be a NOT in this arm type, as seen here based on codex entries.

A very interesting quirk is that the codex doesn't seem to record things that can't be found in that region. When I performed my test to get RUBEUM Metallic Crystals to appear in OUTOTZ YX-N C21-0, I attempted to scan the Albulum Gourd Molluscs and they did not trigger a codex entry. I suspect that Albulum Gourd Molluscs is not allowed to spawn within the Sanguineous Rim region, and so no entry was created.

 

[EdzUp]

Im wondering if this is why the codex entries have to be confirmed by others entering the system looking for those entries. As this cannot happen with this misreported entey due to carrier jump it should be removed from the codex after a time period and no new cmdrs see the entry in question

 

[Marxanthius]

and if anyone likes codex oddities, here is a good one.

Been tracking the codex for over a year now, and yes it is filled with errors and issues. Generally though they remain static issues, you just mark them down and move on.

3 weeks ago, one of those oddities that I had since the start of recording the codex twitched, then it twitched again the following week, then a gap of week and again it twitched.

Bit of tinfoil hattery in my writeup.

What is the Pilot’s Federation hiding from us?

What is the Pilot’s Federation hiding from us? April 2, 3308 Updated April 9, 3308 - Info at end of article Updated April 23, 3308 - Info at end of article Updated May 7, 3308 - Info at end of article Updated June 8, 3308 - Info at end of article Updated Dec 3 , 3308 - Info at end of article U...

docs.google.com

 

[varonica]

Yeah I have said for several years they need to can the codex and redo it from start, you would think something like that would work properly after all it's just taking data from players and recording it, what could go wrong? Lots apparently!

 

[Codger]

I rarely even look at the Codex. It's rife with errors, and even if it wasn't is mostly useless due to the bizarre design.

I'm glad someone is keeping track, though.

 

[Frankymole]

Given all the nods to The Hitchhiker's Guide to the Galaxy, I wonder if it's intentional / lore that the Codex is full of "much that is apocryphal, or at least wildly inaccurate"...

 

[marx]

Im wondering if this is why the codex entries have to be confirmed by others entering the system looking for those entries. As this cannot happen with this misreported entey due to carrier jump it should be removed from the codex after a time period and no new cmdrs see the entry in question

Thing is, new Codex entries don't have to be confirmed by others. Somebody reports something new, it gets added to the Codex - the "confirmed on" part is just in an individual player's version. But if entries did require verification by other CMDRs, that could help filter out such errors.
Since Frontier have never used Rumoured entries and seem to have no intention of doing so, they could just make it so that one discovery puts the entry into Rumoured, and another player scanning the same thing will move it to Reported.

But worse bugs have lingered in the game for long times, so I wouldn't hold my breath on any of this :/