Penalty Shootout I — Scratch L2 Lesson 37

Learnt27 min · the aim, the arrow, the kick, the goal
Basic25 min · build the penalty
Challenge 1–327 min · aim, kick, judge
Extrabonus · pick your corner

WHAT IT SHOULD LOOK LIKE

A new game. Point at the goal, click, and the ball flies to that exact spot. Inside the posts and under the bar is a goal.

aiming for the top corner

click

faded sprite = where it ends up · panels run left to right

Review — the Road Crossing 5 min

Every car in a lane is a clone of one sprite.
A variable made For this sprite only gives each clone its own (speed).
To ride a log, the player moves by the log’s speed while touching it.

Quick-fire

Ten clones all read (speed). They all move at the same speed. Why?

Reveal the answer

(speed) was made For all sprites. There is only one of it, so every clone reads the same number. Today’s variables are the opposite: we want one shared (aim x) that every sprite can read.

Today’s Topic 3 min

An aim marker that follows the mouse
An arrow that points towards it
Two kinds of click: on a sprite, and on the Stage
A kick that goes exactly where you clicked
Four comparisons that decide GOAL or miss

Learning outcome

By the end of this lesson you will be able to:

Make a sprite follow the mouse, and another face it.
Save the mouse’s x and y at the moment of a click.
Test whether a point is inside a box, using four comparisons and and.

Learnt — aim, kick, judge 27 min

1 · The rules, before the blocks

The ball starts on the penalty spot.
You point at the goal with the mouse.
You click. The ball flies to that spot.
Inside the posts and under the bar is a goal. Anything else is a miss.

That is a whole game. Next lesson adds power, then a keeper who fights back.

WHAT IT SHOULD LOOK LIKE

Everything today is measured on this backdrop. The ball starts on the white dash, the penalty spot.

the Soccer backdrop

2 · An aim marker on the mouse

You met this in the Shooting Game. A marker that sits on the mouse, for ever, in front of everything.

Add a small sprite for the marker. A circle with a cross is plenty. Name it Aim.
From Looks, add go to [front v] layer.
From Motion, put go to [mouse-pointer v] inside a forever.
Click the green flag and move the mouse. The marker sticks to it.


when flag clicked
set size to (70) %
go to [front v] layer
show
forever
  go to [mouse-pointer v]
end

The Aim sprite. It never does anything else.

3 · An arrow that points towards it

A kicker looks where they are aiming. Our arrow does the same job. It stays over the spot and turns to face the marker.

Add the Arrow1 sprite from the library. Name it Arrow.
Put it just above the ball: go to x: (0) y: (-85).
From Motion, drag point towards [mouse-pointer v] into a forever.
Click the flag. Circle the mouse round the goal. The arrow turns with it.


when flag clicked
go to x: (0) y: (-85)
forever
  point towards [mouse-pointer v]
end

The arrow never moves. It only turns.

WHAT IT SHOULD LOOK LIKE

The marker sits on the mouse. The arrow stays over the spot and turns to face the marker.

mouse at the left post

mouse at the right, up high

panels run left to right

Runs here in the page. Nothing to install.

How to use this: Click the green flag, then move the mouse over the goal. The marker follows it and the arrow turns to face it. Nothing to click yet.

The marker sits on the mouse. The arrow stays put and turns to face it.

Why an arrow and not the ball? A ball is round, so you cannot see it turn. point towards [mouse-pointer v] works on any sprite, but it only shows on a sprite with a front. Arrow1’s first costume points right, which is direction 90 — exactly what point towards [mouse-pointer v] expects.

4 · Two ways to hear a click

Scratch has two click hats in Events. Each click goes to only one of them.


when this sprite clicked
say [You clicked me!] for (1) seconds

On the keeper. Runs when you click the keeper.


when stage clicked
broadcast [stage clicked v]

On the Stage. Runs when you click where no sprite is.

The Stage cannot talk, so it sends a message. The keeper hears it and speaks for it:


when I receive [stage clicked v]
say [You clicked the grass.] for (1) seconds

Also on the keeper.

WHAT IT SHOULD LOOK LIKE

Clicking a sprite and clicking the Stage are two different events. Only one of them happens per click.

click the keeper

click the grass

panels run left to right

Runs here in the page. Nothing to install.

How to use this: Click the green flag. Then click the goalkeeper, and then click the grass. Each click is heard by a different script.

Click the keeper, then the grass. One click, one hat — never both.

So which one kicks the ball? Neither. A penalty is aimed at the goal — where the keeper, the marker and the net all are. Click the keeper and when stage clicked never runs. So the kick uses <mouse down?> from Sensing. It says yes whatever is under the pointer.

5 · The kick — save the mouse first

The ball waits for the mouse button. Then it saves where the mouse is, and glides there.

Make two variables, aim x and aim y, For all sprites.
On the ball, add wait until <mouse down?> inside a forever.
Then set [aim x v] to (mouse x) and set [aim y v] to (mouse y). The round reporters are in Sensing.
Then glide (0.5) secs to x: (aim x) y: (aim y).
Wait a second, and send the ball back to the spot.


when flag clicked
go to x: (0) y: (-118)
forever
  wait until <mouse down?>
  set [aim x v] to (mouse x)
  set [aim y v] to (mouse y)
  glide (0.5) secs to x: (aim x) y: (aim y)
  wait (1) seconds
  go to x: (0) y: (-118)
end

The Ball. (0, -118) is the white dash on the Soccer backdrop.

WHAT IT SHOULD LOOK LIKE

The click saves the mouse’s x and y. The ball then glides to the saved spot, even if the mouse has moved on.

the click

half a second later

panels run left to right

Runs here in the page. Nothing to install.

How to use this: Click the green flag, then point at the goal and click. The ball flies to where you clicked, waits, and comes back.

Click, then whip the mouse away. The ball still lands where you clicked.

6 · Inside the goal? Four tests

A shot is a goal when it is inside a box. The box has four edges, so there are four tests.

WHAT IT SHOULD LOOK LIKE

Four edges make the goal. A shot is in only when all four tests say yes.

the four numbers

two shots

panels run left to right

Edge	A goal must be…	The test
Left post	to the right of it	`<(aim x) > (-100)>`
Right post	to the left of it	`<(aim x) < (100)>`
Goal line	above it	`<(aim y) > (-25)>`
Bar	below it	`<(aim y) < (85)>`

All four must be true. <<> and <>> from Operators joins two answers. So we build it in two halves, then join the halves.


<<(aim x) > (-100)> and <(aim x) < (100)>>

Between the posts.


<<(aim y) > (-25)> and <(aim y) < (85)>>

Between the line and the bar.

Drag out one <<> and <>>. Put a <() > (50)> in its left side and a <() < (50)> in its right.
Drop (aim x) into both. Type -100 and 100.
Build the second half the same way with (aim y).
Drag a third <<> and <>>. Drop one half into each side.
Put the whole thing in an if / else after the glide.


if <<<(aim x) > (-100)> and <(aim x) < (100)>> and <<(aim y) > (-25)> and <(aim y) < (85)>>> then
  say [GOAL!] for (1) seconds
else
  say [Miss!] for (1) seconds
end

Three ands hold four answers. Only four yeses make a goal.

This demo takes eight shots for you at random spots. Watch the numbers, then the verdict.


when flag clicked
repeat (8)
  go to x: (0) y: (-118)
  set [aim x v] to (pick random (-180) to (180))
  set [aim y v] to (pick random (-60) to (150))
  glide (0.5) secs to x: (aim x) y: (aim y)
  if <<<(aim x) > (-100)> and <(aim x) < (100)>> and <<(aim y) > (-25)> and <(aim y) < (85)>>> then
    say [GOAL!] for (1) seconds
  else
    say [Miss!] for (1) seconds
  end
end
go to x: (0) y: (-118)

A test robot. (pick random (-180) to (180)) plays the part of your hand.

Runs here in the page. Nothing to install.

How to use this: Click the green flag and watch. Eight shots are taken for you at random spots. Nothing to press.

Eight random shots, each one judged. Read aim x and aim y, then guess before the ball says.

Basic — build the penalty 25 min

New project. Choose the Soccer backdrop. Three sprites: Ball, Arrow, Aim.

Step 1 — the ball on the spot

Add Soccer Ball from the library. Name it Ball.
Set its size to 60.
Add go to x: (0) y: (-118) under a green flag. Check it sits on the white dash.

Step 2 — the aim

Paint or pick a small marker. Name it Aim.
Build its stack from Learnt 2. Test it.

Step 3 — the arrow

Add Arrow1. Name it Arrow and set its size to 70.
Build its stack from Learnt 3. Test it.

Step 4 — two variables

Make aim x and aim y, For all sprites.
Make goals and shots too. Leave their boxes showing on the Stage.

Step 5 — the kick and the verdict

Build the Ball’s kick from Learnt 5.
Replace the wait with the if / else from Learnt 6.
Add change [shots v] by (1) after the glide, and change [goals v] by (1) inside the GOAL half.

Step 6 — reset at the flag

Click the Stage in the sprite list.
Give it when flag clicked, set [goals v] to (0) and set [shots v] to (0).

Step 7 — check against this


when flag clicked
go to x: (0) y: (-118)
forever
  wait until <mouse down?>
  set [aim x v] to (mouse x)
  set [aim y v] to (mouse y)
  glide (0.5) secs to x: (aim x) y: (aim y)
  change [shots v] by (1)
  if <<<(aim x) > (-100)> and <(aim x) < (100)>> and <<(aim y) > (-25)> and <(aim y) < (85)>>> then
    change [goals v] by (1)
    say [GOAL!] for (1) seconds
  else
    say [Miss!] for (1) seconds
  end
  go to x: (0) y: (-118)
end

The whole Ball. Thirteen blocks, one decision.

Every shot says GOAL!, even wide ones.

One of the four tests points the wrong way. Read each one aloud: “aim x is greater than minus one hundred”. The left post wants greater than; the right post wants less than.

Every shot says Miss!, even in the middle.

Check the minus signs. 100 where -100 should be makes a goal impossible. Also check you used (aim y) in the second half, not (aim x) twice.

The ball lands somewhere I did not click.

The glide is reading (mouse x) instead of (aim x). The mouse moved while you waited.

The arrow flies off with the mouse.

It has go to [mouse-pointer v] instead of point towards [mouse-pointer v]. The first moves it; the second only turns it.

Holding the button kicks again and again.

That is what the loop asks for. Add wait until <not <mouse down?>> at the end, as the Shooting Game did.

CHALLENGE 1 · L2-37-M1🪙 30 Adcoins8 min

Aim and point

A marker follows the mouse everywhere, in front of everything.
An arrow sits just above the ball.
The arrow always faces the marker.
The arrow never leaves its place.

WHAT IT SHOULD LOOK LIKE

Challenge 1 — the arrow follows the marker all the way round.

aiming high and wide

aiming low and right

panels run left to right

Done when: you draw a slow circle round the ball with the mouse and the arrow follows it all the way round.

CHALLENGE 2 · L2-37-M2🪙 50 Adcoins9 min

The kick

One click, one kick.
The ball glides from the spot to where you clicked.
It lands there even if you move the mouse straight away.
It goes back to the spot, ready for the next one.

WHAT IT SHOULD LOOK LIKE

Challenge 2 — wherever you click, the ball lands under the marker.

a kick at the right post

faded sprite = where it ends up

Done when: you take ten kicks at ten different spots, and every one lands under the marker.

Teacher note

Ask a pupil to glide to (mouse x) first and flick the mouse during the flight. The ball wanders. Then ask why saving it fixes that. The idea — keep a copy of a changing value — comes back every lesson in this arc.

CHALLENGE 3 · L2-37-M3🪙 70 Adcoins10 min

Goal or miss

Inside the posts and under the bar says GOAL!.
Wide, high or short says Miss!.
goals and shots count on the Stage, and start at 0 each flag.

WHAT IT SHOULD LOOK LIKE

Challenge 3 — just inside is a goal. Just outside is a miss.

inside the post

over the bar

panels run left to right

Done when: you take eight shots — just inside and just outside each post, the bar and the goal line — and all eight are judged right.

Teacher reveal — the four edges

The eight-shot test is the point. Most mistakes hide at one edge only, so a pupil who tests the middle three times will never find them.


<<<(aim x) > (-100)> and <(aim x) < (100)>> and <<(aim y) > (-25)> and <(aim y) < (85)>>>

The check, on its own. Any pupil whose goal box does not match the backdrop can move these four numbers — they are theirs to choose.

Runs here in the page. Nothing to install.

How to use this: Click the green flag, then point at the goal and click to shoot. Watch goals and shots count up.

Today’s game. Try the edges: just in, just out.

EXTRA MISSION · L2-37-MX🪙 100 Adcoinsbonus

Pick your corner

A shot near a post is harder to save. Make it worth more: 3 points for a corner, 1 for the middle.

WHAT IT SHOULD LOOK LIKE

Extra — a shot near a post is worth more than one down the middle.

where the points are

Runs here in the page. Nothing to install.

How to use this: Click the green flag, then click to shoot. A goal near a post scores 3 points; the middle scores 1.

Corners are worth 3, the middle 1. Where will you aim now?

Teacher reveal — one way to build it


when flag clicked
forever
  go to x: (0) y: (-118)
  wait until <mouse down?>
  set [aim x v] to (mouse x)
  set [aim y v] to (mouse y)
  glide (0.5) secs to x: (aim x) y: (aim y)
  if <<<(aim x) > (-100)> and <(aim x) < (100)>> and <<(aim y) > (-25)> and <(aim y) < (85)>>> then
    if <<(aim x) < (-70)> or <(aim x) > (70)>> then
      change [points v] by (3)
      say [Corner! +3] for (1) seconds
    else
      change [points v] by (1)
      say [Goal! +1] for (1) seconds
    end
  else
    say [Miss!] for (1) seconds
  end
end

An if inside an if. The outer one asks “goal?”, the inner one asks “which kind?”. The Stage sets points to 0 at the flag.

Summary 3 min

go to [mouse-pointer v] moves a sprite onto the mouse. point towards [mouse-pointer v] only turns it.
when this sprite clicked and when stage clicked never both run for one click.
<mouse down?> hears a click anywhere.
Save the mouse at the moment of the click. The mouse will not wait.
Four edges, four comparisons, three ands.

Aim: The spot you are pointing at. We keep it in aim x and aim y.
Comparison: A question with a yes or no answer, like “is aim x less than 100?”.
and: Says yes only when both sides say yes.
Region: An area of the Stage, like the inside of the goal.

Next lesson: a power meter. Kick it too hard and the ball sails over the bar.

Learnt27 min · the aim, the arrow, the kick, the goal
Basic25 min · build the penalty
Challenge 1–327 min · aim, kick, judge
Extrabonus · pick your corner

WHAT IT SHOULD LOOK LIKE

A new game. Point at the goal, click, and the ball flies to that exact spot. Inside the posts and under the bar is a goal.

aiming for the top corner

click

faded sprite = where it ends up · panels run left to right

Review — the Road Crossing 5 min

Every car in a lane is a clone of one sprite.
A variable made For this sprite only gives each clone its own (speed).
To ride a log, the player moves by the log’s speed while touching it.

Quick-fire

Ten clones all read (speed). They all move at the same speed. Why?

Reveal the answer

(speed) was made For all sprites. There is only one of it, so every clone reads the same number. Today’s variables are the opposite: we want one shared (aim x) that every sprite can read.

Today’s Topic 3 min

An aim marker that follows the mouse
An arrow that points towards it
Two kinds of click: on a sprite, and on the Stage
A kick that goes exactly where you clicked
Four comparisons that decide GOAL or miss

Learning outcome

By the end of this lesson you will be able to:

Make a sprite follow the mouse, and another face it.
Save the mouse’s x and y at the moment of a click.
Test whether a point is inside a box, using four comparisons and and.

Learnt — aim, kick, judge 27 min

1 · The rules, before the blocks

The ball starts on the penalty spot.
You point at the goal with the mouse.
You click. The ball flies to that spot.
Inside the posts and under the bar is a goal. Anything else is a miss.

That is a whole game. Next lesson adds power, then a keeper who fights back.

WHAT IT SHOULD LOOK LIKE

Everything today is measured on this backdrop. The ball starts on the white dash, the penalty spot.

the Soccer backdrop

2 · An aim marker on the mouse

You met this in the Shooting Game. A marker that sits on the mouse, for ever, in front of everything.

Add a small sprite for the marker. A circle with a cross is plenty. Name it Aim.
From Looks, add go to [front v] layer.
From Motion, put go to [mouse-pointer v] inside a forever.
Click the green flag and move the mouse. The marker sticks to it.


when flag clicked
set size to (70) %
go to [front v] layer
show
forever
  go to [mouse-pointer v]
end

The Aim sprite. It never does anything else.

3 · An arrow that points towards it

A kicker looks where they are aiming. Our arrow does the same job. It stays over the spot and turns to face the marker.

Add the Arrow1 sprite from the library. Name it Arrow.
Put it just above the ball: go to x: (0) y: (-85).
From Motion, drag point towards [mouse-pointer v] into a forever.
Click the flag. Circle the mouse round the goal. The arrow turns with it.


when flag clicked
go to x: (0) y: (-85)
forever
  point towards [mouse-pointer v]
end

The arrow never moves. It only turns.

WHAT IT SHOULD LOOK LIKE

The marker sits on the mouse. The arrow stays over the spot and turns to face the marker.

mouse at the left post

mouse at the right, up high

panels run left to right

Runs here in the page. Nothing to install.

How to use this: Click the green flag, then move the mouse over the goal. The marker follows it and the arrow turns to face it. Nothing to click yet.

The marker sits on the mouse. The arrow stays put and turns to face it.

4 · Two ways to hear a click

Scratch has two click hats in Events. Each click goes to only one of them.


when this sprite clicked
say [You clicked me!] for (1) seconds

On the keeper. Runs when you click the keeper.


when stage clicked
broadcast [stage clicked v]

On the Stage. Runs when you click where no sprite is.

The Stage cannot talk, so it sends a message. The keeper hears it and speaks for it:


when I receive [stage clicked v]
say [You clicked the grass.] for (1) seconds

Also on the keeper.

WHAT IT SHOULD LOOK LIKE

Clicking a sprite and clicking the Stage are two different events. Only one of them happens per click.

click the keeper

click the grass

panels run left to right

Runs here in the page. Nothing to install.

How to use this: Click the green flag. Then click the goalkeeper, and then click the grass. Each click is heard by a different script.

Click the keeper, then the grass. One click, one hat — never both.

5 · The kick — save the mouse first

The ball waits for the mouse button. Then it saves where the mouse is, and glides there.

Make two variables, aim x and aim y, For all sprites.
On the ball, add wait until <mouse down?> inside a forever.
Then set [aim x v] to (mouse x) and set [aim y v] to (mouse y). The round reporters are in Sensing.
Then glide (0.5) secs to x: (aim x) y: (aim y).
Wait a second, and send the ball back to the spot.


when flag clicked
go to x: (0) y: (-118)
forever
  wait until <mouse down?>
  set [aim x v] to (mouse x)
  set [aim y v] to (mouse y)
  glide (0.5) secs to x: (aim x) y: (aim y)
  wait (1) seconds
  go to x: (0) y: (-118)
end

The Ball. (0, -118) is the white dash on the Soccer backdrop.

WHAT IT SHOULD LOOK LIKE

The click saves the mouse’s x and y. The ball then glides to the saved spot, even if the mouse has moved on.

the click

half a second later

panels run left to right

Runs here in the page. Nothing to install.

How to use this: Click the green flag, then point at the goal and click. The ball flies to where you clicked, waits, and comes back.

Click, then whip the mouse away. The ball still lands where you clicked.

6 · Inside the goal? Four tests

A shot is a goal when it is inside a box. The box has four edges, so there are four tests.

WHAT IT SHOULD LOOK LIKE

Four edges make the goal. A shot is in only when all four tests say yes.

the four numbers

two shots

panels run left to right

Edge	A goal must be…	The test
Left post	to the right of it	`<(aim x) > (-100)>`
Right post	to the left of it	`<(aim x) < (100)>`
Goal line	above it	`<(aim y) > (-25)>`
Bar	below it	`<(aim y) < (85)>`

All four must be true. <<> and <>> from Operators joins two answers. So we build it in two halves, then join the halves.


<<(aim x) > (-100)> and <(aim x) < (100)>>

Between the posts.


<<(aim y) > (-25)> and <(aim y) < (85)>>

Between the line and the bar.

Drag out one <<> and <>>. Put a <() > (50)> in its left side and a <() < (50)> in its right.
Drop (aim x) into both. Type -100 and 100.
Build the second half the same way with (aim y).
Drag a third <<> and <>>. Drop one half into each side.
Put the whole thing in an if / else after the glide.


if <<<(aim x) > (-100)> and <(aim x) < (100)>> and <<(aim y) > (-25)> and <(aim y) < (85)>>> then
  say [GOAL!] for (1) seconds
else
  say [Miss!] for (1) seconds
end

Three ands hold four answers. Only four yeses make a goal.

This demo takes eight shots for you at random spots. Watch the numbers, then the verdict.


when flag clicked
repeat (8)
  go to x: (0) y: (-118)
  set [aim x v] to (pick random (-180) to (180))
  set [aim y v] to (pick random (-60) to (150))
  glide (0.5) secs to x: (aim x) y: (aim y)
  if <<<(aim x) > (-100)> and <(aim x) < (100)>> and <<(aim y) > (-25)> and <(aim y) < (85)>>> then
    say [GOAL!] for (1) seconds
  else
    say [Miss!] for (1) seconds
  end
end
go to x: (0) y: (-118)

A test robot. (pick random (-180) to (180)) plays the part of your hand.

Runs here in the page. Nothing to install.

How to use this: Click the green flag and watch. Eight shots are taken for you at random spots. Nothing to press.

Eight random shots, each one judged. Read aim x and aim y, then guess before the ball says.

Basic — build the penalty 25 min

New project. Choose the Soccer backdrop. Three sprites: Ball, Arrow, Aim.

Step 1 — the ball on the spot

Add Soccer Ball from the library. Name it Ball.
Set its size to 60.
Add go to x: (0) y: (-118) under a green flag. Check it sits on the white dash.

Step 2 — the aim

Paint or pick a small marker. Name it Aim.
Build its stack from Learnt 2. Test it.

Step 3 — the arrow

Add Arrow1. Name it Arrow and set its size to 70.
Build its stack from Learnt 3. Test it.

Step 4 — two variables

Make aim x and aim y, For all sprites.
Make goals and shots too. Leave their boxes showing on the Stage.

Step 5 — the kick and the verdict

Build the Ball’s kick from Learnt 5.
Replace the wait with the if / else from Learnt 6.
Add change [shots v] by (1) after the glide, and change [goals v] by (1) inside the GOAL half.

Step 6 — reset at the flag

Click the Stage in the sprite list.
Give it when flag clicked, set [goals v] to (0) and set [shots v] to (0).

Step 7 — check against this


when flag clicked
go to x: (0) y: (-118)
forever
  wait until <mouse down?>
  set [aim x v] to (mouse x)
  set [aim y v] to (mouse y)
  glide (0.5) secs to x: (aim x) y: (aim y)
  change [shots v] by (1)
  if <<<(aim x) > (-100)> and <(aim x) < (100)>> and <<(aim y) > (-25)> and <(aim y) < (85)>>> then
    change [goals v] by (1)
    say [GOAL!] for (1) seconds
  else
    say [Miss!] for (1) seconds
  end
  go to x: (0) y: (-118)
end

The whole Ball. Thirteen blocks, one decision.

Every shot says GOAL!, even wide ones.

One of the four tests points the wrong way. Read each one aloud: “aim x is greater than minus one hundred”. The left post wants greater than; the right post wants less than.

Every shot says Miss!, even in the middle.

Check the minus signs. 100 where -100 should be makes a goal impossible. Also check you used (aim y) in the second half, not (aim x) twice.

The ball lands somewhere I did not click.

The glide is reading (mouse x) instead of (aim x). The mouse moved while you waited.

The arrow flies off with the mouse.

It has go to [mouse-pointer v] instead of point towards [mouse-pointer v]. The first moves it; the second only turns it.

Holding the button kicks again and again.

That is what the loop asks for. Add wait until <not <mouse down?>> at the end, as the Shooting Game did.

CHALLENGE 1 · L2-37-M1🪙 30 Adcoins8 min

Aim and point

A marker follows the mouse everywhere, in front of everything.
An arrow sits just above the ball.
The arrow always faces the marker.
The arrow never leaves its place.

WHAT IT SHOULD LOOK LIKE

Challenge 1 — the arrow follows the marker all the way round.

aiming high and wide

aiming low and right

panels run left to right

Done when: you draw a slow circle round the ball with the mouse and the arrow follows it all the way round.

CHALLENGE 2 · L2-37-M2🪙 50 Adcoins9 min

The kick

One click, one kick.
The ball glides from the spot to where you clicked.
It lands there even if you move the mouse straight away.
It goes back to the spot, ready for the next one.

WHAT IT SHOULD LOOK LIKE

Challenge 2 — wherever you click, the ball lands under the marker.

a kick at the right post

faded sprite = where it ends up

Done when: you take ten kicks at ten different spots, and every one lands under the marker.

Teacher note

CHALLENGE 3 · L2-37-M3🪙 70 Adcoins10 min

Goal or miss

Inside the posts and under the bar says GOAL!.
Wide, high or short says Miss!.
goals and shots count on the Stage, and start at 0 each flag.

WHAT IT SHOULD LOOK LIKE

Challenge 3 — just inside is a goal. Just outside is a miss.

inside the post

over the bar

panels run left to right

Done when: you take eight shots — just inside and just outside each post, the bar and the goal line — and all eight are judged right.

Teacher reveal — the four edges

The eight-shot test is the point. Most mistakes hide at one edge only, so a pupil who tests the middle three times will never find them.


<<<(aim x) > (-100)> and <(aim x) < (100)>> and <<(aim y) > (-25)> and <(aim y) < (85)>>>

The check, on its own. Any pupil whose goal box does not match the backdrop can move these four numbers — they are theirs to choose.

Runs here in the page. Nothing to install.

How to use this: Click the green flag, then point at the goal and click to shoot. Watch goals and shots count up.

Today’s game. Try the edges: just in, just out.

EXTRA MISSION · L2-37-MX🪙 100 Adcoinsbonus

Pick your corner

A shot near a post is harder to save. Make it worth more: 3 points for a corner, 1 for the middle.

WHAT IT SHOULD LOOK LIKE

Extra — a shot near a post is worth more than one down the middle.

where the points are

Runs here in the page. Nothing to install.

How to use this: Click the green flag, then click to shoot. A goal near a post scores 3 points; the middle scores 1.

Corners are worth 3, the middle 1. Where will you aim now?

Teacher reveal — one way to build it


when flag clicked
forever
  go to x: (0) y: (-118)
  wait until <mouse down?>
  set [aim x v] to (mouse x)
  set [aim y v] to (mouse y)
  glide (0.5) secs to x: (aim x) y: (aim y)
  if <<<(aim x) > (-100)> and <(aim x) < (100)>> and <<(aim y) > (-25)> and <(aim y) < (85)>>> then
    if <<(aim x) < (-70)> or <(aim x) > (70)>> then
      change [points v] by (3)
      say [Corner! +3] for (1) seconds
    else
      change [points v] by (1)
      say [Goal! +1] for (1) seconds
    end
  else
    say [Miss!] for (1) seconds
  end
end

An if inside an if. The outer one asks “goal?”, the inner one asks “which kind?”. The Stage sets points to 0 at the flag.

Summary 3 min

go to [mouse-pointer v] moves a sprite onto the mouse. point towards [mouse-pointer v] only turns it.
when this sprite clicked and when stage clicked never both run for one click.
<mouse down?> hears a click anywhere.
Save the mouse at the moment of the click. The mouse will not wait.
Four edges, four comparisons, three ands.

Aim: The spot you are pointing at. We keep it in aim x and aim y.
Comparison: A question with a yes or no answer, like “is aim x less than 100?”.
and: Says yes only when both sides say yes.
Region: An area of the Stage, like the inside of the goal.

Next lesson: a power meter. Kick it too hard and the ball sails over the bar.