My main character has two constraints:

Create a game attribute called game.LevelUnlocked (integer) and a game attribute called game.CurrentLevel (integer)

when the missile first spawns, capture the player's x/y position to some internal self variables using CHANGE attribute. Then accelerate towards that saved position, not the player's position.

Have a Controller actor: if warp1locked = true after 2 (or whatever you want) seconds change attribute warp1locked to false.

Make a global boolean attribute called level2 (or whatever you want).

That is correct. So do I need to set up a different attribute multiplier for each section?

1.I have two attributes declared LastLevelPlayed and HighestLevelPlayed both integers set to 1

Start off small with the beginning state and the end state of the running dog. Save those two images and add them to the GS animate attribute (these would be frames now). See how that looks - probably

"Self" would refer to the actor you are looking at and "start" is a user-defined attribute. See:

* preserve state - i shouldn't have to constantly resize the left panel (attributes, behaviors, etc.). Every time i navigate away the panel resets to its default width. I should be able to set it once

On your enemy actor make an attribute called 'Life'

Maybe try putting a timer, when collide every .. seconds change attribute.

I'm trying to continuously change an actor A's health value while it's touching actor B. However, I can only get health to decrement once when the collision is first detected. How can I keep decremen…

I have constraints all over the place. Right now I have a collision attribute set in the boxes that are resting on top of the platform. but not in the platform itself. if its just one box it seems t

are you using a constrain on the platform? This can be a problem. Try using something other than constrain.

A collision attribute is set on the squares that causes them to collide with the platform and each other.

yeah. you can use constraints with the greater than or equals to OR less than or equals to operators in conjunction with a specific pixel value onscreen. That's how I have done it. You can tell it to

Does the 'save attribute' button save the attribute for good? Cause i could use it to save the high score. For example if i save my attribute 'score', exit the game on my iphone, a day later come back

Attributes -

Woke up this morning with an optimization idea: Know how it is that people tend to recommend minimizing the number of constraints in your project, and it was nagging me that I already have 7 constrain