Revival of this topic which was closed by the OP. I am recreating the topic and taking responsibility over the suggestion again, just as I did before my other Run Green Flag topic was merged with the closed topic I linked.

This is inspired by Scratch 0.x (because the green flag didn't exist, and you had two wave blocks instead) and a Scratch mod related to a species of flightless birds.

click @greenFlag :: control

This block basically emulates clicking the green flag. E.g.

when [space v] key pressed
click @greenFlag :: control

when green flag clicked
turn cw (22.5) degrees

It could be used for restarting if the player makes a mistake.

Other versions:

click @greenFlag :: sensing // Sensing category

click @greenFlag :: control cap // Cap

run @greenFlag :: control // Alternative name

Mockups in 3.0, made here by han614698: Note this still uses the color from Events


In my original topic about this (which was merged with the one that got closed,) the block used to be in Events. However, the stop all block is in Control, and the run green flag block in the penguin version of Scratch is also in Control, so it makes more sense to have this block in control.

when green flag clicked
run @greenFlag :: events

sgary

TheEpikGamer211 wrote:

when green flag clicked
run @greenFlag :: events

sgary

can you explain please?

A-MARIO-PLAYER wrote:

can you explain please?

I thinke that would crash scartch

TheEpikGamer211 wrote:

I thinke that would crash scartch

it wouldnt

if you run that script in the penguin version of scratch, it just acts like putting a forever block with nothing inside under a when gf clicked block.

tldr:

when gf clicked
run @greenFlag :: control

=

when gf clicked
forever

why can't you use broadcasts

Banana

What would happen if somebody did this?

when green flag clicked
forever
click @greenFlag ::control
end

for your example couldnt you just do:

when [space v] key pressed
turn ccw (22.5) degrees

when green flag clicked
turn ccw (22.5) degrees

(maybe this isnt a good solution in all cases, but I'm no coding pro lol :p)

-Rodri wrote:

for your example couldnt you just do:

when [space v] key pressed
turn ccw (22.5) degrees

when green flag clicked
turn ccw (22.5) degrees

What if you had much more scripts there? Waste of valuable project.json storage.

Edit spy

maybe make it so int only works every 10 seconds? that would fix some problems I thought it might have.

So, like this?

broadcast [Scratch-StartClicked v] and wait // This would restart the project from the green flag in Scratch 1.4.

TheCreatorOfUnTV wrote:

So, like this?

broadcast [Scratch-StartClicked v] and wait // This would restart the project from the green flag in Scratch 1.4.

yeah
but you can't do that in scratch 3.0 anymore bruh

A-MARIO-PLAYER wrote:

TheCreatorOfUnTV wrote:

So, like this?

broadcast [Scratch-StartClicked v] and wait // This would restart the project from the green flag in Scratch 1.4.

yeah
but you can't do that in scratch 3.0 anymore

I know - I never suggested it as a workaround.

banana439monkey wrote:

why can't you use broadcasts

Banana

Expanding on this: when you code a project and you use the “when green flag clicked” block, replace it with this block:

when I receive [green flag v]

Then, never use the “when green flag clicked” block, except for one single time where you include this script somewhere:

when green flag clicked
broadcast [green flag v]

Now, whenever you want to use your proposed block, just use "broadcast [green flag v]" instead. This workaround is pretty useful and easy to make.

bump
(i swear i need to create a cubeupload account and make myself a personal bump image)

DangerPuppy10 wrote:

What would happen if somebody did this?

when green flag clicked
forever
click @greenFlag ::control
end

That would effectively be the same as

when green flag clicked
click @greenFlag ::control

because when the green flag is clicked, any previous running code is stopped