I Think there should be a id for each clone (Clone id) that you could use to separate what each clone does

Before anyone says it, yes I know this thread said it was created by me. I transplanted this from a completely unrelated thread it was originally posted in, and that requires me to first make a thread and move the post to it, then delete my OP. Please keep discussion about the idea and not DjangoBB's quirks.

This is an interesting idea! Having some kind of way to identify clones is potentially useful and is a pretty common idea in other languages - I'm interested what similar solutions the community has already devised.

Harakou wrote:

Before anyone says it, yes I know this thread said it was created by me. I transplanted this from a completely unrelated thread it was originally posted in, and that requires me to first make a thread and move the post to it, then delete my OP.

This is an interesting idea! Having some kind of way to identify clones is potentially useful and is a pretty common idea in other languages - I'm interested what similar solutions the community has already devised.

Ohhhh. I got confused XD

Clone IDs are already possible using local variables, but it's not an obvious way.

red_king_cyclops wrote:

Clone IDs are already possible using local variables, but it's not an obvious way.

It's not that hard, I do it all the time

Whenever you create a clone you have to change the ID
Here's an example of what I would do:

Wahsp wrote:

red_king_cyclops wrote:

Clone IDs are already possible using local variables, but it's not an obvious way.

It's not that hard, I do it all the time

Whenever you create a clone you have to change the ID
Here's an example of what I would do:

I did not mean that it is hard to make clone IDs with local variables, I meant that it is not obvious that you use local variables to make clone IDs. It took me many months before I found out that local variables can be used to make clone IDs. How was I supposed to know that local variables have something to do with clones?

Wahsp wrote:

red_king_cyclops wrote:

Clone IDs are already possible using local variables, but it's not an obvious way.

It's not that hard, I do it all the time

Whenever you create a clone you have to change the ID
Here's an example of what I would do:

Whether its easy is irrelevant to how obvious it is.
For example, it's easy to get the warp flute in Mario Bros 3, but to someone who wasn't told how, they most likely wouldn't be able to find it.

What I suggest is an easier way to find out about how local variables work with relation to clones, rather than adding a new feature entirely.

Support, it will help people who don't exactly know cloning yet, and also people who want the clones to do different things without using more sprites.
Just having a variable isn't the obvious way, and it would definitely take longer.

badatprogrammingibe wrote:

Whether its easy is irrelevant to how obvious it is.
For example, it's easy to get the warp flute in Mario Bros 3, but to someone who wasn't told how, they most likely wouldn't be able to find it.

What I suggest is an easier way to find out about how local variables work with relation to clones, rather than adding a new feature entirely.

^ Definitely this.
Although the help feature is kind of hidden I think that the help for the “create clone of ___” block should make a mention about local variables.

This kind of thing has been suggested numerous times before. Here are a few examples:
https://scratch.mit.edu/discuss/topic/6508/
https://scratch.mit.edu/discuss/topic/9318/
https://scratch.mit.edu/discuss/topic/124500/
https://scratch.mit.edu/discuss/topic/184244/
https://scratch.mit.edu/discuss/topic/244243/
https://scratch.mit.edu/discuss/topic/304387/


TBH, though, I don't understand how it's that different from just having a global counter that you increase by one for each clone that's made, and have a “this sprite only” variable that takes the value of that global when a clone gets created:

However, I think what you really want to know isn't so much what a clone's number is, but what a clone is meant to *do* – and you can tell it that by setting a local ‘this sprite only’ variable (or several, if necessary) to some appropriate identifier info before starting a new clone.

This is much more general, allowing you to decide for yourself exactly how a clone identification system is going to work for your particular project.

For example:

As others have mentioned above, though, I do think it's not immediately obvious that a ‘this sprite only’ variable also means each clone has its own independent value for such a variable. Too often a clone is kinda thought of as being a ‘part’ of the sprite it came from, rather than being a sprite in its own right. (I mean, a clone of a sprite is also a sprite, after all!)

It would be nice to see some reference to such things in the help, if possible.

Anyway, hopefully there might be some useful ideas somewhere in there.

TheLogFather wrote:

This kind of thing has been suggested numerous times before. Here are a few examples:
https://scratch.mit.edu/discuss/topic/6508/
https://scratch.mit.edu/discuss/topic/9318/
https://scratch.mit.edu/discuss/topic/124500/
https://scratch.mit.edu/discuss/topic/184244/
https://scratch.mit.edu/discuss/topic/244243/
https://scratch.mit.edu/discuss/topic/304387/
<snip>

Thanks for the link and the awesome work-arounds! It does look like this is a duplicate topic so I'll close it to keep the conversation all in one place.

Please use the oldest existing topic in the links above - I'll start consolidating them back to that one.