Difference between revisions of "Team Elimination"

From gdp3
Jump to: navigation, search
Line 8: Line 8:
 
[[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 goal of eliminating a whole team from gameplay.''
  
 
This pattern is a still a stub.
 
This pattern is a still a stub.

Revision as of 12:07, 31 July 2015

The goal of eliminating a whole team from gameplay.

This pattern is a still a stub.

Examples

One way to win matches in the Counter-Strike series is to kill all members in the other Team.

Using the pattern

Making Team Elimination possible is a way to modify how Teams work in Multiplayer Games. The main way of allowing Team Elimination in games is through Player Elimination in games with Teams. The possibility to cause Team Elimination can be a Mutual Goal for other Teams.

Team Elimination can be viewed as a Collection of Eliminate goals, so designing such goals is one way to encourage Team Elimination if it is possible to Eliminate the Team members.

The presence of Spawning making Team Elimination impossible since new Team members continuously enter gameplay.

Consequences

Team Elimination is a Shared Penalty between also those in a Team can be cause Game Over for them. In some cases they can lead to Spectacular Failure Enjoyment.

Relations

Can Instantiate

Game Over, Shared Penalties, Spectacular Failure Enjoyment

Can Modulate

Multiplayer Games, Teams

Can Be Instantiated By

Player Elimination in games with Teams

Can Be Modulated By

Mutual Goals

Collections together with Eliminate

Possible Closure Effects

-

Potentially Conflicting With

Spawning

History

An updated version of the pattern Team Elimination that was part of the original collection in the book Patterns in Game Design[1].

References

  1. Björk, S. & Holopainen, J. (2004) Patterns in Game Design. Charles River Media. ISBN1-58450-354-8.

Acknowledgements

-