2024 checking in. Still bugged.
'Infiltrate the Data Link' missions being broken by 'Log already accessed' scan output
Yep still bugged.. Hard to get easy neofabric Insulation
Plz keep voting
issues.frontierstore.net
Plz keep voting
Issue Tracker
issues.frontierstore.net
Last edited:
That's probably the ticket that made them break it like it is now 
Stacking megaship missions unfortunately has a tendency to bug out; been stacking them with success at other times so it is finicky.
-i do remember there was a reproducable issue with the cargo containers on them that got fixed.
Maybe the root of the issue stems from megaships being able to change systems, idk.
-i do remember there was a reproducable issue with the cargo containers on them that got fixed.
Maybe the root of the issue stems from megaships being able to change systems, idk.
Didnt really read the ticket. The posts below do cover the issue. The stacking of the megaship scans missions is broken as @Planewalker mentions.
LOG ALREADY SCANNED!
They're not even meant to be stackable. This was their "fix" for missions not completing when you were carrying more than one (from the 16.01 update notes):
example
forums.frontier.co.uk
'Infiltrate the Data Link' missions being broken by 'Log already accessed' scan output
Trying to get myself access to the Sirius system for that engineer. I head over to the Takurua system where there are 3 different Sirius stations and a grab a bunch of missions from all the stations to start banging out. I don't mine or trade, and the only remaining mission type was "Infiltrate...
Yes
You can take a second mission to the same megaship later. They will end in a "LOG ALREADY SCANNED!"
I just got odyssey today so I don't know if it's fixed with odyssey or not since I haven't tried the mission after the upgrade. But I can say for sure that I encountered a bug while playing in horizons. I took 1 copy of this mission, I went to the location, similarly had some issues as others had with being confused about what I needed to actually do. I used hacking limpets and went around interacting with all kinds of stuff before I finally found and figured out what I was actually supposed to do. By that point, the pirates had destroyed all the capacitor things on the megastructure. I scanned the data uplink thing just like you're supposed to do, and the mission didn't complete. I then tried jumping to another system and back again, I tried relogging, I tried going back to the mission giver, I tried everything I could think of and nothing worked. I couldn't re-scan the object. I tried going to OTHER megaships to see if scanning them would work.
That is a seperate issue and not related to mission stacking.
-one of the megaship missions needs you to scan/hack #xyz which also bugs out.
In any case all megaship missions are currently finicky, but they can also work just fine.
There is also the issue of people confusing scanning with hacking and Uplink with another node.
No matter what, the megaship needs a good portion of TLC and QOL to be streamlined and informative.
Now that I have Odyssey I decided to try this mission again. I took a mission to scan the log uplink. I warped to the system. The megaship signal was highlighted in blue. I went straight to it, straight to the nav uplink, I ignored everything and scanned it right away - annnnd I was unable to. It said I have already scanned it. I think a simple solution would be to allow players to scan the log uplink more than once. Or maybe have the game keep track of whether or not you have already scanned that one and then block further missions from sending you to ones you have already scanned until they reset on thursday.
They work sometimes, so it is not a critical bug per se. (did three the other day)
As long as one is mindful that they can bug out especially when stacking, it is workable.
And yes they need streamlining/fixing and QOL as stated.
As long as one is mindful that they can bug out especially when stacking, it is workable.
And yes they need streamlining/fixing and QOL as stated.
If that is possible it could be a solution, idk.
