%META:TOPICINFO{author="DominikSlusarczyk" date="1082150340" format="1.0" version="1.1"}% %META:TOPICPARENT{name="MeetingMinutes"}%

• Discussed content of game design document. Names in parentheses specify who this portion of the design document has been delegated to.
  • Main gameplay objective: Amass score by completing in-game "intermediate gameplay objectives" (missions). (Ed)
  • Storyline: "Beer Pong: Drunken Adventure." Gameplay objectives will relate to the beer pong theme. (Ed)
  • Controls: Shift-z-space-/-Shift (standard pinball). F2 opens new game. P pauses/unpauses. (Dom)
  • User Interface: Besides the pinball board, the following information will be available on the screen: score, lives, time, current intermediate game objective (with instructions). Camera will be fixed. (Dom)
  • Obstacles: Obstacles will appear on the board as aggregated triangle meshes. Block off ramps, change direction of ramp forks, etc. Other features will include bumpers & game-state-changing collision detectors (rollover & bump). (John)
  • Lives: Each user will start out with three lives. Opportunities to gain additional lives through intermediate gameplay objectives will be available. (John)
  • Scoring/Advancing: Intermediate gameplay objectives will provide most scoring opportunities. Many objectives will involve some kind of time limit. High score table will exist. High scores will survive on disk. (John)
  • Risk Analysis: Three major risky features have been discussed: flippers, multi-ball, dynamic level behavior. Flippers are an essential component of the game, and hence must be tackled by Milestone II. Flippers are risky because we need to develop a rotating triangle mesh and tweak associated physics parameters. Multi-ball is risky because it requires us to develop ball-ball collisions and tweaking individual ball timesteps to avoid unrealistic behaviors. Dynamic level behavior is risky becuase it requires underlying triangle mesh support, which in turn will probably require polygon data to be stored in intermediate aggregate objects. (Ed)
  • Use cases completed by group in meeting.
  • Individual components of the design document are due by noon Saturday (by e-mail to the group). Dom will compile into a single document by 1:30.

-- DominikSlusarczyk - 16 Apr 2004