After a week of various issues and bugs players are experiencing in No Man's Sky, Hello Games has hired some backup to help address these issues. In a blog post, director Sean Murray says they've hired a Quality Assurance team to compliment the Sony provided team, and that should help them address player issues more quickly than with their current team. In fact, the QA team is actually larger than the staff of Hello Games!

If you own No Man's Sky, here's what you need to know...

• A ticketed support system will be implemented next week for players to report bugs and glitches they experience.
• If you are having issues right now and need assistance click here to report your issue.
• A patch is on the way to fix the game's more critical issues.

Players who believe they are stuck or stranded are encouraged to remember they can use their jetpack an unlimited duration when pushed against an object, they have two saves in the options menu they can go back to, and that their ship can be summoned from a variety of locations should they lose track of it.

Finally, for the crowd that is having issues with the pre-order bonus, Murray addressed them directly...

It has been reported that some players have not received a pre-order bonus. In most cases so far, the player has either not redeemed their bonus correctly from the PS store or from the Options Menu. Also sometimes players have received the bonus, but the name displayed in-game was incorrect. The Alpha Vector ship is named Domanish S84 in-game, and (in the US) the Rezosu AZ65 is named Final Shadow XIV in game.

It has been reported that using the pre-order bonus ship will leave some players stranded, if they purchase or transfer to a new ship that does not have a hyperdrive (if done very early in game). In most cases the player is actually able to continue (107 of the 135 reports emailed so far). The game already detects the player needs a hyperdrive and directs them to a nearby NPC who will give the player the hyperdrive they need. Some other players were able to resolve this issue by restarting their console.