Make a attribute called spawnfollow or whatever you want to call it. Have it set to 0

To further clarify what crazyfishdev is saying you can put a rule inside of the timer attribute and then set it to a specific time to run for.

Are you using the save attribute behavior and then the load attribute when you load he game?

already doable if you Index game.Attribute for list of actors... and have event trigger Index change and therefore all particulars of that actor

you can use triggers via Rules to implement changeImage behavior... moving actor's attribute (ex: position)

I am using a "Save attribute" behavior, does that count for this? It says I could be in severe penalties. Help would be nice (Image)

I've also tried constrain in place of change, that didn't work.

He has a change velocity rule in there that has a formula for the speed value. I think you could basically take the Y axis stuff out of the ball actor and use the formula found in the speed of velocit

Like sctunes set your problem is that constrain isnt effecting the physics so it doesnt have a velocityl. Its just constantly updating its position to what its constrained to

you could constrain its linear velocity Y to whatever you want it to be.

Create and invisible actor and call it "barrier 1" (or whatever you want). In that actor (barrier 1) have it change a game attribute say..."don't cross", or again

For the "when my actor comes within a certain distance of that actor" I would constrain a hidden object to your actor and make a rule that when your player character overlaps/collide

If game.attribute = 1

simply get the graphic and drag instances of an actor with an attribute named myLetter to the appropriate area of the scene....and have a gameAttribute named letterSelected (Text type) ... assign corr

heathcc - I do have a BallSpeed game.attribute. I've been experimenting with different ways to do this, but speeding them up just doesn't seem to help.

I would use my own attribute variable and not MaxSpeed, but only because I'd be afraid that I wasn't changing it and thus other velocity assignments would conflict.

I created two attributes called 'Create random number' and 'Score'. In the 'Create random number' actor I did.

I've got the slow down effect figured out (I just changed the max speed on the ball based on a game.attribute).

Sounds like you have a bad actor or rule that is maybee missing an attribute

simply create an Index Attribute in Game set to 0