In this project, you’ll build a complex game. It’s a platform game, where Felix the Cat jumps around, dodging baddies and collecting keys to escape the cavern. When he’s done that, he’ll go to the next cavern and do it all over again.

In the first week of this project, you’ll be learning how to make Felix move and interact with various things. In the second week, you’ll design your own levels. In the third week, you’ll put the levels together into a complete game.

Week 1: Building Blocks

Platform games, like Manic Miner and Mario Bros, are all about the central figure moving around a world and bumping into things. Some things, like walls and floors, just stop you moving. Some things, like baddies, will kill you. Some things, like keys, you want to collect. Some things are just scenery and don’t affect the game at all.

That means that knowing when you’ve bumped into something (called collision detection) is important. Scratch gives you a few blocks for collision detection: <touching? [sprite]>, <touching color []?>, <color [] is touching []?>, and (distance to [sprite]). However, to make the game, you need to know more than just whether you’re touching something: you need to know which side is touching it. If you walk up to a wall on the left, you can’t go left any more. But you can still go right, or jump, or fall if there’s no floor.

Touching a baddie may hurt you; but if you touch it with your feet, you may hurt the baddie. None of the built-in Scratch blocks tell you about direction of contact. So we’ve got to build our own collision detectors.

Task 1: Collision detectors

We’ll have four sprites that follow Frantic Felix around. Each will detect collisions in one direction and set a variable if it’s detected one. The main Felix sprite will use these variables to control how Felix can move. Each collision detector will have a bar of colour and use the <color [] is touching [] ?> block to detect things. We’ll use black for the floor and green for obstacles. We’ll use red for the collision detectors.

Activity Checklist

  • Open a new project. Add the frantic-felix/testlevel background and delete the plain white background1.
  • Rename Sprite1 as Felix. Make sure his costume can only flip left-right.
  • Create four new sprites from the images frantic-felix/top, frantic-felix/bottom, frantic-felix/left, and frantic-felix/right. These sprites are the collision detectors. Call the new sprites Top, Bottom, Left, and Right. Make sure that their costumes can’t rotate or flip.
  • Create four variables (for all sprites): blocked top, blocked bottom, blocked right, and blocked left.
  • Give each of the detector sprites this script:

    when FLAG clicked
        go to [Felix v]
        if <color [] is touching [] ?> then
            set [blocked right v] to (1)
            set [blocked right v] to (0)

  • Change the variables for each detector. The bottom detector needs an or block so that it sets blocked bottom if it’s touching either green or black. Hint: It’s easier to pick the colours in one sprite, then drag the script to the other sprites and change the variables being set. It saves having to find the right colours four times. At the moment, Felix just needs a script to follow the mouse pointer forever.

Test Your Project

Click the green flag.

You should see Felix follow the mouse pointer around, surrounded by a red rectangle. The rectangle is the collision detector. If you watch the variables, you should see them change as you drag Felix around and he touches different parts of the screen. At the moment, Felix moves through the platforms and the green obstacle. We’ll fix that in the next couple of steps.

Save Your Project

Task 2: Walking, floors and falling

Test Your Project

Use the mouse to drag Felix to somewhere on the stage and then click the green flag. If Felix jumps to the mouse pointer, you need to remove that script!

You should be able to use the left and right buttons to make Felix walk from side to side. If he’s not standing on the floor, he should fall gently.

When you click the green flag, the collision detectors should disappear. They’ll reappear when you press the red stop sign.

Save Your Project

Task 3: Jumping

The final part of making Felix move is jumping. Let’s have the space key make Felix jump. There are a few wrinkles to jumping:

  1. We don’t want Felix to fall if he’s going up.
  2. We don’t want Felix to be stopped by floors when he’s going up, but we still want him to be stopped by floors when he’s coming down.
  3. We don’t want Felix to jump up into the underside of a green obstacle.
  4. We want the jump to be animated, so we don’t want Felix to instantly move up a large distance.
  5. Felix should only be able to jump if he’s standing on a floor. The game would be too easy if Felix could jump off thin air.

Test your project

Click the green flag. Does Felix jump? Does he jump from one platform to another? Does he still fall when he walks off the end of a platform? What if he jumps off the end of a platform? What if he tries to jump underneath the green block on the right? What happens if you press the space bar while Felix is falling?

Save Your Project

Task 4: Keys and goals

We’ve got Felix moving around the world. Now to make him finish a level.
We’ll put three keys around the cavern. Felix collects a key by touching it. When he’s collected all three, he’ll be able to climb into an escape pod and flee!

Test Your Project

Click the green flag.

Save Your Project

Task 5: Baddies and deadly scenery

Now, baddies!

We’ll have two types of dangerous things. One type will be baddies that wander around and hurt Felix if he bumps into them. The other type will be bits of dangerous scenery.

Let’s do the roving baddie first. It will just move along a fixed path.

Activity Checklist

Test Your Project

Click the green flag. Does the vase move along? Does it stop and turn round at the ends? What happens when Felix walks into it? What happens if Felix jumps into it, whether from below or above? Does Felix disappear? Does the pod say the right thing? Can you still win the game?

Save Your Project

Next, dangerous scenery! Let’s say that anything bright blue is deadly to Felix.

Test Your Project

Click the green flag. Does Felix die if he touches the blue rose? What if he touches other things?

Save Your Project


What you’ve built is a very simple platform game. As it stands, it’s a pretty rubbish game. But that’s not the point. This game is a toolkit for how to build your own platform game levels. You’ll design your own levels next week.

Week 2: Designing levels

Last week, you built all the parts of a platform game. This week, you’ll use those pieces to make your own levels.

To recap, you made several things happen:

  1. Felix can walk left and right and jump.
  2. Felix falls unless a black floor stops him.
  3. Felix can’t move through green obstacles.
  4. Blue bits of scenery and baddies kill Felix.
  5. Baddies move around fixed patrol routes.
  6. Baddies kill Felix if he touches them.
  7. If Felix moves into a key, he collects it.
  8. When Felix has all the keys, an escape pod lights up to take him to safety (or the next level).

Treat these bits as a toolkit. Use them to build your own levels.

You want to create a series of levels for Felix to go though. Next week, you’ll look at how to connect the levels.
Levels can have large platforms or small ones, many platforms or few. There can be lots of baddies or none. There could be lots of obstacles or lethal bits of scenery. Don’t make the level too constrained; it should like there are a few routes to success, even if one is easier than others. Think about how hard or easy the level is.

You can change the special colours (black, green, and blue) but you need to update the colour touching blocks in all the scripts, but you need to keep the same colours in all the levels. (You could have different colours in different levels, but that would mean putting lots of or blocks around the colour-touching blocks.)

Test your levels. If you have time, create your levels in Scratch and play them. Check that they’re not too hard and not too easy. If you implement the levels, make sure to save the backgrounds you make and note the starting positions of Felix, they keys, and any baddies. Also make sure you note the directions the baddies move in and how far they go.

If you’ve already come up with a few levels, and put them in Scratch, try these extension tasks:

Extension: Stomping

How about making baddies die if they’re stomped on? Perhaps you could add a script to the baddies that does something if the baddie is touching the bottom collision detector sprite.

Extension: Power pills

You could create a “power pill” that allows Felix to destroy the baddies. When Felix collects the power pill, Felix destroys any baddie he touches. The effects wear off after a while.

It’s up to you to think about how to make that work. You might want to make the baddies look different when Felix can destroy them.

Test Your Project

Click the green flag.

Save Your Project

Week 3: Assembling the game

You’ve got some levels. You have enough tools to make each one work. Now all you have to do is put them all together into a whole game! If you’re able to put some levels together quickly, you may want to look at tasks 2 and 3 before playing your games.

Task 1: Displaying a new level

When Felix completes one level, we need to move on to the next one. That means intercepting the escape pod needs to send a start level message (instead of the win message) when Felix gets all the keys in climbs in the pod. We can use the start level message to set up the next level. We also need a variable, current level, set by the escape pod before it sends the start level message.

Pretty much everything needs to respond to the start level message to set up the next level.

The Stage needs to display the correct background. Each of the baddies, each of the keys, and the escape pod all need to move to the correct positions. The baddies’ paths need updating. Felix needs to move to his new starting position. Then the level needs to start.

Most of the sprites will need to respond to the start level message instead of the green flag. That means, for most scripts, you need to change the hat blocks.

Save Your Project

Before you do anything, save your work. You’ll be making changes throughout the Frantic Felix game, so keep saving your work regularly.

Test Your Project

Keep testing your game after every change. Keep testing the bits you’ve already changed, to make sure they keep working. We won’t tell you how to make all the changes. However, we’ll show you Felix’s revised scripts to show you the sort of thing you need to do.

when I receive [start level v]
        go to x:(item (current level) of [xs v])y:(item (current level) of [ys v])
        point in direction (item (current level) of [directions v])
            if <<key[left arrow v]pressed?> and <(blocked left)=(0)>> then
                point in direction (-90)
                move (2) steps
            if <<key[right arrow v]pressed?> and <(blocked right)=(0)>> then
                point in direction (90)
                move (2) steps
            if <<key[space v]pressed?> and <(blocked bottom) =(1)>> then
                set [height to jump v]to[100]

You’ll notice that the initial x, y, and direction for Felix are set with lists. We created some lists for each sprite (each list private to that sprite) to store all the values we need for that sprite. You need one list for each thing you store. You don’t have to use lists: you can use if blocks that check the current level and do the right thing depending on its value.

And here’s the escape pod, which handles all the level-changing:

        when FLAG clicked
        set [current level v] to [1]
        broadcast [start level v]

    when I receive [start level v]
        go to x:(item (current level) of [xs v])y:(item (current level) of [ys v])
            if <(keys to get) = [0]> then
            change [color v]effect by [25]
                if <touching [Felix v]?> then
                    if <(current level) = (length of [keys per level v])> then
                        say [You win!]
                        broadcast [win v]
                        stop all
                        change [current level v] by [1]
                        broadcast [start level v]

Task 2: Play!

You’ve got games. Your fellow Code Clubbers have games. Play all the games! Can you beat theirs? Can they beat yours?

Extension: Multiple lives

Felix will probably need a few lives to try to get through the levels. Create a new sprite with three costumes, showing one, two, and three hearts.

Use the frantic-felix/1-heart, frantic-felix/2-heart, and frantic-felix/3-heart costumes. Make the sprite appear in the corner of the stage. When the green flag is clicked, it should show three hearts. Every time it receives a lose message, it should show one fewer heart. Instead of showing zero hearts, it should hide and send a game over message.

The game over and win messages should be handled by a new sprite, which hides when the green flag is clicked and shows the right banner when the game over and win messages are sent. This sprite should also stop all the scripts when it displays itself.

You’ll also need to modify how the escape pod handles winning and losing, as that is now the responsibility of the lives and finish banner sprites.

You may find that your baddies are a bit too quick on the mark, pouncing on Felix before the level properly restarts. If Felix loses more than one life when he bumps into a baddie. hide the baddie as soon as it sends the lose message. That gives the rest of the game (including Felix) to reset before the baddie detects another collision with Felix.

Extension: Time limits

Put Felix against the clock! Use the Timer Scratch card to add a time limit. If the timer runs out, send the lose message. Remember to reset the timer at the start of each level.