Challenge & Difficulty in Game Design

Main ideas & lessons

• Designers constantly face conflicting impulses

  • One “voice” urges designers to be kind to players and ensure they have a good time.
  • The other urges designers to make players’ lives harder.
  • The development process involves listening, debating, and choosing a direction for challenge/difficulty.

• Not all games center on challenge

  • Some games are primarily interactive stories (the player experiences a world) or toys (no real failure/success evaluation).
  • For genres like action, strategy, and puzzle, challenge and difficulty are core to the experience.
  • Larger projects may blend multiple elements; smaller indies may focus on one or two.

• The “difficulty mode” conversation is partly semantic

  • The video notes a trend: replacing “easy mode” with “story mode” to better match what players actually want (e.g., play for narrative, not repeated failure).

• Even “non-skill” genres need friction

  • If a game doesn’t revolve around player skill/failure, designers still must:
    • define the player’s goal
    • provide interesting friction so the goal isn’t reached instantly

• Key definitions: difficulty vs challenge (video framing)

  • Difficulty = quantitative (“how much”)
    • Implemented via sliders/accessibility controls, global variables, and numerical changes.
    • Often affects variables broadly or at specific progression points/modes.
  • Challenge = qualitative (“what kind”)
    • Determines which skills the game tests (reaction, planning, navigation, judgment, etc.).
    • Shapes the player’s intended thinking and reactions.

• Indie development mistake: balancing too early

  • Many devs prematurely focus on difficulty tuning and data-driven balancing before the game is proven fun and viable.
  • Balancing requires:
    • spreadsheets/data systems
    • knowledge of what “kind of challenge” the game actually provides
  • Before that stage, the priority is finding the fun and validating the game’s core challenge.

• Project timeline context (why balancing is late-stage)

  • Pre-production: prototype, early playtesting, write short planning docs—figure out what game you’re making and whether it’s worth finishing.
  • Production point / “green light”: enough prototypes tested; art style and appeal validated.
  • Balancing/tuning comes near the end, after the game’s direction and fun are established.

• You can’t tune difficulty while barriers to play exist

  • Players may struggle for unintended reasons (bad readability, control complexity, usability issues).
  • If the player is failing due to barriers, you can’t accurately judge whether the intended challenge is enjoyable.
  • Example (Spelunky anecdote): removing “the net” when the real issue is a “broken racket” (controls).

• Design levers: ways to vary challenge

  • Challenge can be modified by changing the game’s “situation” and context.
  • Examples by game type:
    • Action/reaction games: different opponents and how they behave.
    • Puzzle games: different components, arrangement possibilities, and red herrings/misinformation.

• Practical challenge example: dungeon crawling

  • To increase challenge for a player getting stronger, change it in different ways—each tests different skills:
    • More enemies at once: mostly increases time/pressure; may not test new skills much.
    • Deadlier enemies: tests combat ability (blocking/dodging, timing, survival).
    • More variety of enemy types: tests identification, prioritization, spatial awareness, and increases cognitive load.

• Cognitive load matters

  • Cognitive load = how much mental effort is demanded at a time.
  • High cognitive load isn’t automatically bad:
    • boredom often happens when load is too low
    • “good learning difficulty” matches complexity to the player’s learning stage

• Fun is linked to learning and “play”

  • Referenced ideas: fun helps us learn; curiosity; testing system “play”/flexibility.
  • Varied challenge and thematic content generally increase engagement and longevity.

• Genre as a shortcut to expected challenge

  • Genres help align audience expectations with the skill checks they want.
  • Indies should treat playing games as research to understand genre patterns and player motivations.
  • Blindly entering an unfamiliar genre wastes far more time than the play-research it replaces.

• Genre mechanics example: how tags imply challenge

  • Metroidvania/Soulslike
    • Metroidvania → navigation/spatial awareness and memorization.
    • Combat → timing/reflexes/enemy behavior knowledge.
    • Soulslike → corpse runs create stronger friction/punishment (double punishment).
  • Casual strategy/incremental
    • Planning and resource investment/spending decisions.
    • “Casual” often means fewer long-lasting punishments compared to hardcore resource-heavy games.

• Skill floor/ceiling: range of player expression

  • Skill floor: minimum skill to function at all (controls/usability competence).
  • Skill ceiling: maximum skill achievable.
  • Games differ by how wide/narrow this range is:
    • “Rage” games may offer little “degree of success” (very binary success/failure).
    • Systems like grades/stars create degrees of success, helping weaker players feel progression while still supporting improvement.

• How games pressure players: aspirational vs continuous difficulty

  • Continuous difficulty: how hard the game pushes you toward losing (e.g., likely/frequent failure or costly mistakes).
  • Aspirational difficulty: how hard it is to succeed well (there’s a “better way,” mastery yields better outcomes).
  • Good design often aims to:
    • enable success as learning (aspirational)
    • control “pressure toward failure” (continuous) using friction/punishment design
  • Example: Celeste strawberries
    • Not a hard-mode requirement, but optional harder content.
    • Preserves flexibility and supports curiosity/completionist motivation.

• Challenge doesn’t always need explicit modes

  • Players can create “self-created challenges” through system mastery (e.g., using physics/automation to turn milk into cheese more efficiently).

• A 2-axis mapping of game types

  • Places game styles on an aspirational/continuous difficulty spectrum:
    • digital toys → low/no difficulty
    • punishing action → high continuous difficulty; often high skill ceiling
    • roguelites → continuous difficulty exists but softened by progression
    • cozy life sims/idle incrementals → more grind/time investment; less “trying to kill you”
  • Key takeaway: challenge affects emotion
    • continuous difficulty → stress/relief cycles
    • aspirational difficulty → achievement from doing well

• Difficulty and presentation link to emotional tone

  • “Casual vs hardcore” aren’t insults; they’re market/design terms:
    • Casual: intuitive, low skill floor, interruptible, non-threatening aesthetics
    • Hardcore: demanding, less interruptible, complex, edgier aesthetics
  • Designers should intentionally choose emotional outcomes:
    • “punishing/cruel but rewarding” vs “relaxing/kind/forgiving”
  • Final framing: games are about feelings—if you don’t understand what feelings your game is meant to create, it won’t fit anyone.

---

Methodology / framework presented

1) Use two internal “voices” to decide your design direction

• Choose which philosophy you’re serving:
  • kindness / good time
  • punishment / “living hell”
• Make an explicit decision rather than letting development drift.

2) Identify whether your game needs challenge/difficulty

• If mainly:
  • interactive story or toy → don’t focus on challenge/difficulty as core.
• If action/strategy/puzzle (or mixed) → treat challenge/difficulty as core experience.

3) Provide friction even when skill isn’t the focus

• For the player’s goal:
  • list the tools available
  • define the goal
  • add complications/friction to prevent instant success

4) Distinguish “challenge” from “difficulty”

• Challenge (qualitative):
  • determine what skills are tested (reaction, planning, observation, navigation)
• Difficulty (quantitative):
  • determine how much pressure/testing happens
  • implement via variables, sliders, global modifiers, mode differences

5) Don’t balance/tune until the game is validated

• Focus earlier on:
  • prototyping
  • early playtesting
  • determining the intended challenge type
  • establishing art/theme appeal
• Delay:
  • spreadsheet/data-driven balancing
  • difficulty modes
  • extensive tuning
• Only after the project earns “green light.”

6) Eliminate barriers to play before tuning difficulty

• Audit why players fail:
  • unintended barriers (controls, usability, readability)
  • then only proceed to adjust intended difficulty/challenge
• Rule of thumb:
  • if players struggle for the wrong reason, perceived difficulty ≠ designed challenge.

7) Use “design levers” to vary challenge context

• Modify the situation so the player faces new scenarios:
  • different opponents/behaviors (action)
  • different puzzle components/arrangements/misinformation (puzzle)
• Ensure the core question stays central:
  • “What skills am I testing?”
  • “How does the game evolve so players don’t get bored once they improve?”

8) When increasing challenge in a leveling system, choose what skill you want to test

• Options include:
  • increase count (more enemies)
  • increase danger (more health/damage; more dodging/blocking)
  • increase variety (different enemy roles → prioritization/cognitive load)
• Decide which approach fits the intended “feel.”

9) Manage cognitive load deliberately

• Recognize:
  • early learning requires higher conscious focus
  • overloading the player can be harmful, but too little leads to boredom
• Aim for learning difficulty that matches player stage.

10) Plan progression of “degrees of success” and avoid binary frustration (if desired)

• Consider:
  • skill floor/ceiling range
  • partial rewards (stars/grades) to support progression even when not perfect
  • motivation to improve without forcing repetitive replays due to hard gating

11) Balance pressure using aspirational vs continuous difficulty

• Continuous difficulty:
  • reduce “how much the game pushes toward losing”
  • adjust punishment/friction and failure likelihood
• Aspirational difficulty:
  • raise “how hard it is to succeed well”
  • support mastery paths with better outcomes
• Use optional challenges (e.g., Celeste-style) instead of hard-mode mandates that block progress.

12) Use genre study as research to ensure intended challenge aligns with audience expectations

• Always play similar games to learn:
  • which skills the genre tests
  • why players enjoy the experience
• Avoid “designing blindly” in genre spaces you don’t understand.

---

Speakers / sources featured

Speakers

• Derek Yu (mentioned; referenced via his discussion/book about Spelunky).
• The video narrator / presenter (unnamed in the subtitles; speaks throughout).

Sources (books/articles/videos) mentioned

• Heartbeast: book on pre-production vs production (and a video about it).
• Thomas Stewart: video related to Heartbeast’s book.
• Raf Costa (and “other thinkers”): theories behind fun/learning.
• Ian Bogost: discussed regarding play (“wiggle room/play of a machine”).
• Derek Yu again: referenced as the author/discussant on Spelunky.
• Article (nearly 10 years old): introduces aspirational difficulty and continuous difficulty.
• Spelunky (game) and Spelunky-making discussion context.
• Celeste, Hades, Hollow Knight, Dark Souls, Darkest Dungeon, Blasphemous, Overcooked, Hotline Miami, Stardew Valley, NodeBuster, Bennett Foddy’s Getting Over It (examples referenced).
• Tiny Glade (examples of toy/story-like games).
• Espu (book author mentioned in difficulty/casual-hardcore marketing context; likely referring to game design discourse).