HTML-Fan wrote:

DarthVader4Life wrote:

now that's CoRrect.

Whatever the typos should mean.

cooldude-222 wrote:

DarthVader4Life wrote:

cooldude-222 wrote:

DarthVader4Life wrote:

I'm getting real sick and tired of people saying “No support, there's a workaround.” Very rarely does a block get removed because of a workaround. so rare in fact, that the only instance of a block getting removed because of a workaround that i am 100% sure happened is the forever if block. even then the extremely simple workaround wasn't the only factor, apparently users didn't understand it either. and because a block has a workaround DOESN'T mean it shouldn't be added. so if you could kindly read this, that'd be great.

You are so right there are so many blocks already in scratch that have workarounds but still make scratch easier an example is if else.

here's some more examples.

change x by ()
change y by ()
next costume
next backdrop
when [ v] key pressed
forever

end
wait until <>
(() - (0))
change [ v] by (0)

Don’t forget

 
If on edge bounce :: motion

cooldude-222 wrote:

Don’t forget

 
If on edge bounce :: motion

HTML-Fan wrote:

cooldude-222 wrote:

Don’t forget

 
If on edge bounce :: motion

That's more complicated, more then just adding var + for change var by.

cooldude-222 wrote:

HTML-Fan wrote:

cooldude-222 wrote:

Don’t forget

 
If on edge bounce :: motion

That's more complicated, more then just adding var + for change var by.

All you need is an if statement

HTML-Fan wrote:

cooldude-222 wrote:

HTML-Fan wrote:

cooldude-222 wrote:

Don’t forget

 
If on edge bounce :: motion

That's more complicated, more then just adding var + for change var by.

All you need is an if statement

Two to be more precise. And some math. Maybe you haven't noticed, but that block does more then going to the opposite direction. It mirrors one axis. Anyway, kinda off-topic.

stop [this script v]

dimayajonelcid wrote:

I don't really post in the forums, but hey, first post?

Anyway, I would like to support this because this is a very great idea about running 2 lines of code at once in just one script. It would make projects simpler, and the BEST part about it? I could really use the shown block in my projects:

stop [this script v]

It is near impossible to stop a single script while in a scenario like the block (wait (5) seconds) without this block.

So, yeah. this would really make things simpler in scratch projects, especially when using “stop this script.”

dimayajonelcid wrote:

I don't really post in the forums, but hey, first post?

Anyway, I would like to support this because this is a very great idea about running 2 lines of code at once in just one script. It would make projects simpler, and the BEST part about it? I could really use the shown block in my projects:

stop [this script v]

It is near impossible to stop a single script while in a scenario like the block (wait (5) seconds) without this block.

So, yeah. this would really make things simpler in scratch projects, especially when using “stop this script.”

set [stopScript v] to [false] // when you want to start the script
broadcast [example v]
...
set [stopScript v] to [true] // when you want to stop the script
broadcast [example v]

when I receive [example v]
if <(stopScript) = [false]> then
script contents :: grey stack
end

when green flag clicked
set [my energy units] to [0]
do two things at once
set [my energy units] to [1000]
and
if <[my energy units] = [1000]> then
say [Lorem] for (1) secs
end
end

define run while running
...
...

while <> {
}::control

when green flag clicked
broadcast [Script1 v]
broadcast [Script2 v]

when I receive [Script1 v]
...

when i receive [Script2 v]
...

LankyBox01 wrote:

when green flag clicked
broadcast [Script1 v]
broadcast [Script2 v]

when I receive [Script1 v]
...

when i receive [Script2 v]
...

LankyBox01 wrote:

when green flag clicked
broadcast [Script1 v]
broadcast [Script2 v]

when I receive [Script1 v]
...

when i receive [Script2 v]
...

ZaqGames wrote:

Actually, running 2 things at once is near impossible or you will run in a problem like

when green flag clicked
set [my energy units] to [0]
do two things at once
set [my energy units] to [1000]
and
if <[my energy units] = [1000]> then
say [Lorem] for (1) secs
end
end

But will it say “Lorem” or it won't?

scratch978654 wrote:

Actually you can still use broadcasts in CBs.

• “when I receive” blocks have to be outside the custom block;
  
• if it's run without screen refresh, broadcasts will run after the block returns.