I like custom blocks and can find a way to put them in my backpack which I wish you can just put the scripts in there alone (I would link my suggestion about it but it doesn’t exist yet) but I walkways see “run without screen refresh” and can’t figure out what it could do. Can someone help me out?

It makes the scripts inside the custom block run instantly. It does cause a lot of lag when you use blocks with a delay, though.

Technically, turbo mode for a custom block.

ScratchCat1038 wrote:

It makes the scripts inside the custom block run instantly. It does cause a lot of lag when you use blocks with a delay, though.

So is it Turbo mode but with the block?

Scratchfangs wrote:

Technically, turbo mode for a custom block.

Ok, I guess I’m done here

Screen refreshes refer to when the screen needs to be redrawn. Scratch aims to refresh the screen approximately 30 times per second (30 FPS).
Some blocks force Scratch to wait until the screen is refreshed before continuing. For example, loops. At the end of each loop cycle, the loop will wait for the screen to get refreshed before running again. By running without a screen refresh, you can make scripts run way faster as they are not limited by these delays. They basically run as fast as possible within the time allocated to running scripts.

Scratchfangs wrote:

Technically, turbo mode for a custom block.

No it's not. Turbo mode runs a loop as fast as it can while constantly refreshing the screen after each loop, while a custom block with ‘run without screen refresh’ enabled will run all the code attached to it then refresh the screen.

It does everything at once, for example,

define move (x)
move (x) steps
move (x) steps

will move ((x)*2) steps; not x and then another x.
It's the same as

move ((x::custom) * (2)) steps

han614698 wrote:

It does everything at once, for example,
snip
will move ((x)*2) steps; not x and then another x.
It's the same as
snip
[Original post]

I think move blocks run instantly and don't wait between them.
This may be a better example:

define move (x)
repeat (10)
 move (x) steps
end

In a RwSR block, it will function like

move ((x :: custom-arg) * (10)) steps

But in a normal custom block, it will refresh and wait 1 frame each time it moves once.

Basically it will just do anything that is attached to the define block straight away and eat your cookies

Run without screen refresh will freeze the screen (as long as it can) until the script in it finishes.

when green flag clicked
repeat (30)
move (1) steps
end

The above script will make the sprite move one step, and then wait 0.33333333… seconds to refresh the screen so that you can see it move, it repeats it 30 times.

define run without screen refresh block
repeat (30)
move (1) steps
end

The above script will freeze the screen, then move 30 steps, then show the screen, so it basically functions like

move ((1) * (30)) steps

uhh whats going on here?

Trollers_sword wrote:

uhh whats going on here?

Don’t necropost, and see Single Frame if you are confused

medians wrote:

Trollers_sword wrote:

uhh whats going on here?

Don’t necropost, and see Single Frame if you are confused

i still dont understand

Trollers_sword wrote:

medians wrote:

Trollers_sword wrote:

uhh whats going on here?

Don’t necropost, and see Single Frame if you are confused

i still dont understand

Okay, can you elaborate on which part is confusing in a new topic?
Basically, it will try running in a single frame.