Mini Minds Hub · Free printable
Star Catcher Game Blueprint: Free Printable Worksheet for Year 5
- ForYear 5
- StageKey Stage 2
- CostFree
- FormatPrintable PDF
Star Catcher Game Blueprint is a free printable computing worksheet for Year 5 (ages 9 to 10). Children plan a star catching game on paper, write the code blocks as short lines, then find and fix the rival bugs. It needs only a pencil. Page 2 gives the grown-up notes, help ideas, a stretch idea and the answers.
It comes from the Mini Minds Hub, the free library of printables from Jaques of London, the British games and toy company that has been making games for families since 1795. Print both pages, give page 1 to your child and keep page 2 for yourself. Black and white printing works well.
What is on the sheet
Children work on paper like a game designer. They fill in a table to plan the game, then answer numbered questions about the goal and the variables. There is space for the code blocks, written as short lines. Boxes for drawing or notes give room to think. When the plan is done, children turn detective and fix the rival bugs. No computer is needed.
- 1. My goal. What must the player do to win?
- 2. My variables. Score starts at ___ and lives start at ___. Why?
- 3. Event or if block
- My code blocks
Why plan a game on paper?
Block style programming lets children build programs by snapping instructions together instead of typing them. Because the blocks are short and readable, the focus stays on the ideas: what starts the code, what the game remembers, and what happens when something is true. On paper, children can practise exactly those ideas. Writing each block as a short line keeps the thinking clear without needing a computer or any particular software.
Games are a good way to learn about variables, events and if statements. A game has things that change, such as points and chances left, and things that happen, such as two objects meeting. Planning first saves time, because a designer decides the rules before writing any code. Debugging is part of the job too. Even experienced programmers find mistakes in their own work, so spotting a bug is a normal skill to build.
Skills and curriculum link
- Designing a program
- Using variables
- Using if statements
- Understanding events
- Finding and fixing bugs
- Explaining your thinking
Ideas to talk about with your child
- VariablesA variable is a named place where a program keeps something that can change. Ask your child which things in a favourite game the computer must remember.
- EventsAn event is something that happens and makes code run, such as a key being pressed. Ask what starts the action in a game they know.
- If statementsAn if block runs its instructions only when a condition is true. Try everyday examples, such as if it is raining, take a coat.
- DebuggingA bug is a mistake in a program. Debugging means testing, spotting what went wrong and fixing it. Reading code aloud, one line at a time, is a good way to find bugs.
Key words
- BlueprintA plan made before you build something. Here it is a plan for a game.
- VariableA name for something the program remembers, such as a score. Its value can change.
- EventSomething that happens and makes code start, such as pressing a key.
- ConditionA test that is either true or false. An if block checks it.
- BugA mistake in a program that makes it behave in the wrong way.
- DebugTo find a bug and fix it.
How to use it
- Print both pages. Page 1 is for your child. Keep page 2, which has the notes and answers.
- Read the sheet through together the first time. Talk about each choice before your child writes.
- Ask your child to complete the plan first. Then they write the blocks in short lines and move on to the rival bugs.
- Check the work against the notes and answers on page 2. Ask, "How did you decide that?" The reasoning matters as much as the answer.
- Come back to the sheet another day. Repeating a familiar activity builds confidence.
Help, stretch and game ideas
If it feels too hard
Give your child the word bank: set, change, forever, if, touches, score, lives. Let pairs say each script aloud before they write anything. Start with the goal, and read it back as one clear sentence. Then write one block at a time, each as a short line.
To stretch confident children
Add a new rule, such as a bonus star worth 5 points. Write the blocks and the variable changes it needs. Then ask whether the new rule affects anything else in the game. Test it with a partner, and fix any bug you find.
Make it a game
Swap sheets with a partner. Read their blocks one line at a time and act out what happens, using a paper player and a paper star. Say aloud every change to the score and lives. If the game cannot be won, tell the author where to look.
Talk about it
- What is the goal of your game, and how will a player know they have won?
- Which things in your game change while it is played? Which things stay the same?
- What event starts each part of the action?
- Why did you choose those starting numbers? Would the game feel different with other numbers?
- How did you spot the bugs? What did you do first?
- If you could add one new rule, what would it be and what would it change?
Take it off the page
Act it out
Make a paper star and a paper player. Move them around the room while a friend reads the blocks aloud. Stop whenever the blocks do not match what happens.
Board game rules
Think of a board game your family plays. Write its rules as if statements, such as if you land on this square, then do that. Check them with the people playing.
Robot instructions
Write step by step instructions to guide a family member to a hidden object. Test them exactly as written. Fix any step that sends them the wrong way.
Who it is for
Parents
Sit beside your child for the first go, then let them lead. You do not need to know any coding. Ask them to explain their game out loud, and use page 2 to check the answers together afterwards.
Teachers
Use it as a starter, a plenary, an early finisher task or a table activity alongside your computing unit. It needs no preparation beyond printing. Pairs can swap sheets to test each other's blocks. Page 2 gives support and stretch ideas for mixed ability groups.
Home educators
Print it as part of a wider computing plan. It works well without a device, and it pairs well with building real board games or making up rules for outdoor games. Brothers and sisters can swap sheets and debug each other's work.
Where this fits in computing
In Key Stage 2, children learn to design, write and debug programs. This includes sequences of instructions, repeating actions, selection with if, and using variables. Before this sheet, children often meet sequences and simple events that start a program.
After this, children can try building a game on a computer using blocks, or move on to bigger programs that use more rules and inputs. They can also test and improve their own programs. The planning and debugging habits on this sheet carry over to all of it.
Questions parents and teachers ask
- What age is Star Catcher Game Blueprint for?
It is written for Year 5 (ages 9 to 10), in Key Stage 2. Children who are a little younger or older can try it too. Adjust the support using the help and stretch ideas on page 2.
- What will children practise?
Children practise designing, writing and debugging simple block style programs. The sheet covers variables, events and if statements, and asks children to explain their choices as well as write the blocks.
- Do children need a computer?
No. The sheet is completely screen free and needs only paper and a pencil. Children write their blocks as short lines, so they can think about how a program works without any software.
- What if my child finds it hard?
Give them the word bank on page 2 and let them talk through each script aloud first. Work on one part at a time. Praise the thinking, and come back to the harder parts another day.
- Is it free to print?
Yes. It is free to print for home and classroom use. You can print it again for brothers and sisters, or for revision a few weeks later.
- Can teachers use it in class?
Yes. It works as a starter, a plenary, an early finisher task, homework or a table activity. It needs no preparation beyond printing, and page 2 has support and stretch ideas.
- Do I need to print in colour?
No. It prints well in black and white on plain A4 paper. Print both pages, give page 1 to the child and keep page 2 for the grown-up.
Preview the full PDF
Made by Jaques of London, making games for families since 1795. A printable supports classroom learning and does not replace a teacher.