Prototype I Risks

• Texture parsing/display
  • Course of Action: Active investigation of texture use, loading, and display
  • Assigned To: Everyone
  • Alternative: No textures
  • Status: Completed.

• Full MilkShape3D ASCII parsing
  • Course of Action: Looking into existing MilkShape3D ASCII parsers and file format
  • Assigned To: PaulScott
  • Alternative: Hard-coded levels
  • Status: Completed.

Prototype II Risks

• On screen menus w/ text and mouse interface
  • Course of Action: Messing around with glut's callback functions and searching for existing programs with mouse-based UI
  • Assigned To: RyanRiegel
  • Alternative: Keystroke- or console-based interface
  • Status: Used Windows-style pop-up menus; works pretty well.

• Transparancies and other graphical effects
  • Course of Action: Check NeHi, OpenGL references, and Z for advice
  • Assigned To: CalPierog
  • Alternative: No transparencies, etc.
  • Status: Seems to be working well, but took a bit of effort.

Prototype III Risks

• Animation for 3D models
  • Course of Action: Researching MilkShape3D 'bones' and searching for examples
  • Assigned To: ?
  • Alternative: No animation or sprite-based animation
  • Status: All animating has been scrapped; effects are indicated via text.

Final Version Risks

• Getting good graphics
  • Course of Action: Peruse the Internet for graphics
  • Assigned To: PaulScott
  • Alternative: Bad graphics; either homemade sprites or whatever we can find.
  • Status: Some good graphics have been found.

• AI
  • Course of Action: Test a few heuristics to see if they're any good
  • Assigned To: RyanRiegel
  • Alternative: Two player mode, anyone?
  • Status: AI performs complete search on unit's possible actions and looks for what results in the most damage dealt to the players or most health recovered to the enemies. I half expected this would take far too long to be playable, but it seems to be pretty quick (maybe units have less options than I estimated).

-- RyanRiegel - 18 Apr 2004