You must add a block which deletes all the clones of one sprite/all the clones.
Thanks!

Yeah, that would definitely help.

Why not just use messaging?

Seems easy enough to me. No need for a block for that.

Easy enough? In that case, why don't we eliminate forever if <>; () - (); turn ccw () degress; set, change and glide blocks for movement; change block for variable; timed say and think blocks; play sound until done; all hat blocks besides greenflag and broadcast received; all list blocks; ifthenelse; and repeat(#)? There is a workaround for each of those blocks, but for some reason, they were implemented.

Ok, I admit using variables as a list with a delimiter would be painstaking, but some of the others are much easier, especially using + negative instead of -, and turning clockwise negative degrees.

We HAVE eliminated the forever if block.

I like this idea. Heck, redundencies can be good things.

The reason I don't like the idea is because it does not follow Object Oriented Programming practices.

BoltBait wrote:

The reason I don't like the idea is because it does not follow Object Oriented Programming practices.

+1

Also, I hate the glide block, because you can't have anything else going on while it's gliding.

OrcaCat wrote:

Also, I hate the glide block, because you can't have anything else going on while it's gliding.

…In the same thread.

broadcast (do stuff)
glide (2) secs to x: (20) y: (30)

when I receive (do stuff)
reset timer
repeat until {{timer} > (3)}
turn (3) degrees ccw

My blackjack game uses the glide block for dealing cards and they also spin while gliding.

So, it's possible. You just need to be tricky and use 2 scripts.

BoltBait wrote:

My blackjack game uses the glide block for dealing cards and they also spin while gliding.

So, it's possible. You just need to be tricky and use 2 scripts.

@ nXIII/BoltBait Thanks!

BoltBait wrote:

Why not just use messaging?

Seems easy enough to me. No need for a block for that.

Oh wow. I was searching for an answer to delete all clones.I feel dumb now

OrcaCat wrote:

BoltBait wrote:

The reason I don't like the idea is because it does not follow Object Oriented Programming practices.

+1

Also, I hate the glide block, because you can't have anything else going on while it's gliding.

Yes, that block is very annoying. I only used it about 2 years ago when I started Scratch.

BoltBait wrote:

Why not just use messaging?

Seems easy enough to me. No need for a block for that.

+1
Thought the same when i red the title.

@LiquidMetal
When we add for every small thing like this (which needs just a had and the dlete block and a sender), we would have too many blocks. Also you can't argue with ever block has a work around. Many things are useful althought they can be work arounded with a small ammount of blocks. Like change varibale by 1 or set variable to variable +1 is the same, but the change var by 1 is very often used, for me more than the set block. Other blocks are similar. Like the turn: Turn 15 degrees or set direction to direction +15. Imagine you would always have to build the last one.

The ammount of usage of blocks is important. So when a block is often used, however small and easy the workaround is, the block should exist. But the delete all clones seems to be a rare used block. So i think we do not need it, because you even when you need this block, you would use it only a few times in the project and then never again.

BoltBait wrote:

Why not just use messaging?

Seems easy enough to me. No need for a block for that.

Clones don't respond to when I receive blocks

everybodyedit wrote:

BoltBait wrote:

Why not just use messaging?

Seems easy enough to me. No need for a block for that.

Clones don't respond to when I receive blocks

When clones do not respond to messages, how do all my projects with clone work? I work at the momen on 3 big projects, all 3 use clones and all use in the clones at least one receive block. So i think you should check your scripts

OrcaCat wrote:

BoltBait wrote:

The reason I don't like the idea is because it does not follow Object Oriented Programming practices.

+1

Also, I hate the glide block, because you can't have anything else going on while it's gliding.

Check out galaga in my signature that is pretty much all gliding!

I agree a delete all might be handy for rogue clones that slip through openings in your code.

everybodyedit wrote:

BoltBait wrote:

Why not just use messaging?

Seems easy enough to me. No need for a block for that.

Clones don't respond to when I receive blocks

They do respond to those blocks.

A “Delete All Clones” Block would be nice, and it would solve the problem of going through all the coding just to delete every single clone that had been made. It'd Be nice, but not necessary- I Would like scratch add this, but it isn't IMPORTANT….
Thanks for your Consideration Scratch!
-Post By User: block_push-