A new type of custom block (:

unisparks8

(I checked T7SD and this is not there, so I'ma assume this is not a dupe)
Currently, we have the option of 2 different types of Custom Blocks

(Sorry for large image)
Normal, and run without screen refresh. Normal…

when green flag clicked
WOW
This continues after WOW is done, in other words, one second.::grey
define WOW
Wait (1) seconds

Then “Run without screen refresh”

when green flag clicked
RWSR
define RWSR//This would do all of it instantly. It would change five costumes at once.
repeat (5) times{
next costume
} @loopArrow::control

I want a new type: one that continues the script after being used.

when green flag clicked
Wh4t3v37
switch costume to (costume v) //The costume would still switch without waiting one second.
define Wh4t3v37
Wait (1) seconds

This would make it where we don't need to have unnecessary broadcasts to do stuff.

Last edited by unisparks8 (March 31, 2026 17:40:22)

ScodexPerson

Workaround:

when green flag clicked
broadcast (define v)
...
when I receive [define v]
custom block :: custom
define custom block
...

Last edited by ScodexPerson (March 30, 2026 13:08:09)

unisparks8

ScodexPerson wrote:

Workaround:

when green flag clicked
broadcast (define v)
...
when I receive [define v]
custom block :: custom

…Everything has a workaround.

ScodexPerson

unisparks8 wrote:
ScodexPerson wrote:
Workaround:
when green flag clicked
broadcast (define v)
...
when I receive [define v]
custom block :: custom
…Everything has a workaround.

Yeah, but that one is very easy.

TutorKing

unisparks8 wrote:
ScodexPerson wrote:
Workaround:
when green flag clicked
broadcast (define v)
...
when I receive [define v]
custom block :: custom
…Everything has a workaround.

That's a way to prove that anything can be done in Scratch!

r3hehehehehhe

TutorKing wrote:
unisparks8 wrote:
ScodexPerson wrote:
Workaround:
when green flag clicked
broadcast (define v)
...
when I receive [define v]
custom block :: custom
…Everything has a workaround.
That's a way to prove that anything can be done in Scratch!

i can't eat in scratch, what do you mean

Haycat2009

The workaround is good, but leads to spaghetti code in the long term. Given how Scratch emphasises how simple it is, this will be suitable.

Blobfish_Industries

Semi-support! Also, what would you call the feature? All the names that come to mind seem a tad too advanced for eight year olds.

unisparks8

Blobfish_Industries wrote:
Semi-support! Also, what would you call the feature? All the names that come to mind seem a tad too advanced for eight year olds.

“Continue script” wouldn't be too confusing for an 8 year old.

HAL95131

ScodexPerson wrote:

Workaround:

when green flag clicked
broadcast (define v)
...
when I receive [define v]
custom block :: custom
define custom block
...

It would be better practice to be able to directly call a function in parallel instead of this extra layer. The workaround was obvious and didn't need to be stated.

unisparks8

HAL95131 wrote:
ScodexPerson wrote:
Workaround:
Snip
It would be better practice to be able to directly call a function in parallel instead of this extra layer. The workaround was obvious and didn't need to be stated.

I already stated there is a workaround…

HAL95131

unisparks8 wrote:
HAL95131 wrote:
ScodexPerson wrote:
Workaround:
Snip
It would be better practice to be able to directly call a function in parallel instead of this extra layer. The workaround was obvious and didn't need to be stated.
I already stated there is a workaround…

Yes? That's what I'm saying. The workaround is annoying.
Unless you're saying that because I didn't snip the person who posted it T_T

Last edited by HAL95131 (March 31, 2026 17:41:24)

unisparks8

HAL95131 wrote:
unisparks8 wrote:
HAL95131 wrote:
ScodexPerson wrote:
Workaround:
Snip
It would be better practice to be able to directly call a function in parallel instead of this extra layer. The workaround was obvious and didn't need to be stated.
I already stated there is a workaround…
Yes? That's what I'm saying. The workaround is annoying.
Unless you're saying that because I didn't snip the person who posted it T_T

The word around is annoying, 101% agree. Its so much easier to just make a custom block, it gives you a lot of broadcasts to scroll thru to get it. Its just so much easier if this was added to sustom blocks.

Rosics

ScodexPerson wrote:

Workaround:

when green flag clicked
broadcast (define v)
...
when I receive [define v]
custom block :: custom
define custom block
...

Workaround for:

go to x: (0) y: (0)

Here:

set x to (0)
set y to (0)

medians

Rosics wrote:
Workaround for:
go to x: (0) y: (0)
Here:
set x to (0)
set y to (0)

what if the pen is down XD

TimothyLawyer

That would be confusing because even though the blocks are sequentially connected they don't execute sequentially. The workaround is the correct way to do this.

unisparks8

Bump

unisparks8

unisparks8 wrote:
Bump

Whatdidyousay245

TutorKing wrote:
unisparks8 wrote:
ScodexPerson wrote:
Workaround:
when green flag clicked
broadcast (define v)
...
when I receive [define v]
custom block :: custom
…Everything has a workaround.
That's a way to prove that anything can be done in Scratch!

datastores

Last edited by Whatdidyousay245 (April 17, 2026 14:10:54)

Discuss Scratch