Generic Adversaries - Revision history

Staffan Björk at 12:45, 31 August 2015

2015-08-31T12:45:54Z

← Older revision		Revision as of 12:45, 31 August 2015
Line 1:		Line 1:
	[[Category:Patterns]]		[[Category:Patterns]]
	~~[[Category:Needs work]]~~
	[[Category:Needs revision]]		[[Category:Needs revision]]
	~~[[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]]~~
	''More or less adversary diegetic entities that are indistinguishable from other similar entities.''		''More or less adversary diegetic entities that are indistinguishable from other similar entities.''

Staffan Björk at 12:44, 31 August 2015

2015-08-31T12:44:50Z

← Older revision		Revision as of 12:44, 31 August 2015
Line 10:		Line 10:
	''More or less adversary diegetic entities that are indistinguishable from other similar entities.''		''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.		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"/>.''

Staffan Björk at 12:44, 31 August 2015

2015-08-31T12:44:05Z

← Older revision		Revision as of 12:44, 31 August 2015
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~~.''		''More or less adversary diegetic entities that are indistinguishable from other similar entities.''

	~~This pattern is a still a stub~~.		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.

	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"/>.''

Staffan Björk at 12:18, 31 August 2015

2015-08-31T12:18:13Z

← Older revision		Revision as of 12:18, 31 August 2015
Line 25:		Line 25:

	== 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 ==
	~~[[Randomness]]~~

	=== Can Instantiate ===		=== Can Instantiate ===
	[[Enemies]],		[[Enemies]],
	[[Grinding]],		[[Grinding]],
			[[Inhabitants]],
	[[Kiting]],		[[Kiting]],
	[[NPCs]],		[[NPCs]],
	[[~~Inhabitants~~]],		[[Repetitive Gameplay]],
	[[Units]],		[[Units]],
	[[Waves]]		[[Waves]]
Line 48:		Line 47:

	=== Can Be Modulated By ===		=== Can Be Modulated By ===
	[[Loot]]		[[Loot]],
			[[Randomness]]

	=== Possible Closure Effects ===		=== Possible Closure Effects ===

Staffan Björk at 12:15, 31 August 2015

2015-08-31T12:15:34Z

← Older revision		Revision as of 12:15, 31 August 2015
Line 20:		Line 20:

	== Using the pattern ==		== Using the pattern ==
	[[Generic Adversaries]] are diegetically intentional entities that are identical to each other. As such, they can fill roles for [[Enemies]] ~~(especially~~ in [[Waves]]), [[Inhabitants]], and [[NPCs]] that ~~need to exist in large numbers~~. ~~They~~ 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).		[[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.		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.

Staffan Björk: /* Examples */

2015-08-31T12:13:38Z

Examples

← Older revision		Revision as of 12:13, 31 August 2015
Line 15:		Line 15:

	=== Examples ===		=== 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]].

	~~==== Anti-Examples ====~~		The regular "infected" that players encounters in the [[Left 4 Dead series]] may look different from each other but are otherwise [[Generic Adversaries]].
	~~optional~~

	== Using the pattern ==		== Using the pattern ==

Staffan Björk: /* Using the pattern */

2015-08-31T12:10:22Z

Using the pattern

@@ Line 20: / Line 20: @@
 == Using the pattern ==
-[[Generic Adversaries]] are diegetically intentional entities that are identical to each other. As such, they
+[[Generic Adversaries]] are diegetically intentional entities that are identical to each other. As such, they can fill roles for [[Enemies]] (especially in [[Waves]]), [[Inhabitants]], and [[NPCs]] that need to exist in large numbers. They 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).
-[[Enemies]]
+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 ==

Staffan Björk: /* Relations */

2015-08-31T11:52:19Z

Relations

← Older revision		Revision as of 11:52, 31 August 2015
Line 50:		Line 50:

	== Relations ==		== Relations ==
			[[Randomness]]

	=== Can Instantiate ===		=== Can Instantiate ===
	[[Enemies]],		[[Enemies]],

Staffan Björk: /* Using the pattern */

2015-08-31T11:52:11Z

Using the pattern

← Older revision		Revision as of 11:52, 31 August 2015
Line 20:		Line 20:

	== Using the pattern ==		== Using the pattern ==
			[[Generic Adversaries]] are diegetically intentional entities that are identical to each other. As such, they

			[[Enemies]]

			The design involved in creating [[Generic Adversaries]] consists of making a template for them

	=== Can Instantiate ===		=== Can Instantiate ===
	~~[[Enemies]]~~,		,
	[[Grinding]],		[[Grinding]],
	[[Kiting]],		[[Kiting]],

Staffan Björk: /* Consequences */

2015-08-31T11:48:50Z

Consequences

← Older revision		Revision as of 11:48, 31 August 2015
Line 39:		Line 39:

	== Consequences ==		== Consequences ==
	~~=== Can Instantiate ===~~		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]].
	[[~~Grinding~~]],
	[[Kiting]],		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 ==