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.
Your goal is to relate the 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.
Describe the steps you took in your role as producer. Typical items include group scheduling mechanisms, links to meeting notes, descriptions of team logistics problems with their resolution, project organization tools (e.g., timelines, dependency/task tracking, Gantt charts, etc.), and repository management methodology.
Describe your user interface and how it relates to gameplay. This can be done via the template. Describe the default input configuration.
Add an entry for each platform or input style your project supports.
Describe the basics of movement and physics in your game. Is it the standard physics model? What did you change or modify? Did you make your movement scripts that do not use the physics system?
List your assets, including their sources and licenses.
Describe how your work intersects with game feel, graphic design, and world-building. Include your visual style guide if one exists.
Document the game states and game data you managed and the design patterns you used to complete your task.
List your assets, including their sources and licenses.
Describe the implementation of your audio system.
Document the sound style.
Add a link to the full results of your gameplay tests.
Summarize the key findings from your gameplay tests.
Document how the narrative is present in the game via assets, gameplay systems, and gameplay.
Include links to your presskit materials and trailer.
Describe how you showcased your work. How did you choose what to show in the trailer? Why did you choose your screenshots?
Document what you added to and how you tweaked your game to improve its game feel.