Skip to content

Final Project Release

Pippin Barr edited this page Mar 12, 2018 · 5 revisions

Due: Sunday, 29 April 2018

Brief

Polish your three class projects into a final state and officially release them publicly on itch.io.

Specifics

The games

You are not required to add any new features to your games. Instead, you should focus on making sure that each game:

  • Has a title screen before play begins (unless this is inappropriate to the game)
  • Successfully represents your vision in terms of its engagement with its topic (Lights, Camera/Sound/3D Objects)
  • Incorporates feedback you have received from Pippin, classmates, and other playtesters
  • Has sufficient instructions that a player can understand and play it (the instructions for controls can either be in the game itself, a text file accompanying a download, and/or on the game's itch.io page)
  • Has polished and final art, including models, textures, sounds, etc. (again, not this does not mean the game needs to look like it's AAA, just that it is cohesive and looks and sounds like you intend)
  • Has polished and final gameplay, including controls, AI behaviours, scripting, etc.
  • Has no glitches or bugs that affect gameplay

The release

You should release all the games on a single itch.io page, so you should come up with a name for the collection. You may release each game as a separate build or combine them into a single build with some menu system to select which game to play.

Follow itch.io's requirements in the game uploading interface to include

  • A description (this can come from your Press Kit)
  • A trailer (this can come from your Press Kit)
  • Screenshots (this can come from your Press Kit)
  • Mac OS X and Windows builds of your single game (with menu system) or multiple separate games

Provide a link to your Press Kit from the release page!

Process Journal

During your creation of the release you should write a minimum of four process journal entries:

  • One entry per game which represents your reflections on the prototype version and how you will transform (or have transformed) it into the release version, focusing most of all on the reasons for your decisions
  • One entry at the end of the entire process that represents a changelog of all the work you have done on the three games between the full prototype version and the release version

Grading

Grading will focus on the polish, improvements, and changes you have made to your games since their full prototype state (the changelog entry in your process journal will be important for this).

Clone this wiki locally