This is an archived course. A more recent version may be available at ocw.mit.edu.

Projects

This course is organized around a series of four team projects, each building upon the skills and techniques learned in the previous.

Game Engine Tutorial: Due Session 4

Each student is asked to complete a simple tutorial in a free game engine, in preparation for the Game Engine discussion during Session 4. No turn ins, other than the discussion group, are required. See the Game Engines section of the Useful Tools list (PDF).

Project 1: Non-Digital Prototyping (Team Size: 4) 15 pts

Concepts: Basic game design practices; rapid iterative design techniques; group game design; Wizard of Oz prototyping practices; tracking design changes.

Goal: Create a non-digital game to serve as the prototype for a digital game, while tracking and understanding how your game design changes over time. (You will not be required to turn this prototype into a digital game.) The prototype has the following required constraints:

  • Single player.
  • A complete playthrough takes no more than 5 minutes.
  • The game experience is different for each playthrough.
  • Naive players will be provided one minute of spoken explanation or a half page of written instructions.

Project Resources:

Project 2: Digital Prototype with Project Management (Team of 4) 15 pts

Goal: Create a complete playable digital prototype in a short time frame, while integrating project management concepts into the team's process. Use previously developed prototyping skills as part of a larger digital project.

Project Constraints:

  • Single player game.
  • Game takes no more than 5 minutes to play through.
  • Game uses randomization as a central element (e.g. maps, AIs, level, actions, etc.)
  • Players can pick up & start playing the game with no external instructions.
  • Game must be delivered as a browser game that runs on Chrome. (Teams should host the game & provide a URL for project submissions.)
  • Meets minimal play & legal requirements listed in Appendix I.

Project Resources:

Project 3: Digital Prototype II: Aesthetics (Teams: 5–6 people) 15 pts

Goals: Practicing project management with a larger team, independent user testing, design iteration using user feedback, creating consistent aesthetics inside a game. (i.e. art, audio, and game mechanics work together to create a unified 'feel' for the game.)

Constraints:

  • Single Player Game.
  • Game takes no longer than 5 minutes to play through.
  • Games uses randomization as a central element.
  • Game does not rely on single use content as a key mechanic (although may use it as placeholder for prototyping reasons.)
  • No playthrough is identical to a previous one.
  • The games' art, audio, and mechanics should support each other to create a cohesive fiction and / or aesthetic.
  • Game must use & play audio for the player.
  • Game should aim to entertain spectators as well as the player.
  • Game must be delivered as a browser game, running on Chrome. (Teams should host the game & provide a URL for project submissions.)
  • Game meets the minimal play & legal requirements in Appendix I.

Project Resources:

Project 4: Small Game Project (Teams of 8) 30 pts

Goals: Create a small but fully functional and well-polished web browser game, using the project and team management techniques learnt in this class. Use design iteration techniques throughout early prototyping and focus testing to improve your ideas throughout development.

Constraints:

  • Single Player Game.
  • Game takes no longer than 10 minutes to play through.
  • Games uses randomization as a central element.
  • Game does not rely on single use content.
  • No playthrough is identical to a previous one.
  • The games' art, audio, and mechanics support each other to create a unified fiction and/or aesthetic.
  • Game must use & play audio for the player.
  • Game entertains spectators as well as the player, and is capable of being run on a large project screen (players can play at the computer/keyboard; only spectators are required to watch the projection screen.)
  • Game must be delivered as a browser game, running on Chrome. (Teams should host the game & provide a URL for project turn ins.)
  • Game meets the minimal play & legal requirements in Appendix I (Requirements change for the Game vs previous prototypes, so do review the appendix!)

Project Resources: