forever if <>

end

awecool wrote:

forever if <>

end

This is a simple concept. It would forever check something. I know there are simple workarounds, but I feel this would be really useful and cause a little less lag.

forever
if <> then

end
end

DominoDragon1 wrote:

awecool wrote:

forever if <>

end

This is a simple concept. It would forever check something. I know there are simple workarounds, but I feel this would be really useful and cause a little less lag.

1) already suggested
2) use this:

forever
if <> then

end
end

Having your block would take away basically no lag.

I can see how this might make it easier for new scratchers though…

Just do this:

forever
if <> then
...
end
end

The block had an advantage, though: it runs some milliseconds faster than its replication, so it could be used to combat extreme lag.

Despite the simple workaround, multiple users have suggested the block be brought back, because it seems more natural to use for those newer to programming.

Paddle2See wrote:

It was removed because many beginning Scratchers found it overly confusing. Showing the two functions that it performs as separate blocks seems to be easier for beginners to understand.

So, sorry, I don't think we are interested in seeing it come back at this time.