Game design Study Guide

📖 Core Concepts Game mechanics & systems – the rules and objects that dictate how a game functions. Gameplay – the interaction what the player does with those mechanics. Player experience – the emotional/feeling response a user has while playing. Iterative development cycle – design → prototype → play‑test → revision → repeat. Roles Game Designer: invents concept, core mechanisms, rules, theme. Game Developer: fleshes out details, runs play‑tests, revises based on feedback. Game Artist: creates and refines visual/graphic elements. Concept phase – brief statement of core play, objectives, theme, player identity. Design phase – expands concept into concrete components (board, cards, tokens) and writes full rules (start, turn order, win conditions). Prototype – draft version used to explore ideas and gather feedback. Play testing – evaluates gameplay, component usability, rule clarity, learning curve, and fun; identifies balance problems. Purposes of game design – entertainment, education, exercise/experiment, gamification (applying game principles outside games). Game studies – academic discipline that examines games, their design, players, and cultural impact (social‑scientific vs. humanities approaches). --- 📌 Must Remember Iterative cycle: design → prototype → test → revise → (possible redesign). Balance problems discovered in testing trigger revisions to rules, components, or presentation. German‑style board games prioritize meaningful choices, low randomness, streamlined rules. Card games rely on shuffling → randomness; dice games have independent rolls. Gamification ≠ a game; it’s the application of game design principles to non‑game contexts. Vygotskian scaffolding in play‑based learning = teacher‑provided targeted feedback & encouragement. Game studies: Social‑scientific → “What do games do to people?” (surveys, experiments). Humanities → “What meanings are made through games?” (interviews, ethnography). --- 🔄 Key Processes Concept Creation – write a concise description of core mechanisms, objectives, theme, player identity. Design Expansion – translate concept into physical/virtual components; draft detailed rule set (setup, turn sequence, actions, win conditions). Prototype Build – create a low‑fidelity version (paper, cardboard, simple software). Play Testing Observe player actions. Record issues: unclear rules, component confusion, balance gaps. Revision Fix rule ambiguities. Adjust component values or add/remove elements. If major flaws, consider a redesign of the concept. Iterate – repeat steps 3‑5 until play testing shows consistent fun, clarity, and balance. --- 🔍 Key Comparisons Game Designer vs. Game Developer – Designer creates what the game is; Developer builds how it works and refines it. Game Developer vs. Game Artist – Developer handles mechanics & testing; Artist handles visual style & graphic polish. Board Game vs. Card Game – Board: emphasizes rule‑driven interaction, often less hidden information; Card: built on shuffled randomness & hidden hands. German‑style Board vs. Traditional Board – German: minimal luck, strong player agency; Traditional: may rely more on chance and thematic storytelling. Dice Game vs. Card Game (randomness) – Dice rolls are independent events; card draws are dependent on previous draws (depletion). --- ⚠️ Common Misunderstandings Game design = game theory – they are distinct; design focuses on creating experiences, theory on mathematical strategies. Prototype = finished product – prototypes are deliberately low‑fidelity, meant for testing ideas, not for release. Play testing only checks “fun” – it also evaluates rule clarity, component usability, learning ease, and balance. Gamification is a game – it’s the use of game design elements (points, badges, leaderboards) in non‑game settings. --- 🧠 Mental Models / Intuition Conversation Model – think of a game as a dialogue: the mechanics speak, the player listens and responds; design tunes the conversation for engagement. Scaffolding Ladder – each play‑test adds a rung; feedback from the “teacher” (designer) helps the player climb toward mastery. Balance as a Scale – every rule change adds weight to one side; testing shows if the scale tips too far (overpowered) or stays level (fair). --- 🚩 Exceptions & Edge Cases New media adaptations – many new platforms first copy older games before exploiting unique digital affordances. Casino games – despite simple rules, they often include multiple winning conditions to boost entertainment. Cooperative card games – relax typical communication limits to force collective problem‑solving. --- 📍 When to Use Which Board game design – choose when you want rich social interaction, strategic depth, and a physical play space. Card game design – ideal for hidden information, quick setup, and randomness from shuffling. Dice game design – best when you need independent random events and simple scoring combos. Gamification – apply when the goal is to motivate behavior in education, work, or health contexts, not to create a standalone game. German‑style design principles – use when the target audience prefers skill‑based, low‑luck experiences. --- 👀 Patterns to Recognize Iterative loop in questions: “After play testing reveals X, the next step is …” → expect a revision step. Balance cue: mentions of “overpowered,” “underutilized,” or “dominant strategy” → look for rule tweaks or component adjustments. Player experience descriptors (immersion, tension, satisfaction) → often tied to mechanics that give meaningful choices. Hidden information → likely a card‑game scenario; independent randomness → dice‑game scenario. --- 🗂️ Exam Traps Confusing “game design” with “game theory” – answer choices that mention Nash equilibria belong to game theory, not design. Assuming a prototype is final – questions that describe a “draft version” expect you to identify it as a prototype for testing, not a finished product. Mixing up roles – a statement that the “artist decides the win condition” is wrong; that’s the designer’s job. Gamification vs. Game – options that call a loyalty‑points system a “game” are misleading; it’s a gamified system. Randomness source – if a problem says “each event is independent,” it’s pointing to dice, not cards (which are dependent).