Now that the man’s winding down his career, let us honor Yu Suzuki for his most important contribution to game design: the QTE. Hey now. I can hear you rolling your eyes. We might be sick of pressing the X button every single time Crystal Dynamics wants Lara Croft to kick a tiger with style, but the quick time event provides us with some of videogames’ most satisfying thrills. They aren’t inherently bad. They’re just implemented very, very poorly. This week, you’ll be able to walk out into the world and pick up a copy of From Software’s Ninja Blade. Hell, you can go home right now and download a demo of Ninja Blade just to have a taste. One level is all you need to exemplify just how good quick time events can be in a game.
Here’s why.
First, a definition. In God of War’s wake, “quick time event” has transformed from a noun into a sort of critics’ short hand. It’s a blanket term to describe when, in a game where you have direct control of a character, the normal control is taken away and you watch a unique or atypical animation. While the animation plays, you must press a specific button as prompted on the screen. If you don’t, you’ll have to replay the sequence. Now, there are many parts of modern games that can be described this way and not all of them are quick time events. For example, in action games like MadWorld and Yakuza 2, you’re prompted with special inputs — press X next to a car, swing the Wiimote down — to finish off enemies. The most colorful finishing moves have you stringing these inputs together. These are not quick time events. They’re contextual actions. A quick time event is a choreographed, dramatic sequence where prompts imitate an action that you do not have direct control over. Resident Evil 4 has some classic examples. You, the player, steer Leon to the top of a hill and move forward. The game then shifts the camera to a group of enemies on a cliff above you. They push a boulder off said cliff that chases you and to escape you repeatedly press a button, which keeps Leon running. That button has nothing to do with movement during regular play. If you don’t press it here, the game ends. That’s a quick time event. They can, and have, enrich games with emotionally charged moments the game wouldn’t have otherwise.
The chief argument against quick time events is that they pull you out of a game by stripping away control, if only partially. They’re gaudy cheats to mask the passive storytelling devices of film instead of relying on a game’s interactivity to inform its drama and incident. It’s a valid argument against bad quick time events. The most recent games starring the aforementioned Lara Croft, particularly Tomb Raider Legend, have terrible quick time events made up of sixty second cinematics halved by a single, easy to miss button press. When implemented well, though, a quick time event is anything but a mask for inactive game sequences, as in Quantic Dream’s Indigo Prophecy. The game allows you limited sequences of full character control, relying on quick time events with inputs that imply the action to make up most of the play. Lucas Kane is running from police officers and needs to dodge left so you’re prompted to press both analog sticks in that direction. You aren’t moving Lucas, but the movement of both sticks translates as urgency, and agency, for you. These QTEs are fast to match the pace of the game and end up making for affecting play because of their speed and mimicry of the action. That’s the key to QTE success; tying your input as close to possible to dramatic actions that are impossible to depict, or make interactive, in the game itself.
Ninja Blade’s first level is about half quick time events and they are incredible spectacles. The level ends with a fight against a giant, grotesque spider on top of a skyscraper. The first part of the fight is familiar three-dimensional action; you move around with the level analog stick and press X, Y, and B buttons on the Xbox 360 controller to slice and stab with a sword. The second part, after whittling down the spider’s defenses, has you riding the spider up a skyscraper before riding a wrecking ball across the night sky, and then crushing the spider with it. There isn’t a way in games to make this one-hundred percent interactive and retain its presentation. Not yet at least. So sequence is a quick time event, and through a mixture of rumble in the control, speed of button prompts, and inputs that approximate other actions in the normal game, it’s completely engaging.
Like I said, QTEs don’t damn a game. They’re just another tool. Quality depends on the craftsmen.
Related links:
Love-Hate: In Defense of the Cutscene
Overpowering the Flavor: Cooking Mama World Kitchen and Cutscene Clutter
Whatcha Playing: Weight of the Stone
Sonic Unleased: Worse Than Syphilis
Sega's Yu Suzuki Steps Down
Where is Yu Suzuki?