Automated Responses - Revision history

Staffan Björk at 09:31, 15 July 2016

2016-07-15T09:31:43Z

Staffan Björk at 21:18, 5 July 2015

2015-07-05T21:18:06Z

Staffan Björk: /* Examples */

2015-07-05T21:17:55Z

‎Examples

Staffan Björk at 21:15, 5 July 2015

2015-07-05T21:15:09Z

Staffan Björk at 21:48, 4 July 2015

2015-07-04T21:48:42Z

Staffan Björk at 21:47, 4 July 2015

2015-07-04T21:47:11Z

Staffan Björk: /* Examples */

2015-07-04T21:44:18Z

‎Examples

Staffan Björk at 21:42, 4 July 2015

2015-07-04T21:42:43Z

Staffan Björk: /* Relations */

2015-07-04T21:37:17Z

‎Relations

Staffan Björk: /* Examples */

2015-07-04T21:33:02Z

‎Examples

@@ Line 30: / Line 30: @@
 [[Automated Responses]] are ways of modulating [[Avatars]], [[Characters]], or (at least) [[Chat Channels]]. By doing so they can created [[Enforced Agent Behavior]] or provide [[Player Augmentations]]. When they are combined with [[Player/Character Skill Composites]], the resulting effect can become [[Player/System Action Composites]]. However, the use of [[Automated Responses]] can create the loss of [[Player Agency]].
-[[Automated Responses]] can help players have [[Smooth Learning Curves]]. When [[Automated Responses]] brings players' attention to certain features about the current game state, they function as [[Point of Interest Indications]].
+[[Automated Responses]] can help players have [[Smooth Learning Curves]]. When [[Automated Responses]] brings players' attention to certain features about the current game state, they function as [[Point of Interest Indicators]].
 == Relations ==
@@ Line 36: / Line 36: @@
 [[Enforced Agent Behavior]],
 [[Player Augmentations]],
-[[Point of Interest Indications]],
+[[Point of Interest Indicators]],
 [[Smooth Learning Curves]]

@@ Line 1: / Line 1: @@
 [[Category:Mechanical Patterns]]
 [[Category:Needs revision]]
 [[Category:Needs references]]
 [[Category:Patterns created on the Wiki]]

@@ Line 12: / Line 12: @@
 Encountering boss monsters in some games in the [[Super Mario series]] trigger cut scenes where the monsters are clearly presented so players are made aware of their significance.
+A weak examples of [[Automated Responses]] is the "look" action in [[:Category:Adventure Games|Adventure Games]] such as [[Maniac Mansion]] and the [[Zork series]], which while they do inform players about game elements are in fact triggered by specific actions by players rather than game state configurations. Stronger examples can be found in Multiuser Dungeons such as [[DragonMud]] and [[Kingdoms]] where players can create [[Automated Responses]] by writing code which interprets output from the game and produces input to the game for the players. [[Ultima Online]] and [[World of Warcraft]] provided similar functionality.
 A weak examples of [[Automated Responses]] is the "look" action in [[:Category:Adventure Games|Adventure Games]] such as [[Maniac Mansion]] and the [[Zork series]], which while they do inform players about game elements are in fact triggered by specific actions by players rather than game state configurations.
 == Using the pattern ==

@@ Line 11: / Line 11: @@
 === Examples ===
 Encountering boss monsters in some games in the [[Super Mario series]] trigger cut scenes where the monsters are clearly presented so players are made aware of their significance.
 A weak examples of [[Automated Responses]] is the "look" action in [[:Category:Adventure Games|Adventure Games]] such as [[Maniac Mansion]] and the [[Zork series]], which while they do inform players about game elements are in fact triggered by specific actions by players rather than game state configurations.

@@ Line 1: / Line 1: @@
 [[Category:Mechanical Patterns]]
 [[Category:Needs revision]]
 [[Category:Needs examples]]
 [[Category:Needs references]]
 [[Category:Patterns created on the Wiki]]
 [[Category:To be Published]]
 ''Events triggered by game state configurations designed to either inform players or make responses for them.''
-Many game designs have either wish to ensure players to be aware of certain facts about some specific game states as they occur or want to ensure specific responses by the game elements players control. Both of these things can be created by [[Automated Responses]], triggered events that the game system executes based on detecting certain game states.
+Many game designs have either wish to ensure players to be aware of certain facts about some specific game states as they occur or want to ensure specific responses by the game elements that players control. Both of these things can be created by [[Automated Responses]], triggered events that the game system executes based on detecting certain game states.
 === Examples ===
@@ Line 29: / Line 26: @@
 === Narration Aspects ===
-Since [[Automated Responses]] can provide narration (e.g when used with [[Voice-overs]]), the pattern can be an [[:Category:Narration Patterns|Narration Pattern]].
+Since [[Automated Responses]] can provide narration (e.g. when used with [[Voice-overs]]), the pattern can be a [[:Category:Narration Patterns|Narration Pattern]].
 == Consequences ==

@@ Line 19: / Line 19: @@
 == Using the pattern ==
-Designing [[Automated Responses]] consist of deciding what responses show exist (and why) and when they should be given. The types of responses can be divided into two main categories: the ones that affect the game state and the ones that only inform players about the game state. [[Voice-overs]] is one way of creating [[Automated Responses]] without affecting game states while [[Algorithmic Agents]] and [[Mules]] can perform gameplay actions as [[Automated Responses]].
+Designing [[Automated Responses]] consist of deciding what responses show exist (and why) and when they should be given. The types of responses can be divided into two main categories: the ones that affect the game state and the ones that only inform players about the game state. [[Cutscenes]] and [[Voice-overs]] are ways of creating [[Automated Responses]] without affecting game states while [[Algorithmic Agents]] and [[Mules]] can perform gameplay actions as [[Automated Responses]].
 When [[Automated Responses]] should be given are typically bound tightly to the specific responses that should be possible, e.g. providing specific information about a game element, or related to it, when it is encountered. Quite naturally, [[Line of Sight]] can be used to make the [[Automated Responses]] only be made about things the player is actually looking at.
 === Interface Aspects ===
@@ Line 36: / Line 38: @@
 == Relations ==
 === Can Instantiate ===
 [[Enforced Agent Behavior]],

← Older revision		Revision as of 21:33, 4 July 2015
Line 13:		Line 13:

	=== Examples ===		=== Examples ===
		+
		+

	A weak examples of [[Automated Responses]] is the "look" action in [[:Category:Adventure Games\|Adventure Games]] such as [[Maniac Mansion]] and the [[Zork series]], which while they do inform players about game elements are in fact triggered by specific actions by players rather than game state configurations.		A weak examples of [[Automated Responses]] is the "look" action in [[:Category:Adventure Games\|Adventure Games]] such as [[Maniac Mansion]] and the [[Zork series]], which while they do inform players about game elements are in fact triggered by specific actions by players rather than game state configurations.