Script access to attached hinges and lasers

[immibis]

Scripts on an object (possibly in onCollide or onLaserHit) should be able to access the properties of hinges and lasers which are attached to that object, maybe with e.this.lasers(0).size for example. (If there was more than one laser the order would be unpredictable). A similar thing should enable hinges to be accessed, like with e.this.hinges(0).motorSpeed. Again, the order would be unpredictable for more than one hinge.

[Conundrumer]

A temporary solution is to make motors out of circles inscribed in rings with materialvel

[immibis]

You still can't access them from what they're attached to.

[Bronie12345]

you can acces them through the ray already (only the lasers), but as far as i know, not through the attached object

would be nice for hinges, but unnneccasary for lasers

[Sonic]

We can do this already, but just not in the way you describe. This is unnessesary. I don't support.

[Bronie12345]

not the way who describes?

[immibis]

Me.
Using Bronie's way for lasers, that means a) the laser has to collide with the object it's attached to, (b) that object has to be transparent, (c) that object has to be immortal (for a cutter laser), (d) the laser's script has to differentiate between hitting that object and others, OR the object's script has to differentiate between that laser and others.

[fox11trot]

i was just going to sugjest this!!!

i fully support idk why anyone wouldnt because it would make phunlet safe hinge/ spring scripting possible

[Conundrumer]

i was just going to sugjest this!!!

i fully support idk why anyone wouldnt because it would make phunlet safe hinge/ spring scripting possible

Technically, anything is phunlet safe since you can delete everything but the phunlet thing and save the scene as a phunlet, thus saving the variables and stuff

You still can't access them from what they're attached to.

Collision menus.

[immibis]

i was just going to sugjest this!!!

i fully support idk why anyone wouldnt because it would make phunlet safe hinge/ spring scripting possible

Technically, anything is phunlet safe since you can delete everything but the phunlet thing and save the scene as a phunlet, thus saving the variables and stuff

It's phunlet safe if you can have multiple copies of it that are identical but don't interfere with each other.

You still can't access them from what they're attached to.

Collision menus.

If this suggestion was implemented, an onCollide script could have: "e.this.hinges(0).motorSpeed = 5;" which is a lot easier than your way.

Is there any particular reason you don't support this?

[Sonic]

Not everything has to be Phunlet safe!

[Bronie12345]

even if you don't have this, you can make stuff phunlet safe (just controll stuff on other ways)
i always try to find new ways to make my stuff phunlet-safe

[fox11trot]

Ok, think about it,
you cant make hinge scripts phunlet safe unless you want to be able to put only one copy of the phunlet in the scene because, right now, the only way to change variables in hinges, springs, lasers, and pens, with oncollide or onlaserhit, is to use scene.my variables

[Username?]

It's nearly the same suggestion like this