Difference between revisions of "Asynchronous Collaborative Actions"
(→Consequences) |
|||
| Line 5: | Line 5: | ||
[[Category:Needs references]] | [[Category:Needs references]] | ||
[[Category:Patterns created on the Wiki]] | [[Category:Patterns created on the Wiki]] | ||
| − | |||
[[Category:Staffan's current workpage]] | [[Category:Staffan's current workpage]] | ||
| − | '' | + | ''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. | |
=== Examples === | === Examples === | ||
== Using the pattern == | == 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. | + | [[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. | [[Time Limits]] can be used to either make both voluntary and necessary cooperation feel more forced. | ||
| Line 22: | Line 21: | ||
== Consequences == | == Consequences == | ||
| − | [[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. | + | [[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. |
| − | [[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 | + | [[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]]. |
| − | [[Guilting]]. | + | |
== Relations == | == Relations == | ||
=== Can Instantiate === | === Can Instantiate === | ||
| + | [[Complex Gameplay]], | ||
[[Encouraged Return Visits]], | [[Encouraged Return Visits]], | ||
[[Functional Roles]], | [[Functional Roles]], | ||
Revision as of 09:24, 8 October 2012
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.
Contents
Examples
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.
Interface Aspects
Communication Channels can be used in order to encourage the Asynchronous Collaborative Actions since this lets players remind each other. This also increases the likelihood for Guilting.
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.
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.
Relations
Can Instantiate
Complex Gameplay, Encouraged Return Visits, Functional Roles, Guilting, Possibility of Anonymity, Social Dilemmas
Can Modulate
-
Can Be Instantiated By
Asynchronous Gameplay together with Cooperation
Can Be Modulated By
Communication Channels, Time Limits
Possible Closure Effects
-
Potentially Conflicting With
-
History
New pattern created in this wiki.
References
-
Acknowledgements
-
