Sunday, January 20, 2013

Getting a game plan for Q2


I’ve added the following as my individual focus items for the term:
·         Add other enemies – add a couple more enemy classes to the game.
·         Player achievements – based on these player events:
o   Total score
o   Total score for specific enemy types
o   Some other kind of event
·         Player levels – based on score.
·         Power ups – two basic types:
o   Found in the environment
o   Abilities, skills that get ‘unlocked’ based on player score and level.
Based on the above, I do have a built in hierarchy/dependency tree:
·         Player score breaks down into:
o   Total Score
o   Total Score by specific enemy types
·         Player level which is based on Total Score
·         Power ups which also have a dependency on player score and player level.
Okay, so now I can do some planning.  Looks like for now the work is going to be done in the back end:
1.       Add more functionality to the playerScore, playState modules that will take care of incrementing both total score and total score by enemy types. 

2.       Make a decision as to keeping with the current JSON tables, or start making more use of SQLite to hold onto this data.

3.       Once the scoring is taken care of, achievements will have to be addressed.  Currently achievements are based solely on total score – what gets delivered is some text based on a set of ranges.  If the players score falls between certain ranges then what gets displayed is the text for that range.   That’s fine for now, but the next steps will need to be saving player achievements – probably in the SQLite database.  This way calculations/algorithms only get hit once per achievement.

No comments:

Post a Comment