PacMath: Difference between revisions
No edit summary |
|||
| Line 120: | Line 120: | ||
* Collision detection does not always work - look into other pygame modules for collision detection? | * Collision detection does not always work - look into other pygame modules for collision detection? | ||
* It seems that our PacMan sprite can only eat two ghosties and answer two questions, then the game just continues, collision detection doesn't work and a new question can never be answered | * It seems that our PacMan sprite can only eat two ghosties and answer two questions, then the game just continues, collision detection doesn't work and a new question can never be answered | ||
==Milestones - Fall 2010== | |||
* By Week 7 | |||
** <s>Gain git access</s> | |||
** Evaluate game direction and idea | |||
**Determine whether to reuse or refuse the current PacMath code | |||
<br/> | |||
* By Week 8 | |||
** Document game idea and play | |||
** Decide on feedback mechanism (Score, Lives, …) | |||
** Refactor collision detection system | |||
<br/> | |||
* By Week 9 | |||
** Sugarize the activity | |||
** Implement multiple level capability | |||
** Refine ghost movement | |||
<br/> | |||
* By Week 10 | |||
** Improve game speed | |||
** Beautify game, intuitively redesign the UI | |||
<br/> | |||
* By Week 11 | |||
** Finishing touches | |||
** Usability testing | |||
** Release evaluation | |||
** Potential release | |||
<br/> | |||
Division of Labor: | |||
<br/> | |||
*Mike: | |||
** Ghost movement | |||
** Implementation of feedback mechanism | |||
<br/> | |||
*Abbi: | |||
** Sugarization | |||
** Map/Maze representation | |||
<br> | |||
* Both: | |||
** Game design and idea | |||
** Collision Detection | |||
** Game Speed | |||
** UI redesign | |||
==Milestones - Winter 2009== | ==Milestones - Winter 2009== | ||