I work with the constrain attribute too...and it's handle fine!

@Mcccccc‌ -- you can use the Constrain Attribute behavior. But you first need to unlock the instance actor on the scene to access a different instance's attributes.

From the Guide: "Actor attributes can only be accessed by an instance actor, but can be initially defined and used in an prototype actor so that all instance of that prototype can have predef

@jigglybean‌ I added a save attribute after the change attribute set game.bestscore to game.score (right under)

Not wanting to sound rude . . but you might be better off working your way through the GameSalad cookbook, this will give you all the basics about how GameSalad works, time invested here will save you

Yeah DP5 still crashes when you try and mess with attribute behaviors and such. That's a shame, I was hoping for a fix.

Just make each part an actor and constrain them to the body. Make rules such as when actor collides with danger - destroy actor But the problem is finding out how to constrain them to the positions t

@BBEnk: I tried but the editor doesn't give me the possibility to constrain an actor's attribute to another actor's attribute… Probably it's a "jurisdiction" problem, in fact I can c

How i can control my Puck? are there other methods as well as the change position to mouse position? because when i use constrain to mouse it overrides the collision! are there a couple of method to

Why can't you use the constrain it should be straight forward.

Hello, I need to create an actor composed by more than one part (when the body moves, legs and arms should follow it as a unique person!). Is it possible to constrain the legs' and arms' position to t

Is it possible to constrain the legs' and arms' position to the body's? I couldn't use the "Constrain Attribute" Behavior to directly constrain the actors attributes.

Ah ok. then have you added a save attribute after? Or if you are using tables, save table

Change the Scene attribute color from black to some other color than what your fullsize image has on its edges (this is how you see the issue).

Change attribute

----Change Attribute game.multiply to game.multiply * tableCellValue(yourtable, x, 1)

Not automated, I guess that would be the wrong word for me to use, I guess I should say more easily accesible, like how theres already attributes built in to each actor to affect friction and so on an

----Change Attribute game.bottomY to random([minHeight], [maxHeight])

You don't need any extra attribute (but you might - depends on what you're going to do with the result), but you do need to use * to multiply, not x.

do change attribute set: game.bestscore to game.score