<!-- Your game, in your own words. This file is yours: fill it in before onboarding, after it, or
whenever you like, for a new game or one that's already underway.

- Write as much or as little as you want, and leave a section blank if you haven't decided. Your
  own words are the point; no need to match the style of the other files.
- The agent reads this file and never edits it. It builds the Game Design Document (design/gdd.md)
  and the decision log (design/decisions.md) from it, marks what it inferred so you can confirm it,
  and turns anything undecided into an open question.
- Why it helps: a written document gives the agent your intent and the context behind it, which the
  chat interview can't carry as well, and it sets the stage for every later design session and build.
- If you update it later, tell the agent ("my design document changed") and it brings the GDD in
  line, again showing what it inferred.
- The latest version of this template: https://raw.githubusercontent.com/Freakling/Godot-Director/v4.9.0/project/design/director-gdd.md
-->

# Game Design Document (GDD): \[Game Title\]

**Engine:** Godot Engine (v4.x recommended)

**Genre:** \[e.g., 2D Platformer, 3D Rogue-lite\]

**Target Platform:** \[PC, Mobile, Web, Console\]

**Status:** \[Concept / In Development / Prototype\]

---

## 1. Game Overview & Concept

* **Elevator Pitch:** *A 1-2 sentence hook describing your game.*
* **Core Loop:** *What does the player do second-to-second, minute-to-minute, and session-to-session? (e.g., Explore dungeon → Fight enemies → Collect loot → Upgrade stats).*
* **Unique Selling Proposition (USP):** *What makes this game stand out or feel different?*

---

## 2. Gameplay Mechanics & Controls

### Control Scheme

Which supported peripherals?

| Action | Keyboard / Mouse | Gamepad | Godot Input Map Name |
| :--- | :--- | :--- | :--- |
| **Move** | A / D or Arrow Keys | Left Stick | `move_left`, `move_right` |
| **Jump / Confirm** | Spacebar | Bottom Face Button (A/Cross) | `jump` |
| **Interact** | E | Right Face Button (X/Square) | `interact` |

### Character Controller (`CharacterBody2D` / `CharacterBody3D`)
* **Movement stats:** Speed, acceleration, friction, gravity, jump velocity.
* **Physics logic:** Mention if using `move_and_slide()` and how custom states (idle, run, jump, fall) are handled.

---

## 3. Art & Visual Style

* **Art Style:** \[e.g., Pixel Art 16x16, Low-Poly 3D, Hand-drawn vector\]
* **Godot Rendering Settings:** 
  * Renderer: **Forward+** (High-end 3D), **Mobile** (Optimized 3D), or **Compatibility** (WebGL/Low-end 2D/3D).
  * Lighting & Post-Processing: \[e.g., Use WorldEnvironment for Glow/SSAO, CanvasItem shaders for visual effects\].

---

## 4. Audio & Sound Design

* **Music:** Style, mood, and implementation (e.g., AudioStreamPlayer with interactive buses).
* **SFX:** Key sound effects needed (jump, hit, menu click, UI feedback).

---

## 5. Levels / World Design

* **Level Structure:** \[e.g., Linear progression, open-world, hub-based rooms\]
* **Godot Implementation Strategy:** 
  * Will levels be built using `TileMapLayer` (Godot 4) or modular 3D packed scenes?
  * How are transitions handled? (e.g., `SceneTree.change_scene_to_file()`, loading screens).

---

## 6. UI / UX Design

* **Menus:** Main Menu, Pause Menu, Game Over Screen, Settings.
* **Godot UI Nodes:** Use `Control` nodes with anchors, containers (`VBoxContainer`, `HBoxContainer`), and custom themes (`.tres` / `.theme`).

---

## 7. Milestone Roadmap

* [ ] **Prototype:** Core movement mechanics and basic physics working in Godot.
* [ ] **Vertical Slice:** One complete level with art, sound, UI, and win/loss states.
* [ ] **Content Alpha:** All core features implemented; bug fixing and balancing phase.
* [ ] **Beta / Polish:** Performance optimization, export templates testing for target platforms.