Team Development: Difference between revisions
From gdp3
Jump to navigationJump to search
| Line 28: | Line 28: | ||
== Relations == | == Relations == | ||
=== Can Instantiate === | |||
[[Abstract Player Construct Development]] | [[Abstract Player Construct Development]] | ||
==== with [[PvP]] ==== | ==== with [[PvP]] ==== | ||
[[Player Balance]] | [[Player Balance]] | ||
| Line 46: | Line 47: | ||
=== Can Be Instantiated By === | === Can Be Instantiated By === | ||
[[Character Development]] or [[Gameplay Mastery]] in games with [[Teams]] | |||
=== Can Be Modulated By === | === Can Be Modulated By === | ||
- | [[Player-Planned Development]] | ||
=== Possible Closure Effects === | === Possible Closure Effects === | ||
Revision as of 08:08, 1 August 2015
The one-sentence "definition" that should be in italics.
This pattern is a still a stub.
Examples
Anti-Examples
optional
Using the pattern
Diegetic Aspects
Interface Aspects
Narration Aspects
Consequences
Relations
Can Instantiate
Abstract Player Construct Development
with PvP
with Teams
Improved Abilities, New Abilities
with TvT
Can Modulate
Can Be Instantiated By
Character Development or Gameplay Mastery in games with Teams
Can Be Modulated By
Possible Closure Effects
-
Potentially Conflicting With
History
An updated version of the pattern Team Development that was part of the original collection in the book Patterns in Game Design<ref name="Bjork & Holopainen 2004"/>.
References
<references> <ref name="Bjork & Holopainen 2004">Björk, S. & Holopainen, J. (2004) Patterns in Game Design. Charles River Media. ISBN1-58450-354-8.</ref> </references>
Acknowledgements
-
