Difference between revisions of "Winning by Ending Gameplay"
Line 3: | Line 3: | ||
[[Category:Mechanical Patterns]] | [[Category:Mechanical Patterns]] | ||
[[Category:Patterns]] | [[Category:Patterns]] | ||
− | |||
[[Category:Needs revision]] | [[Category:Needs revision]] | ||
− | |||
[[Category:Needs references]] | [[Category:Needs references]] | ||
[[Category:Patterns created on the Wiki]] | [[Category:Patterns created on the Wiki]] | ||
− | |||
[[Category:To be Published]] | [[Category:To be Published]] | ||
− | |||
''Games which are one by achieving a required game state which ends gameplay.'' | ''Games which are one by achieving a required game state which ends gameplay.'' | ||
Revision as of 15:21, 21 January 2015
Games which are one by achieving a required game state which ends gameplay.
A majority of games are designed so they end at some point. Those that reward a player by letting them win by doing so use a Winning by Ending Gameplay design solution (the typical other solution with winners is to end gameplay and then determine the winner).
Contents
Examples
Chess is won by checkmating one's opponent (or making him or her surrender) while Settlers of Catan ends as soon as a player can show that he or she has 10 points. Racing Games such as Formula D, Hare and Tortoise, Pachisi, and Snakes and Ladders can be seen as weak examples of Winning by Ending Gameplay since only the winner may actually have gameplay ended if the other players continue playing to see what positions they got; two-player versions of these games are however strong examples.
Many games with narratives, e.g. the Fallout series, the Half-Life series, and the Mass Effect series, end with a "victory" when the player has completed the last challenges and been told the end of the story.
Using the pattern
The design of Winning by Ending Gameplay is in practice designed a goal which ends gameplay and declares the player who reached the goal the winner. General examples, to the level that they are patterns, which support this is Races and games where you win by having a certain Score.
One design consideration that needs to be taken for the pattern is however if several players can, or should be allowed to, end gameplay simultaneously. Scores can be used as Tiebreakers if this is the case and Tied Results are unwanted.
Consequences
Winning by Ending Gameplay causes Game Over for players. The pattern can be used to let players have a chance of ending Time Limited Game Instances prematurely by winning, but can also be used to designate Tied Results or a Game System Player to win if no player has won when time has run out.
Due to its definition, Winning by Ending Gameplay is incompatible with Unwinnable Games and Winner determined after Gameplay Ends.
Relations
Can Instantiate
with Time Limited Game Instances
Game System Player, Tied Results
Can Modulate
Can Be Instantiated By
Can Be Modulated By
Possible Closure Effects
-
Potentially Conflicting With
Unwinnable Games, Winner determined after Gameplay Ends
History
New pattern created in this wiki.
References
-
Acknowledgements
-