Quick Time Events. So many games have used them to some extent in the last five years that just about every gamer has an opinion on them. Mine is that they are the worst gameplay gimmick to take the industry by storm in a long time, and I wouldn't mind seeing them all packed into a burlap sack filled with leeches and thrown into the depths of a volcano. They're tacky, they're unintuitive, and their attempts to engage players in cinematic animations backfire and break the sense of immersion one has with a game. And unfortunately for me, they're just about everywhere these days.
Two behemoths let loose in early 2005 can be thanked -- or blamed -- for the salvo of games that have featured QTEs in the last five years. The first, with a January 11 release date, was Resident Evil 4. The game was extremely well-received: it won many Game of the Year awards, offered a fresh take on the aging Resident Evil formula, and gave Gamecube owners a third-party exclusive worth bragging about. The other member of the gruesome twosome that brought us into the era of QTEs is known as God of War. Released just two months after Resident Evil 4, the game received just as many accolades and turned heads back to the PS2 as quickly as they'd been lost to the Gamecube's horror hit. Is it any wonder that the industry went in the direction it did when two such monumental successes as these both prominently featured a relatively unused gameplay gimmick?
Today we'll take a look at how the smart use of QTEs helped put these two games on the map, and watch a few examples of QTEs gone wrong. And trust me, there was a huge pool of resources for the latter.