Final Game Prototype

Now that our solo adventures are done, it's time to start work on our final games. And to help keep schedules on track, we're going to have some check-ins.

Grading Criteria

Every team's game will be different, but there are a few key elements we want to see present in your first prototype build:

Organization (2 points)

• Logically organized code (0.5)
• Clearly commented code (0.5)
• Runs from localhost w/ no major programming errors (game bugs are OK) (0.5)
• Include a comment in the header of your source with your team name and all team members (0.5)

Structure (6 points)

• A "core loop," i.e., you have defined states (yes, plural) and some means to switch between them (1)
• Player interaction. - The player can interact with the game. You should have at least one primary mechanic operational. If you make a platformer, perhaps movement and jumping are implemented. If you make a narrative game, perhaps the dialog boxes are implemented. If you're making a hidden object game, perhaps the basic point/click verbs are implemented. It all depends on your game. (1)
• Temporary graphical assets. What good are core loops and interactions if there is nothing to look at? These should be assets *you* create, even if they are geometric primitives, quick doodles, or magazine cutouts. (1)
• Temporary sound assets. Don't leave decisions about sound until the end of the design process. Sound is integral to making a game feel "real." Make sure your game makes some noise. (1)
• Version control. You must have your git workflow established. GitHub is the standard we are using. Make sure you have a repository setup. Add a comment in your source header with a link to your GitHub repository. (2)

Please submit your game as a .zip file that includes all necessary dependencies (e.g., framework, assets, etc.).