Week 9: Project Pitch & Game Design Document
🎯 Project Pitch & Game Design Document
Week 9: Personal Project Kickoff
Game Programming - CSCI 3213
📚 Session Objectives
- 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
Goal: Leave today with a clear, scoped project plan and GDD foundation
🎤 Elements of a Strong Pitch
Your 3-Minute Pitch Should Include:
- The Hook (30 seconds):
- Game title and genre
- One-sentence description
- What makes it unique?
- Core Gameplay (1 minute):
- Primary game mechanic
- Player goal/objective
- Core loop (what players do repeatedly)
- Visual Style (30 seconds):
- Art direction (2D/3D, style)
- Reference images/games
- 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):
- 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
Remember: Better to have a polished, small game than an incomplete large one
💬 Pitch Presentations
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?
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):
- Game Overview
- Title, genre, target platform
- High-level concept (elevator pitch)
- Target audience
- Core Mechanics
- Player controls
- Primary mechanics (how players interact)
- Game loop (what players do repeatedly)
- Visual & Audio Style
- Art direction and references
- UI/UX considerations
- Sound design approach
🔧 GDD Technical Requirements
- Technical Architecture
- Which design patterns will you use?
- Key systems (inventory, combat, etc.)
- Data structures needed
- Third-party assets/plugins
- 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
- Risk Assessment
- Technical challenges
- Mitigation strategies
- Features to cut if needed
📄 GDD Format & Tools
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
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:
- Create your GDD document (Google Docs recommended)
- Fill out the required sections
- Add visual references and sketches
- Define your milestone goals for each week
- 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
Due: Submit GDD link to Canvas by end of day
🚀 Getting Started After Today
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
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):
- 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)
📝 Summary & Deliverables
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
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! 🎮
1 / 16