CSCI 171: project phase III option A: proof of concept (game demo)

Deliverables and expectations

This deliverable represents your completed game project, including: the working game, all code, image, and sound files, readme file, in-game help, promo sheet, screenshots, game design documentation, and the list of sources for image and sound files..

All components are to be submitted to the course instructor by the deadline noted above.

• All the files must be submitted on a thumbnail drive.
• The drive must be submitted in an envelope with your name on it.
• The drive must not contain files or folders that are not directly related to the course project.
• The game must run either on the machines in the CS linux lab or be compatible with a PC running a typical XP or Vista setup.

If any of the requirements above are not met, then your assignment may not be accepted for grading.

Keep your own, seperate, copy of all the files you submit on the thumbnail drive! It might take some time before the instructor is able to complete grading of your submission.

Submission expectations:

• In-game help
  The game must include solid in-game help, easily accessible and clearly visible, including at least the following:
  • A short description of the game premise and any necessary background - setting up the motivation and objectives for a new player.
  • A short description of the player goals, tasks, and objectives, and how you win or lose.
  • A brief list and description of any key characters (PC and NPC) the player may play or encounter, including key abilities or properties and back story.
  • A description of any other key gameplay elements (empires, artifacts, items, etc.) the player may use or encounter, again identifying their key abilities or properties and back story.
  • A list of the game's default keyboard/mouse/joystick commands, what each does, and where the player would use it.
  • A description of each of the different interface screens/panels, menus, commands, options, etc. available to the player - logically organised and supported with images or screenshots where appropriate.
  • A section on tactics and advice, aimed at the first-time player.
  • A discussion of any common problems the player may encounter (related to game play) and solutions for them.

• Readme Documentation
  The main game folder (see below) must include a Readme file (also in .txt or .pdf format) which contains at least the following:
  • Detailed instructions on how to install the game and troubleshoot any likely problems.
  • Detailed instructions on how to run the game and access the in-game help.
  • Detailed discussions of all known issues or bugs associated with the currently submitted version.

• File and folder naming and organization
  The files for your game must be appropriately organized into folders with intuitive names (e.g. Sound, Backgrounds, Sprites, etc.) -- you should not have everything lumped together into one or two folders.

• Code design document
  This should be submitted in hardcopy, and should provide the instructor with a general understanding of the code organizaton and structure (what code components are found in which files, what classes and key routines are used for what purposed, etc).

• Code, sound, and image files
  The final submission must include copies of all source code, sound, image, and documentation files used in the final game submission.

• Sources, citations, and intellectual property rights
  For all creative content that is not your own work, you must clearly identify the source and clearly identify why/how you have the intellectual property rights to include that content in your submitted game.

  This includes code, sounds, images, animations/video, and storylines/dialogue written or developed by someone other than yourself.

The game features submitted must not result in game crashes or hangs . It is better to leave the feature out than to have the game crash or force the instructor to manually kill the game process.

Marking Criteria for the game prototype/demo

As different students typically emphasize vastly different facets of their games, the evaluation will attempt to account for cases where a student has sacrificed depth in some areas in order to provide increased depth in others. The general criteria considered are:

• Game premise and originality
• Use of audio and visual images and effects
• Artistic development (self-developed sound, imagery, dialogue, etc)
• Game content (levels, characters, maps, storyline, etc)
• Playability and stability
• User guidance (user manuals, in game help, readme file, tutorials, etc)
• Tools and add-ons (level editors, map generators, test tools, etc)
• Technical depth (sophistication and effectiveness of code components)
• Technical structure (clarity/organization, comments/documentation, etc)
• Intangibles, fun factor, "other"