Write a Game Design Document You Can Check | Assignment 4

Write a game design document around a player action, a clear promise and evidence you can inspect.

Walker Claude connects its core loop, controls, visual design and bounded scope to an actual game. The worked GDD distinguishes implemented behavior from proposals and turns broad intentions into decisions a reviewer can check.

CSYE 7270, Assignment 4: Professor Bear’s worked example.

Your turn Read my game and current design notes. Draft a game design document covering name, concept, flow, assets, character, story, gameplay, graphics with examples, sound and technical description. Separate existing features from proposals. Flag every claim that needs real output or human review.

Chapters 0:00 Introduction 0:37 Name The Promise 1:26 Follow The Player 2:32 Make The Design Visible 3:28 Keep The Promise Inspectable 4:25 Closing

Sources and credits CSYE 7270 assignment brief; Walker Claude source, design records, test receipts and engine captures. Teaching direction: Nik Bear Brown. AI-assisted implementation, analysis and film production. Liam, in for Bear: synthetic Kokoro narration. Scripted engine input is labeled; no human playtest or learner approval is claimed.

Professor Bear Does His Assignments https://www.youtube.com/playlist?list=PLM51lFDKue_A

What this video covers

• 0:00 — Introduction
• 0:37 — Name The Promise
• 1:26 — Follow The Player
• 2:32 — Make The Design Visible
• 3:28 — Keep The Promise Inspectable
• 4:25 — Closing

Transcript

A lightly formatted transcript of the video, with timestamps so you can jump to any section on YouTube.

Introduction

[0:00] CSYE7270 assignment walkthroughs. Design Walker Claude. Turn a game idea into a design document whose promises you can inspect. Hello, this is Liam in for Bear for CSYE7270. A game design document turns a vague idea into decisions a reader can inspect. Walker Claude is our instructor example. The document is a design argument with existing work separated from proposals. Four terms, concept means the central promise. Flow means the sequence a player follows. A mechanic is an action and its consequence. Scope says what this version includes and excludes.

Name The Promise

[0:37] Start with the name and concept. Walker Claude promises small inspectable decisions. Move, try an action, see a consequence, and reset. The document connects those decisions to source and engine evidence. Shipping Lane is a two-dimensional platforming extension. Signal Garden is a three-dimensional signal room. They share a repository, but the document does not pretend they are one seamlessly released game. The story gives the mechanic a reason to exist. A gardener sends a signal that opens a path. It does not imply that dialogue, a campaign, or additional rooms have been implemented. The correct canvas brief asks for the name, concept, flow, assets, character, story, gameplay, graphics, sound, and technical description. It's total is five points. Production polish is not an extra requirement.

Follow The Player

[1:26] Write the room as a sequence. Arrive, reach the pad, charge, open the gate, reach the destination, reset. Each transition should identify what the player does and what changes in response. The goal is completion. The platformer offers movement, jumping, and optional rewards. The room offers movement and a committed signal action. New abilities belong in the proposal column until someone actually implements and checks them. Explain failure and recovery explicitly. The platformer has obstacle contact and retry. The room has reset including interruption of charging. Good play involves reading geometry, timing jumps, positioning, and recognizing feedback. Perceived fairness still needs human observation. This is the actual course driven by scripted keyboard input. The original first steps route still works. Beyond its old finish, Cloud crosses four new gaps, reads walking bugs, climbs the raised lane, and reaches the shipping flag. The camera follows the extended bounds. Completion and replay work without collecting every token. This demonstrates a route, not a human judgment about difficulty.

Make The Design Visible

[2:32] Assets serve player decisions. The gardener, pad, gate, and finish zone form the room. Keep character appearance, collision boundaries, presentation effects, and game rules distinct so a visual edit cannot secretly change the mechanic. The example has a block gardener in two and three dimensions plus an original rigged model. Shipping lane extends the route. Signal Garden stays one room. Extra levels remain proposals rather than evidence of completed work. Make styling visual with the actual model sheets, the route diagram, and engine captures. Terracotta, cream, charcoal, and mint establish related visual roles. A palette name alone cannot show whether the pad or destination is readable. Separate original test tones from model generated assets. A step, charge, gate, reset, or finish queue should correspond to its event. The design says music and mute do not decide game state. Listening suitability remains a separate judgment.

Keep The Promise Inspectable

[3:28] The technical description names the engine, renderer, and source owners. Then connect design to implementation. A named check actual output and its limit. A checked state is useful evidence, but it cannot establish human play feel. This example uses Godot 4.7.2, GDScript, and the compatibility renderer. The default project launches Shipping Lane. A separate command opens Signal Garden. These facts make the design reproducible instead of merely plausible. The source and recorded game establish a working route, rig, and signal loop. Expanded assignment labs are being completed. Human play feel, accessibility, and teaching effectiveness remain unmeasured. Keep those categories visible when the design changes. The GDD was drafted by AI from the actual repository and Bear's direction. It does not claim that Bear wrote every sentence or personally played every case. Credit the real contribution and revise the document when evidence changes.

Closing

[4:26] Let's recap with Claude. Name a concrete promise and bound its scope. Write the player actions, consequences, and recovery. Show the character layout, styling, and sound roles. Connect the design to source, evidence, and honest limits. Read my game and current design notes. Draft a game design document covering name, concept, flow, assets, character, story, gameplay, graphics with examples, sound, and technical description. Separate existing features from proposals. Flag every claim that needs real output or human review. Design walker Claude at Nick Bear Brown.