Video game development Study Guide

📖 Core Concepts Video game development – multidisciplinary creation of a game (programming, design, art, audio, UI, writing). Game engine – off‑the‑shelf (Unity, Unreal, Godot) or proprietary software that provides core systems (physics, rendering, audio). Agile & Scrum – iterative development methods that rely on prototypes, feedback loops, and short sprints instead of a strict waterfall. Milestones – predefined checkpoints (first playable, alpha, code‑freeze, beta, gold master) that trigger publisher payments and guide schedule. Revenue split – typical console retail split: developer 13 %, publisher 32 %, retailer 32 %, manufacturer 5 %, console royalty 18 %; digital distribution can give developers up to 70 % (or 100 % on self‑hosted platforms). Independent (indie) vs AAA – indie = small, self‑funded or crowdfunded teams; AAA = large studios, publisher‑funded, budgets often > $100 M. --- 📌 Must Remember Budget growth: AAA budgets rose from $1–4 M (2000) to > $200 M (2023); typical multiplatform game $18–28 M. Milestone order: First Playable → Alpha (feature‑complete) → Code Freeze → Beta → Code Release → Gold Master. Revenue percentages (console): Dev 13 % | Pub 32 % | Retailer 32 % | Manuf. 5 % | Royalty 18 %. Digital vs physical: Digital can give developers 70 % of sales; self‑hosted → 100 %. Roles: Producer (internal/external), Publisher (finances & IP), Designer (game rules & narrative), Artist (2D/3D assets), Programmer (code & tools), Level Designer (maps/missions), Sound Engineer (SFX, music, voice), Tester (QA). Agile hallmark: iterative prototyping, frequent feedback, continuous integration of new features. First playable timing: usually 12–18 months before final release. --- 🔄 Key Processes Pre‑production Generate high‑concept → pitch → concept document → production plan (tasks, schedule, cost). Prototyping Create rapid (paper or simple digital) mock‑ups → test gameplay ideas → iterate or discard. Production Simultaneous asset creation, programming, level building, audio. Track progress with milestones; each triggers payment. Testing & QA Functional, compatibility, localization, playability testing → regression testing after each code change. Post‑production / Polishing Bug fixing, performance optimization, final QA, certification, localization, prepare for distribution. Release & Maintenance Ship gold master → issue patches/updates → live‑service support (MMO, DLC). --- 🔍 Key Comparisons AAA vs Indie AAA: large team, publisher‑funded, budgets $10⁷–10⁸+, high risk‑averse titles. Indie: small/self‑funded, may use same engines, flexible scope, often digital‑only distribution. Proprietary vs Off‑the‑Shelf Engine Proprietary: built in‑house, full control, high upfront cost. Off‑the‑Shelf (Unity, Unreal, Godot): licensed, faster start, community support, revenue share models. Agile vs Waterfall Agile: iterative, adaptable, frequent builds, early testing. Waterfall: linear phases, hard‑locked specs, risky for changing requirements. --- ⚠️ Common Misunderstandings “First playable = finished game.” – It’s only a rough, playable prototype; many features and assets still missing. “Digital distribution always pays more.” – Revenue share varies; platform fees and marketing costs can reduce net profit. “All AAA games are profitable.” – Majority of commercial games do not generate profit; budgeting is critical. “Crunch is inevitable.” – Crunch is a symptom of poor planning; it can cause burnout and project failure. --- 🧠 Mental Models / Intuition “Pipeline = Funnel” – Early phases (ideas, prototypes) are broad; each stage narrows to a refined, playable product. “Milestone as a paycheck checkpoint” – Treat each milestone as a mini‑release that must satisfy both technical and business criteria. “Engine as a toolbox, not a magic wand” – Even with Unity/Unreal, custom code is needed for gameplay specifics. --- 🚩 Exceptions & Edge Cases Revenue split for digital – Not a fixed 70 %; platform (Steam, Epic, console stores) may take 20–30 % fees, leaving the rest to the developer. Out‑sourced programming – Rare but possible for specialized tech (e.g., network code, AI) when internal expertise is lacking. Late‑stage feature addition – Occasionally allowed if it resolves a critical gameplay issue, but risks missing beta or gold master dates. --- 📍 When to Use Which Choose engine: Use Unity/C# for 2D/indie projects, rapid iteration. Use Unreal/C++ for high‑fidelity 3D AAA titles needing advanced graphics. Use Godot for lightweight, open‑source projects or when licensing costs matter. Select development methodology: Scrum for teams needing regular sprint reviews and clear backlog. Kanban for smaller indie teams preferring continuous flow without fixed sprints. Funding model: Self‑fund or crowdfunding → retain full revenue, suitable for low‑budget indie. Publisher advance → needed for large budgets, but share IP and revenue. --- 👀 Patterns to Recognize “Feature complete → bug‑fix only” appears at Alpha → Code Freeze → Beta. “Prototype → iteration → discard” for early levels; first level often longest. “Revenue split shift” when moving from physical to digital distribution. “Crunch spikes” 3–4 months before code freeze or beta, indicating schedule slip. --- 🗂️ Exam Traps Confusing “first playable” with “gold master.” – First playable is an early prototype; gold master is the final, ship‑ready build. Assuming all AAA games use proprietary engines. – Most AAA studios license engines (Unreal, Unity) or use hybrid solutions. Believing indie games never use publishers. – Some indie titles receive publisher advances or distribution deals while keeping creative control. Mixing up revenue percentages: Remember the developer’s 13 % applies to physical console sales, not digital platforms. ---