Quick Time Events
Sequences of interface actions given by games that players need to perform at once.
Games need to give players challenges and one of the simplest forms to achieve this is for them to give players simple instructions that have to be performed immediately. Quick Time Events are formalized versions of this in computer-based games where they provide a sequence of instructions, often accompanied by animations of diegetic events. Failing to perform these quite often lead to the death of players' characters but can also just result in more unfavorable outcomes.
Contents
Examples
The Dragon's Lair series was an early example of games that used Quick Time Events to let players avoid having their characters dying while trying to free a princess kidnapped by a dragon. While in this game all the actual gameplay was in form of Quick Time Events, later games such as the Shenmue series, Fahrenheit, and Heavy Rain uses Quick Time Events interjected with other types of gameplay.
The WarioWare series can be said to consist of a large collection of mini games that are actually Quick Time Events. Likewise, the main interaction provided by the toy Simon[1] can be said to be Quick Time Events.
Wikipedia has an entry about Quick Time Events including several examples[2]
Using the pattern
The gameplay aspects of design Quick Time Events are rather straight forward: what sequences of actions players need perform and when the events should occur. While some games (e.g. the Dragon's Lair series and the WarioWare series) consist only of Quick Time Events, others use them to handle situations that are not covered by the main gameplay actions (e.g. Fahrenheit and Resident Evil 4). Obviously, they require that the games are Real-Time Games. Succeeding with Quick Time Events does not often provide Rewards to players; it is more common that Penalties are handed out for failing to follow the instructions and these Penalties are often harsh, e.g. the death of player's Avatars.
Although not that common, Quick Time Events can let players choose from several actions to perform to let them have a Limited Set of Actions.
Diegetic Aspects
As a form of Cutscenes, Quick Time Events can provide specific presentations of Game Worlds but - as the Simon toy shows - this is not always the case since some Quick Time Events are abstract.
Narrative Aspects
Quick Time Events can, like Cutscenes, be used to convey parts of Predetermined Story Structures.
Consequences
Quick Time Events are a way of introducing Rhythm-Based Actions (which may devolve into Button Bashing) into games in the form of Cutscenes or Minigames. They give players explicit Ephemeral Goals and the arrival of these can be Surprises that give Tension.
In games where Quick Time Events are context-specific events with specifically produced animations, they can make players feel that the game designers are trying to engage in Player Killing since the events have very consciously been designed to try and kill them in that given situation.
Quick Time Events can work against Spatial Engrossment since they give players instructions of what to do through Non-Diegetic Features. This can also work against them fully appreciating the production work put into any animations that are part of the Quick Time Events.
Relations
Can Instantiate
Button Bashing, Cutscenes, Ephemeral Goals, Limited Set of Actions, Minigames, Non-Diegetic Features, Player Killing, Rhythm-Based Actions, Surprises, Tension
Can Modulate
Predetermined Story Structures, Real-Time Games
Can Be Instantiated By
-
Can Be Modulated By
Possible Closure Effects
-
Potentially Conflicting With
History
New pattern created in this wiki.
