set [time executed] to (timer)
set [execute time] to [number in seconds]
repeat until <(timer) = ((time executed) + (execute time))>
...
end

kennaminecraftz wrote:

(#182)
If you dont want to reset timer you could do this instead:

set [time executed] to (timer)
set [execute time] to [number in seconds]
repeat until <(timer) = ((time executed) + (execute time))>
...
end

kennaminecraftz wrote:

(#182)
If you dont want to reset timer you could do this instead:
✂

set [time executed] to (timer)
set [execute time] to [number in seconds]
repeat until <not <(timer) < ((time executed) + (execute time))>>
. . .
end

when green flag clicked
wait (foo) secs
set [Temp v] to [1]

when green flag clicked
set [Temp v] to [0]
repeat until <(Temp) = [1]>
...
end

VoltageGames wrote:

No support.
If I have a script like
repeat for 10 seconds,
with a wait 11 seconds in it, what happens?

If I have a script like wait 10 seconds
with blocks inside of it,
what happens when the 10 seconds are up and it's in the middle of the scripts?
Will the rest of the scripts inside continue even though the 10 secs are up? Or will they stop and skip ahead of the repeat?

VoltageGames wrote:

No support.
If I have a script like
repeat for 10 seconds,
with a wait 11 seconds in it, what happens?

VoltageGames wrote:

If I have a script like wait 10 seconds
with blocks inside of it,
what happens when the 10 seconds are up and it's in the middle of the scripts?
Will the rest of the scripts inside continue even though the 10 secs are up? Or will they stop and skip ahead of the repeat?

set [timer v] to (x)
broadcast (start timer v)
repeat until <(timer :: variables) = (0)>
…
end

when I receive [start timer v]
repeat until <(timer :: variables) = (0)>
change [timer v] by (-1)
wait (1) secs
end

Unithlees3 wrote:

This is literally how easy the workaround is:

set [timer v] to (x)
broadcast (start timer v)
repeat until <(timer :: variables) = (0)>
…
end

when I receive [start timer v]
repeat until <(timer :: variables) = (0)>
change [timer v] by (-1)
wait (1) secs
end

This is very easy to do; therefore using a block for it is unnecessary.

Edit: I've just realised I've done a post about a different workaround like a year ago. But it really doesn't matter. This one doesn't use the timer.

SavetheAtlantic wrote:

Little_Mittle12345 wrote:

Stop No support easy workaround. its a HARD WORKAROUND. forever block has a workaround. Can you remove it? or many blocks?

It's nothing. And just because some blocks have an easy workaround doesn't mean that we should remove them, or that we should add more blocks with easy workarounds. With that justification, you could suggest ridiculous blocks like these:

play sound [ v] and then go to x: () y: () ::sound
broadcast [ v] until [var v] = () ::events

You get the point.

play sound [ v]

go to x: () y: (0)

thunderclwd wrote:

-snip-
While you are correct that that would work as a workaround it is counter-intuitive and making this block would help make it simple for new scratchers, as well as decreasing the amount of blocks and therefore the lag (Slightly, not by much, but slightly). Also, I'd like to point out that you'd need o make a new variable for each script you're running simultaneously.
Therefore, for all these reasons, I think that this block should be in scratch.

…
set [script id v] to (y)
repeat (script id)
wait (0) secs // Optional – for better manipulation of timer adding
end
add (x) to [timers v]
repeat until <(item (script id) of [timers v] :: list) = (0)> // "script id" referring to the id of the script. Set it to the placement of the timer of the list
if <(x) = (item (script id) of [timers v])> then
broadcast (timer v)
end
…
end
replace item (script id) of [timers v] with () // Or just delete the item entirely if this is the only script utilising this
when I receive [timer v]
repeat until <(x) = (0)>
wait (1) secs
change [x v] by (-1)

repeat (12)
...
wait (1) secs
end

TheEpikGamer211 wrote:

(#194)
workaround.

repeat (12)
...
wait (1) secs
end