CT-7569 wrote:

(#35)
bump

CT-7569 wrote:

(#42)
bump

CT-7569 wrote:

(#45)

CT-7569 wrote:

(#42)
bump

CT-7569 wrote:

(#46)

CT-7569 wrote:

(#45)

CT-7569 wrote:

(#42)
bump

CT-7569 wrote:

(#48)

CT-7569 wrote:

(#46)

CT-7569 wrote:

(#45)

CT-7569 wrote:

(#42)
bump

hill_walker123 wrote:

why isn't this getting any more discussion
it's like my posts, just not getting attention

man-o-valor wrote:

S-U-P-P to the O-R-T!

Roblox888i wrote:

Why? Please be constructive.

CT-7569 wrote:

(#49)

CT-7569 wrote:

(#48)

CT-7569 wrote:

(#46)

CT-7569 wrote:

(#45)

CT-7569 wrote:

(#42)
bump

Yellowsheep43 wrote:

I think clone indexes should be added as an extension, since I'm not sure if new scratchers would understand them

UI-coder wrote:

Yellowsheep43 wrote:

I think clone indexes should be added as an extension, since I'm not sure if new scratchers would understand them

new scratchers don't even understand operations, I say fully add them

hill_walker123 wrote:

hill_walker123 wrote:

why isn't this getting any more discussion
it's like my posts, just not getting attention

CT-7569 wrote:

Many games have enemy-to-enemy collisions and other similar things, and they are extremely hard to recreate in Scratch because it doesn't have a few cloning features. This suggestion is for a clone index and counter, and a few more clone-related blocks, to make it easier to make such projects.

1. Built-In Clone Index and Counter
   
   A clone index would be a variable local to each clone of a sprite. The actual sprite would have a clone index of 0, and all the clones would have a clone index increasing by 1 depending on the order of creation, i.e. the original sprite would have a clone index of 0, the first clone created would have a clone index of 1, the second a clone index of 2, and so on. It would be in the “Sensing” category, and it would look like this:
   

   clone index :: control reporter

   
   A clone counter would report the number of clones created by a particular sprite, so if Sprite A had cloned 8 times, its clone counter variable would report 8, and if Sprite B had cloned twice, its clone counter would report 2. It would look like this:
   

   clone count :: control reporter

   
   
2. Modify ([…] of [sprite]) block for clones
   This would look like this:
   

   [... v] of clone index (0) of [sprite v] :: sensing reporter

   This would work as the currently existing block, but it would also include sensing for clones. You can use a clone index of 0 to get information about the original sprite.
   
   
3. Modify the <touching > block for clones
   This would look like this:
   

   touching clone index (0) of [sprite v] ? :: sensing boolean

   This would function the same as before and would include sensing for clones. As in suggested block #2, using a clone index of 0 would check for the original sprite.
   
   
4. Modify the (distance to [sprite]) block
   This would look like this:
   

   distance to clone index (0) of [sprite v] :: sensing reporter

   It would function the same , and the modifications work the same way as in block #2 and #3.
   
   
5. Modify these three motion blocks
   Pretty self-explanatory by now.
   

   point towards clone index (0) of [sprite v] :: motion
   
   go to clone index (0) of [sprite v] :: motion
   
   glide (1) secs to clone index (0) of [sprite v] :: motion

If this would be too complicated for New Scratchers, it should probably be an extension, as suggested by @Yellowsheep43.

Please reply with your ideas and suggestions.