Imagine if you had a game variable playerX. You have some logic in your code for your hero that says "constrain game.playerX = self.X", this becomes constrain game.bob to self.x&

You can do that as long as the actor is unlocked in the scene. IF its unlocked you can access all the other actors attribute that are in the scene.

ok so i just find out this, from a template i bought, there is a actor that will do something according to another actor velocity, so before i need it to constrain my car velocity to a global attribut

Ok I added rule to the digit > dragged change attribute to it> but I don't see self.color.alpha as an option...

Where do you get self.alpha from? Do you create a rule and "change attribute" for each digit?

constrain X position to AAA*cos(self.time*BBB)+CCC

For circular collisions they are using the same kind of calculation, but with radius in place of width.

-Calling a local attribute in another actor

You will need two attributes:

Then it's not working correctly for me. I have a timer that interpolates an actor's alpha to 0 after 12 seconds (for a duration of 5 seconds). I have a rule within the actor that says if an attribute

No thats the way resets been. You have to change the attribute back yourself with change attribute behaviors when you reset.

Make a self attribute in the actor called touched.

you could just have an actor in the scene which constrains the camera rotation to a global attribute you make, you could then access that from a prototype, and have it so that when two actors collided

twice in arrow, so i add when touch change attribute "send me" +1 and when "send me " is =2 to change position to where it was in the beginning but is not working

Not that it makes a difference now, but out of curiosity, did you ever try using the interpolate behavior instead of change attribute?

Not that it makes a difference now, but out of curiosity, did you ever try using the interpolate behavior instead of change attribute?

If you use an integer attribute to calculate your position rather than adding directly to the actors X and Y you will avoid incorporating GSs erratic sub pixel behaviour.

If you use an integer attribute to calculate your position rather than adding directly to the actors X and Y you will avoid incorporating GSs erratic sub pixel behaviour.

I am using the display text attribute to display the value of vectortoangle(Accelerometer X, Accelerometer X ) on one of my actors.

You can't save a behavior, but you can attach that behavior to a boolean attribute, and save that.