9. "Don't save more than 3 attributes at once." Why? What kind of diminishing returns would I be looking at?

✓ 5. Turn every attribute under the physics tab in the actor editor to 0 on actors who do not need it." Is this really worth it? It'll take a long time but I can't see why it would affect pe

and if this is also not working you can constrain his x position to the position you want?

(Quote)

to when tapped. When a letter is tapped, either constrain the x and y of the letter to the x and y of the space, or move the letter to the x and y of the space.

also when they hit the floor, i was looking to make the change velocity to 0. but i could not figure it out. i probably need a attribute for that huh. Thank you GameSalad

Use a timer with run to completion unchecked in your rule. Put the change attribute in the timer.

Fajlajp.. i reckon the Attribute is an Integer which is by default on 0..

You need to create three different rules and one different attribute(we call it RandomAction)

If actor touches the ground actor for longer than 1.5 seconds then change attributes "xyz" to "whatever" BUT if the same actor touches the "ground&quot

in the actor where the attribute decrease with 1 when is pressed say

One of my integer attribute increase of 1 every second and decrease of 1 when one of the actor is touched but i don't want to let it goes below zero, could you help me?

Also you can make an attribute to hold your timer. And make a timer every 1 second change timer to timer+1.

Set Self.Touched = True (this is an attribute)

I think it's better like you said with the real attribute directly into the actor and not in the game

I put a real attribute

Set up two 'real' attributes on the actor called

If so try storing the last random position x and y in an attribute and if the next random x is higher than the last x it's going right (change image/animation accordingly), otherwise it's going left.

I have 4 real game attributes (one for each player), which store their scores:

I bet if you didn't use scene attributes but constrained the X/Y out to a game attribute - it'd work fine.