Difference between revisions of "Beat the Leader"
(→Examples) |
(→Examples) |
||
| Line 15: | Line 15: | ||
=== Examples === | === Examples === | ||
| − | [[:Category:Board Games|Board Games]] with more than two players and where players have quite much control over their actions give rise to [[Beat the Leader]] activities quite often. Examples of such games are [[Concordia]], [[Lords of Waterdeep]], and [[Settlers of Catan]], but many more could be listed. The "beating" done in these case is not often, or even seldom, direct attacks against the perceived leaders but may rather take the form of boycotts, voting pacts, and pooling resources or efforts in various races. Exception to this can be game instances of [[Diplomacy]] or [[Advanced Civilization]] (including the computer-based variants [[Civilization series]]). | + | [[:Category:Board Games|Board Games]] with more than two players and where players have quite much control over their actions give rise to [[Beat the Leader]] activities quite often. Examples of such games are [[Concordia]], [[Lords of Waterdeep]], and [[Settlers of Catan]], but many more could be listed. The "beating" done in these case is not often, or even seldom, direct attacks against the perceived leaders but may rather take the form of boycotts, voting pacts, and pooling resources or efforts in various races. Exception to this can be game instances of [[Diplomacy]] or [[Advanced Civilization]] (including the computer-based variants [[Civilization (video game) series|Civilization series]]). |
Deathmatch version of games in the [[Quake series|Quake]] and [[Doom series]] often exhibit [[Beat the Leader]] situations since all players can see each others scores. However, this is a weak example since whenever players come within shooting distance of each other in these games they tend to engage in combat, so the main effect might be in trying to get close to the perceived leader. | Deathmatch version of games in the [[Quake series|Quake]] and [[Doom series]] often exhibit [[Beat the Leader]] situations since all players can see each others scores. However, this is a weak example since whenever players come within shooting distance of each other in these games they tend to engage in combat, so the main effect might be in trying to get close to the perceived leader. | ||
Revision as of 13:07, 15 January 2015
The one-sentence "definition" that should be in italics.
This pattern is a still a stub.
Contents
Examples
Board Games with more than two players and where players have quite much control over their actions give rise to Beat the Leader activities quite often. Examples of such games are Concordia, Lords of Waterdeep, and Settlers of Catan, but many more could be listed. The "beating" done in these case is not often, or even seldom, direct attacks against the perceived leaders but may rather take the form of boycotts, voting pacts, and pooling resources or efforts in various races. Exception to this can be game instances of Diplomacy or Advanced Civilization (including the computer-based variants Civilization series).
Deathmatch version of games in the Quake and Doom series often exhibit Beat the Leader situations since all players can see each others scores. However, this is a weak example since whenever players come within shooting distance of each other in these games they tend to engage in combat, so the main effect might be in trying to get close to the perceived leader.
Using the pattern
Beat the Leader can occur both in games with PvP and with TvT since a leader can be either an individual player or a Team. The actual design of Beat the Leader consists of providing to characteristics to a game design: making it possible for players to perceive a leader and giving them means to work together against that perceived leader.
Perfect Information, Predictable Winner, and Score Tracks are all ways to give players possibilities of perceived who is leading (even if this may be an erroneous perception). In contrast, the use of End State Scoring, Secret Goals, and Secret Scoring Mechanisms makes it more difficult or impossible to judge who is the leader.
Players of PvP or TvT games may already have actions available that can be used to directly Beat the Leader, e.g. Aim & Shoot but indirect means can also be considered; Games that have Player-Decided Distributions or Player-Decided Results are for example likely to be used for Beat the Leader if this is possible for players to perceive a possible leader. Interruptible Actions, Trading, and Voting and other examples of actions where players can easily come together to Beat the Leader if they can agree that a leader exists.
Interface Aspects
While Beat the Leader is not a Interface Pattern per se, it does rely on how players can make judgments about who is leading a game instance.
Consequences
Beat the Leader make players enter Temporary and Uncommitted Alliances against perceived leaders, and this can is some cases take the form of Betrayal. Players engage in Beat the Leader activities to perform a Balancing Effect, but this is not necessarily correct if they have misjudged how is the leader (or if some players have successfully intentionally point out somebody as a leader which isn't one). The use of Beat the Leader creates Excluding Groups in that the leader is excluded from the other players.
Relations
Negotiation Bluffing Scapegoat
Can Instantiate
Balancing Effects, Betrayal, Excluding Groups, Temporary Alliances, Uncommitted Alliances
Can Modulate
Can Be Instantiated By
Aim & Shoot, Interruptible Actions, Perfect Information, Player-Decided Distributions, Player-Decided Results, Predictable Winner, Score Tracks, Trading, Voting
Can Be Modulated By
-
Possible Closure Effects
-
Potentially Conflicting With
End State Scoring, Secret Goals, Secret Scoring Mechanisms
History
New pattern created in this wiki.
References
-
Acknowledgements
-
