"Run, and run" E block (READ THE ENTIRE OP BEFORE POSTING)

fdreerf

gosoccerboy5 wrote:
Which one of the scripts will end the E block and continue the next script if it ends? How about, if one script ends, both end?

I think it should wait until both scripts are finished, as your suggestion will more or less make the block much more difficult to use.

Last edited by fdreerf (Dec. 15, 2020 17:23:42)

gosoccerboy5

fdreerf wrote:
gosoccerboy5 wrote:
Which one of the scripts will end the E block and continue the next script if it ends? How about, if one script ends, both end?
I think it should wait until both scripts are finished, as your suggestion will more or less make the block much more difficult to use.

Actually, that makes a looooottttt more sense, thanks for clearing that up.

portalpower

ok_ohheck wrote:
no support. easy workaround:
when green flag clicked
forever
move (10) steps
wait (0.5) secs
next costume
end

the title wrote:
(FOR THE LOVE OF ALL THAT IS GOOD READ THE ENTIRE OP. I ASKED NICELY BEFORE BUT PEOPLE DON'T SEEM TO CARE. Bruh.)

MeIzAwezomeDede

ok_ohheck wrote:
no support. easy workaround:
when green flag clicked
forever
move (10) steps
wait (0.5) secs
next costume
end

Wh… Those are just random blocks how is that a workaround

Also read the op jeez

xXRedTheCoderXx

gosoccerboy5 wrote:
Which one of the scripts will end the E block and continue the next script if it ends? How about, if one script ends, both end?

xXRedTheCoderXx wrote:
Yes, you could put code underneath this block, unlike the forever block. Code stacked underneath this block will run when all code is done running in the run, while running bock(s). So, if you put a forever loop in one of the branches of this block, code underneath it will never run.

Please read the entire OP.

lovecodeabc

What if

do {
...
stop [this script v]
}while doing{
... 
}

Is the script below stopped by the above?

xXRedTheCoderXx

lovecodeabc wrote:
What if
do {
...
stop [this script v]
}while doing{
... 
}
Is the script below stopped by the above?

Finally! A question that hasn't been answered yet and that adds to the discussion!

(No offense

)

Anyway… I'll gladly answer this question.

No, the only thing that's stopped is the code in the same branch as the “stop this script” block, as the other branches are essentially their own scripts. That means the other branches will be unaffected, along with any additional code that was placed under the “run, and run” E block.

mybearworld

lovecodeabc wrote:
What if
do {
...
stop [this script v]
}while doing{
... 
}
Is the script below stopped by the above?

This makes me think about

do {
omg hahaaha :: #ff6680
} while doing {
omg hahaaha :: #ff6680
} :: #ffab19

definе {omg hahaaha :: #FF4D6A stack} :: #ff6680 hat // run without screen refresh
forever {
omg hahaaha :: #ff6680
} :: #ffab19

xXRedTheCoderXx

mybearworld wrote:

This makes me think about

do {
omg hahaaha :: #ff6680
} while doing {
omg hahaaha :: #ff6680
} :: #ffab19

definе {omg hahaaha :: #FF4D6A stack} :: #ff6680 hat // run without screen refresh
forever {
omg hahaaha :: #ff6680
} :: #ffab19

There are already many ways to crash Scratch, using similar methods to that, but either way it's against the ToS.

gosoccerboy5

xXRedTheCoderXx wrote:
gosoccerboy5 wrote:
Which one of the scripts will end the E block and continue the next script if it ends? How about, if one script ends, both end?
xXRedTheCoderXx wrote:
Yes, you could put code underneath this block, unlike the forever block. Code stacked underneath this block will run when all code is done running in the run, while running bock(s). So, if you put a forever loop in one of the branches of this block, code underneath it will never run.
Please read the entire OP.

Oh, ok (insert embarrassed face here)
fdreerf helped me on that one

Futurebot5

Support! I was just trying to make a workaround for another block (Repeat for () seconds) then realized that it couldn't be in a custom block because I had to have a timer running at the same time.

NanoPIex

Support! This would be useful!

gosoccerboy5

NanoPIex wrote:
Support! This would be useful!

wait why

NanoPIex

gosoccerboy5 wrote:
NanoPIex wrote:
Support! This would be useful!
wait why

Oops! Well, this would really help with clones! (Sorry, I was really in a hurry)

cheatcodeman

This would be useful with the music extension. Support.

NanoPIex

Bump!
r
i
n
g

u
p

MeIzAwezomeDede

NanoPIex wrote:
Support! This would be useful!

Literally a few pages ago you were spamming about "no support because *insert workaround that doesn't even work*" multiple times but ok i guess

lovecodeabc

Also, is the below a workaround?

define yeah i think this is a block (a parameter)
broadcast [1 v]
broadcast [2 v]
...
when gf clicked
set [2? v] to [false]
yeah i think this is a block (a value)

when I receive [2 v]
set [2? v] to [true]

when I receive [1 v]
wait until <(2?) = [true]>
move (a parameter) steps
...

Last edited by lovecodeabc (Dec. 17, 2020 01:11:45)

gosoccerboy5

But the E block proposed will continue once both scripts are done, whereas this one will continue immediately (I think???)

Leekalo

Support! This will allow scripts with waiting to all be placed in one giant script!

Discuss Scratch