Is there a way of detecting if a clone is touching another clone, and which clone it is touching?
I know you could use the touching colour block, but that doesn't detect which clone it is touching…

I've come up with one method:

when I start as a clone
change [NextID v] by (1)
set [id v] to (NextID)
set [color v] effect to ((id) * (10))
check for touch

define check for touch
if<touching color [#FF0000]?>
set [touchingID v] to [1]
end
if<touching color [#DD6600]?>
set [touchingID v] to [2]
end
if<touching color [#CC8800]?> //continuing this as many times as you have clones
set [touchingID v] to [3]

Is there a more efficient way of doing this?

It depends what exactly you are trying to achieve as to how you might solve it. One way is to record the positions of all the clones in a list, then when your “if touching” test triggers, you could use the coordinates in the list to ascertain which clone is the closest and hence the one that is touching.

There are other ways of doing it, but the best way will depend on what your project is attempting to do.

you can store x/y positions of all clones in a list, and use hitboxes….

The problem with storing x and y positions, is it ends up appearing incredibly laggy with only 2 clones, even in turbo mode….
It has to check if anything is touching it constantly, while moving, so it's constantly updating the list, and constantly checking it…

xlk wrote:

you can store x/y positions of all clones in a list, and use hitboxes….

Psiborg just said the same thing…

Splodgey wrote:

The problem with storing x and y positions, is it ends up appearing incredibly laggy with only 2 clones, even in turbo mode….
It has to check if anything is touching it constantly, while moving, so it's constantly updating the list, and constantly checking it…

It really shouldn't lag, I've done this with loads of clones before. I imagine there are some optimisations that could be made in your code to get it working.

Splodgey wrote:

The problem with storing x and y positions, is it ends up appearing incredibly laggy with only 2 clones, even in turbo mode….
It has to check if anything is touching it constantly, while moving, so it's constantly updating the list, and constantly checking it…

xlk wrote:

you can store x/y positions of all clones in a list, and use hitboxes….

Psiborg just said the same thing…

Challenge Accepted. I'll try to make a project like that! please wish me luck!

Psiborg wrote:

Splodgey wrote:

The problem with storing x and y positions, is it ends up appearing incredibly laggy with only 2 clones, even in turbo mode….
It has to check if anything is touching it constantly, while moving, so it's constantly updating the list, and constantly checking it…

It really shouldn't lag, I've done this with loads of clones before. I imagine there are some optimisations that could be made in your code to get it working.

It's laggy even with one clone, and I can't think of or see any optimisations I could make… All they do is move at a speed based on item (id) of a list, and randomly turn, and adding the x position and y position lists causes it to lag horribly…

Splodgey wrote:

It's laggy even with one clone, and I can't think of or see any optimisations I could make… All they do is move at a speed based on item (id) of a list, and randomly turn, and adding the x position and y position lists causes it to lag horribly…

Both of the projects in my sig store the x and y coordinates of clones in lists and this doesn't present any performance issue. Perhaps you can share your project and we can see what the issue is?

when I start as a clonechange NextID by 1set id to NextIDset color effect to id * 10check for touch
definecheck for touchif touching color ?set touchingID to 1if touching color ?set touchingID to 2if touching color ?continuing this as many times as you have clonesset touchingID to 3
Is there a more efficient way of doing th

I just want a simple way of doing this.

http://scratch.mit.edu/projects/23988940/

Its a bit messy. Im sure somebody can improve on it…its getting late anyways

Uhhhh…. I think that this is a duplicate: https://scratch.mit.edu/discuss/topic/14349/?page=1

QuantumSingularity wrote:

Uhhhh…. I think that this is a duplicate: https://scratch.mit.edu/discuss/topic/14349/?page=1

Shoot, necropost, I had multiple tabs open. SORRY!

QuantumSingularity wrote:

QuantumSingularity wrote:

Uhhhh…. I think that this is a duplicate: https://scratch.mit.edu/discuss/topic/14349/?page=1

Shoot, necropost, I had multiple tabs open. SORRY!

o-o