In this week's lecture we looked at Class Responsibility Collaboration (CRC) cards. First was to look at the objects. For my game, they are: stage, player (cat), path of dots, sun, start/stop, timer.
I then created a card for each of these and looked at the attributes (variables) and abilities (functions).
This process raised an interesting question for my game, what moves? I had to quickly sketch it up to understand the relationship between the moving objects. Using this, I was able to refine my goal for the next prototype (IP1) - how do the movements work and work together.
So far, I have:
- the player moves along the path (right) of coloured dots through keyboard inputs
- the path is longer than the screen so the path has to move as well
- the path moves to the left as the player moves (e.g. it does not move independently, if the player doesn't move, the path doesn't move)
- sun starts near the middle and moves to the end of the path
- how fast the sun moves depends on the level
- the sun's movement is a fixed speed and time
- if the sun reaches the end before the player reaches the sun = game over
- if the sun goes off screen but has not reached end yet, timer informs player of time left
Writing out all the movements, it feels a little complicated. It might also be confusing to have the sun go off the screen.
Current:
Goal is to reach sun (location) for nap before sun reaches end of path (second location)
Suggested change:
Goal is to reach end of path (location) before sun (day) becomes night (timer)
I am going to ruminate a bit more on this change and discuss it at our next workshop for more feedback.
No comments:
Post a Comment