Re-implement warp speed block [run without screen refresh]

TheCreatorOfUnTV

Here is a better name for it:

run instantly{

} :: control

medians

Bringing this topic up.

8to16

block mockups:

warp {

} :: grey

warp {

} :: control

warp speed {

} :: control

all at once {

} :: control

instantly {

} :: control

run without screen refresh {

} :: control

medians

medians
Bringing this topic up.

redspacecat

medians wrote:
medians
Bringing this topic up.

I didn't realize I was following this topic

medians

medians
Bringing this topic up.

medians

medians
Bringing this topic up.

medians

medians
Bringing this topic up.

Scyth3d

Full support. It’s annoying to have so many blocks. And I’m too lazy to name them so it ends up being

No refresh
No refresh1
E
Eee
Eeeeeee
Eeeeeeee
Kjfsdjkhgf
Jhwdqjhkgqhjg

Last edited by Scyth3d (May 2, 2025 14:36:11)

lfg30700

Support. This prevents like a million custom blocks from having to exist because I need to do things faster Ohviously I'm going to still use custom blocks but if it's a thing that only needs to run once in the project why use up YET ANOTHER custom block? Definitely could be useful.
That can prevent this:

instantcreate1::custom
instantdestroy3::custom
instantskip2::custom
...//etc

medians

medians
Bringing this topic up.

medians

medians
Bringing this topic up.

medians

qwertycodechamp90411
Hmmm, maybe an option to ‘run at warp speed’ in the right-click menu?

Support

I think that might make it difficult to tell which part is ran at warp speed/run without screen refresh

Thethree13

bump + support. this one seems like a no-brainer. would look like:

all at once {
code::grey
}::control

or

run without screen refresh {
code::grey
}::control

suswhopper123

Thethree13 wrote:
bump + support. this one seems like a no-brainer. would look like:
all at once {
code::grey
}::control
or
run without screen refresh {
code::grey
}::control

I believe that

all at once {

}::control

is *maybe, haven`t checked* a hacked block.

Thethree13

suswhopper123 wrote:
Thethree13 wrote:
-snip-
I believe that
all at once {

}::control
is *maybe, haven`t checked* a hacked block.

It is a hacked block, however it is non-functional. This topic (and others) are trying to make the block work again, and add it back to the pallete.

suswhopper123

Thethree13 wrote:
suswhopper123 wrote:
Thethree13 wrote:
-snip-
I believe that
all at once {

}::control
is *maybe, haven`t checked* a hacked block.
It is a hacked block, however it is non-functional. This topic (and others) are trying to make the block work again, and add it back to the pallete.

Oh! Then support. It would make scripts less bad-looking. But when the update will be implemented, where would it be? Below the control pallete so you`ll have to scroll for it, or visible almost instantly?

Thethree13

suswhopper123 wrote:
Thethree13 wrote:
It is a hacked block, however it is non-functional. This topic (and others) are trying to make the block work again, and add it back to the pallete.
Oh! Then support. It would make scripts less bad-looking. But when the update will be implemented, where would it be? Below the control pallete so you`ll have to scroll for it, or visible almost instantly?

Are you asking where in the block pallete it would be?

In it's current state it's a control block, so I would guess it would be maybe before/after the forever loop? since those blocks are similar to it (non conditional c blocks)

suswhopper123

Thethree13 wrote:
-snip-

OK! Also, is there a way to convince ST to add a suggestion to Scratch other than Contact Us?

Thethree13

suswhopper123 wrote:
Thethree13 wrote:
-snip-
OK! Also, is there a way to convince ST to add a suggestion to Scratch other than Contact Us?

You're in the forum for it right now. That's all the options at one's disposal, unfortunately.

Discuss Scratch