Introduction to Game Development
Group Assignment 2: Unity and Mobile
Due: Tuesday, December 15 at Noon
Fall 2015 Games
- Caitlin Klein
- Trish O'Connor
- Alex Nguyen
- Kenneth Crowell
- Alena Borisenko
- Greta Jochem
- Jeremy Slavitz
- Kevin Dorosh
- Kevin Liu
- Jordan Kemp
- Ben Machlin
- Ariel Serruya
- Matt Asnes
- John Gallagher
- David Taus
- Mike Yang
The Orb (Android Only)
- Sosena Bekele
- Nick Carlino
- Rohun Dhar
- Maya Saxena
- Eliza Schreibman
- Jason Brillon
- Chase Crumbaugh
- Justin Lee
- Ben Pall
- Quinn Collins
- Brian Rappaport
- Colin Watts
- Nathan Watts
- Yi Ding
- Nick Flores
- Zach Zager
Due to the complexity involved in developing games, game engines have become standard in the video game industry. By providing an intuitive interface and comprehensive layers of abstraction, game designers and developers can focus on the important parts of development. For our second project, we will use the Unity Engine to produce games that can run on any platform and with a variety of control schemes.
We expect every student in this class to:
- Work effectively in a group of 3-4 contributors
- Use modern agile development practices
- Contribute consistently and impactfully throughout the project
- The game can use either 2D or 3D graphics.
- The game must have multiple scenes.
- The game must have sound effects and music.
- The game shall be designed to be mobile-first (that is, playable on a mobile device).
- The game shall have a website as part of final deliverable.
Additionally, each project must use one of the following (extra credit for more than one)
- Networked or local multiplyaer
- Particle effects
- Multiple cameras
Note: the list of "pick two" items is subject to additions.
- Game Design Document - Due in class on Tuesday, Tuesday, November 3rd
- Digital Game Prototype - Due in class on Thursday, November 12th
- Alpha Demo, Iteration 1 - Due in class on Thursday, November 19th. Must Unity.
- Alpha Demo, Iteration 2 - Due in class on Thursday, December 3rd
- Beta with Test Plan - Due in class on Thursday, December 10th
- "Gold" Game with Website - Due at Noon, Tuesday, December 15
The Test Plan
This document will be distributed to all students (a.k.a., players) in the class, one page maximum. This document shall have the following sections:
- Game title (duh!)
- Authors (your name; duh!)
- Description of game in 255 words or less
- Brief instructions (rules)
- Controls (for every control scheme in your game)
- A checklist of at least 5 tasks that you want the player to test with a section for comments. Briefly describe each task with proper outcome. Example: press [an object or overlay] 5 times => produces a special move
- Section for additional comments and suggestions
There must be a web page that details your game (e.g., objectives, instructions). Most of the past projects showcased above are good examples. You can host the web page and your game on your personal web space on Tufts CS or use GitHub. Hosting your game on GitHub has many benefits. Many features are provided for free such as revision control (duh), issues tracking, simple web hosting, and even a wiki. It is an avenue for others to learn from your development efforts. The source code should be made publicly available, unless you have a good reason not to do so. On the main web page, please make sure to list the people who worked on the project!
- My friend and former classmate James Kraemer's senior project from spring 2002.
- Rocket Jump by Alex Miller (Spring 2012)
- Sky High by Amanda Bell, Tolga Zeybek, Gabriel Siu (Spring 2012)
- Spray Play by Brian Jordan (Spring 2012)
- Virus by Max Goldstein and Eva Parish (Spring 2012)
All works and ideas are owned by the members of the team. We (Arthur and I) cannot take ownership of any of your work. We do not have stake or equity in any project created in my classes for that matter.