The problem is that you are using a timer to set the attribute to "no" every second but the player won't necessarily click/tap at exactly one second intervals. For example, let's sa

(Quote)

Just replace "game.Time" with your own counter attribute. Something like this:

efficient that the alternative - which is three constrain behaviours - the only downside is that the whole length of the actor collides, even the invisible bit, if this is an issue you will probably

constrain attribute:

http://www.deepblueapps.com/collisions-with-tables-template/

(Quote)

i Constrain self Y position to:

Make an integer game attribute called Total.

The thing to remember is that Change Velocity is not a behavior. It is an 'action' and is meant to only fire once. (Just like Change Attribute is not a behavior, but is an action.)

Yep, I can verify that the Change Velocity behavior only changes the value once. This would be similar to a Change Attribute behavior. It doesn't continually change the value. For that, you'd need

I had this happen to me multiple times while creating two games for one of my clients. Whenever I use a change velocity rule and set the speed as a global attribute, the rule does not fully fire, caus

Constrain Y position to:

Turns out I didn't have run to completion checked off. I made the custom hibernation page that automatically resets game. I also threw in a rule to turn off the moving actor sound attribute. Will repo

So what I do in my games is I create a actor called "tack" and constrain that to camera origin, and this way I have something to keep things were I want them. So this way you could c

If I try using a change attribute behaviour as a reset button and for Attribute I have game.total score what do I put it to?

I just tried copying it to another attribute but it isn't working, The score on the post score screen still shows up with a 0.

Transfer/copy the post game score to somewhere safe, like another attribute, so it doesn't get reset . . .

You need to manually reset each attribute. So for example, if you are changing scene, right before the Change Scene behavior, you would have something like Change Attribute game.score to 0 and Change

I'm guessing that you have other things that add to the score besides the coins. If so, make a separate attribute called game.coins and only add the coins to that attribute. Then add the other score