Unity代写|final project requirements



SUBMIT: A Game Design Document (pdf), presentation slides (pptx or pdf), and 10-minute presentation using the slides covering the 5 required topics (see Stage 1 below)

  • Create an innovativesingle-playergame with 3-5 min gameplay
  • All assets for the game should be of your own creation or in the public domain/free/open license (do not purchase assets)
  • All team members must contribute and talk about their contributions
  • Games must be equivalent to ESRB rating of T or younger.Links to an external site.
  • Grading will focus on the innovationgameplay, and team member contribution

(This week) Stage 1. Game Design Document (1 page minimum) + Presentation (10 minutes max) + Participation Credit (speak + give feedback)

Design an innovative single-player game concept (multiplayer optional). We will be looking for a brief discussion on all of the points listed below .

Game Design Document

  • Game Title
  • Game Genre
  • Premise/Narrative/Story
  • Player’s Role and Game Goal (How do you beat the game?)
  • Gameplay/Mechanics (What abilities, activities, puzzles must be solved?)
  • Scoring or other feedback  (How is player progress and performance quantified?)
  • Writing/Art/Music style (What perspective, ambiance, or time period is conveyed?)
  • Innovation (What is unique about the design or implementation?)
  • Team Member Roles (Division of labor, timelines?)


  • Present all game design elements from above
  • Describe what will be shown in next week’s minimum viable product
  • Each person describes their planned contribution to next week’s minimum viable product


  • Speak in the presentation
  • Provide written feedback for each one (feedback form will be provided)

If your team receives feedback that your game may be trivial, lacking innovation, or considered a clone, please meet with faculty to revise the design. Although your team may not have known about the prior art or intentionally cloned a game, the problem must still be addressed. Analogous to playtesting feedback, teams may be penalized for not addressing presentation feedback.

Make sure to address all feedback you receive in next week’s presentation. Since the game will be published, our intent to encourage innovation and non-triviality (which is a small portion of the overall grade) is intended to help all teams produce a portfolio piece that impresses the broader community and potential employers.

(Next week) Stage 2. Minimum Viable Product (Unity project + Presentation)

  • Demonstrate key gameplay in a live, 1 minute playable demo
  • Final assets, art, audio are not needed
  • Submit a .zip of the project and instructions to Canvas and demo during presentation

(Week 3) Stage 3. Content Integration (Unity project + Presentation)

  • Add additional levels, art, sound, and music to the game
  • Use free, public domain, royalty-free assets
  • Submit a .zip of the project and instructions to Canvas and demo during presentation

(Week 4) Stage 4. Playtest feedback (Canvas Submission + Presentation)

  • Playtest your content-integrated game with at least 5 other individuals
  • Log feedback and responses/changes or limitations for not responding
  • Submit playtesting log to Canvas and present summary and plans to address playtesting during presentation

(Week 5) Stage 5. Game publication to itch.io and Submission to Canvas

  • Submit game project .zip to Canvas and publish executable on itch.io
  • Projects that do not compile or crash during play will be penalized

(Week 6) Stage 6. Final Game Presentation 12-3p Tues May 3 Bingham 140 (submit slides to Canvas)

  • 5 min presentation (including game demo)
  • Sides should cover
    • Game title
    • Game description
    • Innovation

Grading Criteria

Your final grade for the game assessment will be based on four factors:

Is the game fully functional?

The most important thing that we’re looking for is a working game. It must include scoring that reflects (at least in a significant way) player ability, multiple lives for the player, and the ability to play multiple games. If the game is almost but not quite finished or still contains bugs your grade will suffer much more than if it is a working game with fewer features. When you design your game make sure you can finish the project within the given time frame. Create a schedule and stick to it. The best plan is not to try to code the whole thing before getting anything to run. Do incremental development – get something running and then add more features.

Is the game nontrivial?

You won’t get a good grade if your final game is just pong or breakout with different colors and a bigger paddle. Your game should be something you of which you are proud. More specifically, we will be looking at how many objects can be in the game at once, how they interact – how good/realistic are any physics and/or collision detection, sound, (your own) music, originality, artwork, etc.  Other ways to make the game more complex are having terrain, a playing area larger than the screen with scrolling, the use of tiles, objects that behave independently of the player, etc.

Is the game well designed?

This includes things like how much fun it is to play, whether it looks good (has good graphics), if it has good “feel” in controlling the objects, … The game should not be too easy or too hard (maybe it can have different levels of difficulty).

You individual contribution to the game.

The grade that you receive will be a combination of the overall project grade (a team grade) and an individual grade for your contribution to the team as determined by your team members.


Present your contributions each week and provide feedback to other teams.