Galnet & Twitter: "an unknown vessel needs our help!"

Oh you poor summer children :)

It's done. I was kinda hoping there would be more clues to allow people to find it in-game, but it seems this one was always meant be to solved using twitter. Ugh.
 
Oh you poor summer children :)

It's done. I was kinda hoping there would be more clues to allow people to find it in-game, but it seems this one was always meant be to solved using twitter. Ugh.
Again...feel free to let us poor plebs know all the info you do :) Otherwise I call rubbish that you know as all as everyone else
 
Myself I am somewhat disappointed it wasn't a breadcrumb search like what you can find with some of the listening posts (in the Maia system for example), tracking from system to system, picking up partial clues from each location until you get enough to triangulate the location. you know, actually have use your brain to get the solution and not just brute force a solution.

To me that would be much more fun and could easily have stretched the full week.....
I enjoyed those and was really hoping this one would be similar
 
I did have a ship (Keelback) drop in near me (when i was at the Crashed Anaconda), fly about a bit then High-Wake out. I would have followed if I had a wake scanner... It did this 3 times!

Extra info if anyone wants to check it out: It was blue/turqoise, Called "Barbosa" (or something v. similar), NOT wanted, and was registered to/allied with the "LTT 1935 Confederacy".

I went to the Crashed Anaconda in LTT 1935 to check for the Keelback. Did not find it, jumped in and out of supercruise 3 times, not one time was there anything flying around. So I think it was only random.
What I got on the third time I popped out of Glide at the Crashed Anaconda was a wanted Anaconda landed close to the crashed one. Name was Frood and belonged to the LTT 1935 Drug Empire. I scanned it with my SRV, no response. I bumped into it, no response. I waited around for a bit in my Asp Explorer, nothing happened,so I lost patience, tried to shoot it, it responded with trying to kill me,I jumped away. Waited around thinking I might catch it in space, nothing happening. So I came back to the crashed Anaconda and it was gone. Either way I don't think this has anything to do with the Mystery, just that there are random events happening near the crashed Anaconda at LTT 1935 6a, probably all the way back from when it appeared in the game.

Frood_near_CrashConda.jpg
 
Last edited:
If you have more info then us feel free to post it as a spoiler. I didnt see where Frontier said everything was done...
Frontier never do. I posted this before.


I don't think it's over. They said a few weeks ago there would be less clues given, so why would they set a "go here, that's it all done" thing.
They didn't say "go here, that's it" though.

They said "Go here, now look for a single system in a search radius from there encompassing ~5000 systems", with no further clues, as opposed to the Adamastor puzzle which gave the means to pretty much pinpoint the next system at each step. So brief met I guess?

Unfortunately for FD, where they positioned the target system meant a brute-force search would actually only cover at most 500 systems before discovery. For a single player, 500 systems might be a lot, let alone 5,000. But for 10-20 players, this is only a few hours of work. For potentially hundreds of players? Over in a pinch. On top of that, given the location of the target system relative to the start point and anywhere else around it, it very easily could have been picked as the first random system someone visited. It simply wasn't a very big search space.

Thing is, FD's activities have never been particularly complicated or difficult, and wild speculation from people generally leads to a huge amount of red herrings without some common knowledge about the game.

For example, I notice people have been spotting/chasing ships landed around the area. Those ships are random spawns which can happen anywhere in unpopulated systems within (iirc) 150Ly of a populated system. Nearest populated systems to the target are ~ 128Ly, so this is nothing of interest. In a similar vein, that's why people will also find wrecked ships, minor outposts and other procedurally generated, temporal things.

tl;dr if you haven't done many/any of these things before, it's easy to speculate this isn't the end of the puzzle. But if you have, it's pretty obvious this is it, until FD publish something new via galnet or some other mechanism.
 
Last edited:
Frontier never do. I posted this before.



They didn't say "go here, that's it" though.

They said "Go here, now look for a single system in a search radius from there encompassing ~5000 systems", with no further clues, as opposed to the Adamastor puzzle which gave the means to pretty much pinpoint the next system at each step. So brief met I guess?

Unfortunately for FD, where they positioned the target system meant a brute-force search would actually only cover at most 500 systems before discovery. For a single player, 500 systems might be a lot, let alone 5,000. But for 10-20 players, this is only a few hours of work. For potentially hundreds of players? Over in a pinch. On top of that, given the location of the target system relative to the start point and anywhere else around it, it very easily could have been picked as the first random system someone visited. It simply wasn't a very big search space.

Thing is, FD's activities have never been particularly complicated or difficult, and wild speculation from people generally leads to a huge amount of red herrings without some common knowledge about the game.

For example, I notice people have been spotting/chasing ships landed around the area. Those ships are random spawns which can happen anywhere in unpopulated systems within (iirc) 150Ly of a populated system. Nearest populated systems to the target are ~ 128Ly, so this is nothing of interest. In a similar vein, that's why people will also find wrecked ships, minor outposts and other procedurally generated, temporal things.

tl;dr if you haven't done many/any of these things before, it's easy to speculate this isn't the end of the puzzle. But if you have, it's pretty obvious this is it, until FD publish something new via galnet or some other mechanism.
All that makes sense. I guess we're just hoping there's more
 
All that makes sense. I guess we're just hoping there's more
I think there will be more, just not yet.

This actually feels a bit like a stop- gap activity tbh... the fact it had a computer-generated voice for the logs, even though that was explained in those logs, screamed a bit of "voice actors have just come off leave from chrissy and have a backlog of Odyssey work, so couldn't do this one"... I'd argue the fact the logs explicitly explain why it's a computer voice is a bit of a guilty- conscience move, but that's a bit of an unfair claim too.

Guess we'll see later this week if something comes up.
 
Crashed ship? Gee, doesn't sound like a prelude to Odyssey.

No, not at all.

Of course it's not over, and of course it was meant to be found quickly.
 
Question: The Unknown Vessel puzzle that started last week, is this a multi-part event?
Answer: It is there for a reason but we can’t comment on specifics.

Question: Would other things like this event also be a way to use the codex rumor system that since its release in Dec 2018 has yet to be used?
Answer : Please see above answer.
 
I'm just wondering if it is over?
Where did they go?
Did anyone else spot the npc anaconda leaving as you arrived?
Did anyone wake scan it?
Could be missing something more to this
 
Back
Top Bottom