custom blocks, they have parameters which I'm guessing u know, taking in consideration how talented the scratch team is in coding and developing, the local variables in functions are really useful for custom blocks but I'm inquiring if you can add them into clones, it wouldn't be that hard for most of the community to understand, they have the same thing in custom blocks, and if that's a obstacle to cross u can maybe add it as a extra extension just in case.
when I create a clone it doesn't have any custom parameters right? nothing to really customize it how u want to, it could let children and people who use scratch have a lot have the freedom freedom to create, it could provide people with a core understanding on how parameters work

when I start as a clone

imagine this is a clone block -

define when I start as a clone ( Custom clone variable )  

just pls explore this idea and take it into consideration, its not that big of a addition and u already have something close to it in custom blocks so it wouldn't be a major adjust inside the community

What is this suggesting

Kanyata wrote:

What is this suggesting

its suggesting the ability to have custom variables for each clone created

I support! this would be extremely useful.

Kanyata wrote:

I support! this would be extremely useful.

Thanks! I hope the scratch team will see this

you can workaround this with “for this sprite only” variables (when a clone is created, all sprite-only variables get copied over from the main sprite)

CST1229 wrote:

you can workaround this with “for this sprite only” variables (when a clone is created, all sprite-only variables get copied over from the main sprite)

wait so I could label every individual clone with their own number that only each individual clone holds?

Kilko4 wrote:

CST1229 wrote:

you can workaround this with “for this sprite only” variables (when a clone is created, all sprite-only variables get copied over from the main sprite)

wait so I could label every individual clone with their own number that only each individual clone holds?

yes, and then you could:

when green flag clicked
set [thisSpriteOnly v] to [0] // this variable has "for this sprite only" enabled
repeat (2)
change [thisSpriteOnly v] by (1)
create clone of [myself v]
end
...

when I start as a clone
if <(thisSpriteOnly) = (1)> then 
...
  

else
if <(thisSpriteOnly) = (2)> then // It can keep going past this
...
  

else
...
end

end

hill_walker123 wrote:

Kilko4 wrote:

CST1229 wrote:

you can workaround this with “for this sprite only” variables (when a clone is created, all sprite-only variables get copied over from the main sprite)

wait so I could label every individual clone with their own number that only each individual clone holds?

yes, and then you could:

when green flag clicked
set [thisSpriteOnly v] to [0] // this variable has "for this sprite only" enabled
repeat (2)
change [thisSpriteOnly v] by (1)
create clone of [myself v]
end
...

when I start as a clone
if <(thisSpriteOnly) = (1)> then 
...
  

else
if <(thisSpriteOnly) = (2)> then // It can keep going past this
...
  

else
...
end

end

thx, if I knew that before so many things I could of made would of been a lot better

Kilko4 wrote:

hill_walker123 wrote:

-snip-

thx, if I knew that before so many things I could of made would of been a lot better

yeah, I use that a lot

You could also use a different sprite-specific variable, like

(costume [number v])

to do that kind of thing instead, if each clone has a different costume

when green flag clicked
switch costume to [#1 v]
create clone of [myself v]
...


when I start as a clone
if <(costume [number v]) = [1]> then
...
else
...
end