Video summary

혼자 게임 만들기 전에 꼭 알아야 할 기획의 기본

Main summary

Key takeaways

Educational

Main ideas / lessons (planning fundamentals for solo game development)

  1. Know yourself before building anything

    • Clearly identify:
      • What you’re good at
      • What you’re not good at
      • What you like
      • What you dislike
    • For solo development, defining your workable scope helps prevent overwhelm from overly ambitious goals and supports steady progress.
    • Use self-analysis to shape the game direction based on your strengths and constraints.
    • Example adjustment: if you’re strong in planning/design but weak in drawing:
      • reduce graphical scope
      • use simpler visuals (e.g., sprite/“SS”-style replacements mentioned in the subtitles) and reallocate effort elsewhere

  2. Use frameworks / methods to evaluate your competitiveness

    • Suggested approaches:
      • SWOT analysis (subtitles mention “S analysis”)
      • VRIO framework
    • Treat a solo developer like a one-person business to assess competitiveness.
    • Also helpful: “objectify yourself” by using conversations with ChatGPT (subtitles: “Chatchi Piti”) to uncover your competitive edge.

  3. Start small and iterate

    • When brainstorming ideas, begin within your capabilities.
    • Real development progress often comes from:
      • accumulated know-how over time
      • technology improving, which can make projects more complex
    • Key principle: everyone goes through a small → bigger progression (companies, indie teams, solo devs).
    • Starting too big early can cause loss of direction or quitting.
    • Starting small also helps you:
      • remove unnecessary elements
      • focus on the core elements the game truly needs
    • This encourages you to question the essence of the game you want.

  4. Prototype to verify “core fun” before investing in content

    • Build a prototype specifically to test whether the core gameplay is actually fun.
    • Even without art resources or extra content, test:
      • whether the gameplay is enjoyable
      • whether it has potential
    • If it isn’t fun at this stage, adding cool art/content later likely won’t fix boredom.
    • Conclusion: the core fun point may have been set incorrectly from the start.

  5. Define the core fun through the “core loop”

    • The most important planning task is defining core fun.
    • Planning focuses on:
      • what behavior the player is encouraged to do
      • what rewards follow that behavior
      • why the player repeats it
    • Example concept: StarCraft repeats resource gathering → unit production → battles → victory.
    • The repetitive structure is called the core loop.
    • Key claim: while UI/systems/content may change, the core loop is the game’s skeleton and primary mechanism.
    • From a planner’s perspective, designing the loop affects:
      • rhythm and difficulty
      • growth and immersion
    • Core loop design is delicate and includes:
      • why repetition is fun
      • what emotions it evokes
      • how quickly/slowly rewards are given

  6. Planning is necessary and must have clear intent

    • Planning should connect to:
      • necessity (“why this project must happen”)
      • timeliness/purpose (“why now,” “for what reason”)
    • There may be no single “correct” plan, but the attitude should be:
      • continuously search for a slightly better direction
      • refine a more persuasive plan
    • Suggested habit: ask yourself “Why did I plan it this way?” to clarify intent.

  7. Develop “reverse planning” by studying existing games

    • Even if you don’t write design docs, you can:
      • play/watch existing games
      • ask: “Why do these rules exist?”
      • ask: “Why include this system?”

  8. Systems/rules are always intentional (example: League of Legends “Rush”)

    • The video references a League of Legends mode called “Rush.”
    • Subtitles describe it as:
      • a short, intuitive deathmatch-like mode
      • earn points by placing minions into goals at both ends and/or killing enemies
    • Likely reasons the mode was introduced:
      • League has become older/more complex → fewer new users
      • long playtime fatigue increases
      • demand grows for fast, light “short” content
    • Therefore, the design likely aims to:
      • provide a fresh experience
      • let players try various champions with less pressure
      • enable fast, intuitive gameplay

  9. What planning ultimately means

    • Planning is presented as:
      • not a field with fixed answers
      • an ongoing process of asking questions, observing, and making choices
    • More important than tools/language: the ability to persuade/convince others (and yourself) that the plan is necessary.
    • Consistent intentional choices are framed as the path to making a good game.

Detailed bullet list: practical methodology/instructions implied

  • Before development

    • Identify your strengths/weaknesses and preferences:
      • good at / not good at
      • like / dislike
    • Define your solo-development scope so goals stay realistic.

  • Self-evaluation

    • Run analyses to understand your position as a “one-person business”:
      • SWOT-style self-analysis (called “S analysis” in subtitles)
      • VRIO
    • “Objectify” yourself and find your competitive edge using:
      • conversations with ChatGPT.

  • Early development strategy

    • Start small, even when brainstorming.
    • Avoid overly ambitious early goals to prevent losing direction.
    • Build a prototype to verify the core fun:
      • test core gameplay without relying on art/content
    • If core fun is missing in the prototype, don’t assume later content/art will fix it.

  • Core loop design

    • Define the core loop by specifying:
      • encouraged player behavior
      • rewards tied to that behavior
      • the reason players repeat the loop
    • Design the loop by considering:
      • why repetition is fun
      • what emotions it creates
      • what reward timing/frequency keeps engagement meaningful

  • Justification and refinement

    • Maintain clarity on necessity and purpose:
      • why the project must happen
      • why this plan is timely
    • Use a continuous refinement habit:
      • ask “Why did I plan it this way?”
      • improve the plan’s intent and persuasion

  • Reverse planning practice

    • Study existing games:
      • ask why specific rules/systems exist
      • infer the design intent behind them

  • System intention check (training the planner’s sense)

    • When you see new modes/systems (e.g., “Rush” in LoL), analyze:
      • what player pain points/time constraints might be addressed
      • what fresh experience the rule design is trying to enable

Speakers / sources featured

Speaker / creator

  • Chorama (presenter/voice in the video)

Sources / examples mentioned

  • Celeste (development starting point example; Pico-8 noted)
  • Pico-8 (simple engine used initially)
  • StarCraft (core loop example)
  • League of Legends (example; new “Rush” mode discussed)
  • ChatGPT (referenced as a tool for conversation/objectification)
  • VRIO framework (named for analysis)
  • SWOT analysis (implied by “S analysis” wording)

Original video