This generation of video games is known by many names, some more successful than others: the DLC generation, the sequel generation, the digital format generation, or the generation of bugs a cascoporro. Well, we are going to focus on the latter, and with nuances.
Yes, it is the generation of errors, but that does not mean that in the past there were not. Because there were. Not so many in comparison, but also because many of today's games require much more development time, with developers mincing code until the wee hours of the morning and with more complex functions. Everything is more complex.
Hence, being human as we are, we can err. Except now, unlike before, it can be corrected. Well, with the PC generation it was already possible in the form of an update, but with today's consoles it can also be done. And of course, this results in that sometimes a product comes out in a hurry and then it is corrected. Yes, it is ugly. Especially considering that not everyone, oddly enough at this point, has access to the Internet to download the update on duty to correct these errors.
Despite this, it is also true that products are reviewed before they are published, and that there are beta-testers who are dedicated to going through every nook and cranny of a product over and over again looking for any flaws. But even with everything there is never the total certainty that it does not have any fault. Without going any further, I have a kind of curse about this, since I usually find faults of all kinds. Partly also (I imagine) because of my curious nature and restless ass when I face a new world. "Go to such a place." No, you leave me to myself ... And then the problems come, of course. Damn scripts ...
How errors in video games is something that will never go out of styleToo bad we are, and in view of the fact that I have recently found more errors, what better way than to review those that, in my opinion, are the XNUMX bugs that completely screw up the gaming experience. Or, speaking in silver, five bloody mistakes in video games. And with first-person examples, too.
Corrupted game due to autosave
What is the term used to talk about code errors in English? Bug. And what is that translated into our language? Bug. Just the kind of species we think of as a worm. And where can we see worms? In the new ‘Worms Revolution’ by Team 17. To say that I was looking forward to it is an understatement. Not for nothing have I been (am) worms-addicted since I tried the original on my Amiga 500.
As soon as I debuted in the usual download services, I bought it, and started with it. After getting through the required (and boring) tutorials, I started the real campaign, customized my gear, spent in-game money buying some bullshit for my worms, unlocked the scientist worm, and even tried (not without enduring multiple failed attempts) the mode online against three strangers. So far so good. The problem came the next day, when I wanted to continue advancing in the campaign and in the challenges to be able to launch myself later with its analysis, and that is that I got this warning message:
“The saved file is corrupted and progress has been lost. The file will be overwritten the next time you save "
And of course, it bothered me the unspeakable, because nothing made me suspect that it had been saved badly at the end of the game the day before. Since then I have it parked there, because I refuse to replay that mandatory tutorial to get to where I got in the campaign. All because of one of the worst additions of recent generations: automatic saving. To the stake with him.
A script that fails: either we reboot or we stay there
Another resource that I detest the most of this generation is scripts abuse, those events that have to occur when arriving at a site, when performing certain actions. In theory we cannot miss them. But of course, sometimes something fails, and consequently the script does not load. Outcome? That we get stuck, unable to do anything, with the only solution to restart the game or load in a previous scene if the game has several save slots. Thing this last thing that we could not do before a game with automatic save ... They combine both and ... boom!
One of the errors that most discouraged me and of which I have visual proof is the one related to 'Dante's Inferno' from Visceral Games and published by EA. As I described in my YouTube profile to explain to those responsible for the game itself, in an area of worldly splendors, after collecting a relic and ventilating all the enemies in a room, I took a few steps back to save game and return to that living room. The problem is that when he returned to that room he could no longer activate the lever to continue advancing. And of course, there was nothing he could do anymore. Luckily it was later fixed via patch. But we are not always lucky enough to see these types of bugs fixed. The video was this:
Video | Youtube
Screen freezes: we have to restart the console
Who says console also says PC, of course. Any entertainment platform. Because do not tell me that it has never happened to you, that of playing a game and that suddenly, for no apparent reason, "the game gets caught." With screen frozen. Without responding to any action. The only solution, therefore, is to reboot the device, and trust that this inconvenient error will not happen again. Oh! Naive that we are… Yes it can happen. In some cases for life, of course.
It happened to me recently with him ‘Hell Yeah! Wrath of the Dead Rabbit’ of Arkedo Studios taking advantage of the gift of PSN Plus, and luckily it did not corrupt my game, but if I have to give a bloody and repetitive example is that of ‘Battlefield: Bad Company’. I have such power that I can cause that failure. Yes, as it sounds. How? Very simple. In online mode, instead of selecting Quick Game I choose Custom Game, and boom! The screen and the game itself freeze. Or well, it froze. Because I just put the game back on and to my surprise, after a year and a half of complaints, shortly after my vice with 'Battlefield: Bad Company 2', it no longer fails. I have finally been able to see the custom game options! Seeing is believing, never better said. But this is the exception, since in its day I even registered in the EA forums to explain the problem and I was not ignored. I don't know why this has been fixed by itself (countless times I've entered custom game), but better not touch it.
Failure to delimit the walls or floors
This error is very common since we enter the three dimensions. We move forward as if through a field and suddenly we sink, we begin to see everything blue, as if it were the sky ... but in reality we are below the ground. Or we try to go through a wall and before finding it, a couple of meters before, we see an invisible barrier that prevents us. Or the other way around, we go through the wall and come to an unexplored area ... and that shouldn't be there. Examples there are thousands.
Of this, as expected, I have many examples. Of the first, you could remember, for example, the ‘Lineage II’, contemplating, to my amazement, how "I fell without falling." Of the second I could give the example of ‘Homefront’, which abuses the invisible barriers a lot (too much) in campaign mode, which certainly breaks the magic of the game. And from the third, with an added error (that of dying), from the recent 'Borderlands 2' and that I have about candy for analysis, to all this.
The error in question is about an outpost, in Thousand Cuts, right next to the subject of the mission "A shot in the other's face" (top of the map; see photo). As an explorer that I am, I like to explore each area in depth, and if I see a path that can be passed, then I pass, as I am. In that area there is a small drop over a cliff. The funny thing is that reaching almost the end of that path the character dies. It is not that he falls into the void and dies, no. He "stumbles", falls to the ground (off the road), and dies. You can do the test, if you want. Go there if you see yourself loose of money.
AI (Artificial Intelligence) gets stuck and slows down the game
Another classic error, that of AI (Artificial Intelligence). Everyone knows that much progress has been made in this field, but before things were more limited, more experimental. And of course, there could be situations in which the machine was not able to react correctly, such as a narrow passage, forming a significant bottleneck that led to a drop in the performance of the game itself. Yes, the dreaded slowdowns. Either we would solve the problem ourselves (cleaning the problem with lead, or whatever), or things could get worse and even cause the game to crash. Come on, a whole poem. Although today it is more difficult to see this.
My most graphic memory of this error is without a doubt that of the first two ‘Command & Conquer’, both ‘Tiberian Dawn’ as the ‘Red Alert’. This error occurred 99,9% of the time when the AI sent us a mass of tanks and troops of different fur through narrow passages, causing a significant slowdown (especially in Playstation and Saturn) that we could only solve, as already we go ahead, eliminating that mass with our lead. Or with a nuclear bomb, as we were. Without going any further, I remember that in the PSone version I frequently used the bomb trick when the machine got stuck, otherwise the games would lengthen exponentially in terms of duration. It goes without saying that there were other types of errors, such as the sandbags, but in this case they were forgiven, especially for extra missions, such as Covert Operations and others. This gave us time to form our army and set up the base well. Sandbags FTW!
These have been just five examples. Those that personally irritate me the most (saving the specific detail of the sandbags), although there are others, such as that of sloppy translations into our language. Yes, we must be grateful for translating a product, but not at any price. That sometimes you see blunders and senseless fat people. And it can't be either.
