The Elder Scrolls V: Skyrim - 10 Video Game Actions That Broke Video Games
Hi folks, it's Falcon and today on GameRanks are 10 article game actions that crash your game.
starting off at number 10 in WWE 2K20, playing the game on January 1st, 2020. Like wwe 2k20 was and still is a mess of a game, but most of its many bugs are not game breaking. This bug, though, would absolutely crash your game for the crime of playing it in the year 2020.
Yeah, it's basically Y2K all over again. For whatever reason. WWE 2K20 would completely crash the game as players booted it off in the new year, and it definitely had something to do with the year 2020, because the method to get around this was to set your system clock to the previous year. I mean, all right.
So it's a bug that 2K managed to squash relatively quickly, but once again, it is one of many bugs. It is just beyond ridiculous that this is a game literally called "WWE," 2K20, and if you tried to play it in the year that the game itself takes place in, it would crash. It's just another thing to add to the pile of things that make this game an absolute mess, but it's perhaps the most glaring, ridiculous, and yes, game-breaking.
And number nine in model war and fair three, try staying close to some friendly tanks as they go down a specific street in the goal post level. This will cause the infamous reliable command buffer overflow bug. It's super annoying and I'll go into a little bit more detail on the PC. In Call of Duty: Modern Warfare 3, you have to go exactly where the game wants you to go at a certain moment or the game will crash.
This reliable command buffer overflow can be found in a few different spots in the game, but the most well-known and therefore most reliable is in Is this part of the level goal post and Act 2 of the game? After you leave the parking garage section level, you're supposed to keep pushing on the road, but if you actually do that, the game is likely to crash, and it's not something that's been totally fixed either.
There are still people complaining about this glitch out there even now, and it's even specifically referred to in this game's entry on the PC gaming wiki, so it's a pretty common problem. Actually, what you're supposed to do is go into the side building and continue down that way instead of continuing to move forward.
There's no way to continue down the road like you eventually hit a dead end. Even if you aren't affected by the glitch by some miracle, it's probably one of those bizarre ways to crash a game by going down a road rather than into a building.
Half life 2
And number eight in Half-Life 2, when you lure a poisoned headcrab zombie into a barnacle. So the barnacle is one of the Half-Life series' most annoying enemies. If you've played it, you know exactly what we're talking about. These monsters hang from the ceiling and try to grab you with their big tongues.
They're pretty indiscriminate about what they'll eat too. For one thing, the poison headcrab and zombies. For whatever reason, the game cannot handle it if a barnacle manages to grab one of these guys. And, yeah, it still works. Even now, the game just immediately crashes if one of these nasty dudes touches the tongue of a barnacle.
I guess it has something to do with the physics engine. I mean, I don't really know, but it always works like consistently , and it's number seven on the normandy in Mass Effect 3.
Mass effect 3
If you stand on the exact wrong spot on the bridge, you know the command center for the entire three-game series.
If you find the wrong spot between Joker and Edie, you will get stuck permanently. You can't keep playing the game, period. It's so bad that it happens in a place that you thought was safe, like the bridge. Most players that get hit by this bug are forced to reload a save that's like an hour old, or you know, oftentimes an auto save isn't a great thing to lean on, and who really expects the game to freeze in the heart of the ship, the place you spend probably the most reliable amount of time constantly.
It was safe in the last two Mass Effect games, but just dixie-there for good in Mass Effect 3. And it's still an issue, at least if this comment from January this year on the official ea support forum can be believed. It is the original version of Mass Effect 3, not the redone one, but I mean it still has a ton of issues. This version of the game is blatantly bad as this one is.
And number six, if you play too many hours in Oblivion. The Elder Scrolls games are meant to be played for a very long time. There's a ton of content, and if you want to do all of it, it's going to take literally hundreds of hours for players that like to spend a lot of time with the game.
That's no big deal, but the issue here is that the game starts to break down the longer you end up playing it. The issue is actually fairly common with a lot of their games. Fallout New Vegas has the same issue where the game starts to run slower and less stable the more you play, but Oblivion probably has the worst, especially on consoles.
It's known as the "a-bomb bug." You have to play the game for an extremely long time, like 400-500 hours, but when it hits, it hits hard. What's really game-breaking is that stuff like oblivion gates just stop working, like regular dungeon gates even stop functioning. You can't progress in the game without those things.
It all seems to be some kind of memory leak issue, and players have used dozens of different methods to work around it, but if you're playing on consoles like the Xbox 360, you're basically screwed. I feel like there is a Bethesda game metaphor in there somewhere.
At number five in Assassin's Creed Brotherhood When you use the tunnels When it first came out, Assassin's Creed Brotherhood had a pretty nasty bug. All you had to do was use the tunnels that act as sort of a fast travel system in the game.
That's it they just use them and then the game will be totally broken down for some reason. It would be impossible to leave the damn tunnels, and Atio would get stuck just going through the tunnels forever. What made this worse was that there was nothing you could do if you got hit by this bug. You'd be trapped down there forever.
The only fix was to start a new game and hope it didn't happen again. What makes this so bad is that the tunnels were not optional. You go into these dark tunnels and you could be trapped there forever. It'd be really spooky if it wasn't so infuriating.
Mario kart ds
and number four in Mario Kart DS is holding two buttons and turning. It's one of the most randomly specific but really easy to replicate bugs I have ever seen to crash Mario Kart DS. Like literally freezing the game right on the spot. All you have to do is play the Luigi's Mansion track drive until you get to the steps that lead to the mansion and then hold a and b at the same time and turn.