Quick Time Events - Revision history

Staffan Björk at 15:39, 28 July 2014

2014-07-28T15:39:16Z

← Older revision		Revision as of 15:39, 28 July 2014
Line 32:		Line 32:

	[[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]].		[[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]].

			[[Scripted Information Sequences]] is an alternative to [[Quick Time Events]]; the difference between them is that [[Scripted Information Sequences]] take place without players being able to affect them but also leaves them free to do other actions.

	== Relations ==		== Relations ==

Staffan Björk at 15:27, 28 July 2014

2014-07-28T15:27:03Z

← Older revision		Revision as of 15:27, 28 July 2014
Line 42:		Line 42:
	[[Non-Diegetic Features]],		[[Non-Diegetic Features]],
	[[Player Killing]],		[[Player Killing]],
			[[Predetermined Story Structures]],
	[[Rhythm-Based Actions]],		[[Rhythm-Based Actions]],
	[[Surprises]],		[[Surprises]],
Line 47:		Line 48:

	=== Can Modulate ===		=== Can Modulate ===
	~~[[Predetermined Story Structures]],~~
	[[Real-Time Games]],		[[Real-Time Games]],
	[[Traps]]		[[Traps]]

Staffan Björk at 12:26, 17 October 2011

2011-10-17T12:26:36Z

← Older revision		Revision as of 12:26, 17 October 2011
Line 27:		Line 27:

	== Consequences ==		== 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]].		[[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]]. They provide one option for game designers to let players have chances to avoid [[Traps]] (besides using [[Movement]] to avoid triggering them or moving out of their effect).

	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.		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.
Line 48:		Line 48:
	=== Can Modulate ===		=== Can Modulate ===
	[[Predetermined Story Structures]],		[[Predetermined Story Structures]],
	[[Real-Time Games]]		[[Real-Time Games]],
			[[Traps]]

	=== Can Be Instantiated By ===		=== Can Be Instantiated By ===

Staffan Björk at 09:06, 18 September 2011

2011-09-18T09:06:01Z

← Older revision		Revision as of 09:06, 18 September 2011
Line 1:		Line 1:
	~~[[Category:Staffan's current workpage]]~~
	[[Category:Patterns]]		[[Category:Patterns]]
	[[Category:Mechanical Patterns]]		[[Category:Mechanical Patterns]]
Line 7:		Line 6:
	''Sequences of interface actions given by games that players need to perform at once.''		''Sequences of interface actions given by games that players need to perform at once.''

	Games need to give players challenges and one of ~~this~~ simplest forms 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.		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.

	=== Examples ===		=== Examples ===
Line 17:		Line 16:

	== Using the pattern ==		== 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]] do not often provide [[Rewards]]~~. Rather,~~ [[Penalties]] are handed out for failing to follow the instructions and these are often harsh, i.e. the death of player's [[Avatars]].		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]].		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]].

Staffan Björk at 09:00, 18 September 2011

2011-09-18T09:00:16Z

← Older revision		Revision as of 09:00, 18 September 2011
Line 17:		Line 17:

	== Using the pattern ==		== 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]].		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]] do not often provide [[Rewards]]. Rather, [[Penalties]] are handed out for failing to follow the instructions and these are often harsh, i.e. the death of player's [[Avatars]].

	[[Penalties]]

	[[~~Limited Set of Actions~~]]

			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 ===		=== Diegetic Aspects ===
Line 32:		Line 29:
	== Consequences ==		== 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]].		[[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]].		[[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]].
Line 40:		Line 39:
	[[Cutscenes]],		[[Cutscenes]],
	[[Ephemeral Goals]],		[[Ephemeral Goals]],
			[[Limited Set of Actions]],
	[[Minigames]],		[[Minigames]],
	[[Non-Diegetic Features]],		[[Non-Diegetic Features]],
			[[Player Killing]],
	[[Rhythm-Based Actions]],		[[Rhythm-Based Actions]],
	[[Surprises]],		[[Surprises]],
Line 54:		Line 55:

	=== Can Be Modulated By ===		=== Can Be Modulated By ===
	-		[[Penalties]]

	=== Possible Closure Effects ===		=== Possible Closure Effects ===

Staffan Björk at 08:53, 18 September 2011

2011-09-18T08:53:40Z

← Older revision		Revision as of 08:53, 18 September 2011
Line 2:		Line 2:
	[[Category:Patterns]]		[[Category:Patterns]]
	[[Category:Mechanical Patterns]]		[[Category:Mechanical Patterns]]
	~~[[Category:Needs work]]~~
	[[Category:Needs revision]]		[[Category:Needs revision]]
	~~[[Category:Needs examples]]~~
	[[Category:Needs references]]		[[Category:Needs references]]
	[[Category:Patterns created on the Wiki]]		[[Category:Patterns created on the Wiki]]
	~~[[Category:Stub]]~~		''Sequences of interface actions given by games that players need to perform at once.''
	''~~The one-sentence "definition"~~ that ~~should be in italics~~.''

	~~This pattern~~ is a ~~still a stub~~.		Games need to give players challenges and one of this simplest forms 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.

	=== Examples ===		=== Examples ===
Line 20:		Line 17:

	== Using the pattern ==		== 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]]).		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]].

			[[Penalties]]

			[[Limited Set of Actions]]


	=== Diegetic Aspects ===		=== Diegetic Aspects ===
Line 31:		Line 33:
	[[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]].		[[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]].

	[[Quick Time Events]] can work against [[Spatial Engrossment]] since they give players instructions of what to do through [[Non-Diegetic Features]].		[[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 ==		== Relations ==
Line 45:		Line 47:

	=== Can Modulate ===		=== Can Modulate ===
	[[Predetermined Story Structures]]		[[Predetermined Story Structures]],
			[[Real-Time Games]]

	=== Can Be Instantiated By ===		=== Can Be Instantiated By ===

Staffan Björk: /* Using the pattern */

2011-09-18T08:41:59Z

Using the pattern

← Older revision		Revision as of 08:41, 18 September 2011
Line 20:		Line 20:

	== Using the pattern ==		== 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. ~~They~~		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]]).



	=== Diegetic Aspects ===		=== 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.		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.

Staffan Björk: /* Examples */

2011-09-18T08:38:37Z

Examples

← Older revision		Revision as of 08:38, 18 September 2011
Line 14:		Line 14:
	=== Examples ===		=== 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 [[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''<ref name="Simon"/> can be said to be [[Quick Time Events]].		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''<ref name="Simon"/> can be said to be [[Quick Time Events]].

Staffan Björk: /* Examples */

2011-09-18T08:38:30Z

Examples

← Older revision		Revision as of 08:38, 18 September 2011
Line 13:		Line 13:

	=== Examples ===		=== 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 [[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''<ref name="Simon"/> can be said to be [[Quick Time Events]].		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''<ref name="Simon"/> can be said to be [[Quick Time Events]].

Staffan Björk: /* Using the pattern */

2011-09-18T08:38:10Z

Using the pattern

← Older revision		Revision as of 08:38, 18 September 2011
Line 20:		Line 20:

	== Using the pattern ==		== 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. They



	=== Diegetic Aspects ===		=== 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.		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.