Video game Study Guide

📖 Core Concepts Video game – an electronic, interactive audiovisual experience that reacts to player input and updates the visual display. Platform – the combination of hardware (CPU, GPU, display, controllers) and system software that runs a game; examples: arcade cabinet, home console, PC, mobile, VR, cloud‑streaming. Genre – defined by how you play (gameplay interaction), not by story or setting (e.g., action, RPG, shoot‑‘em‑up, battle‑royale). Development pipeline – designers → programmers → artists/sound → QA → post‑release patches; modern games rely on engines and middleware for core systems. IP protection layers – copyright (code, art, music), patents (novel tech), trademarks (brand/logo). Gameplay mechanics themselves are not copyrighted. Industry structure – publishers fund & market; distributors ship physical copies or run digital storefronts; hardware makers supply the platform; journalists & influencers shape demand; esports adds a competitive‑play market. --- 📌 Must Remember First electronic game: 1947 cathode‑ray tube amusement device (missile‑firing simulation). Golden Age of arcades: late 1970s – early 1980s. 1983 crash: U.S. market fell from ≈ $3 B to $0.1 B by 1985; Nintendo’s NES revived it in 1985 with strict licensing. 2020 global revenue: > $159 B; mobile = 48 % of total, console = 28 %, PC = 23 %. Rating boards: ESRB (U, E10+, T, M, AO) in the U.S.; PEGI (3+, 8+, 12+, 16+, 18) in Europe. Team size: typical development teams 5–50; AAA studios > 100. Indie rise: enabled by digital distribution and low‑cost tools (mid‑2000s onward). Legal status of games: U.S. Supreme Court (2011) recognized games as protected speech/art. --- 🔄 Key Processes Concept → Design Document – outline core mechanics, story, target platform(s). Prototype – rapid build (often in a game engine) to test fun factor. Pre‑production – assemble team, choose engine/middleware, set milestones. Production – create assets, write code, integrate audio/visuals, iterate with internal QA. Testing & QA – systematic bug hunting; create test cases for each platform’s hardware quirks. Certification – meet platform holder requirements (e.g., Sony, Microsoft) and rating board standards. Launch – ship physical media or upload to digital storefront; begin marketing push. Post‑release support – patches, DLC/expansion packs, community‑driven updates. --- 🔍 Key Comparisons Arcade vs. Console vs. PC vs. Mobile vs. Cloud Arcade: single‑game cabinet, built‑in controls, coin‑operated. Console: dedicated hardware, standardized controller, TV output. PC: modular hardware, mouse/keyboard + many controllers, high graphics scalability. Mobile: touchscreen primary input, always‑on connectivity, micro‑transaction‑friendly. Cloud: no local processing; streaming quality limited by bandwidth. Indie vs. Triple‑A Indie: small team, limited budget, experimental mechanics, often digital‑only. Triple‑A: large studio, $10 M+ budgets, high production values, multi‑platform releases. Ludology vs. Narratology Ludology: focuses on rule systems & gameplay. Narratology: treats games as storytelling media (“cyberdrama”). Copyright vs. Patent vs. Trademark Copyright: protects expression (code, art, music). Patent: protects novel technical inventions (e.g., a unique physics algorithm). Trademark: protects brand identifiers (logo, title). --- ⚠️ Common Misunderstandings “All games have win conditions.” → Walking simulators, empathy games, and some sandbox titles lack explicit goals but are still video games. “Gameplay mechanics are copyrighted.” → Only the expression of a mechanic (art, code) is protected; the underlying idea can be copied. “Violent games cause real‑world aggression.” → Major health agencies find insufficient causal evidence. “Gaming disorder = addiction for everyone who plays a lot.” → WHO classifies it as a disorder only when gaming impairs daily functioning. “All VR experiences are platforms.” → VR is an input/output technology; the underlying console/PC still defines the platform. --- 🧠 Mental Models / Intuition Game = Input → System → Output loop – think of a game as a black box that takes controller actions, processes them through rules/engine, and spits out updated video/audio. Platform as a “phone” – just as a phone combines CPU, screen, and OS, a console bundles hardware + OS + certification, limiting what can run on it. Genre = Core Loop – identify the repeated player activity (e.g., “run + shoot” = shooter; “explore + level‑up” = RPG). IP layers as a “matryoshka doll” – copyright inside, patent around it, trademark on the outer shell (brand). --- 🚩 Exceptions & Edge Cases Zero‑player games – simulations that run autonomously after setup (e.g., AI‑driven city builders). Adaptive triggers & haptic feedback – not present on all controllers; treat as optional enhancements. Games without physical media – cloud‑streamed titles have no local storage, affecting patch distribution. Hybrid genres – action‑adventure blends two top‑level loops; don’t force a single‑genre label. --- 📍 When to Use Which Choose platform – mobile for casual, touch‑friendly, micro‑transaction models; console for high‑budget, exclusive titles; PC for moddability and high‑performance simulations. Select engine – Unity for 2D/mobile cross‑platform; Unreal for high‑fidelity 3D/AAA; proprietary engines when custom performance or licensing is needed. Pick distribution – digital storefront (Steam, Epic, App Store) for rapid global reach; physical media for collector markets or regions with low broadband. Apply rating – use ESRB for U.S. releases, PEGI for Europe; always check age‑appropriateness of content (violence, language, gambling‑like loot boxes). --- 👀 Patterns to Recognize Revenue shift pattern: Mobile share ↑ → AAA console share ↓ over each decade. Crash‑recovery cycle: Market saturation → crash → licensing control → consolidation → new tech wave. Emergent narrative cue: Presence of AI‑driven systems + player‑choice → likely emergent story moments. Indie success indicator: Early access + strong community feedback → higher chance of breakout hit. --- 🗂️ Exam Traps “All video games are classified by story genre.” – The exam may list “action‑adventure” as a gameplay genre, not a narrative one. Confusing rating symbols: ESRB “M” = Mature (17+); PEGI “16+” is a different rating system – don’t assume they map 1‑to‑1. Assuming copyright protects mechanics: A question describing a “cloned” game will test knowledge that only assets are protected. Mixing up “platform” vs. “device”: A “VR headset” is an input/output device; the underlying console/PC is the true platform. Over‑generalizing “gaming disorder”: The exam may ask which organization defines it (WHO) vs. which treats it as a myth (American Psychiatric Association). ---