timeline logs specs documentation images forum home

Specs
1a. What kind of game are you planning to build?

1. Driving battle game.

1b. What are the goals of the game, how do players win, how do they lose?

1. Convert more of the campus than the opponent in a set amount of time.
2. Prevent opponents from converting people to their beliefs.

1c. What are the interesting or unique aspects to your game?

1. 2 players per cart (1 driver, 1 turret)
2. based on UCSD
3. cheats/hack
4. power ups
5. teamwork required to get super power ups

1d. What are the list of features of your game? Prioritize them into at least three categories: "Must have, Would be really nice, cool but only if we have time"

Must Have:

• 2 cart designs
• team play with 4 players
• Ability to destroy other players
• weapons
• newspapers
• NPC model
• Win based on control status
• Driver view(1st person)/turret view (1st person)
• Sound effects and background music
• Mini-map
• Intro scene
• Keyboard/mouse control input
• Chatting
• Documentation

Would be really nice:

• collision damage between carts
• make NPC moves
• Extra views, driver (3rd person)
• Rearview view
• Power ups / more weapons / more models
• Stats of carts / more models
• Ramps
• Mini-games (driver objectives)
• Death-match mode
• Teamwork moves/abilities
• Controller / Steering wheel input
• 6 player game
• VoIP
• A Splode!
• Surround Sound

Cool but only if we have time:

• single player mode
• Customize cars
• Practice arena
• Multiple radio stations
• Story mode
• Documentation for dummies (Javadoc in C)

2a. What are the major roles in your group’s management?

• We’re all equal (Democracy!)

2b. How will decisions be made? By leader, consensus?

• Consensus

2c. How will you communicate? Email, meetings in the lab, discussion board?

• E-mail, mailing list, meetings

2d. How will you know when you’re off schedule, and how will you deal with schedule slips?

• We’ll have a schedule made and we know if we’re late

2e. Who will produce the weekly group status reports?

• Andrew

3a. What are the development roles and who will handle them?

• team leaders:
• Graphics, Tim
• Network, Yong
• Physics, Al
• Game Engine, Joe
• Input, Andrew
• Web, Carrie
• Sound, Al

3b. What tools will you use?

• OpenGL
• DirectInput
• DirectSound
• WinCVS
• 3D Studio Max
• Microsoft .NET
• and others…

3c. How will you do testing?

• Unit testing

3d. How will you do documentation (both internal group documentation as well as external player documentation)?

• in progress, probably use something like javadoc for C

4a. Define a set of milestones with a specific definition of what each milestone is, what it means to complete each milestone, and when you expect to complete them. Define the milestones at two scales, a high level set of key milestones like integration and design freeze, and a low level set of weekly milestones. See Timeline