The Forever If Block

If you don't know what it is, let me explain. The Forever If block was a block that looked something like this

forever if <>::control

end

That used to exist in 1.4 Scratch. It was removed in 2.0 because it had a very easy workaround:

forever
if <> then

end
end

This is a Scratch 1.4 editor, you can see the Forever If there
And what i suggest is: bring it back! I know it has a very easy workaround, but Scratch is a programming language that even people with no experience can learn. It would be useful for New Scratchers who have no experience. And, sorry, i HAVE to say this: that is one of the cutest blocks i've ever seen. Sorry, i simply had to say that.
But for a New Scratcher that block could be useful, because they can reason like this “When i start, do this forever but ONLY if …”
So they'd like to do something like

when green flag clicked
forever if <...>::control
...
end

but they have to figure out that block thing. Maybe make a video tutorial that explains that those blocks are the same, because all New Scratchers reason differently. Some reason like “When i start, if … then …” so they are fine with the current blocks, but, as i said above, some reason like “When i start, do this forever but ONLY if …” It's the same but people reason differently. I hope you bring the forever if back! (thanks @Spaceflyer234 for teaching me how to make them yellow)

Spaceflyer234 wrote:

Support this would be helpful for new scratchers.
Also add “::control” after the scratch blocks so it isn't red like this:

forever if <> ::control

end

Thanks (lop we decided to make this) and finally they're yellow!

WindOctahedron wrote:

You can make a block look as if it belongs to a certain category like this:

blocka blocka :: control

becomes:

blocka blocka :: control

Spaceflyer told it before you so someone's been Ninja'd

I don't support. Even as a New Scratcher, you should still know what “forever” means and “if _____ then” means. Combining them together is simple.

Scratch removed it during Scratch 2.0 because of how easy the workaround was. When Scratch rejects something, it's usually not going to come back. The

forever if <> ::control

end

has an extremely easy workaround, as you have stated:

forever
if <> then

end
end

You said New Scratchers won't know this. Most New Scratchers don't have any experience at all with programming. Once they get started using the blocks, they'll figure it out after a short period of time.

Super_Scratch_Bros20 wrote:

I don't support. Even as a New Scratcher, you should still know what “forever” means and “if _____ then” means. Combining them together is simple.

Scratch removed it during Scratch 2.0 because of how easy the workaround was. When Scratch rejects something, it's usually not going to come back. The

forever if <> ::control

end

has an extremely easy workaround, as you have stated:

forever
if <> then

end
end

You said New Scratchers won't know this. Most New Scratchers don't have any experience at all with programming. Once they get started using the blocks, they'll figure it out after a short period of time.

I know, but i think that some users find it more comfortable because they reason as i stated in the OP

Col_Cat228 wrote:

Super_Scratch_Bros20 wrote:

-snip-

I know, but i think that some users find it more comfortable because they reason as i stated in the OP

We know that all people think differently, but some ways of thinking are more common than others. Wait, Scratch is for everyone…
And honestly, I've never seen anyone having problems with figuring it out.

It would be more efficient for large projects, because it is less blocks, but again, simple workaround. I am pretty impartial on this

WindOctahedron wrote:

Col_Cat228 wrote:

Super_Scratch_Bros20 wrote:

-snip-

I know, but i think that some users find it more comfortable because they reason as i stated in the OP

We know that all people think differently, but some ways of thinking are more common than others. Wait, Scratch is for everyone…
And honestly, I've never seen anyone having problems with figuring it out.

Some people just reason differently i reason with the Forever If block. People don't actually have problems, but some are just more comfortable with the

forever if <>::control

end

PizzaAddict4Life wrote:

It would be more efficient for large projects, because it is less blocks, but again, simple workaround. I am pretty impartial on this

This Scratcher just gave another reason to support this suggestion

Col_Cat228 wrote:

PizzaAddict4Life wrote:

It would be more efficient for large projects, because it is less blocks, but again, simple workaround. I am pretty impartial on this

This Scratcher just gave another reason to support this suggestion

But is it a pain to drag a block into another block?

forever
if <> then

end
end

Still no support.

Col_Cat228 wrote:

PizzaAddict4Life wrote:

It would be more efficient for large projects, because it is less blocks, but again, simple workaround. I am pretty impartial on this

This Scratcher just gave another reason to support this suggestion

Doesn't change the fact that I am impartial about it.

I am fine if it is added, and I am fine if it is not

Here's what @Za-Chary* has previously said about this:

Za-Chary wrote:

This block used to exist in Scratch 1.4, but was removed because the workaround was so easy:

forever
if <> then

end
end

I would say that this block is not coming back.

(Source)

(Deleted by BlueNoodle29)
Reason: people saying it was not constructive even after I edited it to explain why

No support, I joined Scratch recently and I already found out what the forever and if then blocks were, this wouldn't be useful.

Actually, it wasn't removed because it had an easy workaround. 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.