Difference between revisions of "Game Over"

From gdp3
Jump to: navigation, search
(Examples)
Line 2: Line 2:
 
[[Category:Mechanical Patterns]]
 
[[Category:Mechanical Patterns]]
 
[[Category:Patterns]]
 
[[Category:Patterns]]
[[Category:Needs work]]
 
 
[[Category:Needs revision]]
 
[[Category:Needs revision]]
 
[[Category:Needs examples]]
 
[[Category:Needs examples]]
 
[[Category:Needs references]]
 
[[Category:Needs references]]
 
[[Category:Patterns created on the Wiki]]
 
[[Category:Patterns created on the Wiki]]
[[Category:Stub]]
 
 
[[Category:To be Published]]
 
[[Category:To be Published]]
 
[[Category:Staffan's current workpage]]
 
[[Category:Staffan's current workpage]]
''The one-sentence "definition" that should be in italics.''
+
''The event which makes a player no long able to participate in the gameplay of a game instance.''
  
This pattern is a still a stub.
+
Most games are design to end at some point, and some are designed to make some players stop playing before all other do. A [[Game Over]] event is when a player is locked out from gameplay due to some rule in the game.  
  
 
=== Examples ===
 
=== Examples ===

Revision as of 18:52, 25 January 2015

The event which makes a player no long able to participate in the gameplay of a game instance.

Most games are design to end at some point, and some are designed to make some players stop playing before all other do. A Game Over event is when a player is locked out from gameplay due to some rule in the game.

Examples

Asteroids, Donkey Kong, Outrun, Pong, and Pac-Man are all games where players experience Game Over when they run out of lives. However, in original Arcade version it was possible to pay for more lives. Gauntlet is a latter example.

Getting killed in the Counter-Strike series or losing ones last card in Coup results in players being thrown out of the game. However, since each game round is so short and one typically play many rounds back-to-back, the effects of Game Over are not too severe.

Using the pattern

Designing Game Over events in a game consists of choosing what causes them. A typical cause is simple that it is Death Consequence, typically cause by losing all Lives or suffering from a Permadeath. However, Player Elimination or Player Kicking can also function as can Time Limits that create Time Limited Game Instances. Of course, winning a game also causes a Game Over but the pattern can also be applied to Unwinnable Games since Game Over events can be penalties.

End State Scoring is an option to add some Tension after gameplay has ended and can be used to support Winner determined after Gameplay Ends. Another, which adds a consequence and possible goal to want to reach a Game Over event, is to use Winning by Ending Gameplay. Pay to Play is an option to let players begin playing again if they are willing to play.

Consequences

Game Over causes players to not be able to play. In practice this becomes Downtime if another game instance will start soon, as is the structure of quick games such as Coup or The Resistance but otherwise can force the former players to start doing something else. Unless Game Over occurs to all players at the same time in Multiplayer Games, it can create Unsynchronized Game Sessions.

Relations

Can Instantiate

Downtime

with Multiplayer Games

Unsynchronized Game Sessions

Can Modulate

Unwinnable Games, Winner determined after Gameplay Ends

Can Be Instantiated By

Death Consequences, Lives, Permadeath, Player Elimination, Player Kicking, Time Limited Game Instances, Time Limits, Winning by Ending Gameplay, Winning the game

Can Be Modulated By

End State Scoring, Pay to Play

Possible Closure Effects

-

Potentially Conflicting With

-

History

New pattern created in this wiki.

References

-

Acknowledgements

-