Quiet is easily one of the most powerful allies Snake has in Metal Gear Solid V: The Phantom Pain. Not only can she run ahead and scout out areas for Snake, but her sniping abilities are unmatched: for anyone trying to play through the game stealthily, using Quiet is one of best options available.

However, it seems that Quiet may actually end up being some players' worst nightmare. According to Konami, using Quiet in certain missions can break the game - what's worse is that this isn't some minor glitch that can be solved by simply restarting the game. As it turns out, using Quiet in two late-game missions can corrupt your entire save file, resulting in players losing all of their progress. Considering it takes 20 or so hours just to reach that point in the game, it's a huge problem.

So, how did something like this manage to get past Konami? Well, as of this writing, the publisher has yet to make any official statement outside of a single tweet - and even that didn't offer up much information. So far, players only know that using Quiet on Mission 29 or 42 can trigger the glitch, and if it happens, prepare to start the game over from scratch.

Warning: there are some spoilers from here on out. Nothing about the story, but if you want to stay in the dark about the game's missions, be warned.

For those wondering, the glitch seemingly has something to do with one of the game's later boss fights against the Skulls. 'Mission 29: Metallic Archaea' isn't all that special in terms of design: for the most part, it's a pretty standard fight against the Skulls. The same holds true for Mission 42, the 'Extreme' variant of the same mission. Having played through the mission, there's seemingly nothing that would trigger the glitch.

Thankfully, neither mission is all that suited for Buddies anyways: as with most of the game's bosses, the Skulls focus on Snake and Snake alone, so it's not like players will be missing all that much by not having Quiet at their side.

Even so, it's amazing that a glitch of this magnitude was able to make it past testing, especially considering how long it took for the game to launch. We'll update this story if any new information on why the glitch is in the game (or how to fix it) as it comes along.

Be sure to follow T-Lounge on Twitter and visit our Facebook page!