Asynchronous Collaborative Actions - Revision history

Staffan Björk: /* History */

2014-09-21T07:33:39Z

‎History

Staffan Björk: /* Can Modulate */

2014-09-13T06:39:26Z

‎Can Modulate

Staffan Björk: /* Can Modulate */

2014-09-13T06:39:07Z

‎Can Modulate

Staffan Björk at 13:54, 8 October 2012

2012-10-08T13:54:41Z

Staffan Björk at 10:02, 8 October 2012

2012-10-08T10:02:34Z

Staffan Björk at 09:51, 8 October 2012

2012-10-08T09:51:37Z

Staffan Björk: /* Examples */

2012-10-08T09:47:55Z

‎Examples

Staffan Björk at 09:24, 8 October 2012

2012-10-08T09:24:08Z

Staffan Björk: /* Consequences */

2012-10-08T09:10:09Z

‎Consequences

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

2012-10-08T09:01:10Z

‎Using the pattern

@@ Line 55: / Line 55: @@
 == History ==
-New pattern created in this wiki.
+New pattern created for this wiki by [[User:Staffan Björk|Staffan Björk]].
 == References ==

@@ Line 39: / Line 39: @@
 === Can Modulate ===
-[[Abilities]]
 === Can Be Instantiated By ===

@@ Line 39: / Line 39: @@
 === Can Modulate ===
+[[Abilities]]
 === Can Be Instantiated By ===

@@ Line 1: / Line 1: @@
 [[Category:Patterns]]
-[[Category:Needs work]]
+[[Category:To be Published]]
 [[Category:Needs revision]]
 [[Category:Needs examples]]
 [[Category:Needs references]]
 [[Category:Patterns created on the Wiki]]
 ''Collaboration between players where the actions do not need to be done simultaneously or be observed by the other collaborators.''
-Many games allow players to collaborate. In many cases the collaboration is done by players doing actions simultaneously and being able to observe each other, and in these cases players can easily notice that everyone is doing what they committed themselves to doing and how the collaboration progresses. However, collaboration can be achieved by players without them doing the actions at the same time and without them being aware of others' actions as they are being done. In these [[Asynchronous Collaborative Actions]] players have to place trust in other players, and while this may make it more difficult to achieve it at the same time can provide more satisfaction when it works.
+Many games allow players to collaborate. In many cases the collaboration is done by players doing actions simultaneously and being able to observe each other, and in these cases players can easily notice that everyone is doing what they committed themselves to doing and how the collaboration progresses. However, collaboration can be achieved by players without them doing the actions at the same time and without them being aware of others' actions as they are being done. In these [[Asynchronous Collaborative Actions]], players have to place trust in other players, and while this may make it more difficult to achieve it at the same time can provide more satisfaction when it works.
 === Examples ===
@@ Line 16: / Line 15: @@
 == Using the pattern ==
-[[Asynchronous Collaborative Actions]] is basically [[Cooperation]] through [[Asynchronous Gameplay]], but can be seen as a pattern in itself since it gives rise to some consequences that neither of the two more basic patterns do on their own. One primary design choice for the pattern is how many actions in sequence is necessary for the [[Cooperation]] to give benefits, and another is if [[Rewards]] are given out simultaneously or not. While these choices exists for [[Cooperation]] in general, they more strongly affect the probability that it will occur for [[Asynchronous Collaborative Actions]] since players need to trust each other more for these actions.
+[[Asynchronous Collaborative Actions]] is basically [[Cooperation]] through [[Asynchronous Gameplay]], but can be seen as a pattern in itself since it gives rise to some consequences that neither of the two more basic patterns do on their own. One primary design choice for the pattern is how many actions in sequence are necessary for the [[Cooperation]] to give benefits, and another is if [[Rewards]] are given out simultaneously or not. While these choices exists for [[Cooperation]] in general, they more strongly affect the probability that it will occur for [[Asynchronous Collaborative Actions]] since players need to trust each other more for these actions.
-While [[Cooperation]] is a clear way to create the pattern, it can also be achieved in a more voluntary form through [[Altruistic Actions]]. In this case, the pattern emerges from several individual actions that form as collaboration when viewed together over time.
+While [[Cooperation]] is a clear way to create the pattern, it can also be achieved in more voluntary form through [[Altruistic Actions]]. In this case, the pattern emerges from several individual actions that form as collaboration when viewed together over time.
 [[Time Limits]] can be used to either make both voluntary and necessary cooperation feel more forced.
@@ Line 26: / Line 25: @@
 == Consequences ==
-[[Asynchronous Collaborative Actions]] is more difficult to achieve that [[Cooperation]], and for that reason it can be a way to provide [[Complex Gameplay]]. It provides a [[Possibility of Anonymity]] since players do not need to observe or directly interact with each other. It does however not in itself enforce the anonymity since players may be able to notice each other and may be able to synchronize the collaboration even if they do not engage in gameplay at the same time. The pattern gives [[Encouraged Return Visits]] when the [[Asynchronous Collaborative Actions]] consists of several steps or can be repeated.
+[[Asynchronous Collaborative Actions]] is more difficult to achieve that [[Cooperation]], and for this reason, it can be a way to provide [[Complex Gameplay]]. It provides a [[Possibility of Anonymity]] since players do not need to observe or directly interact with each other. It does however not in itself enforce the anonymity since players may be able to notice each other and may be able to synchronize the collaboration even if they do not engage in gameplay at the same time. The pattern gives [[Encouraged Return Visits]] when the [[Asynchronous Collaborative Actions]] consist of several steps or can be repeated.
 [[Functional Roles]] can be seen as one consequence of [[Asynchronous Collaborative Actions]] since either the specific [[Abilities]] of players dictate different roles or that the time when they should do the actions define roles. The dependence on others that the pattern creates can cause [[Social Dilemmas]] and make players engage in [[Guilting]].

@@ Line 11: / Line 11: @@
 === Examples ===
+[[Momentum]] requires players in each team to do many types of collaboration but not necessarily at together. One example is putting effort into having control of different parts of the game world.
 Social media games such as [[FarmVille]] and [[Zombie Lane]] are weak examples of [[Asynchronous Collaborative Actions]] since the collaboration consists of independent altruistic actions.

@@ Line 17: / Line 17: @@
 == Using the pattern ==
 [[Asynchronous Collaborative Actions]] is basically [[Cooperation]] through [[Asynchronous Gameplay]], but can be seen as a pattern in itself since it gives rise to some consequences that neither of the two more basic patterns do on their own. One primary design choice for the pattern is how many actions in sequence is necessary for the [[Cooperation]] to give benefits, and another is if [[Rewards]] are given out simultaneously or not. While these choices exists for [[Cooperation]] in general, they more strongly affect the probability that it will occur for [[Asynchronous Collaborative Actions]] since players need to trust each other more for these actions.
 [[Time Limits]] can be used to either make both voluntary and necessary cooperation feel more forced.
@@ Line 41: / Line 43: @@
 === Can Be Instantiated By ===
-[[Asynchronous Gameplay]] together with [[Cooperation]]
+[[Asynchronous Gameplay]] together with [[Altruistic Actions]] or [[Cooperation]]
 === Can Be Modulated By ===

← Older revision		Revision as of 09:47, 8 October 2012
Line 11:		Line 11:

	=== Examples ===		=== Examples ===
		+
		+
		+	Social media games such as [[FarmVille]] and [[Zombie Lane]] are weak examples of [[Asynchronous Collaborative Actions]] since the collaboration consists of independent altruistic actions.

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

@@ Line 22: / Line 22: @@
 == Consequences ==
-Since [[Asynchronous Collaborative Actions]]
+[[Asynchronous Collaborative Actions]] provides a [[Possibility of Anonymity]] since players do not need to observe or directly interact with each other. It does however not in itself enforce the anonymity since players may be able to notice each other and may be able to synchronize the collaboration even if they do not engage in gameplay at the same time. The pattern gives [[Encouraged Return Visits]] when the [[Asynchronous Collaborative Actions]] consists of several steps or can be repeated.
-[[Encouraged Return Visits]],
+[[Functional Roles]] can be seen as one consequence of [[Asynchronous Collaborative Actions]] since either the specific [[Abilities]] of players dictate different roles or that the time when they should do the actions define roles. The dependence on others that the pattern creates can cause [[Social Dilemmas]] and make players engage in
+[[Guilting]].
-[[Possibility of Anonymity]],
-−
-−
-[[Functional Roles]],
-−
-−
-[[Guilting]],
-[[Social Dilemmas]]
 == Relations ==

@@ Line 14: / Line 14: @@
 == Using the pattern ==
-[[Asynchronous Collaborative Actions]] is basically [[Cooperation]] through [[Asynchronous Gameplay]], but can be seen as a pattern in itself since it gives rise to some consequences that neither of the two more basic patterns do on their own. [[Time Limits]] can be used to either make both voluntary and necessary cooperation feel more forced.
+[[Asynchronous Collaborative Actions]] is basically [[Cooperation]] through [[Asynchronous Gameplay]], but can be seen as a pattern in itself since it gives rise to some consequences that neither of the two more basic patterns do on their own. One primary design choice for the pattern is how many actions in sequence is necessary for the [[Cooperation]] to give benefits, and another is if [[Rewards]] are given out simultaneously or not.
 === Interface Aspects ===