Week 9: Project Pitch & Game Design Document

🎯 Project Pitch & Game Design Document

Week 9: Personal Project Kickoff

Game Programming - CSCI 3213

📚 Session Objectives

Goal: Leave today with a clear, scoped project plan and GDD foundation

🎤 Elements of a Strong Pitch

Your 3-Minute Pitch Should Include:

  1. The Hook (30 seconds):
    • Game title and genre
    • One-sentence description
    • What makes it unique?
  2. Core Gameplay (1 minute):
    • Primary game mechanic
    • Player goal/objective
    • Core loop (what players do repeatedly)
  3. Visual Style (30 seconds):
    • Art direction (2D/3D, style)
    • Reference images/games
  4. Scope & Features (1 minute):
    • MVP features (minimum viable product)
    • Stretch goals if time permits
    • Technical challenges you foresee

⚖️ Scoping Your Project

✅ Appropriate Scope (7 weeks):

❌ Too Ambitious:

Remember: Better to have a polished, small game than an incomplete large one

💬 Pitch Presentations

Presentation Format:

Questions to Consider:

Take Notes: Write down feedback you receive - it will help refine your GDD

📝 Game Design Document (GDD)

What is a GDD?

A living document that describes your game's vision, mechanics, and implementation plan.

GDD Sections (Minimum):

  1. Game Overview
    • Title, genre, target platform
    • High-level concept (elevator pitch)
    • Target audience
  2. Core Mechanics
    • Player controls
    • Primary mechanics (how players interact)
    • Game loop (what players do repeatedly)
  3. Visual & Audio Style
    • Art direction and references
    • UI/UX considerations
    • Sound design approach

🔧 GDD Technical Requirements

  1. Technical Architecture
    • Which design patterns will you use?
    • Key systems (inventory, combat, etc.)
    • Data structures needed
    • Third-party assets/plugins
  2. Development Milestones
    • Week 11: First Playable
    • Week 12: Core Mechanic Demo
    • Week 13: Vertical Slice
    • Week 14: Alpha Build
    • Week 15: Beta Build
    • Week 16: Public Play Day
  3. Risk Assessment
    • Technical challenges
    • Mitigation strategies
    • Features to cut if needed

📄 GDD Format & Tools

Recommended Tools:

Length Guidelines:

Living Document: Update your GDD as your game evolves - it's not set in stone!

💡 Example Scoped Projects

Well-Scoped Ideas:

Example 1: "Gravity Shift"

  • Genre: 2D Puzzle Platformer
  • Core Mechanic: Flip gravity to navigate levels
  • MVP: 5 levels, simple collectibles
  • Patterns: Command (undo), State (gravity direction)

Example 2: "Tower Chaos"

  • Genre: Tower Defense
  • Core Mechanic: Place towers with unique abilities
  • MVP: 3 tower types, 5 waves, 1 map
  • Patterns: Object Pool, Strategy, Observer

Example 3: "Card Battler"

  • Genre: Turn-based Card Game
  • Core Mechanic: Build deck, battle AI opponents
  • MVP: 15 cards, 3 enemy types
  • Patterns: Strategy, Decorator, Observer

📅 7-Week Development Plan

Week Milestone Deliverable
9 (Today) Pitch & GDD GDD draft, concept approved
10 Development Core systems implemented
11 First Playable Basic gameplay loop functional
12 Core Mechanic Demo Primary mechanic polished
13 Vertical Slice One complete level/experience
14 Alpha Build Feature-complete, rough edges OK
15 Beta Build Polished, bug-tested
16 Public Play Day Final build, showcase ready

🎯 Applying Design Patterns

Requirements:

Your project must implement at least 3 design patterns from the course.

Pattern Selection Guide:

Game Type Recommended Patterns
Shooter/Action Object Pool, Observer, Command
Puzzle Command (undo), State, Strategy
RPG/Inventory Visitor, Decorator, Adapter
Tower Defense Object Pool, Strategy, Spatial Partition
Any Game Singleton (GameManager), Service Locator
Document It: Explain in your GDD where and why you use each pattern

💻 Work Session: Build Your GDD

Task for Remainder of Class:

  1. Create your GDD document (Google Docs recommended)
  2. Fill out the required sections
  3. Add visual references and sketches
  4. Define your milestone goals for each week
  5. List 3+ design patterns you'll implement

Resources Available:

Due: Submit GDD link to Canvas by end of day

🚀 Getting Started After Today

Week 10 Action Items:

Best Practices:

Weekly Check-ins:

Come to office hours or schedule 10-minute check-ins to show progress and get feedback.

📚 Useful Resources

Asset Sources (Free/Affordable):

GDD Examples:

Tutorial Sites:

📝 Summary & Deliverables

Today's Accomplishments:

Due by End of Day:

Next Week (Week 10):

Remember: Start small, iterate often, and don't be afraid to pivot if something isn't working!

❓ Questions?

Let's discuss your project ideas, concerns, or questions about the GDD process.

Office Hours:

Monday/Wednesday 2:00-4:00 PM
SSM 204A

Email:

bobby.reed@okcu.edu

Good luck with your projects! 🎮