Initial Concept: Game Description
The basic concept of our game will be an artillery style action game inside a full 3D environment. There will be a light hearted cartoony feel to the graphics, physics, and sound which will lend itself to a wacky and outrageous style. The emphasis will be on interesting graphics and fun play over realism.
In addition, each player will be in control of a moving gun platform that fires shells which can morph their characteristics on the fly to suit the players needs. You will be able to adjust the ammo's muzzle velocity, rate of fire, explosion radius, and mass, as well as add characteristics such as guidance and 'bounceiness'. Each of these values will draw from a common pool of points which limits the amount that can be spent overall. This will allow a variety of play styles and strategies which can be adjusted as the game plays out.
Work will be broken up into a 3 basic phases: Raw Design, Implementation, and Testing. The Waterfall workflow approach will be used for the implementation phase, with a top down approach using stub functions. The program will be broken down into major systems, and each member will be in charge of at least one. We will be using a cvs repository so that each member will be responsible for their code intergration as each system increases in complexity.
In addition, each player will be in control of a moving gun platform that fires shells which can morph their characteristics on the fly to suit the players needs. You will be able to adjust the ammo's muzzle velocity, rate of fire, explosion radius, and mass, as well as add characteristics such as guidance and 'bounceiness'. Each of these values will draw from a common pool of points which limits the amount that can be spent overall. This will allow a variety of play styles and strategies which can be adjusted as the game plays out.
Work will be broken up into a 3 basic phases: Raw Design, Implementation, and Testing. The Waterfall workflow approach will be used for the implementation phase, with a top down approach using stub functions. The program will be broken down into major systems, and each member will be in charge of at least one. We will be using a cvs repository so that each member will be responsible for their code intergration as each system increases in complexity.
posted by illuminus at 3:37 PM
0 comments
