Hotseating - Revision history

Staffan Björk at 13:47, 21 August 2015

2015-08-21T13:47:14Z

Staffan Björk at 10:50, 31 October 2012

2012-10-31T10:50:41Z

Staffan Björk at 10:15, 31 October 2012

2012-10-31T10:15:52Z

Staffan Björk at 09:32, 26 September 2011

2011-09-26T09:32:07Z

Staffan Björk at 09:31, 26 September 2011

2011-09-26T09:31:31Z

Staffan Björk at 09:29, 26 September 2011

2011-09-26T09:29:35Z

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

2011-09-26T09:26:42Z

‎Using the pattern

Staffan Björk: /* Can Modulate */

2011-09-26T09:21:18Z

‎Can Modulate

Staffan Björk: /* Consequences */

2011-09-26T09:21:10Z

‎Consequences

Staffan Björk: /* Relations */

2011-09-26T09:17:29Z

‎Relations

@@ Line 21: / Line 21: @@
 == Using the pattern ==
-The main gameplay design issue with [[Hotseating]] is to determine when the game should make players hand over control to other players, i.e. how [[Turn Taking]] should be enforced. In [[Turn-Based Games]] this is trivial although [[Time Limits]] may be of more interest than usual since one can assume that there are players with [[Downtime]] waiting for their turn. In fact, one could argue that all most non-digital [[Turn-Based Games]] (e.g. [[Chess]] and [[Go]]) use [[Hotseating]] as only one player can interact with the game system at a time. This does however rarely mean that game designers of those games need to consider the design options described in this pattern. This since no effort from designers need to be exerted for it to exist and also since players can for efficiency reasons ignore this and simultaneously interact with the games if everybody agrees that this is okay. Other ways of determining the switch over between players include the loss of [[Lives]], or finishing [[Minigames]] or [[Levels]].
+The main gameplay design issue with [[Hotseating]] is to determine when the game should make players hand over control to other players, i.e. how [[Turn Taking]] should be enforced. In [[Turn-Based Games]] this is trivial although [[Time Limits]] may be of more interest than usual since one can assume that there are players with [[Downtime]] waiting for their turn. In fact, one could argue that all most non-digital [[Turn-Based Games]] (e.g. [[Chess]] and [[Go]]) use [[Hotseating]] as only one player can interact with the game system at a time. This does however rarely mean that game designers of those games need to consider the design options described in this pattern. This since no effort from designers need to be exerted for it to exist and also since players can for efficiency reasons ignore this and simultaneously interact with the games if everybody agrees that this is okay. Other ways of determining the switch over between players include [[Death Consequences]], or finishing [[Minigames]] or [[Levels]].
 That [[Hotseating]] requires a form of [[Turn Taking]] does not automatically make [[Real-Time Games]] impossible to combine with [[Hotseating]]. [[:Category:Pinball Games|Pinball Games]] are for example games where players take turns playing but each player's turn contain real-time gameplay.
@@ Line 52: / Line 52: @@
 === Can Be Modulated By ===
 [[Levels]],
 [[Minigames]],
 [[Time Limits]]

@@ Line 35: / Line 35: @@
 [[Split-Screen Views]] can be said to be incompatible with [[Hotseating]] since they address the same design problem and it is superfluous to use both. Games with [[Hotseating]] can, unlike those with [[Split-Screen Views]], make use of gameplay which requires [[Asymmetric Information]] as long as the players can be assumed to facilitate that they do not look at each other's game views.
-As long as players are not supposed to view each others moves, [[Hotseating]] is likely to make those not currently playing into [[Backseat Players]].
+As long as players are not supposed to view each others moves, [[Hotseating]] is likely to make those not currently playing into [[Backseat Gamers]].
 == Relations ==
 === Can Instantiate ===
-[[Backseat Players]],
+[[Backseat Gamers]],
 [[Downtime]],
 [[Spectators]],

@@ Line 34: / Line 34: @@
 [[Split-Screen Views]] can be said to be incompatible with [[Hotseating]] since they address the same design problem and it is superfluous to use both. Games with [[Hotseating]] can, unlike those with [[Split-Screen Views]], make use of gameplay which requires [[Asymmetric Information]] as long as the players can be assumed to facilitate that they do not look at each other's game views.
 == Relations ==
 === Can Instantiate ===
 [[Downtime]],
 [[Spectators]],

@@ Line 21: / Line 21: @@
 == Using the pattern ==
-The main gameplay design issue with [[Hotseating]] is to determine when the game should make players hand over control to other players, i.e. how [[Turn Taking]] should be enforced. In [[Turn-Based Games]] this is trivial although [[Time Limits]] may be of more interest than usual since one can assume that there are players with [[Downtime]] waiting for their turn. In fact, one could argue that all most non-digital [[Turn-Based Games]] (e.g. [[Chess]] and [[Go]]) use [[Hotseating]] as only one player can interact with the game system at a time. This does however rarely mean that game designers of those games need to consider the design options described in this pattern. This since no effort from designers need to be exerted for it to exist and also since players can for efficiency reasons ignore this and simultaneously interact with the games if everybody agrees that this is okay. Other ways of determining the switch over between players include the loss of [[Lives]], or finishing [[Mini-Games]] or [[Levels]].
+The main gameplay design issue with [[Hotseating]] is to determine when the game should make players hand over control to other players, i.e. how [[Turn Taking]] should be enforced. In [[Turn-Based Games]] this is trivial although [[Time Limits]] may be of more interest than usual since one can assume that there are players with [[Downtime]] waiting for their turn. In fact, one could argue that all most non-digital [[Turn-Based Games]] (e.g. [[Chess]] and [[Go]]) use [[Hotseating]] as only one player can interact with the game system at a time. This does however rarely mean that game designers of those games need to consider the design options described in this pattern. This since no effort from designers need to be exerted for it to exist and also since players can for efficiency reasons ignore this and simultaneously interact with the games if everybody agrees that this is okay. Other ways of determining the switch over between players include the loss of [[Lives]], or finishing [[Minigames]] or [[Levels]].
 That [[Hotseating]] requires a form of [[Turn Taking]] does not automatically make [[Real-Time Games]] impossible to combine with [[Hotseating]]. [[:Category:Pinball Games|Pinball Games]] are for example games where players take turns playing but each player's turn contain real-time gameplay.
@@ Line 51: / Line 51: @@
 [[Levels]],
 [[Lives]],
-[[Mini-Games]],
+[[Minigames]],
 [[Time Limits]]

@@ Line 1: / Line 1: @@
 [[Category:Patterns]]
 [[Category:Interface Patterns]]
 [[Category:Needs revision]]
 [[Category:Needs references]]
 [[Category:Patterns created on the Wiki]]
 ''Gameplay where players take turns using an interface to interact with the game system.''
@@ Line 31: / Line 28: @@
 === Interface Aspects ===
-[[Hotseating]] is an [[:Category:Interface Patterns|Interface Pattern]] and all aspects of it concerns this.
+[[Hotseating]] is an [[:Category:Interface Patterns|Interface Pattern]] and all aspects of it concern this.
 == Consequences ==

@@ Line 24: / Line 24: @@
 == Using the pattern ==
-The main gameplay design issue with [[Hotseating]] is to determine when the game should make players hand over control to other players, i.e. how [[Turn Taking]] should . In
+The main gameplay design issue with [[Hotseating]] is to determine when the game should make players hand over control to other players, i.e. how [[Turn Taking]] should be enforced. In [[Turn-Based Games]] this is trivial
 [[Time Limits]]
@@ Line 31: / Line 31: @@
 requires that
-In fact, one could argue that all most non-digital [[:Category:Turn-Based Games|Turn-Based Games]] (e.g. [[Chess]] and [[Go]]) use [[Hotseating]] as only one player can interact with the game system at a time. This does however rarely mean that game designers of those games need to consider the design options described in this pattern. This since no effort from designers need to be exerted for it to exist and also since players can for efficiency reasons ignore this and simultaneously interact with the games if everybody agrees that this is okay.
+In fact, one could argue that all most non-digital [[Turn-Based Games]] (e.g. [[Chess]] and [[Go]]) use [[Hotseating]] as only one player can interact with the game system at a time. This does however rarely mean that game designers of those games need to consider the design options described in this pattern. This since no effort from designers need to be exerted for it to exist and also since players can for efficiency reasons ignore this and simultaneously interact with the games if everybody agrees that this is okay.

@@ Line 54: / Line 54: @@
 === Can Modulate ===
 [[Multiplayer Games]],
-[[Turn-Base Games]]
+[[Turn-Based Games]]
 === Can Be Instantiated By ===

@@ Line 42: / Line 42: @@
 == Consequences ==
-Given that [[Hotseating]] requires players to take turns playing, it can be seen as a way of modulating [[Turn Taking]] and [[Multiplayer Games]]. By doing so, it makes players have [[Downtime]] although they may be [[Spectators]] to each other.
+Given that [[Hotseating]] requires players to take turns playing, it can be seen as enforcing [[Turn Taking]] to make [[Multiplayer Games]] possible with only an interface for one player at a time. Since most [[Turn-Based Games]] already have [[Turn Taking]], adding [[Hotseating]] to these can be seen as a modification to them. While adding [[Hotseating]] to a game can let more players play, it also makes them have [[Downtime]] while waiting - this may not be that much of a problem since they can be [[Spectators]] to each other.
 [[Split-Screen Views]] can be said to be incompatible with [[Hotseating]] since they address the same design problem and it is superfluous to use both. Games with [[Hotseating]] can, unlike those with [[Split-Screen Views]], make use of gameplay which requires [[Asymmetric Information]] as long as the players can be assumed to facilitate that they do not look at each other's game views.