Week 16: Public Play Day - Showcase Your Game!

🎉 Public Play Day!

Week 16: Showcase Your Game

Game Programming - CSCI 3213

🎮 Congratulations on completing your games! 🎮

📚 Public Play Day Overview

Today's Agenda:

Event Details:
  • When: [Time TBD]
  • Where: [Location TBD]
  • Who's Invited: Students, faculty, friends, family, public

📅 Event Schedule

Public Play Day Timeline:

Time Activity
[30 min before] Setup
Arrange stations, test builds, prepare materials
[Start Time] Opening Remarks
Welcome, overview, showcase begins
[60-90 min] Public Showcase
Open play, visitors rotate through games
[Mid-point] Developer Rotation
Developers get to play each other's games
[End - 15 min] Awards & Recognition
Celebrate achievements, special mentions
[End] Closing & Photos
Class photo, congratulations

🖥️ Your Showcase Station

What You Need:

👨‍💻 Your Role as Developer

During Public Play Day, You Should:

✅ DO:

  • Welcome players warmly
  • Give a quick 15-second pitch
  • Explain controls clearly
  • Let players discover the game themselves
  • Observe how people play
  • Ask for feedback after they play
  • Thank everyone for playing
  • Take notes on common feedback

❌ DON'T:

  • Over-explain the game
  • Backseat-game or give hints constantly
  • Make excuses for bugs or missing features
  • Argue with feedback
  • Ignore players or stay on your phone
  • Be discouraged if someone doesn't like it

🎤 Your Elevator Pitch

Perfect Your 15-Second Pitch:

Formula:

"[Game Title] is a [genre] where you [core mechanic] to [goal]."

Examples:

Practice: Say it out loud 5 times before the event - you'll say it dozens of times today!

💬 Gathering & Handling Feedback

Feedback Collection:

Responding to Criticism:

🎊 Celebrate Your Achievement

What You've Accomplished:

Technical Skills:

  • Built a complete game from scratch
  • Implemented 3+ design patterns professionally
  • Managed code architecture and organization
  • Debugged and optimized performance
  • Version control with Git/GitHub

Design Skills:

  • Created a Game Design Document
  • Iterated based on playtesting feedback
  • Balanced difficulty and progression
  • Polished with juice and game feel
  • Shipped a complete product

Professional Skills:

  • Managed scope and deadlines
  • Adapted to feedback
  • Presented your work publicly
  • Collaborated in code reviews
  • Learned from iteration

🏆 Awards & Recognition

Special Recognition Categories:

Everyone's a Winner: You all shipped a game - that's an achievement most people never reach!

📝 Post-Mortem Document

Final Assignment (Due 1 Week After Play Day):

Write a 2-3 page post-mortem reflection on your project.

Required Sections:

  1. Project Overview:
    • Game title, genre, description
    • Initial vision vs. final result
  2. What Went Well:
    • Technical successes
    • Design wins
    • Proud moments
  3. What Went Wrong:
    • Challenges faced
    • Mistakes made
    • Features cut and why
  4. Lessons Learned:
    • Technical lessons
    • Design lessons
    • Process lessons
  5. Future Improvements:
    • What would you add/change?
    • What would you do differently next time?

📦 Final Deliverables Checklist

Submit to Canvas by [Due Date]:

🚀 Your Game Dev Journey Continues

Next Steps:

🌐 Publishing Your Game

Platforms to Publish:

Recommendation: Publish on itch.io today - it takes 10 minutes and looks great on resumes!

💼 Game Development Career Paths

Roles in Game Development:

Where to Apply:

🙏 Thank You

Acknowledgments:

Thank you for an amazing semester!

Stay in Touch:
  • Office: SSM 204A
  • Email: bobby.reed@okcu.edu
  • I want to see your future projects!

🎮 Keep Making Games!

"The best way to learn game development is to make games."

Final Advice:

Congratulations, Game Developers! 🎉🎮🚀

Now go enjoy Public Play Day - you've earned it!

📸 Time for a Class Photo!

Game Programming CSCI 3213
Spring 2026
Public Play Day

🎓🎮🎉

You did it!