Rule: When game.attribute = 0

the area you've restricted to move since 'move' attribute is not set to zero until you reach your location. So if I click a location and click again while my actor is moving there, move is set to 1

I'd use a self.attribute call it whatever you want, make it an integer or real.

I deleted half my game (now the project size is about 10 mb), set up BG images using the change attribute technigue, and am still seeing no changes in the 'Other' category.

Use a self.attribute for the actor, make it an integer, Call it self.pointC or whatever...

I have it so that when actor collides with the watermelon it changes attribute game.watermelon hitpoint to watermelon hitpoint +1. When attribute game.watermelon hitpoint=1, change image. I also have

When you mean attributes change, do you mean game attributes? self.attributes (like size, width, height, etc.)?

@Metronome49: I've tried this but for some reason the constrain is overriding collision. How did you get around that? That solves the bulkiness of the character's collision, but leaves the issue of

The save attribute function does not work when you are testing using the gamesalad client. You will need to make sure you are using the gamesalad viewer application on your iphone, or you have instal

The save attribute function does not work when you are testing using the gamesalad client. You will need to make sure you are using the gamesalad viewer application on your iphone, or you have instal

Why does it seem to, reset your scene it's better to use the Change Scene attribute to same scene

Change Attribute level1score to 5

When the level is over, I have an attribute that triggers when the level is over.

Ahh, sorry. I'm still in attribute mode. So does it just stay in the same scene when the car is destroyed?

There's some place you aren't loading the attribute, or loading it correctly when it goes into a scene, I think.

Yes, using the save attribute and load attribute behavior.

Use attributes and rules.

I am going to do the interpolate/constrain for the size for sure.

I am going to do the interpolate/constrain for the size for sure.

After the flicking occurs use interpolate to make the thrown object get smaller so it appears to be going off into the distance. Or constrain its height and width to a constant divided by the y positi