Closure Points: Difference between revisions
Created page with "Category:Patterns Category:Needs work Category:Needs revision Category:Needs examples Category:Needs references Category:Stub Category:To be Publishe..." |
No edit summary |
||
| Line 48: | Line 48: | ||
=== Can Instantiate === | === Can Instantiate === | ||
[[Value of Effort]] | |||
==== with ... ==== | ==== with ... ==== | ||
Revision as of 14:45, 18 December 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
Irreversible Events Staries Higher-Level Closures as Gameplay Progresses Levels Excluding Goals Finale Levels Downtime Save Points
Instantiates: Limited Foresight
Modulates: Predictable Consequences, Narrative Structures
Instantiated by: Tournaments, Transfer of Control
Modulated by: Committed Goals
Potentially conflicting with: Never Ending Stories
Can Instantiate
with ...
Can Modulate
-
Can Be Instantiated By
-
Can Be Modulated By
-
Possible Closure Effects
-
Potentially Conflicting With
-
History
An updated version of the pattern Closure Points 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
-
