***** OK so I had same button track the 'game.zoom' attribute. That caused some havoc , can use this thread if it happens to someone else (Image)

(Quote)

In addition to this, make sure you are selecting the attribute from the attribute drop-down list rather than typing it in (which doesn't work).

Make sure your self.ID attribute has an acceptable value, such as 1. It could be that you're referencing a nonexistent row in the table.

if you have alot of stuff going on, you could also add a boolean as a game attribute, and flip this to true when the X&Y attributes don't match the table.

I am writing a TD game, and I need to constrain each radius to it's corresponding tower. I'd like to avoid global attributes, since I'd like players to be able to create as many towers as they can aff

The rule I posted...If attribute game.lose ≤ 0

I don't know what that means. Did you use a Change Attribute behavior or did you set the initial value in the attribute inspector?

Sounds like really need polygonal collisions, Gamesalad doesn't support polygonal collisions unfortunately.

If attribute game.lose <= 0

I'm not sure what game.lose represents in your game but are you sure that that attribute is less than or equal to zero at the end of your game? Try adding a DisplayText behavior or log debugging stat

Change attribute game.score to game.higscore

Hello

Even having it all run of attributes and just change the attribute, instead of using a new Move behaviour, it still doesn't work.

Which is my I can't thank you enough for the time and demos, but constraining a circle doesn't work.

I have a platformer where the character is always moving, so I have their linear velocity x constrained so that they keep moving smoothly after bumping into something for a moment.

(Quote)

c) If Attribute.idle=true, then self.velocity = 0

It really depends what you mean by "continue the story." You'll need to decide what data to save. Once you decide, you use a Save Attribute behavior to save each value and a Load A

(Quote)