Cycle Deck Engines: Difference between revisions
From gdp3
Jump to navigationJump to search
No edit summary |
|||
| Line 31: | Line 31: | ||
== Consequences == | == Consequences == | ||
Rather obvious, a [[Cycle Deck Engine]] is an example of a [[Gameplay Engines|Gameplay Engine]]. | |||
== Relations == | == Relations == | ||
=== Can Instantiate === | === Can Instantiate === | ||
[[Gameplay Engines]] | [[Gameplay Engines]] | ||
Revision as of 16:04, 26 July 2016
The one-sentence "definition" that should be in italics.
This pattern is a still a stub.
Examples
Anti-Examples
optional
Using the pattern
"snurr-lek", Dominion, Spider-man decks in marvel
Diegetic Aspects
Interface Aspects
Narration Aspects
Consequences
Rather obvious, a Cycle Deck Engine is an example of a Gameplay Engine.
Relations
Can Instantiate
with ...
Can Modulate
-
Can Be Instantiated By
-
Can Be Modulated By
-
Possible Closure Effects
-
Potentially Conflicting With
-
History
New pattern created in this wiki.
References
-
Acknowledgements
-
