🎯 Project Pitch & Game Design Document

Game Programming - CSCI 3213

Spring 2026 - Week 9

Oklahoma City University

• Present your game concept to the class
• Receive feedback on feasibility and scope
• Create a comprehensive Game Design Document (GDD)
• Define clear milestones for the semester
• Identify technical challenges and solutions
• Establish a development timeline

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

✅ Appropriate Scope (7 weeks):

• 1-3 core mechanics, polished
• Single game mode or level
• Focus on gameplay over story
• Reusable assets (asset stores are OK!)
• Achievable in ~50-60 hours of work

❌ Too Ambitious:

• Open-world games
• Complex multiplayer systems
• Multiple game modes
• Custom 3D models/animations from scratch
• Story-heavy RPGs

Presentation Format:

• 3 minutes per student
• 2 minutes Q&A and feedback
• Focus on constructive feedback

Questions to Consider:

• Is the scope realistic for 7 weeks?
• Are the core mechanics clear?
• What are the biggest technical risks?
• What features can be cut if time is short?
• What makes this game fun?

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

4. Technical Architecture
   • Which design patterns will you use?
   • Key systems (inventory, combat, etc.)
   • Data structures needed
   • Third-party assets/plugins
5. 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
6. Risk Assessment
   • Technical challenges
   • Mitigation strategies
   • Features to cut if needed

Recommended Tools:

• Google Docs: Easy collaboration, commenting
• Notion: Organized, template-based
• Markdown (GitHub): Version control integration
• Confluence: Professional option

Length Guidelines:

• Aim for 3-5 pages initially
• Add detail as you develop
• Include diagrams, flowcharts, sketches
• Visual communication > walls of text

Well-Scoped Ideas:

Requirements:

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

Pattern Selection Guide:

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:

• GDD template on course website
• Instructor available for 1-on-1 consultation
• Reference successful indie game GDDs

Week 10 Action Items:

• Set up your Unity project structure
• Implement basic player controller
• Create placeholder art/sprites
• Build one core system (movement, combat, etc.)
• Commit code to GitHub repository

Best Practices:

• ✅ Commit to Git daily
• ✅ Test frequently - don't build for weeks without testing
• ✅ Use placeholder art early - polish later
• ✅ Ask for help when stuck
• ✅ Update GDD as plans evolve

Asset Sources (Free/Affordable):

• Unity Asset Store: Free assets section
• itch.io: Game assets, many free
• OpenGameArt.org: Free 2D/3D assets
• Kenney.nl: Free game assets (2D/3D)
• Freesound.org: Sound effects

GDD Examples:

• Celeste GDD (minimal but effective)
• Ori and the Blind Forest (visual-heavy)
• Check course website for student examples

Tutorial Sites:

• Brackeys (YouTube - Unity tutorials)
• Unity Learn (official tutorials)
• Catlike Coding (advanced topics)

Today's Accomplishments:

• ✅ Pitched your game concept
• ✅ Received peer and instructor feedback
• ✅ Started your Game Design Document
• ✅ Defined development milestones

Due by End of Day:

• 📄 Submit GDD (Google Docs link) to Canvas
• 🔗 Share your GitHub repository link

Next Week (Week 10):

• No formal class meeting - work session
• Focus on core systems implementation
• Office hours available for help
• Prepare for Week 11 First Playable demo

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

Good luck with your projects! 🎮