I think that there should be a block that deletes all clones for a certain sprite. I think this would be useful because in my new project, Splash OS 4 which is unshared, I need a way do delete all clones at once and there is no real way to do it from within the one script for the clone.

delete all clones on [this sprite v]

What do you think?

This would be helpful for some new scratchers.

But in the meantime, you could have a different broadcast channel for each sprite, for instance:

broadcast [Delete Sprite1 Clones v]

when I receive [Delete Sprite1 Clones v]//this script is in Sprite1
delete this clone

It's okay if the real ‘host’ sprite runs a [delete this sprite] script, because nothing happens.

I think that would be really useful! On some of my projects, that I haven't shared for this reason, I was too lazy to spend the extra time to use a broadcast or whatever. I think this would be really useful, and most Scratchers would benefit.

when green flag clicked
repeat until <mouse down?>
    
delete this clone
end

Hopefully we don't have to do this script.

LightningGuy wrote:

[scratchblocks]…

The script you made would not do anything. All clones are deleted when the flag is clicked, so it's impossible to have a [when flag clicked] block running inside of a clone.

No support.

CodeLegend wrote:

This would be helpful for some new scratchers.

But in the meantime, you could have a different broadcast channel for each sprite, for instance:

broadcast [Delete Sprite1 Clones v]

when I receive [Delete Sprite1 Clones v]//this script is in Sprite1
delete this clone

It's okay if the real ‘host’ sprite runs a script, because nothing happens.

This, basically. So many things would be helpful for new Scratchers, but just are too easy to workaround. Especially this workaround; it literally is three blocks.

Firedrake969 wrote:

So many things would be helpful for new Scratchers, but just are too easy to workaround.

I completely agree!

Ok. Thanks!

I support!

Couldn't you have the script you already have for your clones run in parallel with:

when I start as a clone
wait until <some condition is met>
delete this clone

to achieve the same effect?

You could have a variable for that condition that is normally set at 0. Whenever that condition would be met in your script, just change the value to 1 or some thing.

when I start as a clone
wait until <(is condition true?) = [1]>
set [ is condition true v] to [0]
delete this clone

JeremiahMacDonald wrote:

Couldn't you have the script you already have for your clones run in parallel with:
[scratchblocks]
You could have a variable for that condition that is normally set at 0. Whenever that condition would be met in your script, just change the value to 1 or some thing.
[scratchblocks]

That would also work, but I still think a broadcast is easier.

JeremiahMacDonald wrote:

Couldn't you have the script you already have for your clones run in parallel with:

when I start as a clone
wait until <some condition is met>
delete this clone

to achieve the same effect?

You could have a variable for that condition that is normally set at 0. Whenever that condition would be met in your script, just change the value to 1 or some thing.

when I start as a clone
wait until <(is condition true?) = [1]>
set [ is condition true v] to [0]
delete this clone

Thank you very, very, much. For a beginner tens of answers to this question where incomprehensible. This solved my problem. My poject for week 0 is on its way now. My poject for week 0 is on its way now.

If you don't want to clog up with broadcasts, then use just one:

when I receive [delete clones v]
if <(ID) = [F4785GVS22]> then // the code can be anything, just make sure all of them have their own unique code
delete this clone
end

One extra variable instead, but…

Hmm… Sorta necroposting but okay. I already got my answer a while ago. I'm just gonna close this,