Star Citizen 3.14 - Players Couldn't Pick Up Ships They Paid For
Star Citizen had to face another serious bug. As a result of patch 3.14, players were unable to use the option to pick up insured ships.
IN A NUTSHELL:
- Star Citizen had to face a serious problem with the new patch;
- Patch 3.14 introduced a bug that left the players unable to use the insurance option for their vessels;
- Fans have found a way out of the situation;
- The crisis is now largely resolved, though not completely.
Over the weekend, patch 3.14 appeared in Star Citizen, implementing, among other things, a new planet and city, but at the same time causing unexpected errors. One of them was the inability to use the option to summon insured ships.
The fear of every daredevil exploring the galaxy is that one day they will lose their ship. Therefore, Star Citizen offers an insurance system that enables us to recover a lost vehicle. Unfortunately, the new patch messed things up a bit and players started encountering problems with summoning their ships. Fortunately, fans themselves came to the rescue and managed to find a workaround for this bug.
It turns out that all we need to do is enter the mobiGlas (personal computer) and quickly switch between the ship, which we do not have access to and another, to which we have. If you do this efficiently enough, we should be able to glitch the selection menu. You should then make a change to the ship components and save it. Some advice from Reddit users suggests that the component we change should be the same as the one we added in the bugged ship.
Of course, the matter of such a serious bug had to be investigated by the developer - Cloud Imperium Games. Yesterday, a representative of the company, Nova-CIG informed on the game's forum that steps have been taken to fix the flawed system.
Comment from one of the representatives of the company
To restore the correct operation of applying for the return of the ship, you need to reset your character. Of course, this is associated with certain inconveniences, such as loss of progress in tasks. The consequences and instructions on how to do this can be found here. In short you should:
- Try to work around the error by other means;
- If that fails, go here;
- Log in to your account.;
- Report the problem here;
- Then go to My Hangar - Settings - Character Reset.
Unfortunately the comments (under the videos about the bug on YouTube and on the aforementioned forum) report that there were also problems with character reset, which sometimes does not work properly. The way to solve this is... patience - apparently everything returns to normal after waiting for about an hour (sometimes a little longer).
Some players are wondering how such a bug could get into the game if it was not detected during testing on the Public Test Universe. One of the representatives of the company pointed out that many factors are responsible for glitches, which can not always happen in the hermetic environment of test servers. Glitches can be the result of increased data flow, some can only be observed in a timely manner, and others have to do with character names. Of course, some mixture of different factors could be the problem.
Bearded-CIG wrote:
"In a nutshell, you could say that games are complicated and break in weird ways. It's hard to predict and find all the problems. It seems to me that the responsibility for making the process easier is on us, and we are having conversations about how to better find problems like this. We are constantly working on the publishing and playtesting process to find various glitches before they cause problems."
The confusion also resulted in some positive accents. Star Citizen's community rose to the challenge and quickly worked out a way around the bug. And on Reddit, user LordScree describes that in the face of losing his ship, another player helped him. A stranger gave him a lift and loaned him money for a second ship. This is how friendships are formed.
Interestingly, the bug about not being able to summon your ships through insurance is nothing new. You can find a thread on Reddit describing this bug (though probably caused by other factors) 2 years ago.
Work on Star Citizen is still in progress and seems to be far from over. Let's hope that in the future there will be as few serious bugs as possible.
