if attribute game.accelerometer.x> 0.05 Then

Make a game attribute of real type and call it bally

Its self attribute . Go to you rocket actor and look on the left side there is plus .

perhaps I need to add the collide behavior not to the wall but to the scrolling background and attribute it to the wall...

#5 on his list is already possible, all actor instances can access and change any attribute of any other actor instance in the scene.

5. Consider a "DOM"-style object tree - Add a new attribute to game objects (sprites, etc) called "ID" or "Name" that is blank by default. If, say

Every himself check his own unique id and if he was touched too, when touched I did set a global attribute of the actor that have right now the status of "touched", this the way I us

Check all ur rules if you delete an attribute it leaves a rule in the programming with no value or left a () off gs doesn't know what to do and images will disappear

constrain self.position.x to touches.touch 1.x

When game.jump is true -->> accelerate at 100 after .2s change attribute game.jump to false

Edit: I've just remembered that I have another Actor with the same Rules, except this stops if it's less than, via an integer attribute changed to the Attribute+1. But this doesn't make sense either,

-----change attribute: game.flipped to false

Hi, for the past two evenings I've been banging my head against a brick wall (well, not literally!). I've a list of Rules, with the beginning conditions valid including: when self.Flipped is false. Th

I have been creating a unique id for each actor, an actor attribute id, when spawn, and have a global attribute that I change to true or false depends the status or action that I need to apply and ea

Well, If your actor is symmetric like a ship, you could change attribute with rotation in 180 degrees, to make left of right.

There's a couple of vids in the Support section that'll help you out there. One thing to mention: as x,y locations refer to pixel position, as you know, it's best to choose an integer attribute.

Density really only comes into play in collisions. If two objects collide the one with the larger density will "win" the collision and push the other one back.

2)Real Attribute

-Attribute= game.Waitforit= 1 (BTW if I enter "true" the scene does not work. "1" works.)

-Change attribute: Waitforit To: True (Is Waitforit an "integer" attribute?)