Final Canvas Submission

our final game is graded based upon the following criteria, in cake-based metaphors:

===THE BATTER===

+5 post your game online (itch.io is the simplest way to do this) and submit a link (see below)

+5 game runs/executes without critical errors or crashes

+5 turn in a .zip of your final game file structure, including assets - game MUST run via localhost with no code tweaking, folder rearranging, etc. (Non-Phaser submissions must submit Mac and PC builds)

+5 game has appropriate title screen, end state, and ability to restart from within the game (based upon your game, genre, etc.)

+5 the player can learn the controls from within the game, whether through tutorial, instruction screen, or other diegetic means

+10 well-structured code, including comments, appropriate data structures, sensible ‘classes’ and states, etc.

+10 properly maintained and updated team GitHub (or equivalent for non-Phaser games) - submit this as a link (see below)

===THE BAKE===

+10 game’s artistic cohesion (does the art/sound/etc. reflect your stated aesthetic/experience goals? do your assets make sense together?)

+10 game’s mechanical cohesion (do the mechanics reflect your stated aesthetic/experience goals? does the game feel good? are the mechanics well-implemented?)

First Prototype Build

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

• A "core loop" is present, meaning you have defined states and some means to switch between them (5 pts.)

• The player can interact with the game. You should have at least one 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. (5)

• Some temporary graphics assets should be in place. 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. (5)

• Some 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. (5)

• You must have your version control workflow established. GitHub is the standard we are using. Make sure you have a repository setup. (5)

First Stable Release

Merge pull request #6 from RaiderSoap/development

Development