A paragraph-length pitch for your game.
Web-playable version of your game.
Trailor
Press Kit
Proposal: make your own copy of the linked doc.
In this section, explain how the game should be played. Treat this as a manual within a game. Explaining the button mappings and the most optimal gameplay strategy is encouraged.
Add it here if you did work that should be factored into your grade but does not fit easily into the proscribed roles! Please include links to resources and descriptions of game-related material that does not fit into roles here.
If your project contains code that: 1) your team did not write, and 2) does not fit cleanly into a role, please document it in this section. Please include the author of the code, where to find the code, and note which scripts, folders, or other files that comprise the external contribution. Additionally, include the license for the external code that permits you to use it. You do not need to include the license for code provided by the instruction team.
If you used tutorials or other intellectual guidance to create aspects of your project, include reference to that information as well.
This section be repeated once for each team member. Each team member should provide their name and GitHub user information.
The general structures is
Team Member 1
Main Role
Documentation for main role.
Sub-Role
Documentation for Sub-Role
Other contribtions
Documentation for contributions to the project outside of the main and sub roles.
Team Member 2
Main Role
Documentation for main role.
Sub-Role
Documentation for Sub-Role
Other contribtions
Documentation for contributions to the project outside of the main and sub roles.
...
For each team member, you shoudl work of your role and sub-role in terms of the content of the course. Please look at the role sections below for specific instructions for each role.
Below is a template for you to highlight items of your work. These provide the evidence needed for your work to be evaluated. Try to have at least four such descriptions. They will be assessed on the quality of the underlying system and how they are linked to course content.
Short Description - Long description of your work item that includes how it is relevant to topics discussed in class. link to evidence in your repository
Here is an example:
Procedural Terrain - The game's background consists of procedurally generated terrain produced with Perlin noise. The game can modify this terrain at run-time via a call to its script methods. The intent is to allow the player to modify the terrain. This system is based on the component design pattern and the procedural content generation portions of the course. The PCG terrain generation script.
You should replay any bold text with your relevant information. Liberally use the template when necessary and appropriate.
Add addition contributions int he Other Contributions section.