Welcome to the AFK Mods bug tracker. In order to report an issue, you need to have a VALIDATED account to post one. Once you have followed the link the registration email sent you, please select a project from the drop down menu below. Select “Open New Issue” and fill out the form with as many details as possible.

Please also consider sending your bug report to Bethesda if you are reporting on an issue with Skyrim Special Edition, Fallout 4, Starfield, or Oblivion Remastered. Doing so will help everyone on all platforms.

Issue Data
Status: New
Issue Type: Bug Report
Project: Unofficial Starfield Patch
Component: Starfield: Vanilla
Category: Quests & Dialogue
Assigned To: Nobody
Platform: All
Severity: Low
Votes: 0
Watching: N/A
Opened By Sclerocephalus on Sep 17, 2025 3:39 pm

Issue #35856: Return to Vectera: Ship wreck (with Heller) can be discovered prematurely

 
This occurred to me after 'Return to Vectera' had started. Instead of heading to Vectera immediately, I did other stuff. Eventually, I got into a fight with enemy vessels and ran low on spare parts. I then checked nearby planets for ship wrecks (because the generic ship wreck site always has a crate where some spare parts can be found), found one and landed there. As it turned out however, this was not a generic ship wreck but the quest specific site where Heller was stranded and which the quest is supposed to send me to only much later. Without having spoken to Lin, the information you get from Heller is somewhat confusing (probably even more so for people who never played the game before). Moreover though, the game then added the slate with the coordinates (which I should have obtained on Vectera) to my inventory. Out of nowhere. If you never played the quest before, this adds to the confusion, and it is also unnecessary because you don't need that slate anymore once you have found Heller.

This confusion could be easily avoided by hiding the map marker of the wreck site until the player has obtained the slate with the coordinates.


NOTE: I didn't check in my most recent playthrough whether the problem still exists, so I pro-actively apologize in case Bethesda fixed it in the meantime.