Access Clone Attributes

Hopscotch Language Evolution
1

A feature I’d like to see in Hopscotch is:

Accessing the attributes of clones.

I’d use it for this type of project:

Idk, but it would be so helpful in so many situations.

Here are some examples of Hopscotch code that could be improved if we had this:

Having massive chains of variables just to save the attributes of 500 clones.

Here is an example design I’ve made:

image
7197FE2A-544D-44FC-A333-1BAA0B2E8BBC.jpeg1704×382 247 KB

Worst photoshopping job I’ve ever done, but you get the picture.

I’ve seen something similar in another programming languages, it looks like this:

…idk. Other programming languages don’t really have ‘clones’.

Umm… @omtl? Whaddaya think?

31 Likes
If (Clone Number) is tapped, pressed, bumped, or touched
Giving Clones Names
Ideas For New Features!
Create variables/images
2

Just to clarify my example design, the first input is the object, the second input is the clone number to check.

I feel like I shouldn’t edit the post cause it might retag omtl.

14 Likes
3

Yes
Yes
Yes
Yes
I have wanted this so badly

10 Likes
4

Same

10 Likes
6

Yes, this would be awesome to have in Hopscotch! Great idea!

7 Likes
7

Very nice :clap: :clap:

6 Likes
8

This is a great idea!

6 Likes
9

Yes
I would love this

7 Likes
10

Should I tag the devs?

4 Likes
11

I would

4 Likes
12

@Ana, @AwesomeOnion, see post 1.

4 Likes
13

YAAAS THIS WOULD MAKE CLONING SO MUCH EASIER
Body clear

4 Likes
14

hmm i like this idea. it would really improve cloning on hopscotch.

5 Likes
15

Agree with this 100%

6 Likes
16

Still want this, need it/a variation of it to continue a game

Like instead of Clone 3, “Any clone”

6 Likes
17

If they add lists and they make it possible to have lists of objects then this could be really easily done.
Just make each object have a list of its clones

9 Likes
18

bump
THT should add this

5 Likes
19

Agreed

3 Likes
20

bump

2 Likes
21

Along with the suggestion: target selector with ( ( Clone Index (#) ) Variable )
There should be a ( (Parent Object) Variable ) target selector that targets the object that made its clone.

This is similar to ( (Original Object) Variable ), but instead of getting the attribute of the original clone, this gets the attribute of the object that made its clone, hence, “Parent Object”

For example:

Clone 1 creates a clone - The new clone has a clone index of 2
Clone 2 wants to move to the (X Position) of Clone 1.
In order to achieve this,
Clone 2 has the code [ Set Position to x ( (Parent Object) X Position ) y ( (Self) Y Position ) ]
The “Child Object” could create its own clones again, becoming the “Parent Object” of the new clone:
Clone 2 creates a clone - The new clone has a clone index of 3
Clone 3 has the code [ Set Position to x ( (Self) X Position ) y ( (Parent Object) Y Position ) ]
Clone 3 moves to the (Y Position) of Clone 2 but not the (Y Position) of Clone 1.

4 Likes