Implementation Instructions

This document gives a general specification for a game implementation, including what to turn in and how to turn it in.

Structure

Your implementation should reside in a git repository forked from the appropriate 15-466-baseN repository. It should include:

• Your game's code and assets; ready to build.
• README.md -- fill in the first section with your game name, title, and some reflections on your game.
• screenshots/*.png -- include one or more screenshots of your game in action.
• Do not submit executables. (Just make your code easy to build.)
• Do not submit the kit-libs-[osx/win/linux] directories. (Using git submodule is file but not required.)

Turn-in Procedure

E-mail a link to the git repository containing your game code to Jim using the link provided in the assignment. Generally, the e-mail address will be jmccann+gameNcode@cs.cmu.edu, with the proper game number filled in.

Scoring

Games are scored out of three points, as follows:

• 1 point -- the game builds and runs.
• 1 point -- the game implements the selected design document.
• 1 point -- README.md has been filled in and a screenshot has been included in the screenshots directory.
• Up to one extra point may be awarded in extraordinary cases.