We'll be making our Game by coding the MicroBit in Python. If time allows we will also use Laser Cutting and 3D printing to make a case for our game.
Game needs to be an electronic version of the Marble Maze game (https://www.youtube.com/watch?v=FmWgAyOAimY)
You decide how hard you want to make this game with any complexities added, but it should:
- Have a maze that needs to be completed from start to finish to win.
- And the player needs to tilt the Game to control the "marble"
The player needs to be able to gain points.
The game needs to be coded in Python on a MicroBIT.
It needs to show the high score of the game when the game starts.
You need to design a case for the MicroBIT, but you don't have to make it.
To Develop our Game we will follow a process to guide us to the end result.
Watch the video on the left and try to filter out the steps that were made to get to the end product.
Key points from the video:
Decide what the MVP (Minimum Viable Product ) should be.
Break down into components.
Work on hardest component first.
Try work out your components using First Principles (back to absolute basics, think basic physics and maths).
Iterate the components till it works (Iteration means lots of failing!).
Put together all your components and test your MVP. This means you will have to think about what you want to test first and then get feedback from possible end-users.
Once you have the MVP sorted, then start adding more features if you have time.
We don't know yet what we are making, so let's do some research and figure out what would be cool to make..
Do research to find out what you are going to make.
Record who are your users and what the user requirements are.
Record what the purpose is and what the specifications are of your game.
Generate design ideas (minimum of 3!).
Produce a chosen design for the handheld game.
>> The results from the above steps then need to be all collated and presented on a double sided A4 in colour.
(Imagine that you need to impress a potential investor to give you money to develop the game!)
Now that you know what you are making, let's get making!
Decide what the MVP (Minimum Viable Product ) should be.
Break down into components.
Work on hardest component first.
Try work out your components using First Principles (back to absolute basics, think basic physics and maths).
Iterate (trail) the components till it works (Iteration means lots of failing!).
Test your final game (MVP!). This means you will have to think about what you want to test first and then get feedback from possible end-users.
Put this in a testing table. Also test for boundary cases.
Once you have made the MVP, then start adding more features if you have time left.