Cycle Deck Engines: Difference between revisions
From gdp3
Jump to navigationJump to search
No edit summary |
|||
| Line 9: | Line 9: | ||
[[Category:To be Published]] | [[Category:To be Published]] | ||
[[Category:Staffan's current workpage]] | [[Category:Staffan's current workpage]] | ||
'' | ''A game engine built around being able to go through as much of a deck as possible.'' | ||
This pattern is a still a stub. | This pattern is a still a stub. | ||
| Line 23: | Line 23: | ||
[[Deck Building]] | [[Deck Building]] | ||
[[Combos]] | [[Combos]] | ||
[[Cards]] | |||
[[Decks]] | |||
=== Diegetic Aspects === | === Diegetic Aspects === | ||
Revision as of 16:06, 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.
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
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
-
