Flippy Pancakes Micro:bit Game
Do you have what it takes to flip the perfect pancake?
We’re going to create a pancake-flipping game where you must flip the pancake at the perfect time. Too fast and your pancake will be mushy. Too slow and it will burn! You’ll learn how to…
- use a Buzzer and ADKeypad with the micro:bit.
- use if-else statements to evaluate conditions.
- create your own function on MakeCode.
- customise your game!
- Plug in your Buzzer to Pin0, making sure the positive lead is connected to the yellow signal pin and the negative lead is connected to the black ground pin on the breakout board.
- Plug in the ADKeypad to Pin1, match the colours of the wires to the ones on the breakout board!
- In Makecode, we’ll be tracking the length of time using two variables. Variables are like buckets that can hold changing values.
- Every time the micro:bit is turned on, a hidden timer keeps track of how long it has been on. We’re going to use this hidden timer to calculate the start time, end time, and total length of the game.
- Make a new variable called startTime (or anything you like, really) in the Variable drawer.
- When we start the game, we want to set our variable startTime to the running time of the micro:bit.
- We also want to display a flat pancake on the screen using the LEDs.
- We want to set up the game so that when you press the A button on the ADKeypad, a pancake-flipping animation will play on the micro:bit!
- To do this, we’re going to create a function. A function is a piece of code that performs a specific task every single time it’s called. In this case, that task is to display the pancake-flipping animation.
- To create your own function, click on the Functions category and click the ‘Make a Function’ button. I named my function ‘flipPancake’
- When you do this, a new block will be added to your screen called ‘function flipPancake.’ This is where we define our function, i.e. what will happen whenever we run the function block!
- In this case, we’re going to add multiple LED blocks inside our flipPancake function so it appears as though our pancake is being tossed into the air and is wobbling as it falls back down.
- Once you have your function defined, you can run it anytime by using the new ‘call function flipPancake’ block inside the Functions category.
- Feel free to customise your own pancake-flipping animation. This is just one example!
- Now we’re going to sense for button presses on the ADKeypad, but to do so, we need to import a special package into MakeCode.
- Expand the ‘Advanced’ section and scroll to the bottom and click on ‘Add Packages’
- In the search box, type in ‘Tinkercademy’. Click on the box labelled ‘tinkercademy-misc’
- Now you’ll see something new in MakeCode – a bright green Tinkercademy category has been added!
- Inside this category you’ll find blocks to sense button presses on the ADKeypad. Note that importing this package only happens for the current project. So if you start a new project and want to use the category, you’ll need to re-import it.
- Now that we can sense button presses, let’s create the main code for the game! We need to calculate the time whenever a player presses the A button and figure out if the pancake is mushy, perfectly cooked, or burnt.
- We start off with a forever loop. Inside the forever loop we put an if-else statement that tests to see if button A is pressed. If-else statements test to see if a condition is true; if it is true, then they do something, else they do something else. Because this if-else statement is inside a forever loop, it will forever test to see if button A is pressed.
- To do this, we’re going to check the current running time of the micro:bit and subtract the value of our startTime variable. This gives us the total time the current game has been running. We store this in another variable called totalTime (you can create this in the Variables category).
- After calculating the totalTime, we call our flipPancake function! This will animate the pancake!
- Next, we need to to test the totalTime to determine if the pancake is mushy, perfect, or burnt. We use if-else statements again for this, but in this case, we’re going to link the if-else statements together to test multiple conditions back-to-back. When if-else statements are linked together, only one can be run – as soon as the micro:bit finds one that is true it skips testing all others that are linked. We can add linked if-else statements by clicking on the gear icon on the if-else block and dragging in more if-else blocks.
- In this case, we start by testing if totalTime is less than 7000 (keep in mind this is milliseconds! So 7000 milliseconds = 7 seconds). If totalTime is less than 7000, we determine that the pancake is mushy and display a frowny face and a MUSHY message. If this first condition is true, the micro:bit will skip testing all the following conditions!
- If totalTime is not less than 7000, we test if totalTime is less than 8000 milliseconds. We know at this point that totalTime is greater than 7000, so if it’s also less than 8000, we determine that the pancake is perfect and display a happy face and a PERFECT message.
- Finally, if neither of the previous two conditions have been true, then we know that totalTime must be greater than 8000, so we determine that the pancake is overcooked and display an angry face and a BURNT message.
- Now that we have the game running, let’s make it so that players can play more than once without resetting the micro:bit.
- To do this, we’ll reset the game when button B is pressed on the ADKeypad. Once again, we use a forever loop and place an if-else statement inside that tests to see if button B is pressed (don’t forget to specify the correct Pin number again!).
- What else do we need to do when we restart the game? In this case, all we need to do is display a new pancake, and reset the starting time!
- Now our game is working (hopefully)! Let’s add some more fun to the game: we have a buzzer attached to the micro:bit but haven’t used it yet! Note: this adds onto your existing code – it’s not a brand new section!
- The micro:bit has lots of pre-programmed music melodies available for us to use. Let’s add in music to our game. Here we add a different melody to each outcome of the game. For mushy or burnt pancakes, we add sad melodies, but for perfect pancakes we play the nyan-cat melody!
- Note that we want to set these melodies to play ‘once in the background’ otherwise it could pause the entire game until the melody is finished playing!
- Finally, let’s add some starting music and a starting message when we first start up the micro:bit. Note: this adds onto your existing code – it’s not a brand new section!
- We can use the buzzer once again to play a melody (once again we want it to play ‘once in background’). We can also display the name of the game as well!
- Now that you’ve learned how to use the ADKeypad, you can try using it to control LEDs, servos, and other components! You also learned about if-else statements and creating your own functions, which can be useful in many micro:bit projects! Try customising your pancake game as well!
- What’s a game without healthy competition! Add a scoring system to compete against your friends!
- Simply add the variable ‘score’ within the ‘on start’ function
- Then ‘change score by 1’ whenever you get a PERFECT pancake
- Have fun cooking up new ideas!