History GameBreakingBug / FirstPersonShooter

* The PC port of ''VideoGame/{{Turok}} 2'' seems to have a major memory leak, causing it to slow down to slideshow levels (even on fast computers) after playing a few minutes, and possibly crash.

** The original Unreal engine also tends to have problems running on [=CPUs=] faster than 3 [=GHz=] or so, causing games on the engine to speed up to levels that make them unplayable. Fortunately, this is relatively easy to fix.

* The Operation Red Crow expansion for ''VideoGame/RainbowSixSiege'' added an operator named Hibana, whose unique gadget, on the PS4 version, can crash the game, disconnect players randomly or drop the frame rate to 0 for seemingly no reason (bearing in mind that the Xbox One and PC versions suffered no issues with it at all). Ubisoft quickly issued a patch (about a day after the launch of the DLC) that, in lieu of actually fixing anything, completely prevents PS4 players from picking Hibana at all. This situation worsened when it was discovered that this fix actually prevented players from progressing past the end of season rewards pop-up. Attempting to click through this pop-up would result in the game crashing. With no other choice, Ubisoft restored Hibana into the game, and thus the glitch with it.
** As if PS4 players hadn't already had it rough; a small bug fix patch, during the Operation Blood Orchid expansion, caused quite possibly one of the worst bugs of the 8th console generation. The bug had the potential to completely brick your Hard Drive beyond repair ( where even a system restore won't help ) and, somehow, your entire PSN account. The bug was triggered by simply trying to invite a friend to your game. If you were unfortunate enough to do this, you would be rendered unable to send game invites to people ever again - on ANY game. And this is "lucky" in comparison to what many players suffered - where their console may be completely bricked through no fault of their own.

* ''VideoGame/Doom2016'' has a rather notorious bug where the "developer mode" will be turned on by itself. Normally this wouldn't seem like a bad thing, since it enables you to use the console... but it also prevents you from gaining achievements and even ''accessing the multiplayer mode at all''.
* ''VideoGame/CallOfDutyBlackOps'' has a strange one--in a level towards the end of the campaign mode, using a shotgun to get your way through the level, without warning an error message [[http://www.youtube.com/watch?v=qzzLQ2ccazM will appear]] warning of "more than 160 bones" (or, sometimes, "bodies"). The exact cause of the error is unknown, and after closing the message box, the game will essentially reset itself and return to the main menu. Reloading the campaign will send you back to the start of the level, so goodbye to all the hard work put in before the message. This glitch can also appear in other ''VideoGame/CallOfDuty'' games made by Treyarch.
** A similar glitch occurs in ''VideoGame/CallofDutyInfiniteWarfare'' on the PC. Picking up any throwables in singleplayer will kick the player to the main menu with the message "Could not allocate a reserved scriptable for entity x - limit is x - try increasing the number in the worldspawn entity in radiant." The only solution is to increase your virtual memory in Windows to 4 GB or more, which causes the cutscenes to exhibit audio stuttering.
** The same mission as the above has one section where, for plot reasons, your RegeneratingHealth does not actually regenerate normally. However, after an update, this broke entirely - you were stuck with limited health for the entire mission. Fortunately this was fixed.
** On the penultimate mission where you discover [[spoiler:you were brainwashed]], you get punched while running down a corridor. However, this sequence will often break, and after being punched, Mason will be stuck in place and [[spoiler:Hudson]] will appear in his Vietnam gear, complete with sunglasses. The unfunny part is you're stuck, and the level has no checkpoints as there's no combat in it, so you have to start the entire mission again.

** ''Call of Duty 2'' has one issue with its more scripted nature than the original game that can grind the game to a halt in the "Comrade Sniper" mission. One of your objectives is to pick up a scoped Mosin-Nagant, then shoot an enemy sniper with it. However, the game doesn't wait until you pick up the sniper rifle to spawn the enemy sniper. You can shoot the sniper with a different sniper rifle, such as one taken from the previous level, but the mission's progress will grind to a complete halt at this point because the "kill the sniper" objective doesn't trigger unless you've held that Mosin-Nagant at least long enough for the "pick up the sniper rifle" objective to count as completed, and doesn't retroactively trigger as completed if you kill the sniper before picking up the rifle.

* An update patch for the XBox360 version of ''VideoGame/FarCry3BloodDragon'' causes the game to crash with a "Disc Unreadable" error during the intro, at least on certain console models.

* Following the release of the April 27, 2017 patch of ''VideoGame/{{Overwatch}}'', D.Va's mere existance caused client crashes, forcing Blizzard to render her unplayable until the issue was fixed.

* The first ''VideoGame/SystemShock'' has received one as time goes on. First, it's designed for old MS-DOS systems and won't run on modern Windows. Fine, there are plenty of good DOS emulators out there that can do the job. Here's the problem: the final battle is a TimedMission of sorts, as you have to destroy SHODAN before she finishes [[MindRape Mind Raping]] you. The countdown is not based on the clock, but instead on your processor cycles... which on a modern machine, run many hundreds of times faster than they did back when the game was released. This can easily render the final battle unwinnable, as there is no way to damage SHODAN enough before you die. You'll have to limit the processor speed on the emulator if you want to have a chance at this. [[UpdatedRerelease The Enhanced Edition]] intermittently fixes this bug (if it doesn't, enabling Vsync in options generally does the trick).

** ''Call of Duty 2'' has one issue with its more scripted nature than the original game that can grind the game to a halt in the "Comrade Sniper" mission. One of your objectives is to pick up a scoped Mosin-Nagant, then shoot an enemy sniper with it. However, the game doesn't wait until you pick up the sniper rifle to spawn the enemy sniper. You can shoot the sniper with a different sniper rifle, such as one taken from the previous level, but the mission's progress will grind to a complete halt at this point because the "kill the sniper" objective doesn't trigger unless you've held that Mosin-Nagant at least long enough for the "pick up the sniper rifle" objective to count as completed.

** If the Patriarch spawns within eyesight of the players, the game will keep everyone in the observer camera mode far longer than it's supposed to, essentially allowing him free hits on the players as they're basically forced to choose between aiming in his general direction and actually having any clue where they are for a couple seconds. Thankfully, this is very rare.

** Random deaths to the environment are a bit of a thing for early games on that engine. ''VideoGame/{{Blood}} II: The Chosen'''s in-engine cutscenes can still affect the player character while they're stuck in place due to said cutscene. One in particular in the second chapter is triggered while the player is walking through a door, which automatically closes just five seconds into said cutscene - if the player happens to be standing in the wrong spot, the door will push them into the door frame and [[TheDoorSlamsYou immediately crush them to death]]. [[GoodBadBugs Which the player will not be aware of until after the cutscene ends, except for the screen temporarily flashing red during it.]]

* ''VideoGame/{{Marathon}} Eternal'' is a [[GameMod fan-made game]] using the open source version of the engine. On the level "Roots and Radicals", there's a medium-sized room which spawns endless amounts of Enemy and Weapons sprites, not to mention unlimited Helpful Drones. Now, there is a wall next to the spawning pad which can not only be switched on to block off the troopers but smash them during their short run outside that area. Letting them spawn instead of blocking off the path can make the game Unwinnable because Alephone will block off Hit Detection due to memory usage exceeding limits.

* ''VideoGame/FirstEncounterAssaultRecon'' has a little bit of an oversight that renders the game unbeatable. At one point, you're asked to download data from a laptop. However, there are laptops with downloadable data all around to get the backstory which look exactly like it, and you're told to download this data nearly two minutes ''after'' you see this laptop. But once you download data from a machine, you can't do it again, even with that mission critical laptop. The mission objectives also didn't say that it was completed. You basically have to restart from the last save and wait for the objective to be given, then download the data. One of the game's later patches fixed this, so that in the event that the player downloads that data before he's told to, Betters will tell them "I see you've already checked the laptop." and proceed as normal.

* The Operation Red Crow expansion for ''Rainbow Six: Siege'' added an operator named Hibana, whose unique gadget, on the PS4 version, can crash the game, disconnect players randomly or drop the frame rate to 0 for seemingly no reason (bearing in mind that the Xbox One and PC versions suffered no issues with it at all). Ubisoft quickly issued a patch (about a day after the launch of the DLC) that, in lieu of actually fixing anything, completely prevents PS4 players from picking Hibana at all. This situation worsened when it was discovered that this fix actually prevented players from progressing past the end of season rewards pop-up. Attempting to click through this pop-up would result in the game crashing. With no other choice, Ubisoft restored Hibana into the game, and thus the glitch with it.

* During the Operation Red Crow expansion for ''VideoGame/RainbowSix: Siege'', an operator named Hibana was added, whose ability, on the PS4 version, can crash the game, disconnect players randomly or drop the frame rate to 0 for seemingly no reason (bearing in mind the Xbox One and PC versions suffered no issue at all). Ubisoft quickly issued a patch (about a day after the launch of the DLC) that, in lieu of actually fixing anything, completely prevents PS4 players from picking Hibana at all.
** This situation worsened when it was discovered that this fix actually prevented players from progressing past the end of season rewards pop-up. Attempting to click through this pop-up would result in the game crashing. With no other choice, Ubisoft restored Hibana into the game, and thus the glitch with it.

* The first ''VideoGame/RedFaction'' has the infamous submarine glitch. At one point, you have to get into an underwater lab, preferably using a submarine. Unfortunately, when being lowered with a crane, the sub will explode 99 times out of 100. While that water passage can be traversed without the submarine, it's suicide on higher difficulties and you can get stuck there with no way to advance. While this bug is frustrating, it is known to be caused by an overly high FPS rate, inevitable on new computers. Start compressing your hard disk in the background, though, and the submarine ride is yours.

* In ''VideoGame/Battlefield2142'', you could move the Titans around, allowing you to use their weapons in an effort to win the round. Unfortunately, doing so lagged many servers as they moved about, not to mention during firefights on a moving Titan, bodies would glitch through the floor, preventing them from being revived. Dice eventually patched the game so that servers could disable Titan movement, unfortunately removing a otherwise useful tactic of the game mode, as most servers went with the disable movement option.

* ''VideoGame/{{Crysis}}'' had one, and at the most climactic moment of the game too: the final boss would randomly become untargetable (and thus invulnerable). This was made especially pernicious as the battle in question involved three separate phases and the bug could manifest itself during any one of these. Saving the game mid-fight did not help, and the community never quite figured out what caused the dreaded bug. The only solution was to save before the fight and keep reloading until it went right. This could take as many as five or six attempts.
** The stage "Relic" had one. When you fight the soldiers in the graveyard, sometimes the helicopter you are supposed to leave in never arrives. You have to replay the whole level again to fix it.
** Also the mission where you have to meet Prophet in a cave would sometimes decide to spawn rocks in front of the entrance so you could not reach him, fortunately this one is easily remedied by enabling the god mode cheat and passing through the rocks.
** ''Crysis'' had plenty of game ending flag bugs right from the very beginning: If you're playing a second time, you'll probably want to run straight to the action. Nope, sorry. Using your nano-suit abilities, given almost immediately after reaching the beach, if you get to the point where you meet your first teammate too quickly, he'll just stand up on the cliffs. Nothing you can do except starting over will get him to come down.
** ''Crysis'' and ''Crysis Warhead'' both had bugs where triggering the start of the final boss fight would remove part of the map's clipping data. If the player happened to be standing in this part of the map, they would fall through the level and be forced to reload. If the player didn't have an earlier save or couldn't get to a safe part of the map fast enough, they had to restart the level.

** In both ''Doom'' and ''Doom 2'', typing "idmus##" will change the music to whatever number you specified. Typing "idmus00" in ''Doom 2'' will cause the game to crash because 00 was the number for the title theme of the first ''Doom'' game, which doesn't exist in ''Doom 2''.
** In Map 06 of ''Doom 2'', pressing the "use" key on the red key door's tracks causes the game to either freeze or crash, depending on the version, because the door tracks were programmed to open a door that didn't exist.

* ''VideoGame/Doom2016'' has a rather notorious bug where the "developer mode" would be turned on by itself. Normally this wouldn't seem like a bad thing, since it enables you to use the console... but it also prevents you from gaining achievements and even ''accessing the multiplayer mode at all''.
* ''VideoGame/CallOfDutyBlackOps'' has a strange one--in a level towards the end of the campaign mode, using a shotgun to get your way through the level, without warning an error message [[http://www.youtube.com/watch?v=qzzLQ2ccazM will appear]] warning of "more than 160 bones" (or, sometimes, "bodies"). The exact cause of the error is unknown, and after closing the message box, the game will essentially reset itself and return to the main menu. Reloading campaign will send you back to the start of the level, so goodbye to all the hard work put in before the message.
** Apparently this glitch can also appear in other ''VideoGame/CallOfDuty'' games made by Treyarch.
** A similar glitch occurs in ''VideoGame/CallofDutyInfiniteWarfare'' on the PC. Picking up any throwables in singleplayer will kick the player to the main menu with the message 'Could not allocate a reserved scriptable for entity x - limit is x - try increasing the number in the worldspawn entity in radiant.' The only solution is to increase your virtual memory in Windows to 4 GB or more, which causes the cutscenes to exhibit audio stuttering.

** On the penultimate mission where you discover [[spoiler:you were brainwashed]], you get punched while running down a corridor, however this sequence would often break and after being punched, Mason would be stuck in place and [[spoiler:Hudson]] would appear in his Vietnam gear complete with sunglasses, the unfunny part is you would be stuck and the level has no checkpoints as there's no combat in it so you have to start the entire mission again.
** The Vorkuta level in general is rather broken, from randomly crashing on PC to randomly refusing to react to audio cues on consoles (even if the player goes on with it like this, the game will eventually hang after the tear gas scene, the player stuck staring at the motorcycle they're supposed to drive for the last part of the level).

** ''World at War'' has semi-scripted sequences during banzai charges where being attacked by a charging Japanese soldier would cause the game to switch to the HUD-less "cinematic" view as he knocked you down, with a QTE to stab him in the neck and get back to the game. Should a lucky shot from an NPC kill the soldier at the exact moment where the banzai stab animation begins but before the player and soldier become invincible, the player will be stuck on the ground permanently (since there's no soldier to stab to return to the game) and the level needs to be restarted.

* ''VideoGame/BoilingPointRoadToHell'' was essentially a game strung together with fatal bugs, as well as a whole bunch of [[GoodBadBugs ones not completely fatal, but amusing nevertheless.]] Excerpts from the patch notes that fixed these problems are now somewhat of an Internet legend:

* ''[[VideoGame/FirstEncounterAssaultRecon F.E.A.R.]]'' had a little bit of an oversight that would render the game unbeatable. At one point, you're asked to download data from a laptop. However, there were laptops with downloadable data all around to get the backstory which look exactly like it, and you're told to download this data nearly two minutes ''after'' you see this laptop. But once you download data from a machine, you can't do it again, even with that mission critical laptop. The mission objectives also didn't say that it was completed. You basically have to restart from the last save and wait for the objective to be given, then download the data. One of the game's later patches fixed this, so that in the event that the player downloads that data before he's told to, Betters will tell them "I see you've already checked the laptop." and proceed as normal.

** In fact, just about every Survival map in both ''Left 4 Dead'' and ''VideoGame/Left4Dead2'' contain spots like these where almost nothing can reach you. In some spots, literally nothing can reach you allowing for utterly absurd times (people have managed to survive for ''days'' using some of these spots). The developers attempted to stop this from happening in Left 4 Dead 2 by spawning Spitter acid in areas that the game considers out of bounds but the addition of the Grenade Launcher meant that you could launch people up to spots where the acid can't spawn. And the thing is Valve can't patch this glitch; it would require completely retooling the physics engine, something that can't be done with a simple patch.
** In Left 4 Dead 2, throwing boomer bile into the safehouse at the start of a level, then having all but one person leave the saferoom, will cause all the zombies to go for the bile as usual. After the bile has run out, though, the zombies will try to kill the person inside, which they can't. With the massive group of zombies around the saferoom door, the game is unable to spawn anymore, allowing the remaining survivors to run through the rest of the level without any opposition, providing the person in the saferoom does not go idle. Special infected will still spawn, but otherwise, this makes every non-finale level pathetically easy.

* The original release of ''VideoGame/QuakeI'' total conversion ''Malice'' had a really bad example of this. In level 8 there is a deep shaft which the player has to parachute down in order to complete the level. But unfortunately the developers forgot to put the parachute in the level! This made it completely impossible to complete the level unless you used the 'fly' cheat from the console. A patch was hastily released by the rather embarrassed developers.

** The Chargin' Targe and the Splendid Screen once had their rate of turning be based on the player's framerate, rendering the weapons borderline useless on slower computers and borderline overpowered on more powerful ones. A side effect of this rendered the Ali Baba's Wee Booties pointless, because the main point of it was to give the player better control over charging; it's actual effects wavered between "negligible" and "''nothing at all''" depending on your rig. In fact, the sheer bizarreness of the bug made it unnoticed until [[https://www.youtube.com/watch?v=mT6iyZ16wkk this user]] showcased a video on how broken the shields actually were.

** Interestingly, the first time you can encounter this bug (the elevator leading to the surface in the level "We've Got Hostiles") it behaves slightly differently. Instead of immediately killing you, you just continuously take damage from some unknown entity. [[NightmareFuel/VideoGames Rather creepy, actually...]]
** This turns into an absolute nightmare in the final section of Interloper, where every single spinning D-pad elevator is susceptible to this bug. So on top of trying to navigate yourself and avoiding the fireballs of the flying aliens, you have to wildly jump up and down on the elevators to ensure no spontaneous deaths, and in the process, may very well jump and fall into the BottomlessPits below the elevator! And did we mention that sometimes, your jumping has to be on the ball, like you have to touch the elevator only ''just after'' it stopped? '''[[SaveScumming Quick Save is your friend.]]'''

* ''VideoGame/HalfLife2'' included a well-known bug near the end of the game (during the chapter "Our Benefactors") that made it impossible to proceed past a certain hallway. [[spoiler:The Confiscation Field in the Citadel incinerates all your firearms and supercharges the Gravity Gun,]] but moving around, jumping, or crouching while the field is in effect will make it impossible to jump at all, even after the field has turned off. This usually goes unnoticed until a few rooms later, when a seemingly innocuous waist-high fence becomes an impassable barrier. The only way to 'fix' the bug is to reload from an earlier save point or start the level over entirely.

* At one point in ''VideoGame/ShogoMobileArmorDivision'', you're supposed to take an elevator down along with your partner. Unfortunately, 90% of the time your partner would inexplicably explode into bloody chunks while riding the elevator with you (presumably the game somehow thought she was crushed by the very elevator she was inside.) Oh, and this was an EscortMission, so it's game over if it happens to you.
** Random deaths to the environment were a bit of a thing for early games on that engine. ''VideoGame/{{Blood}} II: The Chosen'''s in-engine cutscenes can still affect the player character while they're stuck in place due to said cutscene. One in particular in the second chapter is triggered while the player is walking through a door, which automatically closes just five seconds into said cutscene - if the player happens to be standing in the wrong spot, the door will push them into the door frame and [[TheDoorSlamsYou immediately crush them to death]]. [[GoodBadBugs Which the player will not be aware of until after the cutscene ends, except for the screen temporarily flushing red during it.]]

** The AI allies frequently glitch up and begin running into walls and you'll be unable to snap them out of it. Considering your allies need to be by your side to finish a level, this was game-breaking indeed. This isn't even getting into how your allies frequently kill themselves on every stage hazard they can find, resulting in an instant failed mission.

* The 1.0 versions of both ''VideoGame/{{Descent}}'' and ''Descent 2'' infamously had a fatal bug that caused their {{final boss}}es to be [[UnwinnableByMistake unbeatable]] on any difficulty higher than Rookie.
* In ''VideoGame/CallOfCthulhuDarkCornersOfTheEarth'' there is one infamous sequence in which you must fire at several enemies using a deck-mounted cannon. The problem is while the enemies are still there, you can't see them. Nobody knows what causes this bug, and the only known solution is to use the savegame of somebody fortunate enough to not encounter it.
** In another part of the game, there is a cart you are supposed to get onto. On some games, the game just plain refuses to let you advance. In a rage, people realized that shooting a specific point on the cart will let you on. Another way of bypassing the bug is to go back to the control panel of the cart and pushing ''again'' the button starting the (already) moving cart. Despite Jack saying that it did do anything, the invisible wall in the cart is now deleted.

* ''VideoGame/{{Marathon}} Eternal'' is a [[GameMod fan-made game]] using the open source version the engine. On the level "Roots and Radicals", there's a medium-sized room which spawns endless amounts of Enemy and Weapons sprites, not to mention unlimited Helpful Drones. Now, there is a wall next to the spawning pad which can not only be switched on to block off the troopers but smash them during their short run outside that area. Let them spawn instead of blocking off the path can make the game Unwinnable because Alephone will block off Hit Detection due to memory usage exceeding limits.

* In the original ''VideoGame/DeusEx'', it was possible for the player to bring the game to a grinding halt by succeeding when the game needs them to fail. At one point, the plot requires the player character to be arrested and detained at UNATCO headquarters. The main character emerges from a subway station and is confronted by a squad of UNATCO troopers, a cybernetically-augmented agent and a few heavy-duty bipedal combat robots. Normally, the player character can choose either to go quietly or get the tar whipped out of him and wake up in a UNATCO prison cell. However, skilled (or incredibly patient) players can pick off the troops who are meant to take the player down in a hail of bullets, leaving nobody alive but them. Unfortunately this also leaves them with no way to advance to the next chapter, and the player becomes stuck in the decrepit shanty town that surrounds the subway station.
** A subsequent patch fixed this by marking the augmented agent as invulnerable, meaning no matter how many grunts got mowed down there'd always be one unkillable badass ready to put bullets into the player.

* During the Operation Red Crow expansion for ''VideoGame/RainbowSix: Siege'', an operator named Hibana was added who's ability,on the PS4 version, could crash the game, disconnect players randomly or drop the Frame Rate to 0 for seemingly no reason ( bearing in mind the Xbox One and PC versions suffered no issue at all ) Ubisoft were quick to issue a patch ( about a day after the launch of the DLC ) that completely prevented PS4 players picking Hibana at all.
** This situation worsened when it was discovered that this fix actually prevented players from progressing past The End Of Season rewards pop up. Attempting to click through this pop up would result in the game crashing. With no other choice Ubisoft restored Hibana into the game, and thus the glitch with it.
* In the PC version of ''VideoGame/LegendaryTheBox'', the elevator that leads to the final battle will pass right through the player's body, causing them to fall through the floor and die. If you're affected by the bug, it will happen every time you try and is impossible to bypass without messing around with the game's .ini files. The developer's response? "Buy another computer, because [[CreatorsApathy we aren't going to fix this]]".

* The first ''VideoGame/RedFaction'' has the infamous submarine glitch. At one point, you have to get into an underwater lab, preferably using a submarine. Unfortunately, when being lowered with a crane, the sub will explode 99 times out of 100. While that water passage can be traversed without the submarine, it's suicide on higher difficulties and you can get stuck there with no way to advance. While this bug is frustrating, it is known to be caused by an overly high FPS rate, inevitable on new computers. Start compressing your harddisk in the background, though, and submarine ride is yours.
* The first ''VideoGame/SystemShock'' has received one as time goes on. First, it's designed for old MS-DOS systems, and won't run on modern Windows. Fine, there are plenty of good DOS emulators out there that can do the job. Here's the problem: the final battle is a TimedMission of sorts, as you have to destroy SHODAN before she finishes [[MindRape Mind Raping]] you. The countdown is not based on the clock, but instead on your processor cycles... which on a modern machine, run many hundreds of times faster than they did back when the game was released. This can easily render the final battle unwinnable, as there is no way to damage SHODAN enough before you die. You'll have to limit the processor speed on the emulator if you want to have a chance at this. [[UpdatedRerelease The Enhanced Edition]] intermittently fixes this bug (if it doesn't, enabling Vsync in options generally does the trick).

* During the Operation Red Crow expansion for ''VideoGame/RainbowSix: Siege'', an operator named Hibana was added who's ability,on the PS4 version, could crash the game, disconnect players randomly or drop the Frame Rate to 0 for seemingly no reason ( bearing in mind the Xbox One and PC versions suffered no issue at all relating to Hibana ) Ubisoft were quick to issue a patch ( about a day after the launch of the DLC ) that completely prevented PS4 players picking Hibana at all until a patch was issued to fix the bug.

* In the PC version of ''VideoGame/LegendaryTheBox'', the elevator that leads to the final battle will pass right through the player's body, causing them to fall through the floor and die. If you're affected by the bug, it will happen every time you try and is impossible to bypass without messing around with the game's .ini files. Developer Gamecock's response? "Buy another computer, because we aren't going to fix this".

* The first ''VideoGame/SystemShock'' has received one as time goes on. First, as it's designed for old MS-DOS systems, and won't run on modern Windows. Fine, there are plenty of good DOS emulators out there that can do the job. Here's the problem: the final battle is a TimedMission of sorts, as you have to destroy SHODAN before she finishes [[MindRape Mind Raping]] you. The countdown is not based on the clock, but instead on your processor cycles... which on a modern machine, run many hundreds of times faster than they did back when the game was released. This can easily render the final battle unwinnable, as there is no way to damage SHODAN enough before you die. You'll have to limit the processor speed on the emulator if you want to have a chance at this. [[UpdatedRerelease The Enhanced Edition]] intermittently fixes this bug (if it doesn't, enabling Vsync in options generally does the trick).

* In the PC version of ''VideoGame/LegendaryTheBox'', the elevator that leads to the final battle will pass right through the player's body, causing them to fall through the floor and die. If you're affected by the bug, it will happen every time you try and is impossible to bypass without messing around with the game's .ini files. Developer Gamecock's response? "Buy another computer, [[TheyJustDidntCare because we aren't going to fix this]]".

* The first ''VideoGame/SystemShock'' has received one as time goes on. First, as it's designed for old MS-DOS systems, and won't run on modern Windows. Fine, there are plenty of good DOS emulators out there that can do the job. Here's the problem: the final battle is a TimedMission of sorts, as you have to destroy SHODAN before she finishes [[MindRape Mind Raping]] you. The countdown is not based on the clock, but instead on your processor cycles... which on a modern machine, run many hundreds of times faster than they did back when the game was released. This can easily render the final battle unwinnable, as there is no way to damage SHODAN enough before you die. You'll have to limit the processor speed on the emulator if you want to have a chance at this. [[UpdatedRerelease The Enhanced Edition]] intermittently fixes this bug (if it doesn't, enabling VSYNC generally does the trick).

* While rare, it was possible in the first ''Franchise/{{Halo}}'' to checkpoint right at a point of inevitable death. Hello, sticky grenade. This would trap your character in a CycleOfHurting and force you to go back to the start of the level. Future games had a failsafe feature that reverted the game to an earlier checkpoint after a certain number of deaths in such a situation.

* In ''VideoGame/{{Battlefield}} 2142'', you could move the Titans around, allowing you to use their weapons in an effort to win the round. Unfortunately, doing so lagged many servers as they moved about, not to mention during firefights on a moving Titan, bodies would glitch through the floor, preventing them from being revived. Dice eventually patched the game so that servers could disable Titan movement, unfortunately removing a otherwise useful tactic of the game mode, as most servers went with the disable movement option.

** Its other bug is that at some point, the taped messages you find - which explain the story and set up the motivation of the Jackal, who is the guy you're hunting and your entire reason for being there - stop being new messages after the first one you find in the South half of the game. After that point, every tape you find has the same message on it, which means that the Jackal's character development stops halfway, destroying the storyline. You can still play though, the plot resolution just doesn't make any sense.

** Its other bug is that at some point, the taped messages you find - which explain the story and set up the motivation of the Jackal, who is the guy you're hunting and your entire reason for being there - stop being new messages. After that point, every tape you find only has the same message on it, which means that the Jackal's character development stops halfway, destroying the storyline. You can still play though, the plot resolution just doesn't make any sense.

** An update patch for the XBox360 version of ''FarCry3BloodDragon'' causes the game to crash with a "Disc Unreadable" error during the intro, at least on certain console models.

** If the Patriarch spawns within eyesight of the players, the game will keep everyone in the observer camera mode and refuse to give them control again until it has already had the chance to attack them. Thankfully, this is very rare.

* While rare, it was possible in the first ''Franchise/{{Halo}}'' to checkpoint right at a point of inevitable death. Hello, sticky-grenade. This would trap your character in a CycleOfHurting and force you to go back to the start of the level. Future games had a failsafe feature that reverted the game to an earlier checkpoint after a certain number of deaths in such a situation.

** This is also a problem with the floating platforms in Xen and the earlier parts of Interloper. Most of them don't have this problem; the buggy ones are located near the bottom in Xen and at least one exists in the first two parts of Interloper. And sometimes for these guys, all you need is to ''even land on them in the first place'' to trigger this bug. [[CallBack Did we mention Quick Save is your friend?]]

** ''Half-Life: Opposing Force'' has a door about 2/3 of the way through the game which, if opened, may crash the game. Unfortunately, opening this door is also the ONLY way to progress. There are a number of tutorials online on how to engage noclip and skip straight to the next working point in the game - it seems that whatever is behind the door is what crashes the game, not the act of opening it, because even looking in that direction while noclipping triggers the crash, hence the need for tutorials instructing how to noclip to the next area.

* ''VideoGame/TheHouseOfTheDeadOverkill'' hits the player with one during the Crawler boss fight. The only way to avoid taking damage from Crawler's swipes is to shoot its claw as it prepares to attack. However, on occasion, Crawler won't take damage even if you shoot the marked weak spot. The result: you're forced to take several hits until Crawler switches locations.
** The game's "Extra Mutants" mode (which adds enemies to a level) appears to be an afterthought, as enemies spawn in inconvenient (for the game) locations. In one scene in "Ballistic Trauma" where hospital doors blow open and zombies swarm out, one female zombie only present on Extra Mutants can get stuck behind one of the doors. You can't kill her, and the scene won't advance until all enemies are dead. UnwinnableByMistake ensues.
** Not quite game-breaking, but there seems to be a rare bug where mutants forget you're in cutscene mode (i.e. unable to shoot any of them) and start attacking you anyway.

* The first release of ''VideoGame/SiN'' had a rather nasty bug during the Chambers of Darwin trials. After the second chamber, a guard is supposed to open a tunnel passage for the third one. Actually, the soldier keeps redirecting you to the tube, without opening it: more frustration comes through the fact that ''you're slowly dying during the tests''. A couple of months later, Ritual released a patch to cure this glitch.

* The first ''VideoGame/RedFaction'' has the infamous submarine glitch. At one point, you have to get into an underwater lab, preferably using a submarine. Unfortunately, when being lowered with a crane, the sub will explode 99 times out of 100. While that water passage can be traversed "on foot", it's suicide on higher difficulties and you can get stuck there with no way to advance. While this bug is frustrating, it is known to be caused by an overly high FPS rate, inevitable on new computers. Start compressing your harddisk in the background, though, and submarine ride is yours.

** There's also a bug where you get stuck inside an elevator platform, making it impossible to move, the only way out being either a noclip cheat, or reloading the game and hopping like a complete idiot while riding the elevator in hopes that this will prevent the bug.

* When ''VideoGame/DukeNukem3D'' was converted to the Xbox, the team carefully scrutinised the level data for game-breaking glitches, and found just one -- in [=E4M9=], "Critical Mass", there's a staircase (and a room at the top of it) which collapses and becomes impassable once passed. This isn't a problem in single-player, as the level is reset should the player die, nor in deathmatch, because in that mode there's a switch to open a teleporter to bypass the collapsed section; but in co-operative mode, it's possible for one or more players to die and thus be stranded at the start of the level. This was fixed for the Xbox version by making the above mentioned switch appear in co-op mode as well as deathmatch. It is not known whether this was ever fixed in the PC version.

* The first ''VideoGame/SystemShock'' has received one as time goes on. First, as it's designed for old MS-DOS systems, and won't run on modern Windows. Fine, there are plenty of good DOS emulators out there that can do the job. Here's the problem: the final battle is a TimedMission of sorts, as you have to destroy SHODAN before she finishes [[MindRape Mind Raping]] you. The countdown is not based on the clock, but instead on your processor cycles... which on a modern machine, run many hundreds of times faster than they did back when the game was released. This can easily render the final battle unwinnable, as there is no way to damage SHODAN enough before you die. You'll have to limit the processor speed on the emulator if you want to have a chance at this.

** The Chargin' Targe and the Splendid Screen once had their rate of turning be based on the player's framerate, rendering the weapons borderline useless on slower computers and borderline overpowered on more powerful ones. A side effect of this rendered the Ali Baba's Wee Booties pointless, because the main point of it was to give the player better control over charging, but it actually did ''nothing at all'' in reality. In fact, the sheer bizarreness of the bug made it unnoticed until [[https://www.youtube.com/watch?v=mT6iyZ16wkk this user]] showcased a video on how broken the shields actually were.

* The first ''VideoGame/SystemShock'' has received one as time goes on. First, as it's designed for old MS-DOS systems, and won't run on modern Windows. Fine, there are plenty of good DOS emulators out there that can do the job. Here's the problem: the final battle is a TimedMission of sorts, as you have to destroy SHODAN before she finishes {{Mind Rap|ing}} you. The countdown is not based on the clock, but instead on your processor cycles... which on a modern machine, run many hundreds of times faster than they did back when the game was released. This can easily render the final battle unwinnable, as there is no way to damage SHODAN enough before you die. You'll have to limit the processor speed on the emulator if you want to have a chance at this.

* The first ''VideoGame/RedFaction'' has the infamous submarine glitch. At one point, you have to get into an underwater lab, preferably using a submarine. Unfortunately, when being lowered with a crane, the sub will explode 99 times out of 100. While that water passage can be traversed "on foot", it's suicide on higher difficulties and you can get stuck there with no way to advance. While this bug is frustrating, it is known to be caused by an overly high FPS rate, inevitable on new computers. Start compressing your harddisk in the background, though, and submarine ride is yours.