Assignments

Assignment 1

In this assignment, you will create a 3D version of Angry Birds to get you more familiar with physics and collisions in Unity3D. You must design two consecutive levels with a score that carries over from the first to the second level. Each level will consist of hand-arranged rectangluar prisms where the object is to shoot a sphere in order to blast the objects out of the way and hit the goal at the center of the "castle". You are welcome to count points however you like (e.g. points for reaching the goal and/or knocking over cylinders, or limited shots that reduce after each projectile firing), but they must be shared between levels. Projectiles should leave a trail during and after flight to make the next shot easier, but no more than one trail should appear at any given time. You should use a side-view camera where the projectile launch location and the castle are not both in view at the start of the level. The camera should track the projectile as it moves toward the castle.

Homework should be turned in to Google Classroom as either a zipped project file or as a link to your GitHub.

Assignment 2

In this assignment, you will create a basic top-down rpg. Intricate or pretty visuals are not required, but you should make everything easy to see and understandable. The required components of the game include:

• ground-targeted click movement,
• one patrolling enemy,
• a required item to pick up,
• pick-up mechanic such as right clicking the item while in range,
• inventory that shows currently owned items (use "i" to open/close),
• some fight mechanic to disable enemy and pick up the item,
• exit that checks if player has the item,
• camera that follows the player (e.g isometric).

Final Project

You will create a substantial game in groups of 2-4 people. The game must be a Unity 3D game that is either multiplayer or networked (or both). Projects will be run using the scrum methodology and you are required to track all identified tasks. Tracking will include a description, assigned member, time created, time completed, expected time to complete, and priority. Share a google doc with me (one per team) so that I can track your progress as well. At the end of each stage, I will meet with every group individually to assess your progress since last sprint, goals for next sprint, and give feedback on the direction of your game. Each sprint will conclude with a playtesting session which will require you to write up your classmates feedback and known issues.

Initially, each group will create a one-page game pitch that must include relevant details such as:

• Game Title (or proposed title)
• Target systems (e.g. computer, console, tablet, phone)
• Target age of players
• Intended ESRB rating
• Summary of game’s story (if applicable)
• Summary of gameplay aesthetics/dynamics
• Summary of gameplay mechanics, including what the player will be doing from moment to moment
  • This should also include how multiple players interact
• Relationship between story and mechanics (if applicable)
• Relationship between aesthetics and mechanics
• Vision for art/sound direction
• Unique selling points
• Competitive products

Quality of the final projects will be judged holistically as well as your progress at the end of each sprint stage. Individual assignments will be created for each sprint.

In general, projects should show substantial effort from each member of the group, application of features not entirely covered in class, high implementation quality (minimize bugs), and a cohesive gameplay experience that incorporates aesthetics, mechanics, and dynamics.