Game design, rhythm and audio technology
작은 기획을 실제 플레이로 연결하는 순서.
How to write a game design document, drawing on the Diablo proposal, Grim Fandango's puzzle documentation and published studio design materials. Covers design principles, state transitions, hit-window boundaries, content tables and playtesting.
How to build a small game, drawing on the Experimental Gameplay Project, Arkadium's prototype process and Godot's official tutorial. Covers design questions, technical risks, state transitions, restarting, production scope and completion criteria.
Define the input task and music's role, then calculate BPM and loop length. Includes comparison audio using the same drum arrangement at 100, 120 and 140 BPM, with a checklist.
How to design a core loop, using Nintendo's rhythm games, Valve's work on visual clarity and pacing, and the original MDA paper. Covers cues, choices, input feedback, learning, tension and a 16-target comparison exercise.
How to write a playtest report, drawing on Valve's published methods and the Portal postmortem. Covers research questions, facilitator scripts, observation records, units of analysis and revision decisions, with five fictional sessions and a report template.
An 8-second, four-bar loop at 120 BPM explains boundaries and frame counts, followed by clicks, reverb tails and Web Audio loop settings.
Compare drum placement and input targets at 120 BPM, hear half-time and tempo changes separately, and distinguish a mixed WAV, individual stems and scheduled event times.
