but when I've done it I've looked for a saved attribute that an existing (and therefore paid) user will have but a new user will not (as they've never run the app before).

an "actor" ==> change attribute "score" to "score+1", then i added an other actor where i put the "0" first, then i used

* Implemented Collisions for the Owls, so now they can hurt Sour Blob

yeah I have that already but it still won't work. I also have a real attribute RandomTime to 1.

Change Attribute game.number to game.number+1

And then have a rule that changes the attribute self.Image to "taunt"..random(1,20).

We spend a lot of time adding 1 to attributes.

Yes I want to go from 300 to 0, I have and actor that I want to shoot to the screen and Change Attribute when it hit 0

Actually I think what is happening is that the constrain is still happening with the first touched actor... I tested by putting a timer on the constrains and saw the target image jump between all the

How do I reverse the Rules to shirk the actor and Change Attribute. I could make the actor go small to large and change attribute, but I want to do the opposite please help ? here a screen shoot of wh

I am creating a game that involves being able to tap on an enemy to constrain it's X,Y to global variables GlobalX and GlobalY, and then a projectile will aim to that X and Y. Global X,Y are set to 0

Your collisions rules looks correct and when I play it in Mac Creator, it works fine. Maybe there's something about your installation of Windows Creator that isn't working properly. I sent you a vid

(width & height) in the Scene-->Attribute area? Lastly, what size is the actor that is getting cut off?

When attribute game.resetTimer is true Change attribute game.gametimer to 50

Attribute browser does not come up when I press the 'e'. the attribute box goes blue on the frame and that is it. Maybe I'm missing something but this is really annoying. I copy code in but cannot cre

Attribute browser does not come up when I press the 'e'. the attribute box goes blue on the frame and that is it. Maybe I'm missing something but this is really annoying. I copped code in but can crea

Attribute game.gametimer > 0

I couldn't tell that from the screenshots and you didn't provide any evidence of Save Attribute behaviors, nor did you show both Load Attribute behaviors that would be needed for two keys. So I'm jus

Unfortunately, those screenshots aren't very helpful except to show what you're missing (and perhaps that's the problem!). For a high score system to work, you must load the key into an attribute at

Create a Boolean attribute called something like Jump and set it to false,