Ok so I know you could just do

when I receive [ v]
go to [ v]

But what if you wanted to do it with clones?

You couldn’t do it with clones. You’d need to have a new block.

So as an example, you want a clone to generate a projectile. Let’s say these clones pop out at random times

With our new block, we could do this:

when I start as a clone
…
broadcast [ v]
teleport sprite [ v] to me

And in a new sprite

when I receive [ v]
create clone of [myself v]

when I start as a clone
…

Every other method is too complicated for new scratchers, so don’t give me some super complicated workaround.

A very simple workaround, is to save the clone's x and y positions and use the go to block, nothing is complicated.

psaad wrote:

A very simple workaround, is to save the clone's x and y positions and use the go to block, nothing is complicated.

You can do that like this:

Make sure it's for this sprite only

psaad wrote:

A very simple workaround, is to save the clone's x and y positions and use the go to block, nothing is complicated.

Not simple with multiple clones. It you wanted 20+ clones it’d get out of hand fast

Gamer_Logan819 wrote:

psaad wrote:

A very simple workaround, is to save the clone's x and y positions and use the go to block, nothing is complicated.

Not simple with multiple clones. It you wanted 20+ clones it’d get out of hand fast

You can’t create 301 clones. Also, use a list.

chriscreators14 wrote:

Gamer_Logan819 wrote:

psaad wrote:

A very simple workaround, is to save the clone's x and y positions and use the go to block, nothing is complicated.

Not simple with multiple clones. It you wanted 20+ clones it’d get out of hand fast

You can’t create 301 clones. Also, use a list.

..Funny

Also yeah, clone id with a list of the positions of all clones (up to 300/301).

chriscreators14 wrote:

Gamer_Logan819 wrote:

psaad wrote:

A very simple workaround, is to save the clone's x and y positions and use the go to block, nothing is complicated.

Not simple with multiple clones. It you wanted 20+ clones it’d get out of hand fast

You can’t create 301 clones. Also, use a list.

Lists are hard to read with code when it comes to coordinates. The point of the suggestion is to SIMPLIFY the coding.

I never said you needed to create 301 clones, I said 20+

Gamer_Logan819 wrote:

Lists are hard to read with code when it comes to coordinates. The point of the suggestion is to SIMPLIFY the coding.

Where's the hard?

psaad wrote:

Gamer_Logan819 wrote:

Lists are hard to read with code when it comes to coordinates. The point of the suggestion is to SIMPLIFY the coding.

Where's the hard?

If you have 200 clones that 400 list items, one for each clones x, and one for each clones y

cookieclickerer33 wrote:

If you have 200 clones that 400 list items, one for each clones x, and one for each clones y

Why not use separate lists?

psaad wrote:

cookieclickerer33 wrote:

If you have 200 clones that 400 list items, one for each clones x, and one for each clones y

Why not use separate lists?

I’m going to assume you don’t mean 1 list for each clone

What do you mean

cookieclickerer33 wrote:

What do you mean

A list for X, and another for Y.

psaad wrote:

cookieclickerer33 wrote:

What do you mean

A list for X, and another for Y.

Won’t work. IDing clones doesn’t exist.

psaad wrote:

Gamer_Logan819 wrote:

Lists are hard to read with code when it comes to coordinates. The point of the suggestion is to SIMPLIFY the coding.

Where's the hard?

You have to do a whole bunch of coding to get it to read lists and pinpoint which coordinates it is to go to.