Difference between revisions of "Mules"

From gdp3
Jump to: navigation, search
 
(33 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
[[Category:Patterns]]
 
[[Category:Patterns]]
 
[[Category:Agent Patterns]]
 
[[Category:Agent Patterns]]
[[Category:Needs work]]
+
[[Category:Needs references]]
[[Category:Needs examples]]
+
''Code algorithms that can take over the role of players from repetitious tasks.''
[[Category:Stub]]
+
 
''Algorithmic Agents that can take over the role of players from humans.''
+
Some games, especially online games, require players to perform smaller or larger sequences of actions repetitiously. One way to let players avoid this is through letting them relinquish control to a program, a [[Mules|Mule]], for parts of the gameplay. While this may let them escape boring sequences of gameplay, if they are allowed to also create these [[Mules]] they are provided with a possibility of being inventive and creative.
  
 
=== Examples ===
 
=== Examples ===
 +
The first possibilities to creates [[Mules]] appeared in Multiuser Dungeons. While [[DragonMud]] provided a limited way to add more content, [[Kingdoms]] made a programming language similar to C available to trusted players. The commercial massively multiplayer game [[Ultima Online]] provided similar but more restricted functionality through macros<ref name="UO"/>. This was followed in [[World of Warcraft]], which provides players with a set of functions that can be used for writing scripts. These scripts can vary from being practical macros that reduce the amount of excise but can also be more complex scripts capable of interacting with the environment.<ref name="WoWAPI"/>.
 +
 +
Although not created by the players themselves, the bots that can take over their role in the [[Left 4 Dead series]] can be seen as a form of [[Mules]]. This since they can let players take pauses during less important sections of them game.
  
 
== Using the pattern ==
 
== Using the pattern ==
 +
[[Mules]] need to be able to control [[Avatars]] and often make use of the information stored in [[Characters]] ([[Mules]] are typically not applied to [[Units]] - probably due to the complexity of handling groups of agents). The main difference of designing [[Mules]] and [[AI Players]] is that [[Mules]] only need to be able to fill in for players for limited amount of time and limited sets of activities. Since this makes it easier to design them, it is also easier to help players create them. Ranging from [[Action Programming]] to access to a full programming language, this can provide the players with [[Creative Control]] and a form of [[Meta Games|Meta Game]] to design them as well as possible.
 +
 +
The most common use of [[Mules]] is to perform some form of [[Grinding]] concerning [[Character Development]] or the gathering of a [[Resources|Resource]]. To modulate the efficiency of using the [[Mules]], the resource generated may have [[Diminishing Returns]], require [[Skills]], or require the presence of [[Non-Renewable Resources]] or [[Renewable Resources]] with a lower replenishment rate than the rate of consumption set for the [[Mules]]. Since [[Mules]] represent the players, they have to stand in for the [[Social Interaction]] expected on them, letting them control [[Emotes]] is one way of doing this.
 +
 +
The use of [[Mules]] can become a [[Risk/Reward]] tradeoff if there is a chance of having critical failures of the actions being performed, typically leading to the loss of [[Equipment]], attacks by [[Enemies]], and maybe [[Player Elimination]]. These challenges may be simple to deal with if players can monitor the [[Mules]] as [[Spectators]], but when the [[Mules]] are set to do actions without supervision this may leave the [[Mules]] incapable of responding appropriately to these failure situations.
  
 
=== Diegetic Aspects ===
 
=== Diegetic Aspects ===
 +
Depending on what activities the [[Mules]] should be able to handle, this can put various difficulties in achieving [[Thematic Consistency]], where [[Dialogues]] can be an example of a difficult area. When players can create the [[Mules]], this of course puts the responsibility of maintaining [[Thematic Consistency]] into their hands.
  
 
=== Interface Aspects ===
 
=== Interface Aspects ===
 
+
If players should be able to create or modify [[Mules]] they need [[Secondary Interface Screens]].
=== Narrative Aspects ===
+
  
 
== Consequences ==
 
== Consequences ==
 +
[[Mules]] are a limited form of [[AI Players]] that work as [[Proxy Players]] to provide [[Automated Responses]] or make players escape [[Excise]], most often concerning improving [[Characters]]. As such, they are also examples of [[Player Augmentations|Player Augmentation]] through [[Algorithmic Agents]] and [[Agents]]. The use of [[Mules]] is arguably a form of [[Sanctioned Cheating]], either sanctioned by the players or by the game designers.
  
== Relations ==
+
When players can create the [[Mules]] themselves, the pattern also provides [[Creative Control]] and a form of [[Meta Games|Meta Game]].
  
 +
== Relations ==
 
=== Can Instantiate ===
 
=== Can Instantiate ===
 +
[[Automated Responses]],
 +
[[Creative Control]], [[Meta Games]],
 +
[[Player Augmentations]],
 +
[[Proxy Players]], [[Risk/Reward]],
 +
[[Sanctioned Cheating]]
  
 
=== Can Modulate ===
 
=== Can Modulate ===
[[Algorithmic Agents]]
+
[[Avatars]], [[Characters]],
 +
[[Character Development]],
 +
[[Emotes]]  
  
 
=== Can Be Instantiated By ===
 
=== Can Be Instantiated By ===
 +
[[Action Programming]], [[AI Players]], [[Algorithmic Agents]]
  
 
=== Can Be Modulated By ===
 
=== Can Be Modulated By ===
 +
[[Diminishing Returns]], [[Non-Renewable Resources]], [[Renewable Resources]], [[Secondary Interface Screens]], [[Skills]], [[Spectators]]
 +
 +
=== Possible Closure Effects ===
 +
-
  
 
=== Potentially Conflicting With ===
 
=== Potentially Conflicting With ===
 +
[[Thematic Consistency]], [[Excise]], [[Grinding]]
  
 
== History ==
 
== History ==
Line 36: Line 59:
 
== References ==
 
== References ==
 
<references>
 
<references>
 +
<ref name="UO">[http://www.uoguide.com/KR_Macros Entry] about creating macros on the UOGuide site.</ref>
 +
<ref name="WoWAPI">[http://www.wowwiki.com/World_of_Warcraft_API Entry] describing the World of Warcraft API on the WoWWiki.</ref>
 
<ref name="Bjork & Holopainen 2004">Björk, S. & Holopainen, J. (2004) Patterns in Game Design. Charles River Media. ISBN1-58450-354-8.</ref>
 
<ref name="Bjork & Holopainen 2004">Björk, S. & Holopainen, J. (2004) Patterns in Game Design. Charles River Media. ISBN1-58450-354-8.</ref>
 
</references>
 
</references>

Latest revision as of 21:16, 4 July 2015

Code algorithms that can take over the role of players from repetitious tasks.

Some games, especially online games, require players to perform smaller or larger sequences of actions repetitiously. One way to let players avoid this is through letting them relinquish control to a program, a Mule, for parts of the gameplay. While this may let them escape boring sequences of gameplay, if they are allowed to also create these Mules they are provided with a possibility of being inventive and creative.

Examples

The first possibilities to creates Mules appeared in Multiuser Dungeons. While DragonMud provided a limited way to add more content, Kingdoms made a programming language similar to C available to trusted players. The commercial massively multiplayer game Ultima Online provided similar but more restricted functionality through macros[1]. This was followed in World of Warcraft, which provides players with a set of functions that can be used for writing scripts. These scripts can vary from being practical macros that reduce the amount of excise but can also be more complex scripts capable of interacting with the environment.[2].

Although not created by the players themselves, the bots that can take over their role in the Left 4 Dead series can be seen as a form of Mules. This since they can let players take pauses during less important sections of them game.

Using the pattern

Mules need to be able to control Avatars and often make use of the information stored in Characters (Mules are typically not applied to Units - probably due to the complexity of handling groups of agents). The main difference of designing Mules and AI Players is that Mules only need to be able to fill in for players for limited amount of time and limited sets of activities. Since this makes it easier to design them, it is also easier to help players create them. Ranging from Action Programming to access to a full programming language, this can provide the players with Creative Control and a form of Meta Game to design them as well as possible.

The most common use of Mules is to perform some form of Grinding concerning Character Development or the gathering of a Resource. To modulate the efficiency of using the Mules, the resource generated may have Diminishing Returns, require Skills, or require the presence of Non-Renewable Resources or Renewable Resources with a lower replenishment rate than the rate of consumption set for the Mules. Since Mules represent the players, they have to stand in for the Social Interaction expected on them, letting them control Emotes is one way of doing this.

The use of Mules can become a Risk/Reward tradeoff if there is a chance of having critical failures of the actions being performed, typically leading to the loss of Equipment, attacks by Enemies, and maybe Player Elimination. These challenges may be simple to deal with if players can monitor the Mules as Spectators, but when the Mules are set to do actions without supervision this may leave the Mules incapable of responding appropriately to these failure situations.

Diegetic Aspects

Depending on what activities the Mules should be able to handle, this can put various difficulties in achieving Thematic Consistency, where Dialogues can be an example of a difficult area. When players can create the Mules, this of course puts the responsibility of maintaining Thematic Consistency into their hands.

Interface Aspects

If players should be able to create or modify Mules they need Secondary Interface Screens.

Consequences

Mules are a limited form of AI Players that work as Proxy Players to provide Automated Responses or make players escape Excise, most often concerning improving Characters. As such, they are also examples of Player Augmentation through Algorithmic Agents and Agents. The use of Mules is arguably a form of Sanctioned Cheating, either sanctioned by the players or by the game designers.

When players can create the Mules themselves, the pattern also provides Creative Control and a form of Meta Game.

Relations

Can Instantiate

Automated Responses, Creative Control, Meta Games, Player Augmentations, Proxy Players, Risk/Reward, Sanctioned Cheating

Can Modulate

Avatars, Characters, Character Development, Emotes

Can Be Instantiated By

Action Programming, AI Players, Algorithmic Agents

Can Be Modulated By

Diminishing Returns, Non-Renewable Resources, Renewable Resources, Secondary Interface Screens, Skills, Spectators

Possible Closure Effects

-

Potentially Conflicting With

Thematic Consistency, Excise, Grinding

History

A revised version of the pattern Mule that was part of the original collection in the book Patterns in Game Design[3].

References

  1. Entry about creating macros on the UOGuide site.
  2. Entry describing the World of Warcraft API on the WoWWiki.
  3. Björk, S. & Holopainen, J. (2004) Patterns in Game Design. Charles River Media. ISBN1-58450-354-8.

Acknowledgments

Karl-Petter Åkesson