adynamo

Friday 17 December 2010

An Idea of Our Tasks....

Hi guys,
Here are some steps in programming our game. I think we can focus on one each:


1/ the maze &

a/ creating the maze walls

b/ sensing that the ball doesn't pass through the walls


2/ the door &

sensing that:

a/ the ball doesn't touch it before the challenge pops up

b/ the ball doesn't pass through without answering the question by sending the player back some steps when contact is made


3/ the challenge (spelling or what?)

a/ checking for correct or incorrect answers and scoring accordingly

b/ returning back to the game afterwards


4/ bonus objects in the maze

a/ knowing when the player has "picked up" this object, and

b/ updating the scoreboard accordingly


General Coding for:

1/ The game's external controls / commands (would we still need any?)

2/ Background music, sounds and voice-overs

3/ Combining / linking the programmed pieces above into a solid whole



I think the "General Coding" part would come towards the end of the program-wrting. As for the coding, I tried searching and it seems it won't be as easy as we think.


Equally important is the HCI part of our game. We all need to take this into consideration both in the programming, and the interface design. Should this aspect be delegated to one person? Or should it be a duty of all?

No comments: