Análise: Slay the Spire🔗

Definição curta: Slay the Spire (2019) combina roguelike (runs únicas, progressão permanente entre runs) com deckbuilding (construir mazo durante o jogo) para criar um jogo com replayability praticamente infinita — cada run é diferente, cada escolha importa.

O que é🔗

Slay the Spire popularizou o gênero “deckbuilding roguelike” — desde seu sucesso, dezenas de clones apareceram.

flowchart TB
    subgraph StS["Slay the Spire sob MDA"]
        M["Mechanics\n- Cartas\n- Energy system\n- Enemy intents\n- Map with nodes\n- 3 characters/classes"]
        D["Dynamics\n- Deck construction\n- Card synergies\n- Risk assessment\n- Drafting strategy"]
        A["Aesthetics\n- Strategy depth\n- Mastery satisfaction\n- Variable runs\n- 'One more run' addiction"]
    end

    M --> D --> A

Índice de sub-tópicos🔗

• Deckbuilding mechanics
• Roguelike structure
• MDA breakdown
• Lições para game designers

Deckbuilding mechanics🔗

Core loop🔗

1. Start with basic deck (starter cards)
2. Travel through map (choose nodes)
3. Combat: play cards using energy
4. Earn cards (choose 1 of 3 after combat)
5. Earn relics (powerful items)
6. Event nodes: risk/reward choices
7. Shop nodes: buy/sell cards
8. Boss at end of act
9. 3 acts total, then victory or defeat

Table: Example character (Ironclad)🔗

Card types🔗

Attacks: Deal damage
Skills: Non-attack actions (defend, buff)
Powers: Persistent effects
Curses: Negative cards (from enemies)

Card drafting🔗

After each combat, choose 1 of 3 cards:

• Add to deck permanently
• Skip option
• Rare cards are powerful but limited

Roguelike structure🔗

Map as player agency🔗

flowchart LR
    subgraph Map["Mapa (Act 1)"]
        S["Start"]
        N1["Normal\nCombat"]
        N2["Elite\n(Hard combat)"]
        E1["Event"]
        R["Rest\n(Heal 30%)"]
        M1["Merchant\n(Shop)"]
        B["Boss\n(Spheric Guardian)"]
    end

    S --> N1 --> N2 --> E1 --> R --> M1 --> B
    S --> E1 --> N2
    S --> N1 --> R --> B

Linhas são choices — player decides path, balancing risk vs reward.

Node types🔗

MDA breakdown🔗

Mechanics🔗

- Turn-based combat
- Energy system (spend to play cards)
- Enemy intent display (shows next action)
- Map with branching paths
- Card reward selection
- Deck as resource (card draw, discard)

Dynamics🔗

Deck thinning: removing weak cards from deck

Combo discovery: finding card synergies

Risk balancing: elite fights vs rest vs shop

Powers stacking: some effects stack, some don’t

Aesthetics🔗

• Strategy: planning turns ahead
• Mastery: optimizing deck through runs
• Discovery: new card combinations
• Roguelike tension: one bad fight can end run

Lições para game designers🔗

1. Intentional randomization🔗

Slay the Spire shows enemies’ intentions — this REMOVES randomness frustration while keeping randomness.

Before: "Enemy did something unexpected, I died"
After: "Enemy WILL attack for 15 damage, can I block or kill it first?"

Lição: Randomness is frustrating when unpredictable. Show intent, keep randomness.

2. The “one more run” hook🔗

Each run: 30-60 minutes
Each run: different cards, different challenges
Each run: you get slightly better (knowledge)

Result: "One more run to try that new strategy"

Lição: Give player persistent progress in KNOWLEDGE, not just stats.

3. Deck as character expression🔗

Ironclad (tank/strength) vs
Silent (dex/poison) vs
Defect (orbs/evoke) vs
Watcher (stance switching)

Same mechanics, completely different feel

Lição: Multiple “characters” sharing mechanics extends content without full redesign.

4. Card game economy🔗

Card acquisition is THE progression
Shop lets you buy specific cards
Gold is earned, not bought

This means:
- "Perfect deck" is theoretically achievable
- But extremely unlikely
- Player always chasing "better deck"

Lição: Progression tied to gameplay (not XP) feels more meaningful.

5. Enemy design as tutorial🔗

Each enemy teaches something:

• “Slime Boss”: timing of attacks matters
• “Time Eater”: speed matters
• “Champ”: armor mechanics

Lição: Make each challenge teach AND test.

Veja também🔗

• Análise: Minecraft — sandbox/open world
• MDA Framework — framework analítico
• Game Loops — STS loop é referência

Referências🔗

• Schreiber, Ian & Romero, Brenda (2021). Game Balance. CRC Press. ISBN 978-1-351-64341-2.
• Costikyan, Greg (2013). Uncertainty in Games. MIT Press. ISBN 978-0-262-01896-8.
• GDC Vault — acervo de palestras da Game Developers Conference.