Patterns Slay the Spire exemplifies
| Pattern | How Spire uses it |
|---|---|
subtractive-deckbuilding | Power lives in removing weak cards, not adding strong ones. Inverts traditional deckbuilders. |
card-draft-with-skip | Post-fight reward = pick 1 of 3 or skip. Skipping has real value because thin decks are stronger. |
branching-dag-map | Procedural map with partial-info path planning; player commits to a route at the start of each act. |
tight-energy-budget | 3 energy / 5 cards forces hard prioritization every turn. |
expiring-block | Defense doesn't accumulate across turns. Forecast every turn separately. |
enemy-intent-telegraph | Enemies signal next action visibly. Combat = optimization puzzle, not RNG fight. |
rule-breaking-relics | Each relic adds a small modifier that warps a run's identity. Hundreds of relics → hundreds of run flavors. |
bonus-with-drawback | Boss relics (and many uncommon relics) pair upside with a real cost. Forces commit. |
cumulative-modifier-staircase | 20 stacking single-lesson modifiers, not a slider. Now a genre-standard pattern. |
meta-as-variety-not-power | Unlocks expand the space, never raise base stats. Run integrity preserved. |
orthogonal-class-design | Each character is a different system stack on top of the same combat shell, not a stat reskin. |
shared-seed-daily | Same seed for everyone today; leaderboard reveals skill. Low cost, high engagement. |
metrics-driven-balance | Patches driven by win-rate / pick-rate telemetry, not vibes. |
pity-system-anti-streak | Hidden counters bias rare drops upward when unlucky; smooths feel-bad runs. |
handcrafted-pcg-hybrid | Hand-authored content + procedurally arranged map. |