10 Infamous Video Game Glitches That Cost You 100%
When one session of yoga can cost you everything.
Video game glitches can be a lot of fun. They either create hilarity with weird graphical errors or can be used to exploit the game in a way the developers didn't plan for.
However, there is a dark side to the phenomenon of buggy games. A side filled with softlocks, critical errors, and game-breaking issues that ruin the lives of many players across the globe.
Unfortunately, in some cases, games can come out with glitches that prevent you from finishing them. One fatal mistake on your part or even a simple streak of bad luck can trigger these glitches for you and forever stain your game with an error that will cost you a full completion. From that point, your only choice is to start over and lose your progress, or, in more extreme cases, give up on the game entirely.
From corrupted missions to broken NPCs and items, the following bugs are the bane of any perfectionist. If you've never encountered them, consider yourself lucky, and if you did, know that your pain is recognized.
10. Developer Mode - Doom (2016)
Imagine starting a game and unknowingly triggering a bug that prevents it from tracking your progress. Now picture what it would feel like to discover the bug after playing the game for hours, and you get the horror story that a considerable number of Doom players experienced during its initial 2016 launch.
Yes, Doom's 2016 reboot used to contain a bug that would secretly prevent you from obtaining achievements as well as disable all online functions.
The bug would make the Steam versions of the game run in a faux developer mode that didn't actually give you any of the functionalities of the developer mode but still prevented you from cheating with it.
The game never informed you that the mode was on, so if you didn't pay any attention, you could easily play through most of the game and then experience a gut-wrenching shock when you finally discover that your efforts weren't recognized by Steam and you had to redo everything from the start.
That is, if you managed to turn off the developer mode beforehand, and that was easier said than done, requiring a full reinstall of the game and verifying files.
Long story short, be glad the bug was fixed shortly after.