Teams - Revision history

Staffan Björk at 12:11, 19 March 2018

2018-03-19T12:11:18Z

Staffan Björk at 12:10, 19 March 2018

2018-03-19T12:10:39Z

Staffan Björk at 06:52, 27 August 2015

2015-08-27T06:52:38Z

Staffan Björk: /* Can Be Instantiated By */

2015-08-07T12:13:48Z

‎Can Be Instantiated By

Staffan Björk at 12:12, 7 August 2015

2015-08-07T12:12:16Z

Staffan Björk at 15:04, 6 August 2015

2015-08-06T15:04:33Z

Staffan Björk: /* Consequences */

2015-08-06T10:10:28Z

‎Consequences

Staffan Björk at 10:04, 6 August 2015

2015-08-06T10:04:04Z

Staffan Björk: /* Examples */

2015-08-06T10:02:04Z

‎Examples

Staffan Björk at 10:01, 6 August 2015

2015-08-06T10:01:57Z

@@ Line 25: / Line 25: @@
 There are several ways of creating the necessary members of [[Teams]]. The oldest way is simply to require a number of [[Agents]] (including [[AI Players]]) with [[Mutual Goals]] (where each players can actually be seen as a game element in a game that uses [[Heterogeneous Game Element Ownership]]). [[Factions]] and [[Parties]] is similar but can for [[:Category:Computer Games|Computer Games]] be simulated with one player together with [[Companions]] that are controlled by [[Algorithmic Agents]]. [[Units]] together with abilities to do [[Combos]] in [[Single-Player Games]] is another option where only one player is needed. The addition of [[Coaches]] offers to add a special type of players to [[Teams]] than don't perform the regular actions of the team but help with actions related to team management and training. [[Teams]] do not necessarily have to apply to whole game instances, they can also be required to be created before players can enter [Instances]].
-[[Teams]] can have [[Characteristics]] and [[Scores]] attached to them besides way of identifying them and lists of which members they have, and can through this be [[Abstract Player Constructs]]. For games with [[Trick Taking]], e.g. [[Contract Bridge]], having [[Teams]] make it natural to both collect tricks and [[Scores]] jointly within [[Teams]]. Having [[Characteristics]] or [[Abstract Player Constructs]],  this allows for [[Team Development]],  and in the case where players have some [[Freedom of Choice]] on how which direction the development should take, [[Player-Planned Development]].
+[[Teams]] can have [[Characteristics]] and [[Scores]] attached to them besides way of identifying them and lists of which members they have, and can through this be [[Abstract Player Constructs]]. For games with [[Trick Taking]], e.g. [[Contract Bridge]], having [[Teams]] make it natural to both collect tricks and [[Scores]] jointly within [[Teams]]. Having [[Characteristics]] or [[Abstract Player Constructs]],  this allows for [[Team Development]],  and in the case where players have some [[Freedom of Choice]] on how which direction the development should take, [[Player-Planned Development]]. [[Extra-Game Actions]], especially those that can be done before or after game instances can also support [[Team Development]].
 Several patterns relate to [[Teams]] and how members in them behave. [[Reserves]], which can be used both on [[Teams]] consisting of [[Agents]] or those consisting of [[Characters]], can let members rest if gameplay requires [[Physical Enactment]] or [[Player Physical Prowess]]. [[Enforced Agent Behavior]] can be used to make the members act in the best interest of the [[Teams|Team]] to which they belong. [[Drop-In/Drop-Out]], [[Early Leaving Players]], [[Late Arriving Players]], [[Ragequitting]], and [[Surrendering]] are relate to how a game design can or should handle that members can want to join or leave [[Teams]] during ongoing game sessions. [[Invites]] and [[Game Lobbies]] in games that have [[Mediated Gameplay]] can help create [[Teams]] before gameplay begins.

@@ Line 75: / Line 75: @@
 [[Team Combos]], [[Team Strategy Identification]]
-==== with [[Character Development]], [[Characteristics]], [[Gameplay Mastery]], [[Improved Abilities]] or [[New Abilities]] ====
+==== with [[Character Development]], [[Characteristics]], [[Extra-Game Actions]], [[Gameplay Mastery]], [[Improved Abilities]], or [[New Abilities]] ====
 [[Team Development]]

@@ Line 21: / Line 21: @@
 == Using the pattern ==
-The basic requirements of [[Teams]] are that they consist of a number of members (more than one) and that they have [[Shared Rewards]] and [[Shared Penalties]]; not all [[Rewards]] or [[Penalties]] need to be shared but without any there is no core motivation to make the members be a [[Teams|Team]]. There are several ways of creating the necessary members of [[Teams]]. The oldest way is simply to require a number of [[Agents]] (including [[AI Players]]) with [[Mutual Goals]] (where each players can actually be seen as a game element in a game that uses [[Heterogeneous Game Element Ownership]]). [[Factions]] and [[Parties]] is similar but can for [[:Category:Computer Games|Computer Games]] be simulated with one player together with [[Companions]] that are controlled by [[Algorithmic Agents]]. [[Units]] together with abilities to do [[Combos]] in [[Single-Player Games]] is another option where only one player is needed. The addition of [[Coaches]] offers to add a special type of players to [[Teams]] than don't perform the regular actions of the team but help with actions related to team management and training. [[Teams]] do not necessarily have to apply to whole game instances, they can also be required to be created before players can enter [Instances]].
+The basic requirements of [[Teams]] are that they consist of a number of members (more than one) and that they have [[Shared Rewards]] and [[Shared Penalties]]; not all [[Rewards]] or [[Penalties]] need to be shared but without any there is no core motivation to make the members be a [[Teams|Team]]. The possibility of [[Player Elimination]] is one example of [[Individual Penalties]] that often are worth considering in the designs of [[Teams]] (and shows how an [[Individual Penalties|Individual Penalty]] can indirectly affect others since it can weaken [[Teams]]).
 [[Teams]] can have [[Characteristics]] and [[Scores]] attached to them besides way of identifying them and lists of which members they have, and can through this be [[Abstract Player Constructs]]. For games with [[Trick Taking]], e.g. [[Contract Bridge]], having [[Teams]] make it natural to both collect tricks and [[Scores]] jointly within [[Teams]]. Having [[Characteristics]] or [[Abstract Player Constructs]],  this allows for [[Team Development]],  and in the case where players have some [[Freedom of Choice]] on how which direction the development should take, [[Player-Planned Development]].
@@ Line 31: / Line 33: @@
 Some patterns make it more difficult for [[Teams]] to function efficiently or at all. [[Betrayal]] and [[Internal Conflicts]] can cause suspicion and threaten the existence of [[Teams]] while [[Delayed Reciprocity]] can cause them to not be created. [[Internal Rivalry]] make team play more difficult but does typically not threaten to dissolve [[Teams]]. [[Difficulty Levels]] can be created specifically to make team play more difficult by hindering [[Coordination]] (e.g. not should the locations of other team members as is done in the [[Left 4 Dead series]]). [[Friendly Fire]] also makes team play more difficult since members might be eliminated by their own and cause social conflicts among players (or change the opinions [[Companions]] in cases these make up the members of a [[Teams|Team]]). In contrast, [[Chat Channels]], [[Handles]], and [[Mini-maps]] can help [[Teams]] function better by helping them to do [[Coordination]].
-[[Teams]] can modify [[Last Man Standing]] or [[PvP]] gameplay to set up [[TvT]] gameplay. Such designs raises question whether the designs should also have [[Player Killing]], [[Team Balance]], and/or [[Team Elimination]]. In these cases, providing [[Teams]] with [[Privileged Abilities]] can cause problems with [[Team Balance]].
+[[Teams]] can modify [[Last Man Standing]] or [[PvP]] gameplay to set up [[TvT]] gameplay. Such designs raises question whether the designs should also have [[Player Killing]] (and [[Player Elimination]]), [[Team Balance]], and/or [[Team Elimination]]. In these cases, providing [[Teams]] with [[Privileged Abilities]] can cause problems with [[Team Balance]].
 === Interface Aspects ===
@@ Line 178: / Line 180: @@
 [[Geospatial Game Widgets]],
 [[Handles]],
 [[Internal Conflicts]],
 [[Internal Rivalry]],
@@ Line 183: / Line 186: @@
 [[Late Arriving Players]],
 [[Mini-maps]],
 [[Player Killing]],
 [[Privileged Abilities]],

@@ Line 151: / Line 151: @@
 [[Factions]],
 [[Heterogeneous Game Element Ownership]],
-[[Parties]]
+[[Parties]],
 [[Agents]] with [[Mutual Goals]]

@@ Line 21: / Line 21: @@
 == Using the pattern ==
-There are several ways of creating the necessary members of [[Teams]]. The oldest way is simply to require a number of [[Agents]] (including [[AI Players]]) with [[Mutual Goals]] (where each players can actually be seen as a game element in a game that uses [[Heterogeneous Game Element Ownership]]). [[Factions]] and [[Parties]] is similar but can for [[:Category:Computer Games|Computer Games]] be simulated with one player together with [[Companions]] that are controlled by [[Algorithmic Agents]]. [[Units]] together with abilities to do [[Combos]] in [[Single-Player Games]] is another option where only one player is needed. The addition of [[Coaches]] offers to add a special type of players to [[Teams]] than don't perform the regular actions of the team but help with actions related to team management and training. [[Teams]] do not necessarily have to apply to whole game instances, they can also be required to be created before players can enter [Instances]].
+The basic requirements of [[Teams]] are that they consist of a number of members (more than one) and that they have [[Shared Rewards]] and [[Shared Penalties]]; not all [[Rewards]] or [[Penalties]] need to be shared but without any there is no core motivation to make the members be a [[Teams|Team]]. There are several ways of creating the necessary members of [[Teams]]. The oldest way is simply to require a number of [[Agents]] (including [[AI Players]]) with [[Mutual Goals]] (where each players can actually be seen as a game element in a game that uses [[Heterogeneous Game Element Ownership]]). [[Factions]] and [[Parties]] is similar but can for [[:Category:Computer Games|Computer Games]] be simulated with one player together with [[Companions]] that are controlled by [[Algorithmic Agents]]. [[Units]] together with abilities to do [[Combos]] in [[Single-Player Games]] is another option where only one player is needed. The addition of [[Coaches]] offers to add a special type of players to [[Teams]] than don't perform the regular actions of the team but help with actions related to team management and training. [[Teams]] do not necessarily have to apply to whole game instances, they can also be required to be created before players can enter [Instances]].
 [[Teams]] can have [[Characteristics]] and [[Scores]] attached to them besides way of identifying them and lists of which members they have, and can through this be [[Abstract Player Constructs]]. For games with [[Trick Taking]], e.g. [[Contract Bridge]], having [[Teams]] make it natural to both collect tricks and [[Scores]] jointly within [[Teams]]. Having [[Characteristics]] or [[Abstract Player Constructs]],  this allows for [[Team Development]],  and in the case where players have some [[Freedom of Choice]] on how which direction the development should take, [[Player-Planned Development]].

@@ Line 21: / Line 21: @@
 == Using the pattern ==
-There are several ways of creating the necessary members of [[Teams]]. The oldest way is simply to require a number of [[Agents]] (including [[AI Players]]) with [[Mutual Goals]] (where each players can actually be seen as a game element in a game that uses [[Heterogeneous Game Element Ownership]]). [[Factions]] and [[Parties]] is similar but can for [[:Category:Computer Games|Computer Games]] be simulated with one player together with [[Companions]] that are controlled by [[Algorithmic Agents]]. [[Units]] together with abilities to do [[Combos]] in [[Single-Player Games]] is another option where only one player is needed. [[Teams]] do not necessarily have to apply to whole game instances, they can also be required to be created before players can enter [Instances]].
+There are several ways of creating the necessary members of [[Teams]]. The oldest way is simply to require a number of [[Agents]] (including [[AI Players]]) with [[Mutual Goals]] (where each players can actually be seen as a game element in a game that uses [[Heterogeneous Game Element Ownership]]). [[Factions]] and [[Parties]] is similar but can for [[:Category:Computer Games|Computer Games]] be simulated with one player together with [[Companions]] that are controlled by [[Algorithmic Agents]]. [[Units]] together with abilities to do [[Combos]] in [[Single-Player Games]] is another option where only one player is needed. The addition of [[Coaches]] offers to add a special type of players to [[Teams]] than don't perform the regular actions of the team but help with actions related to team management and training. [[Teams]] do not necessarily have to apply to whole game instances, they can also be required to be created before players can enter [Instances]].
 [[Teams]] can have [[Characteristics]] and [[Scores]] attached to them besides way of identifying them and lists of which members they have, and can through this be [[Abstract Player Constructs]]. For games with [[Trick Taking]], e.g. [[Contract Bridge]], having [[Teams]] make it natural to both collect tricks and [[Scores]] jointly within [[Teams]]. Having [[Characteristics]] or [[Abstract Player Constructs]],  this allows for [[Team Development]],  and in the case where players have some [[Freedom of Choice]] on how which direction the development should take, [[Player-Planned Development]].
@@ Line 37: / Line 37: @@
 == Consequences ==
-The main consequence of [[Teams]] is cause [[Agents]], [[Avatars]], or [[Characters]] to have to have [[Cooperation]] and to a lesser degree [[Coordination]]. This can for example be by requiring separation to maximize [[Area Control]], making best use of [[Transferable Items]], or handling the [[Asymmetric Roles]] members get due to having [[Asymmetric Starting Conditions]]. However, the possibilities for [[Individual Rewards]] in [[Races]] can give rise to [[Internal Rivalry]] and the possibility of [[Ninja Looting]] can cause [[Internal Conflicts]]. [[Friendly Fire]] can be another concern for [[Cooperation]], i.e. if [[Player Killing]] of one's own team members is possible through intentional actions or mistakes. Perhaps most problematic of [[Cooperation]], the possibility of [[Betrayal]] makes for [[Complex Gameplay]] and provides a source for [[Tension]] among all members of a [[Teams|Team]]. [[Teams]] can be pitched against each other in [[TvT]] gameplay by applying the design possibilities of [[Last Man Standing]] or [[PvP]] on [[Teams]]. The possibility of succeeding with [[Eliminate]] goals of individual members in [[Teams]] can lead to complete [[Team Elimination]].
+The main consequence of [[Teams]] is to cause [[Agents]], [[Avatars]], or [[Characters]] to have to have [[Cooperation]] and to a lesser degree [[Coordination]]. This can for example be by requiring separation to maximize [[Area Control]], making best use of [[Transferable Items]], or handling the [[Asymmetric Roles]] members get due to having [[Asymmetric Starting Conditions]]. However, the possibilities for [[Individual Rewards]] in [[Races]] can give rise to [[Internal Rivalry]] and the possibility of [[Ninja Looting]] can cause [[Internal Conflicts]]. [[Friendly Fire]] can be another concern for [[Cooperation]], i.e. if [[Player Killing]] of one's own team members is possible through intentional actions or mistakes. Perhaps most problematic of [[Cooperation]], the possibility of [[Betrayal]] makes for [[Complex Gameplay]] and provides a source for [[Tension]] among all members of a [[Teams|Team]]. [[Teams]] can be pitched against each other in [[TvT]] gameplay by applying the design possibilities of [[Last Man Standing]] or [[PvP]] on [[Teams]]. The possibility of succeeding with [[Eliminate]] goals of individual members in [[Teams]] can lead to complete [[Team Elimination]].
 [[Teams]] often can or need to achieve [[Coordination]], e.g. through handling [[Privileged Abilities]] or [[Transferable Items]]. [[Mini-maps]] can help with this, especially when the show the position of the other team members ([[Geospatial Game Widgets]] can help with this as well). Such [[Coordination]] can make [[Team Combos]] possible. Other ways that more concretely offer possibilities for [[Team Combos]] include [[Flanking Routes]] and [[Mini-maps]]. In general, [[Teams]] consisting of [[Characters]] with [[Orthogonal Differentiation]] in [[Abilities]] or [[Characteristics]] or any [[Teams|Team]] where some members have [[Privileged Abilities]] or different [[Skills]] make it likely that [[Team Combos]] can be found. Finding [[Team Combos]] through using [[Mini-maps]] or combining the actions of [[Characters]] with [[Orthogonal Differentiation]] can be cases of [[Team Strategy Identification]].
@@ Line 166: / Line 166: @@
 [[Characteristics]],
 [[Chat Channels]],
 [[Collaborative Actions]],
 [[Conditional Passageways]],

@@ Line 41: / Line 41: @@
 [[Teams]] often can or need to achieve [[Coordination]], e.g. through handling [[Privileged Abilities]] or [[Transferable Items]]. [[Mini-maps]] can help with this, especially when the show the position of the other team members ([[Geospatial Game Widgets]] can help with this as well). Such [[Coordination]] can make [[Team Combos]] possible. Other ways that more concretely offer possibilities for [[Team Combos]] include [[Flanking Routes]] and [[Mini-maps]]. In general, [[Teams]] consisting of [[Characters]] with [[Orthogonal Differentiation]] in [[Abilities]] or [[Characteristics]] or any [[Teams|Team]] where some members have [[Privileged Abilities]] or different [[Skills]] make it likely that [[Team Combos]] can be found. Finding [[Team Combos]] through using [[Mini-maps]] or combining the actions of [[Characters]] with [[Orthogonal Differentiation]] can be cases of [[Team Strategy Identification]].
-[[Teams]] affect [[Multiplayer Games]] and [[Massively Multiplayer Online Games]] more than [[Single-Player]] games due to creating [[Symbiotic Player Relations]] and typically cause many patterns related to [[Social Interaction]]. First, it causes [[Stimulated Planning]] as players need to consider how to have best [[Cooperation]] and [[Coordination]]. Second, it can easily cause [[Social Dilemmas]] (e.g. by [[Individual Rewards]] or the risk of [[Friendly Fire]] or [[Player Killing]]). Third, those with [[Privileged Abilities]] in [[Teams]] can gain [[Game-Based Social Statuses]]. Fourth, in the case where [[Extra Chances]] are available to [[Teams]] rather than individual members, these become [[Shared Resources]] whose use need to be negotiated. Fifth, if players can take on [[Functional Roles]], this can be used to let inexperienced players take on easy role or make it easier for experienced players to explain abilities and responsibility to the new players. This makes for [[Smooth Learning Curves]]. Sixth, players may take on [[Social Roles]] and working together can give rise to [[Social Rewards]] and [[Togetherness]] regardless of if the [[Teams]] actually succeed with their goals. However, failing with achieving goals can lead to [[Guilting]]. Finally, they modify [[Roleplaying]] by encouraging [[Enactment]] of it and not only the fulfilling the goals of [[Characters]]. These pattern can occur even if not all players are actually humans (i.e. if some are [[AI Players]]) but the more games are true [[Multiplayer Games]] the more [[Social Skills]] become important and people can feel that they have achieved [[Team Strategy Identification]] before or during gameplay and [[Team Accomplishments]] after closures. When [[FUBAR Enjoyment]] occurs in these situations, they can become [[Mutual FUBAR Enjoyment]].
+[[Teams]] affect [[Multiplayer Games]] and [[Massively Multiplayer Online Games]] more than [[Single-Player Games]] due to creating [[Symbiotic Player Relations]] and typically cause many patterns related to [[Social Interaction]]. First, it causes [[Stimulated Planning]] as players need to consider how to have best [[Cooperation]] and [[Coordination]]. Second, it can easily cause [[Social Dilemmas]] (e.g. by [[Individual Rewards]] or the risk of [[Friendly Fire]] or [[Player Killing]]). Third, those with [[Privileged Abilities]] in [[Teams]] can gain [[Game-Based Social Statuses]]. Fourth, in the case where [[Extra Chances]] are available to [[Teams]] rather than individual members, these become [[Shared Resources]] whose use need to be negotiated. Fifth, if players can take on [[Functional Roles]], this can be used to let inexperienced players take on easy role or make it easier for experienced players to explain abilities and responsibility to the new players. This makes for [[Smooth Learning Curves]]. Sixth, players may take on [[Social Roles]] and working together can give rise to [[Social Rewards]] and [[Togetherness]] regardless of if the [[Teams]] actually succeed with their goals. However, failing with achieving goals can lead to [[Guilting]]. Finally, they modify [[Roleplaying]] by encouraging [[Enactment]] of it and not only the fulfilling the goals of [[Characters]]. These pattern can occur even if not all players are actually humans (i.e. if some are [[AI Players]]) but the more games are true [[Multiplayer Games]] the more [[Social Skills]] become important and people can feel that they have achieved [[Team Strategy Identification]] before or during gameplay and [[Team Accomplishments]] after closures. When [[FUBAR Enjoyment]] occurs in these situations, they can become [[Mutual FUBAR Enjoyment]].
 [[Teams]] can be [[Abstract Player Constructs]] if the game state contains information about the [[Teams]] besides what members are part of them. In these cases, changes in [[Characteristics]] or rewards of [[Improved Abilities|Improved]] or [[New Abilities]] causes [[Team Development]]. If the [[Teams]] consists of [[Characters]] the presence of [[Character Development]] can do the same, as can the possibility of [[Gameplay Mastery]] in [[Teams]] consisting of people.

@@ Line 1: / Line 1: @@
 [[Category:Mechanical Patterns]]
 [[Category:Patterns]]
 [[Category:Needs revision]]
 [[Category:Needs references]]
 [[Category:To be Published]]
 ''Agents or game elements that use their actions to work towards the same common goal or goals.''
-Games typically have several players that can affect it, and also often have several different game elements that can perform actions. When either of these two groups are give common goals that they can together work towards completing, the game can be said to have [[Teams]].
+Games typically have several players that can affect it, and also often have several different game elements that can perform actions. When either of these two groups are given common goals that they can together work towards completing, the game can be said to have [[Teams]].
 === Examples ===
@@ Line 31: / Line 27: @@
 Several patterns relate to [[Teams]] and how members in them behave. [[Reserves]], which can be used both on [[Teams]] consisting of [[Agents]] or those consisting of [[Characters]], can let members rest if gameplay requires [[Physical Enactment]] or [[Player Physical Prowess]]. [[Enforced Agent Behavior]] can be used to make the members act in the best interest of the [[Teams|Team]] to which they belong. [[Drop-In/Drop-Out]], [[Early Leaving Players]], [[Late Arriving Players]], [[Ragequitting]], and [[Surrendering]] are relate to how a game design can or should handle that members can want to join or leave [[Teams]] during ongoing game sessions. [[Invites]] and [[Game Lobbies]] in games that have [[Mediated Gameplay]] can help create [[Teams]] before gameplay begins.
-Actions of team members can be modified to take into consideration that they are part of [[Teams]]. [[Altruistic Actions]] can let players make actions that only indirectly might help themselves. [[Collaborative Actions]] motive players to have both [[Cooperation]] and [[Coordination]] to perform otherwise impossible actions, some of which may be specific [[Team Combos]]. [[Functional Roles]] and [[Privileged Abilities]] make only some actions available to some team members and thereby also encourage [[Cooperation]] and [[Coordination]]. Related to actions, the use of some patterns that affect [[Game Worlds]], e.g. [[Arenas]], [[Conditional Passageways]], and [[Sniper Locations]], can require extra consideration since they do after teamplay and team dynamics.
+Actions of team members can be modified to take into consideration that they are part of [[Teams]]. [[Altruistic Actions]] can let players make actions that only indirectly might help themselves. [[Collaborative Actions]] motive players to have both [[Cooperation]] and [[Coordination]] to perform otherwise impossible actions, some of which may be specific [[Team Combos]]. [[Functional Roles]] and [[Privileged Abilities]] make only some actions available to some team members and thereby also encourage [[Cooperation]] and [[Coordination]]. Related to actions, the use of some patterns that affect [[Game Worlds]], e.g. [[Arenas]], [[Conditional Passageways]], and [[Sniper Locations]], can require extra consideration since they do after team play and team dynamics.
-Some patterns make it more difficult for [[Teams]] to function efficiently or at all. [[Betrayal]] and [[Internal Conflicts]] can cause suspicion and threaten the existence of [[Teams]] while [[Delayed Reciprocity]] can cause them to not be created. [[Internal Rivalry]] make teamplay more difficult but does typically not threaten to dissolve [[Teams]]. [[Difficulty Levels]] can be created specifically to make teamplay more difficult by hindering [[Coordination]] (e.g. not should the locations of other team members as is done in the [[Left 4 Dead series]]). [[Friendly Fire]] also makes teamplay more difficult since members might be eliminated by their own and cause social conflicts among players (or change the opinions [[Companions]] in cases these make up the members of a [[Teams|Team]]). In contrast, [[Chat Channels]], [[Handles]], and [[Mini-maps]] can help [[Teams]] function better by helping them to do [[Coordination]].
+Some patterns make it more difficult for [[Teams]] to function efficiently or at all. [[Betrayal]] and [[Internal Conflicts]] can cause suspicion and threaten the existence of [[Teams]] while [[Delayed Reciprocity]] can cause them to not be created. [[Internal Rivalry]] make team play more difficult but does typically not threaten to dissolve [[Teams]]. [[Difficulty Levels]] can be created specifically to make team play more difficult by hindering [[Coordination]] (e.g. not should the locations of other team members as is done in the [[Left 4 Dead series]]). [[Friendly Fire]] also makes team play more difficult since members might be eliminated by their own and cause social conflicts among players (or change the opinions [[Companions]] in cases these make up the members of a [[Teams|Team]]). In contrast, [[Chat Channels]], [[Handles]], and [[Mini-maps]] can help [[Teams]] function better by helping them to do [[Coordination]].
 [[Teams]] can modify [[Last Man Standing]] or [[PvP]] gameplay to set up [[TvT]] gameplay. Such designs raises question whether the designs should also have [[Player Killing]], [[Team Balance]], and/or [[Team Elimination]]. In these cases, providing [[Teams]] with [[Privileged Abilities]] can cause problems with [[Team Balance]].

@@ Line 15: / Line 15: @@
 [[Ice Hockey]], [[Soccer]], and [[Tug of war]] are [[:Category:Sports|Sports]] with [[Teams]]. The normal form of [[Tennis]] does not have [[Teams]] but the double variant has. [[Contract Bridge]] is an example of a [[:Category:Card Games|Card Game]] with two-player [[Teams]].
-[[Chess]], [[Go]], and [[Pachisi]] are weak examples of [[:Category:Board games|Board Games]] with [[Teams]] since although the individual game elements under one player's control works towards common goals (the player's), the do not have team characteristics or strong team development.
+[[Chess]], [[Go]], and [[Pachisi]] are weak examples of [[:Category:Board Games|Board Games]] with [[Teams]] since although the individual game elements under one player's control works towards common goals (the player's), the do not have team characteristics or strong team development.
 [[Bloodbowl]] is however a better example since here [[Teams]] have characteristics independent of the members and the members can develop over time (when playing with campaigns). However, for [[:Category:Board Games|Board Games]] [[Teams]] may more often be used to pitch players against the game itself. Examples of such games include [[Battlestar Galactica: The Board Game]], [[Dead of Winter: A Crossroads Game]], [[Shadows over Camelot]], [[Space Alert]], [[XCOM: The Board Game]], and [[Yggdrasil]].

@@ Line 8: / Line 8: @@
 [[Category:To be Published]]
 [[Category:Staffan's current workpage]]
-''The one-sentence "definition" that should be in italics.''
+''Agents or game elements that use their actions to work towards the same common goal or goals.''
-This pattern is a still a stub.
+Games typically have several players that can affect it, and also often have several different game elements that can perform actions. When either of these two groups are give common goals that they can together work towards completing, the game can be said to have [[Teams]].
 === Examples ===
-[[Ice Hockey]], [[Soccer]], and [[Tug of war]] are [[:Category:Sports|Sports]] with [[Teams]]. The normal form of [[Tennis]] does not have [[Teams]] but the double variant has. [[Contract Bridge]] is an example of a [[:Category:Card Games|Card Game]] with two-player [[Teams]]. For [[:Category:Board Games|Board Games]], [[Teams]] are typically used to pitch players against the game itself. Examples of such games include [[Battlestar Galactica: The Board Game]], [[Dead of Winter: A Crossroads Game]], [[Shadows over Camelot]], [[Space Alert]], [[XCOM: The Board Game]], and [[Yggdrasil]].
+[[Ice Hockey]], [[Soccer]], and [[Tug of war]] are [[:Category:Sports|Sports]] with [[Teams]]. The normal form of [[Tennis]] does not have [[Teams]] but the double variant has. [[Contract Bridge]] is an example of a [[:Category:Card Games|Card Game]] with two-player [[Teams]].
-[[Teams]] are not so formalized in [[:Category:Roleplaying Games|Roleplaying Games]] such as [[Dungeons & Dragons]], the various games using the [[Storytelling Systems]], and long-lasting [[:Category:Live Action Roleplaying Games|LARP]] campaigns (as for example some use the [[Mind's Eye Theatre]] system are). Instead, players more or less voluntarily organize in parties or factions but part of the gameplay tension in these may be due to players switching, or threatening to switch, alliances.
+[[Chess]], [[Go]], and [[Pachisi]] are weak examples of [[:Category:Board games|Board Games]] with [[Teams]] since although the individual game elements under one player's control works towards common goals (the player's), the do not have team characteristics or strong team development.
-[[America's Army]], the [[Battlefield series]], the [[Counter-Strike series]], the [[Left 4 Dead series]], and the [[Return to Castle Wolfenstein: Enemy Territory]] are all dedicated team-based [[:Category:Online Games|Online]] [[:Category:Computer Games|Computer Games]].
+[[Teams]] are not so formalized in [[:Category:Roleplaying Games|Roleplaying Games]] such as [[Dungeons & Dragons]], the various games using the [[Storytelling System]], and long-lasting [[:Category:Live Action Roleplaying Games|LARP]] campaigns (as for example some use the [[Mind's Eye Theatre]] system are). Instead, players more or less voluntarily organize in parties or factions but part of the gameplay tension in these may be due to players switching, or threatening to switch, alliances.
 For more examples, see the category of [[:Category:Team-based Games|Team-Based Games]].