Endgame: Difference between revisions
From gdp3
Jump to navigationJump to search
| Line 36: | Line 36: | ||
== Relations == | == Relations == | ||
[[Kingmaker]] | [[Kingmaker]] | ||
[[Player Unpredictability]] | |||
[[ | |||
=== Can Instantiate === | === Can Instantiate === | ||
- | [[Analysis Paralysis]], | ||
[[Higher-Level Closures as Gameplay Progresses]] | |||
=== Can Modulate === | === Can Modulate === | ||
| Line 57: | Line 53: | ||
=== Can Be Modulated By === | === Can Be Modulated By === | ||
[[Construction/Scoring Phase Shift]] | [[Construction/Scoring Phase Shift]], | ||
[[Early Leaving Players]], | |||
[[Player Elimination]] | |||
=== Possible Closure Effects === | === Possible Closure Effects === | ||
Revision as of 21:04, 26 July 2015
The one-sentence "definition" that should be in italics.
This pattern is a still a stub.
Examples
Chess and Go are well-known classical Board Games with distinct Endgame phases.
In the Starcraft series the Endgame is typically called "Late-Game"<ref name="Starcraft"/>.
Anti-Examples
optional
Using the pattern
Diegetic Aspects
Interface Aspects
Narration Aspects
Consequences
Relations
Can Instantiate
Analysis Paralysis, Higher-Level Closures as Gameplay Progresses
Can Modulate
-
Can Be Instantiated By
Entrenching Gameplay, Extermination
Can Be Modulated By
Construction/Scoring Phase Shift, Early Leaving Players, Player Elimination
Possible Closure Effects
-
Potentially Conflicting With
-
History
New pattern created in this wiki.
References
<references> <ref name="Starcraft">Entry for "Late-game" at the Wiki for Starcraft II at teamliquid.</ref> </references>
Acknowledgements
-
