Difference between revisions of "Cycle Deck Engines"
From gdp3
m (Staffan Björk moved page Cycle Deck Engine to Cycle Deck Engines without leaving a redirect) |
(→Consequences) |
||
| Line 35: | Line 35: | ||
== Consequences == | == Consequences == | ||
| − | Rather obvious, a [[Cycle Deck | + | Rather obvious, a [[Cycle Deck Engines]] is an example of a [[Gameplay Engines|Gameplay Engine]]. |
== Relations == | == Relations == | ||
Revision as of 16:30, 26 July 2016
A game engine built around being able to go through as much of a deck as possible.
This pattern is a still a stub.
Contents
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 Engines is an example of a Gameplay Engine.
Relations
Can Instantiate
Can Modulate
-
Can Be Instantiated By
Cards, Deck Building, and Drawing Stacks
Can Be Modulated By
-
Possible Closure Effects
-
Potentially Conflicting With
-
History
New pattern created in this wiki.
References
-
Acknowledgements
-
