Blaze349 wrote:

ScratchJahd2011 wrote:

Blaze349 wrote:

ScratchJahd2011 wrote:

RandomPerson1789 wrote:

These two scripts:

This workaround is interesting… But how would you get the Touching block? By getting it from another sprite? That's called bug exploitation, we need a real implementation.

How is that a bug? It is an easy work-around.

You are using something that is not implemented for easy use.

So? It works…We don't need something if we have a short and easy work-around.

Then the Scratch Team just needs to add the name of the parent sprite in the <touching [v |> block. Which is basically the point of the whole topic.

ScratchJahd2011 wrote:

Blaze349 wrote:

ScratchJahd2011 wrote:

Blaze349 wrote:

ScratchJahd2011 wrote:

RandomPerson1789 wrote:

These two scripts:

This workaround is interesting… But how would you get the Touching block? By getting it from another sprite? That's called bug exploitation, we need a real implementation.

How is that a bug? It is an easy work-around.

You are using something that is not implemented for easy use.

So? It works…We don't need something if we have a short and easy work-around.

Then the Scratch Team just needs to add the name of the parent sprite in the <touching [v |> block. Which is basically the point of the whole topic.

Did you even read the post? We have a short and easy work-around.

Blaze349 wrote:

ScratchJahd2011 wrote:

Blaze349 wrote:

ScratchJahd2011 wrote:

Blaze349 wrote:

ScratchJahd2011 wrote:

RandomPerson1789 wrote:

These two scripts:

This workaround is interesting… But how would you get the Touching block? By getting it from another sprite? That's called bug exploitation, we need a real implementation.

How is that a bug? It is an easy work-around.

You are using something that is not implemented for easy use.

So? It works…We don't need something if we have a short and easy work-around.

Then the Scratch Team just needs to add the name of the parent sprite in the <touching [v |> block. Which is basically the point of the whole topic.

Did you even read the post? We have a short and easy work-around.

It needs to be easier…

But everyone is entitled to their own opinions, so I'll just accept yours.
But I still want the parent name to be added.

ScratchJahd2011 wrote:

Blaze349 wrote:

ScratchJahd2011 wrote:

Blaze349 wrote:

ScratchJahd2011 wrote:

Blaze349 wrote:

ScratchJahd2011 wrote:

RandomPerson1789 wrote:

These two scripts:

This workaround is interesting… But how would you get the Touching block? By getting it from another sprite? That's called bug exploitation, we need a real implementation.

How is that a bug? It is an easy work-around.

You are using something that is not implemented for easy use.

So? It works…We don't need something if we have a short and easy work-around.

Then the Scratch Team just needs to add the name of the parent sprite in the <touching [v |> block. Which is basically the point of the whole topic.

Did you even read the post? We have a short and easy work-around.

It needs to be easier…

But everyone is entitled to their own opinions, so I'll just accept yours.
But I still want the parent name to be added.

Easier? This is six blocks. Not like 40.

Blaze349 wrote:

ScratchJahd2011 wrote:

Blaze349 wrote:

ScratchJahd2011 wrote:

Blaze349 wrote:

ScratchJahd2011 wrote:

Blaze349 wrote:

ScratchJahd2011 wrote:

RandomPerson1789 wrote:

These two scripts:

This workaround is interesting… But how would you get the Touching block? By getting it from another sprite? That's called bug exploitation, we need a real implementation.

How is that a bug? It is an easy work-around.

You are using something that is not implemented for easy use.

So? It works…We don't need something if we have a short and easy work-around.

Then the Scratch Team just needs to add the name of the parent sprite in the <touching [v |> block. Which is basically the point of the whole topic.

Did you even read the post? We have a short and easy work-around.

It needs to be easier…

But everyone is entitled to their own opinions, so I'll just accept yours.
But I still want the parent name to be added.

Easier? This is six blocks. Not like 40.

I meant how to get the parent name inside the touching block…
But I'll use the workaround until the suggestion is added…

ScratchJahd2011 wrote:

Blaze349 wrote:

ScratchJahd2011 wrote:

RandomPerson1789 wrote:

These two scripts:

This workaround is interesting… But how would you get the Touching block? By getting it from another sprite? That's called bug exploitation, we need a real implementation.

How is that a bug? It is an easy work-around.

You are using something that is not implemented for easy use.

Not implemented? Evidently everyone above is satisfied with the simple workaround. (:

dracae wrote:

ScratchJahd2011 wrote:

Blaze349 wrote:

ScratchJahd2011 wrote:

RandomPerson1789 wrote:

These two scripts:

This workaround is interesting… But how would you get the Touching block? By getting it from another sprite? That's called bug exploitation, we need a real implementation.

How is that a bug? It is an easy work-around.

You are using something that is not implemented for easy use.

Not implemented? Evidently everyone above is satisfied with the simple workaround. (:

The conversation we had is already resolved and we are at an agreement.
Also I'm not that satisfied… just tried it lest year, and it didn't work, so I'm just surprised it works now.

ScratchJahd2011 wrote:

dracae wrote:

ScratchJahd2011 wrote:

Blaze349 wrote:

ScratchJahd2011 wrote:

RandomPerson1789 wrote:

These two scripts:

This workaround is interesting… But how would you get the Touching block? By getting it from another sprite? That's called bug exploitation, we need a real implementation.

How is that a bug? It is an easy work-around.

You are using something that is not implemented for easy use.

Not implemented? Evidently everyone above is satisfied with the simple workaround. (:

The conversation we had is already resolved and we are at an agreement.
Also I'm not that satisfied… just tried it lest year, and it didn't work, so I'm just surprised it works now.

Resolved?Agreement? It should always work.

Hello,

I'm just new to Scratch so please be gentle.

I too wanted a

I read with interest the above posts but they used > 1 sprite to solve the problem.

My code below uses only 1 sprite :

Clone Sensing Test

Granted, this is far more complex than the proposed work around above but the code seems to execute quite swiftly.

To my mind, with reference to what Lightnin alludes to in his Suggestions Sticky, I believe this functionality should be included in a future release as it would add to the “low floor” of Scratch.

Just keep it simple…

..or just add the name of the current sprite into the list.

Contest101-test wrote:

I recently posted an identical suggestion (here), which was reported and closed as a duplicate of this suggestion.

As I believe circumstances have changed since 2014 when this suggestion was first posted, I will bump so that it may be discussed again.

In Scratch 3, it might look something like this:

Selecting “this sprite” would allow detection of collision between clones of the same sprite. The functionality of clones touching clones of the same sprite is already in place, but is not intuitive to the inexperienced Scratcher. There are several workarounds: either select the current sprite in a touching block in another sprite and then drag it to the current sprite, or use a variable or join block containing the name of the current sprite in the touching block. Regardless, I think adding “this sprite” to the list in the touching block would be little effort, and would make this functionality much more available.

Some might say “What if there is a sprite called ‘this sprite’ in the project?”. I suggest this is handled the same way as when there's a sprite called “edge” (can be confusing, but not a problem). Alternatively, the actual name of the current sprite could be added to the list.

A sample project where clones touching clones of the same sprite is detected using this functionality, Pole Position (see Car sprite code):

This works :

Very Old

mockups:

turkey3 wrote:

-go into another sprite
-select that sprite in the touching block
-drag it into the other sprite

That’s what I was going to say XD