The 2010 679 Game Project
This is the main "overview" page
The goal of this project is to produce a game by working in a team of 4 people. What game you create is up to your team, but is subject to some Rules.
This project will count for 2/5 of your total class grade. All parts of the project will contribute towards your grade (including your proposal, critiques, and post-mortem).
Ideas for games must be presented as a Proposal, for everyone will write Critiques. You team may choose any one of the proposed designs.
Teams will be assigned on Monday, April 5th. Each team will need to choose a game to build, and create a plan in time for a project meeting with the course staff on Friday, April 9th. The games will be built over the following 3 weeks, culminating in a playtesting session when each person will play each game. (expect to give and recveive lots of demos). The following week will give an opportunity to tune the game and produce the final documentation.
The project Phases:
- Game Proposals (Monday, March 22nd)
- Project Kickoff (Monday April 5th)
- Project Plans and Meetings (Friday, April 9th)
- Signs of Life Demos (Friday, April 16th)
- Tech Demos (Friday, April 23rd)
- Playtests (Friday, April 30th)
- Gold Masters (Friday, May 7th)
- Festival of Games! (Monday, May 10th)
Other potentially useful stuff:
A Brief Discussion of the Phases (with links to each)
- Game Design (Proposal) (due Monday 3/22, noon)
- Pairs of people will propose games for project groups to build. We'll discuss the designs during class
- Game Design Critiques (due Wednesday 3/24 at noon
- Each person will have to do a critique of the other game designs. You need to do your critiques early enough that we can look them over before class.
:Project Kickoff (in class, Monday, 4/5) - Teams will be assigned, and groups will meet
- Game Plans (due Friday 4/9, 9am)
- Each project team will complete a detailed plan. During class time, there will be meetings to discuss the designs (the early deadline is to give the instructor and TA time to read over the plans).
- Signs of Life Checkpoint (due Friday 4/16)
- Each project team will have to provide evidence that they are making progress towards implementing their plan.
- Tech Demo -> Checkpoints (due Friday 4/23, class time)
- Each project team will give a demonstration of the their "technology" implemented to that point.
- Playtests (Monday 5/3)
- In class, we will have a "play testing" session where each person will get to play each other group's game. Prior to the play test
, there will be a code freeze . But enough stuff needs to be prepared (including documentation) such that people can play the game at class time.
Game Reviews (links coming soon) (Monday 5/3)- After play testing, you will need to write a review of each game you played. These will be given (anonymously) to the project team so they can incorporate the feedback.
- Gold Master (Friday 5/7)
- The last day of class, "everything" is due (code, documentation, ...). Official University Policy says things cannot be due after this. Late projects (up until the final deadline) are negotiable.
While the post-mortems are officially due at this time, there is leniency for them.
- Festival of Games! (link coming soon) (Monday, 5/10 - or whatever the registrar schedules our final exam for)
- We won't have a final exam. During the final exam time slot, it is my plan to play the games that you've built. Note: late projects cannot be accepted after the exam period except under extreme circumstances.
