Warning: this project (like everything in this class) is an experiment. If something doesn't seem quite right, please let us know and we'll clarify or fix it. Check back for fixes and updates.
Over the course of the project, you will write 2 proposals:
- The Game Design Proposal (done with a "design partner" and due on Feb 26th)
- The Group Project Proposal (done with your project group, and due on March 6th)
There are lots of examples of class game projects at the page from the class at CMU. Their project is quite different in that they had more time, but smaller groups. They did have to do similar types of proposals and post-mortems (but not exactly the same questions).
I recommend looking through them both for ideas on projects, but also ideas on how to write them up.
Game Design Proposal
The initial game design document must cover the following points:
- Name
- Your Game must have a descriptive name
- Brief Description
- A paragraph or two (tops) giving the basic idea
- Detailed Description
- A longer description, describing the gameplay, the look and feel of the game, ...
- Scalability Plan
- A discussion of how the design can be "scaled" - what is the simplest possible version, what features could be added if there was enough time
- Game Principles Discussion
- A discussion of what game design principles should be employed in order to make sure the game is fun
- Design Challenges
- (closely related to the Game Principles discussion) What challenges face the team building the game in terms of making sure the game is fun? Especially in light of the scalability issue (that the team won't have much time for implementation)
- Technical Overview
- A brief discussion of how you imagine this game being built. What challenges will the team overcome? Do you have ideas as to how the implementation should be done. We don't need details here, just the basic ideas that explain why it should be practical to build it.
- Technical Challenges
- A brief discussion of what challenges will face the team that tries to build the game. This cuts both ways: the game must be sufficiently challenging, but not too challenging. Having contingencies to "hedge" against not being able to address the challenges is good (see "Scalability" above).
Group Project Proposal
The group project proposal should be an updated version of the original game proposal (note: please make it a separate Wiki page so we can compare the two).
You should expand the existing sections. Make any updates to change the design, but also provide more details. You should include pictures (sketches are fine) to better convey a sense of what you're trying to do.
You should also add the following new secitons:
- Response to Critiques
- What criticism did the original design get, and how did it affect your final proposal. Note: you might respond to positive as well as negative feedback.
- Tools Choices
- What tools do you plan to use to implement the project (note: you might change these choices later - but for now, you should have an idea of what to try first)
- Division of Labor
- How do you propose to divide the effort of building the game amongst the members of your team?
- Milestones
- What milestones do you see along the way of building the game? Describe what you expect to have done at the 1 week, 2 week and 3 week marks (at least).
- Risks
- What are the biggest unknowns or risks facing the project that jepordize its chances of success?
