Cutscenes - Revision history

Staffan Björk at 11:49, 17 July 2016

2016-07-17T11:49:08Z

Staffan Björk: /* Can Instantiate */

2016-07-16T09:39:54Z

‎Can Instantiate

Staffan Björk at 09:32, 15 July 2016

2016-07-15T09:32:10Z

Staffan Björk at 15:11, 8 August 2015

2015-08-08T15:11:15Z

Staffan Björk at 06:33, 3 August 2015

2015-08-03T06:33:52Z

Staffan Björk at 16:43, 2 August 2015

2015-08-02T16:43:34Z

Staffan Björk at 21:35, 4 July 2015

2015-07-04T21:35:08Z

Staffan Björk at 08:35, 21 September 2014

2014-09-21T08:35:20Z

Staffan Björk at 08:50, 7 September 2014

2014-09-07T08:50:45Z

Staffan Björk at 08:20, 2 September 2014

2014-09-02T08:20:38Z

@@ Line 32: / Line 32: @@
 === Narrative Aspects ===
-As mentioned above, one of the main reasons for using [[Cutscenes]] is to unfold [[Predetermined Story Structures]]. This may make players more aware of [[Character Defining Actions]] by setting up the situation or stressing the importance of an upcoming choice, but may also ruin it by introducing [[Characters|Character]] actions that players did not feel were appropriate to how they perceive the [[Characters]]. Simply not letting players have a choice even if the actions performed were plausible may also cause players to feel that there are no [[Character Defining Actions]] in a game since the game design has predetermined the actions.
+As mentioned above, one of the main reasons for using [[Cutscenes]] is to unfold [[Predetermined Story Structures]]. This may make players more aware of [[Character Defining Actions]] by setting up the situation or stressing the importance of an upcoming choice, but may also ruin it by introducing [[Characters|Character]] actions that players did not feel were appropriate to how they perceive the [[Characters]]. Simply not letting players have a choice even if the actions performed were plausible may also cause players to feel that there are no [[Character Defining Actions]] in a game since the game design has predetermined the actions. Another reason for using [[Cutscenes]] is that it can help players feel [[Identification]] with [[Player Characters]] based on the narration and diegesis.
 == Consequences ==
@@ Line 74: / Line 74: @@
 [[Unpredictable Behavior]],
 [[Ultra-Powerful Events]]
 === Can Modulate ===

@@ Line 56: / Line 56: @@
 [[Extra-Game Consequences]],
 [[Game Pauses]],
 [[Goal Indicators]],
 [[Lull Periods]],

@@ Line 18: / Line 18: @@
 == Using the pattern ==
-The primary reason for using [[Cutscenes]] are to convey information to players that they should not be able to miss, so designing [[Cutscenes]] need to first and foremost make the presentation clearly describe this information and after that consider when it should be given to the players. The most common use of [[Cutscenes]] are [[Predetermined Story Structures]] but specific cases when they can be used regardless of how they progress [[Predetermined Story Structures]] are transitions between [[Levels]] (the original use), enacting [[Surprise Attacks]] (enforcing players to "act" surprised by not letting them react), giving [[Game State Overviews]] of new [[Levels]], or depicting [[Quick Travel|Quick]] or [[One-Way Travel]] (including some forms of [[Quick Returns]]). Common places for [[Cutscenes]] are when players encounter new [[Enemies]], [[Boss Monsters]], or [[Traces]] so that they can be given [[Point of Interest Indications]], or when they are supposed to experience [[Surprises]]. The scenes can be used to show the presence of the two first, possibly as [[Disruption of Focused Attention]] events, while the last can be fully instantiated by [[Cutscenes]]. Another option (found e.g. in [[Fallout: New Vegas]]) is to provide [[Cutscenes]] that tell what happened after the game has been completed - this can be used to make players realize the presence of [[Open Destiny|Open Destinies]]. Since it may be difficult to time the suitability of when to enforce global [[Downtime]] in [[Multiplayer Games]], it is easier to time [[Cutscenes]] to the events in the game in [[Single-Player Games]] unless [[Game Masters]] are used. For this reason, [[Cutscenes]] are more often applied to [[Penalties]] and [[Rewards]] in [[Single-Player Games]].
+The primary reason for using [[Cutscenes]] are to convey information to players that they should not be able to miss, so designing [[Cutscenes]] need to first and foremost make the presentation clearly describe this information and after that consider when it should be given to the players. The most common use of [[Cutscenes]] are [[Predetermined Story Structures]] but specific cases when they can be used regardless of how they progress [[Predetermined Story Structures]] are transitions between [[Levels]] (the original use), enacting [[Surprise Attacks]] (enforcing players to "act" surprised by not letting them react), giving [[Game State Overviews]] of new [[Levels]], or depicting [[Quick Travel|Quick]] or [[One-Way Travel]] (including some forms of [[Quick Returns]]). Common places for [[Cutscenes]] are when players encounter new [[Enemies]], [[Boss Monsters]], or [[Traces]] so that they can be given [[Point of Interest Indicators]], or when they are supposed to experience [[Surprises]]. The scenes can be used to show the presence of the two first, possibly as [[Disruption of Focused Attention]] events, while the last can be fully instantiated by [[Cutscenes]]. Another option (found e.g. in [[Fallout: New Vegas]]) is to provide [[Cutscenes]] that tell what happened after the game has been completed - this can be used to make players realize the presence of [[Open Destiny|Open Destinies]]. Since it may be difficult to time the suitability of when to enforce global [[Downtime]] in [[Multiplayer Games]], it is easier to time [[Cutscenes]] to the events in the game in [[Single-Player Games]] unless [[Game Masters]] are used. For this reason, [[Cutscenes]] are more often applied to [[Penalties]] and [[Rewards]] in [[Single-Player Games]].
 One part of making the information in [[Cutscenes]] difficult to miss is to not allow players to do anything else while they are taking place; this is most easily done by removing players ability to do actions (i.e. force them to do [[No-Ops]]). The other part if fully control the presentation, this is easiest done through [[Dedicated Game Facilitators]] playing animations, audio recordings, or video recordings. Alternatives to [[Dedicated Game Facilitators]] include [[Game Masters]] or players in [[Self-Facilitated Games]] when they provide [[Effect Descriptions]] or engage in uninterrupted [[Storytelling]]. However, the [[Cutscenes]] played do not have to be fully predetermined: having sets of [[Cutscenes]] allows scenes to be chosen due to the current game state; using the game engine to run the [[Cutscenes]] allows minor variations such as the positions of game elements; and using [[Game Masters]] allow [[Cutscenes]] to be fully modulated with the game state and players.
@@ Line 61: / Line 61: @@
 [[Non-Player Characters]],
 [[No-Ops]],
-[[Point of Interest Indications]],
+[[Point of Interest Indicators]],
 [[Predetermined Story Structures]],
 [[Props]],

@@ Line 18: / Line 18: @@
 == Using the pattern ==
-The primary reason for using [[Cutscenes]] are to convey information to players that they should not be able to miss, so designing [[Cutscenes]] need to first and foremost make the presentation clearly describe this information and after that consider when it should be given to the players. The most common use of [[Cutscenes]] are [[Predetermined Story Structures]] but specific cases when they can be used regardless of how they progress [[Predetermined Story Structures]] are transitions between [[Levels]] (the original use), enacting [[Surprise Attacks]] (enforcing players to "act" surprised by not letting them react), giving [[Game State Overviews]] of new [[Levels]], or depicting [[Quick Travel|Quick]] or [[One-Way Travel]] (including some forms of [[Quick Returns]]). Common places for [[Cutscenes]] are when players encounter new [[Enemies]], [[Boss Monsters]], or [[Traces]] so that they can be given [[Point of Interest Indications]], or when they are supposed to experience [[Surprises]]. The scenes can be used to show the presence of the two first, possibly as [[Disruption of Focused Attention]] events, while the last can be fully instantiated by [[Cutscenes]]. Another option (found e.g. in [[Fallout: New Vegas]]) is to provide [[Cutscenes]] that tell what happened after the game has been completed - this can be used to make players realize the presence of [[Open Destiny|Open Destinies]].
+The primary reason for using [[Cutscenes]] are to convey information to players that they should not be able to miss, so designing [[Cutscenes]] need to first and foremost make the presentation clearly describe this information and after that consider when it should be given to the players. The most common use of [[Cutscenes]] are [[Predetermined Story Structures]] but specific cases when they can be used regardless of how they progress [[Predetermined Story Structures]] are transitions between [[Levels]] (the original use), enacting [[Surprise Attacks]] (enforcing players to "act" surprised by not letting them react), giving [[Game State Overviews]] of new [[Levels]], or depicting [[Quick Travel|Quick]] or [[One-Way Travel]] (including some forms of [[Quick Returns]]). Common places for [[Cutscenes]] are when players encounter new [[Enemies]], [[Boss Monsters]], or [[Traces]] so that they can be given [[Point of Interest Indications]], or when they are supposed to experience [[Surprises]]. The scenes can be used to show the presence of the two first, possibly as [[Disruption of Focused Attention]] events, while the last can be fully instantiated by [[Cutscenes]]. Another option (found e.g. in [[Fallout: New Vegas]]) is to provide [[Cutscenes]] that tell what happened after the game has been completed - this can be used to make players realize the presence of [[Open Destiny|Open Destinies]]. Since it may be difficult to time the suitability of when to enforce global [[Downtime]] in [[Multiplayer Games]], it is easier to time [[Cutscenes]] to the events in the game in [[Single-Player Games]] unless [[Game Masters]] are used. For this reason, [[Cutscenes]] are more often applied to [[Penalties]] and [[Rewards]] in [[Single-Player Games]].
 One part of making the information in [[Cutscenes]] difficult to miss is to not allow players to do anything else while they are taking place; this is most easily done by removing players ability to do actions (i.e. force them to do [[No-Ops]]). The other part if fully control the presentation, this is easiest done through [[Dedicated Game Facilitators]] playing animations, audio recordings, or video recordings. Alternatives to [[Dedicated Game Facilitators]] include [[Game Masters]] or players in [[Self-Facilitated Games]] when they provide [[Effect Descriptions]] or engage in uninterrupted [[Storytelling]]. However, the [[Cutscenes]] played do not have to be fully predetermined: having sets of [[Cutscenes]] allows scenes to be chosen due to the current game state; using the game engine to run the [[Cutscenes]] allows minor variations such as the positions of game elements; and using [[Game Masters]] allow [[Cutscenes]] to be fully modulated with the game state and players.
@@ Line 39: / Line 39: @@
 [[Cutscenes]] stop gameplay, and game time for [[Real-Time Games]], and thereby are a form of [[Game Pauses]] which gives players [[Downtime]] or sometimes [[Lull Periods]] depending on how interesting the players find the [[Cutscenes]]. Even so, they work against [[Minimalized Social Weight]] since they are designed to capture players attention with a story presentation. Even if they are made to be narratively interesting or contain gameplay information, they nearly always cause [[Disruption of Focused Attention]] since they interrupt gameplay. The first time a particular [[Cut Scenes|Cut Scene]] is experienced it may be or include [[Surprises]] and this can be used to give [[Unpredictable Behavior]] to [[Agents]].
-When [[Cutscenes]] involve players or other agents, they are examples of [[Enforced Agent Behavior]] that limit players' [[Freedom of Choice]] and can change their perceptions of their [[Avatars]]. They also enforce players to perform [[No-Ops]] while they are taking place (even if their [[Avatars]] or [[Characters]] are performing actions) - and this is true even if the [[Cutscenes]] do not involve the players. Since it may be difficult to time the suitability of when to enforce global [[Downtime]] in [[Multiplayer Games]], it is easier to time [[Cutscenes]] to the events in the game in [[Single-Player Games]] unless [[Game Masters]] are used.
+When [[Cutscenes]] involve players or other agents, they are examples of [[Enforced Agent Behavior]] that limit players' [[Freedom of Choice]] and can change their perceptions of their [[Avatars]]. They also enforce players to perform [[No-Ops]] while they are taking place (even if their [[Avatars]] or [[Characters]] are performing actions) - and this is true even if the [[Cutscenes]] do not involve the players.
 Given that [[Cutscenes]] takes away players' agency the pattern is difficult to combine with given them an [[Exaggerated Perception of Influence]]. However, [[Cutscenes]] may give [[Strategic Knowledge]] about how to meet future challenges, e.g. through [[Achilles' Heels]], and may thereby function as [[Goal Indicators]] and give players' a [[Determinable Chance to Succeed]] - all which gives rise to [[Stimulated Planning]].
@@ Line 92: / Line 92: @@
 [[Surprises]],
 [[Traces]]
 === Can Be Instantiated By ===

@@ Line 35: / Line 35: @@
 == Consequences ==
-[[Cutscenes]] are [[Automated Responses]] in the form of [[Scenes]] with localized [[Predetermined Story Structures]], and one of the most controlled ways of doing [[Storytelling]] to either present the [[Alternative Realities]] of [[Game Worlds]] or unfold [[Predetermined Story Structures]] to players. Of course, [[Predetermined Story Structures]] can be partly built from [[Cutscenes]], so the patterns can instantiate each other. As events that take control of the game state completely, [[Cutscenes]] are [[Ultra-Powerful Events]] which may cause [[Disruption of Focused Attention]] for players but can guarantee that [[Thematic Consistency]] is maintained. When the [[Cutscenes]] only forward the narrative without changing the game state they can be said to be [[Extra-Game Consequences]].
+[[Cutscenes]] are [[Automated Responses]] in the form of [[Scenes]] with localized [[Predetermined Story Structures]], and one of the most controlled ways of doing [[Storytelling]] to either present the [[Alternative Realities]] of [[Game Worlds]] or unfold [[Predetermined Story Structures]] to players. Of course, [[Predetermined Story Structures]] can be partly built from [[Cutscenes]], so the patterns can instantiate each other. As events that take control of the game state completely, [[Cutscenes]] are [[Ultra-Powerful Events]] which may cause [[Disruption of Focused Attention]] for players but can guarantee that [[Thematic Consistency]] is maintained. If they move players between different locations, [[Cutscenes]] can functionally be [[Transport Routes]]. When the [[Cutscenes]] only forward the narrative without changing the game state they can be said to be [[Extra-Game Consequences]].
 [[Cutscenes]] stop gameplay, and game time for [[Real-Time Games]], and thereby are a form of [[Game Pauses]] which gives players [[Downtime]] or sometimes [[Lull Periods]] depending on how interesting the players find the [[Cutscenes]]. Even so, they work against [[Minimalized Social Weight]] since they are designed to capture players attention with a story presentation. Even if they are made to be narratively interesting or contain gameplay information, they nearly always cause [[Disruption of Focused Attention]] since they interrupt gameplay. The first time a particular [[Cut Scenes|Cut Scene]] is experienced it may be or include [[Surprises]] and this can be used to give [[Unpredictable Behavior]] to [[Agents]].
@@ Line 70: / Line 70: @@
 [[Thematic Consistency]],
 [[Third-Person Views]],
 [[Unpredictable Behavior]],
 [[Ultra-Powerful Events]]

@@ Line 10: / Line 10: @@
 [[Cutscenes]] are used when games cannot progress the entire game story through actions and events and need to give longer descriptions and explanations to players. These scenes are usually located between sections of gameplay that differ significantly, either because of change of location or type of activities required, or located right before a challenge to make players aware of the challenge.
-[[Cutscenes]] are sometimes criticizied in games because they remove agency for players. See Klejver<ref name="Klejver"/> for a discussion regarding the pros and cons of using [[Cutscenes]] in games.
+[[Cutscenes]] are sometimes criticized in games because they remove agency for players. See Klejver<ref name="Klejver"/> for a discussion regarding the pros and cons of using [[Cutscenes]] in games.
 === Examples ===
@@ Line 35: / Line 35: @@
 == Consequences ==
-[[Cutscenes]] are [[Scenes]] with localized [[Predetermined Story Structures]], and one of the most controlled ways of doing [[Storytelling]] to either present the [[Alternative Realities]] of [[Game Worlds]] or unfold [[Predetermined Story Structures]] to players. Of course, [[Predetermined Story Structures]] can be partly built from [[Cutscenes]], so the patterns can instantiate each other. As events that take control of the game state completely, [[Cutscenes]] are [[Ultra-Powerful Events]] which may cause [[Disruption of Focused Attention]] for players but can guarantee that [[Thematic Consistency]] is maintained. When the [[Cutscenes]] only forward the narrative without changing the game state they can be said to be [[Extra-Game Consequences]]. They stop gameplay, and game time for [[Real-Time Games]], and thereby are a form of [[Game Pauses]] which gives players [[Downtime]]. Even so, they work against [[Minimalized Social Weight]] since they are designed to capture players attention with a story presentation. Even if they are made to be narratively interesting or contain gameplay information, they nearly always cause [[Disruption of Focused Attention]] since they interrupt gameplay. The first time a particular [[Cut Scenes|Cut Scene]] is experienced it may be or include [[Surprises]] and this can be used to give [[Unpredictable Behavior]] to [[Agents]].
+[[Cutscenes]] are [[Automated Responses]] in the form of [[Scenes]] with localized [[Predetermined Story Structures]], and one of the most controlled ways of doing [[Storytelling]] to either present the [[Alternative Realities]] of [[Game Worlds]] or unfold [[Predetermined Story Structures]] to players. Of course, [[Predetermined Story Structures]] can be partly built from [[Cutscenes]], so the patterns can instantiate each other. As events that take control of the game state completely, [[Cutscenes]] are [[Ultra-Powerful Events]] which may cause [[Disruption of Focused Attention]] for players but can guarantee that [[Thematic Consistency]] is maintained. When the [[Cutscenes]] only forward the narrative without changing the game state they can be said to be [[Extra-Game Consequences]]. They stop gameplay, and game time for [[Real-Time Games]], and thereby are a form of [[Game Pauses]] which gives players [[Downtime]]. Even so, they work against [[Minimalized Social Weight]] since they are designed to capture players attention with a story presentation. Even if they are made to be narratively interesting or contain gameplay information, they nearly always cause [[Disruption of Focused Attention]] since they interrupt gameplay. The first time a particular [[Cut Scenes|Cut Scene]] is experienced it may be or include [[Surprises]] and this can be used to give [[Unpredictable Behavior]] to [[Agents]].
 When [[Cutscenes]] involve players or other agents, they are examples of [[Enforced Agent Behavior]] that limit players' [[Freedom of Choice]] and can change their perceptions of their [[Avatars]]. They also enforce players to perform [[No-Ops]] while they are taking place (even if their [[Avatars]] or [[Characters]] are performing actions) - and this is true even if the [[Cutscenes]] do not involve the players. Since it may be difficult to time the suitability of when to enforce global [[Downtime]] in [[Multiplayer Games]], it is easier to time [[Cutscenes]] to the events in the game in [[Single-Player Games]] unless [[Game Masters]] are used.
@@ Line 46: / Line 46: @@
 === Can Instantiate ===
 [[Alternative Realities]],
 [[Character Defining Actions]],
 [[Determinable Chance to Succeed]],

@@ Line 18: / Line 18: @@
 == Using the pattern ==
-The primary reason for using [[Cutscenes]] are to convey information to players that they should not be able to miss, so designing [[Cutscenes]] need to first and foremost make the presentation clearly describe this information and after that consider when it should be given to the players. The most common use of [[Cutscenes]] are [[Predetermined Story Structures]] but specific cases when they can be used regardless of how they progress [[Predetermined Story Structures]] are transitions between [[Levels]] (the original use), giving [[Game State Overviews]] of new [[Levels]], or depicting [[Quick Travel|Quick]] or [[One-Way Travel]] (including some forms of [[Quick Returns]]). Common places for [[Cutscenes]] are when players encounter new [[Enemies]], [[Boss Monsters]], or [[Traces]] so that they can be given [[Point of Interest Indications]], or when they are supposed to experience [[Surprises]]. The scenes can be used to show the presence of the two first, possibly as [[Disruption of Focused Attention]] events, while the last can be fully instantiated by [[Cutscenes]]. Another option (found e.g. in [[Fallout: New Vegas]]) is to provide [[Cutscenes]] that tell what happened after the game has been completed - this can be used to make players realize the presence of [[Open Destiny|Open Destinies]].
+The primary reason for using [[Cutscenes]] are to convey information to players that they should not be able to miss, so designing [[Cutscenes]] need to first and foremost make the presentation clearly describe this information and after that consider when it should be given to the players. The most common use of [[Cutscenes]] are [[Predetermined Story Structures]] but specific cases when they can be used regardless of how they progress [[Predetermined Story Structures]] are transitions between [[Levels]] (the original use), enacting [[Surprise Attacks]] (enforcing players to "act" surprised by not letting them react), giving [[Game State Overviews]] of new [[Levels]], or depicting [[Quick Travel|Quick]] or [[One-Way Travel]] (including some forms of [[Quick Returns]]). Common places for [[Cutscenes]] are when players encounter new [[Enemies]], [[Boss Monsters]], or [[Traces]] so that they can be given [[Point of Interest Indications]], or when they are supposed to experience [[Surprises]]. The scenes can be used to show the presence of the two first, possibly as [[Disruption of Focused Attention]] events, while the last can be fully instantiated by [[Cutscenes]]. Another option (found e.g. in [[Fallout: New Vegas]]) is to provide [[Cutscenes]] that tell what happened after the game has been completed - this can be used to make players realize the presence of [[Open Destiny|Open Destinies]].
 One part of making the information in [[Cutscenes]] difficult to miss is to not allow players to do anything else while they are taking place; this is most easily done by removing players ability to do actions (i.e. force them to do [[No-Ops]]). The other part if fully control the presentation, this is easiest done through [[Dedicated Game Facilitators]] playing animations, audio recordings, or video recordings. Alternatives to [[Dedicated Game Facilitators]] include [[Game Masters]] or players in [[Self-Facilitated Games]] when they provide [[Effect Descriptions]] or engage in uninterrupted [[Storytelling]]. However, the [[Cutscenes]] played do not have to be fully predetermined: having sets of [[Cutscenes]] allows scenes to be chosen due to the current game state; using the game engine to run the [[Cutscenes]] allows minor variations such as the positions of game elements; and using [[Game Masters]] allow [[Cutscenes]] to be fully modulated with the game state and players.
@@ Line 93: / Line 93: @@
 [[Predetermined Story Structures]],
 [[Quick Time Events]],
-[[Summary Updates]]
+[[Summary Updates]],
 [[Storytelling]] with [[Game Masters]] or [[Self-Facilitated Games]]

@@ Line 1: / Line 1: @@
 [[Category:Narration Patterns]]
 [[Category:Patterns]]
 [[Category:Needs revision]]
 [[Category:Needs examples]]