Starfield, Bethesda’s highly anticipated space-faring RPG, has been met with a wave of excitement and enthusiasm from players worldwide. However, like any ambitious open-world game, it is not without its share of technical hiccups. One such issue that has been frustrating players is the “High Price To Pay” bug, which can obstruct progress and hinder the overall gaming experience. In this article, we will delve into this bug and explore potential solutions.
Read: [Solved] Starfield Operation Starseed Quest Bug
How to Fix High Price To Pay Starfield Bug
The High Price To Pay bug in Starfield is a particularly vexing issue that has affected some players’ ability to progress in the game. It occurs during the “High Price To Pay” quest, specifically at the stage where you are required to return to your ship. However, the game fails to recognize that you are already in your ship, leading to an impasse in the quest’s progression.
Starfield players have come together to share some potential workarounds. Keep in mind that these methods are not guaranteed solutions, but they may offer some relief to those facing this issue.
Visit Another System and Return
One workaround suggested by players is to visit another system, such as the Sol System, using the space map. After visiting this neighboring system, return to Alpha Centauri. Upon returning, you may find that the option to land at The Lodge becomes available. This method has worked for some players, allowing them to bypass the bug and continue the quest.
Save File Re-load
Another commonly recommended workaround is the “save file re-load” method. To attempt this fix, follow these steps:
- Save your game at your current location.
- Exit the game completely.
- Restart the game and load the saved file from your previous session.
This process has reportedly resolved the bug for some players, allowing them to progress past the problematic stage of the quest. However, it’s important to note that this method is not universally effective, and results may vary.
While Bethesda has not yet released an official fix for this issue, the community has offered several potential workarounds to fix this issue.