Difference between revisions of "Generic Adversaries"
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[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]] | ||
| − | + | ''More or less adversary diegetic entities that are indistinguishable from other similar entities.'' | |
| − | ' | + | |
| − | + | Games often put players in opposition to entities in game worlds, sometimes by making them directly hostile and sometimes by simply making actions impossible or inadvisable. When multiple such entities exist and they are functionally identical to each other, they are [[Generic Adversaries]]. | |
Note: ''This pattern was first identified in the book chapter "Of Heroes and Henchmen: The Conventions of Killing Generic Expendables in Video Games" by René Glas<ref name="glas"/>. TV Tropes uses "Mook" for the same phenomenon<ref name="tvtropes"/>.'' | Note: ''This pattern was first identified in the book chapter "Of Heroes and Henchmen: The Conventions of Killing Generic Expendables in Video Games" by René Glas<ref name="glas"/>. TV Tropes uses "Mook" for the same phenomenon<ref name="tvtropes"/>.'' | ||
| Line 25: | Line 21: | ||
== Consequences == | == Consequences == | ||
| − | As [[Enemies]] that can both be numerous and can easily be created on the fly, [[Generic Adversaries]] can be well suited to create [[Combat]]-oriented [[Grinding]]. | + | As [[Enemies]] that can both be numerous and can easily be created on the fly, [[Generic Adversaries]] can be well suited to create [[Combat]]-oriented [[Grinding]]. Since interacting with them tend to involve the same kind of actions, challenges, and solutions, use of them tend to give rise to [[Repetitive Gameplay]] unless other factors are changed to compensate. |
If the behavior of [[Generic Adversaries]] aren't complex regarding prediction or co-operation, they can open up for [[Kiting]] behaviors from players. | If the behavior of [[Generic Adversaries]] aren't complex regarding prediction or co-operation, they can open up for [[Kiting]] behaviors from players. | ||
== Relations == | == Relations == | ||
| − | |||
| − | |||
=== Can Instantiate === | === Can Instantiate === | ||
[[Enemies]], | [[Enemies]], | ||
[[Grinding]], | [[Grinding]], | ||
| + | [[Inhabitants]], | ||
[[Kiting]], | [[Kiting]], | ||
[[NPCs]], | [[NPCs]], | ||
| − | [[ | + | [[Repetitive Gameplay]], |
[[Units]], | [[Units]], | ||
[[Waves]] | [[Waves]] | ||
| Line 48: | Line 43: | ||
=== Can Be Modulated By === | === Can Be Modulated By === | ||
| − | [[Loot]] | + | [[Loot]], |
| + | [[Randomness]] | ||
=== Possible Closure Effects === | === Possible Closure Effects === | ||
Latest revision as of 12:45, 31 August 2015
More or less adversary diegetic entities that are indistinguishable from other similar entities.
Games often put players in opposition to entities in game worlds, sometimes by making them directly hostile and sometimes by simply making actions impossible or inadvisable. When multiple such entities exist and they are functionally identical to each other, they are Generic Adversaries.
Note: This pattern was first identified in the book chapter "Of Heroes and Henchmen: The Conventions of Killing Generic Expendables in Video Games" by René Glas[1]. TV Tropes uses "Mook" for the same phenomenon[2].
Contents
Examples
While there are many different types of enemies in Super Mario series, all instances within one category of enemies are identical to each other making all but the boss monsters of these games into Generic Adversaries.
The regular "infected" that players encounters in the Left 4 Dead series may look different from each other but are otherwise Generic Adversaries.
Using the pattern
Generic Adversaries are diegetically intentional entities that are identical to each other. As such, they can fill roles for Enemies that need to exist in large numbers, e.g. in Waves. Although they are named as adversaries, they can also be used as Inhabitants and NPCs that are only adversary passively or through their mere presence. In this way, Generic Adversaries are by definition required for the creation of Units. The design involved in creating Generic Adversaries consists of making a template for them and considering when players should encounter them (which might be a question of when they should be spawned).
While Generic Adversaries should be similar enough to be viewed as generic, some variation can be provided to them through Randomness to make gameplay less predictable. One area where this may be especially appropriate is the composition of any eventual Loot they have.
Consequences
As Enemies that can both be numerous and can easily be created on the fly, Generic Adversaries can be well suited to create Combat-oriented Grinding. Since interacting with them tend to involve the same kind of actions, challenges, and solutions, use of them tend to give rise to Repetitive Gameplay unless other factors are changed to compensate.
If the behavior of Generic Adversaries aren't complex regarding prediction or co-operation, they can open up for Kiting behaviors from players.
Relations
Can Instantiate
Enemies, Grinding, Inhabitants, Kiting, NPCs, Repetitive Gameplay, Units, Waves
Can Modulate
-
Can Be Instantiated By
-
Can Be Modulated By
Possible Closure Effects
-
Potentially Conflicting With
-
History
A pattern based on the original introduction by Glas[1].
References
- ↑ 1.0 1.1 Glas, R. (2015). Of Heroes and Henchmen: The Conventions of Killing Generic Expendables in Video Games. In Mortensen, T.E., Linderoth, J. & Brown, A. ML. (2015). The Dark Side of Game Play - Controversial Issues in Playful Environments. Routledge.
- ↑ Entry for "Mooks" in the TV Tropes wiki.
Acknowledgements
René Glas
