PrincessFlowerTV wrote:

Sorry, but this kind of topic doesn't really fit the forum “Requests”. I'll request for it to be moved to “Suggestions”, which is probably a better fit for this topic.

SuperPancake64 wrote:

PrincessFlowerTV wrote:

Sorry, but this kind of topic doesn't really fit the forum “Requests”. I'll request for it to be moved to “Suggestions”, which is probably a better fit for this topic.

Sorry! I've never used the forum before!

SuperPancake64 wrote:

I think you should make an input block that detects how many clones of a specific sprite there are and what number a specific clone is.

when green flag clicked
set [id v] to [0] // The variable must be private.
repeat (some times)
change [id v] by (1)
create clone of [myself v]
end
set [number of clones v] to (length of [list v] :: list)
when I start as a clone
insert [any data about your clones] at (id) of [list v]
forever
replace item (id) of [list v] with [any data that would update]
end

WindOctahedron wrote:

SuperPancake64 wrote:

I think you should make an input block that detects how many clones of a specific sprite there are and what number a specific clone is.

There exists a workaround:

when green flag clicked
set [id v] to [0] // The variable must be private.
repeat (some times)
change [id v] by (1)
create clone of [myself v]
end
set [number of clones v] to (length of [list v] :: list)
when I start as a clone
insert [any data about your clones] at (id) of [list v]
forever
replace item (id) of [list v] with [any data that would update]
end

SuperPancake64 wrote:

WindOctahedron wrote:

SuperPancake64 wrote:

I think you should make an input block that detects how many clones of a specific sprite there are and what number a specific clone is.

There exists a workaround:

when green flag clicked
set [id v] to [0] // The variable must be private.
repeat (some times)
change [id v] by (1)
create clone of [myself v]
end
set [number of clones v] to (length of [list v] :: list)
when I start as a clone
insert [any data about your clones] at (id) of [list v]
forever
replace item (id) of [list v] with [any data that would update]
end

no i mean like is this clone the 7th one that was made since the start flag was clicked

when I receive [Detect! v]
if <(id) = [7]> then
...
end

define create (number) clones
set [id v] to (counter) // private
repeat (number :: custom arg)
change [counter v] by (1) // not private; it's here because if you set the id to 0, the variable will reset
change [id v] by (1)
create clone of [myself v]
end
set [id v] to [0] // This is here, because if you use my script above, the sprite can also execute the command. With this, it is safer.

WindOctahedron wrote:

Also, just an update:

define create (number) clones
set [id v] to (counter) // private
repeat (number :: custom arg)
change [counter v] by (1) // not private; it's here because if you set the id to 0, the variable will reset
change [id v] by (1)
create clone of [myself v]
end
set [id v] to [0] // This is here, because if you use my script above, the sprite can also execute the command. With this, it is safer.

define create (number) clones
set [id v] to [0]
repeat (number)
change [id v] by (1)
create clone of [myself v]
end
set [id v] to [0]

Botcho_Othko wrote:

~snip~
I'd have done this:

define create (number) clones
set [id v] to [0]
repeat (number)
change [id v] by (1)
create clone of [myself v]
end
set [id v] to [0]

I think it uses less variables.
I don't understand why you used “counter”; could you explain to me, please?

Nambaseking01 wrote:

They added Counter so the Id does not reset to 0 every time the loop starts. That was pointless, because the value was set to 0 outside the loop

when green flag clicked
set [counter v] to [0]
...

define create (number) clones
set [id v] to (counter)
repeat (number :: custom arg)
change [counter v] by (1)
change [id v] by (1)
create clone of [myself v]
end

Botcho_Otkho wrote:

~snip~
Oh, I see.

Botcho_Otkho wrote:

WindOctahedron wrote:

Also, just an update:

define create (number) clones
set [id v] to (counter) // private
repeat (number :: custom arg)
change [counter v] by (1) // not private; it's here because if you set the id to 0, the variable will reset
change [id v] by (1)
create clone of [myself v]
end
set [id v] to [0] // This is here, because if you use my script above, the sprite can also execute the command. With this, it is safer.

I'd have done this:

define create (number) clones
set [id v] to [0]
repeat (number)
change [id v] by (1)
create clone of [myself v]
end
set [id v] to [0]

I think it uses less variables.
I don't understand why you used “counter”; could you explain to me, please?

when green flag clicked

[Update the forum]

SuperPancake64 wrote:

They need to update the blocks that you can use in the forum to the 3.0 blocks lol.

Botcho_Otkho and Nambaseking01 wrote:

Basically “The id reset is pointless”.

Troyer_Kem wrote:

SuperPancake64 wrote:

they need to update the blocks that you can use in the forum to the 3.0 blocks lol.

when green flag clicked
[Update the forum] :: #dd0000 stack

Yeah. Some blocks are missing in forum blocks. Like pitch.

Botcho_Otkho wrote:

-snip-
To make it work, I'd do this:

when green flag clicked
set [id v] to [0]
...

define create (number) clones
set [id v] to (counter)
repeat (number :: custom arg)
change [counter v] by (1)
change [id v] by (1)
create clone of [myself v]
end

Nambaseking01 wrote:

Err, shouldn't the Counter variable be set to 0 and not the Id? I am confused.

WindOctahedron wrote:

Botcho_Otkho and Nambaseking01 wrote:

Basically “The id reset is pointless”.

I just added the id reset so that when adressing the last clone that is created, the sprite itself isn't adressed (because the sprite's id is 0).

WindOctahedron wrote:

-snip-
I just added the id reset so that when adressing the last clone that is created, the sprite itself isn't adressed (because the sprite's id is 0).