Another thing along similar lines I'd love to know - common belief is that using tables is more efficient than using attributes (ignoring ease of use). What's believed is that each code cycle every at

* The actor is moving at a default speed of 500, to the left (set using the motion.linear velocity.x attribute, which @Socks set to -500). This is what causes the ball to move to the left.

(Quote)

Thanks @Socks That looks like it should work within my game – and surprisingly simple. I noticed that you didn't enter any values for gravity in the scene attribute. I thought that if something were t

What I've also done is enter a value (3) into the Y coordinate of Gravity in the scene attribute and applied the above. My actors still slide off screen - downward.

Did you try change attribute self linear velocity x 200. Or could be Y. Numer is the speed.

In that case how do you deal with the situation where you want an actor to detect collisions with actors on higher layers?

1 is a non-problem. If you have a text editor, open an actor who has the attribute you want to transfer. In his initial lines, you will see the name of the "attribute" and an &qu

Previously this only seemed to be an issue if an attribute was being constrained but now it seems to just happen when an actor is merely on a lower layer. There is a bug report to that effect here: ht

The problem here is that each attribute has a unique number assigned to it. This is presumably what they use to reference the attribute in the actual code the game is converted to. Let's say I make a

As a workaround, you can often use 'unused' attrbutes to circumvent this issue, for example I'll often use Angular Drag as somewhere to store an attribute or Max Speed (on a non-moving actor) . . etc

The first change attribute condition is wrong.

@tatiang After a hiatus and some re-evaluation i found out that just adding whatever point to the score total actor attribute worked best with the equation you gave me thanks for challenging me and ma

(Quote)

Make an integer attribute ('A') set it to 1 / set Linear Velocity X to 250.

rule > when touch or overlaps whit actor B change attribute "Linear Velocity X" change to "-Linear Velocity X"

gshelper.com/shop/free-templates-and-tutorials/constrain-to-mouse-and-keep-collision-gamesalad/

Cheers for the explanation @Armelline! That makes perfect sense. I had a look around but couldn't find the tutorial you mentioned but you have pointed me in the right direction. I will figure out how

Start with a default of 0 (the default value of a new attribute) and run it through the maths, there's nothing complex there, just basic subtraction and multillication.

* If so are you referencing a table row or column using an attribute?