i changed over collected to a global variable but the problem with that is once 1 coin is hit now they all disappear. this would work if there weren't like 20 instances of the same actor on stage and

@Thrstn: If the "self.collected" is a local attribute, and you reset the scene, then it will reset the attribute, however, if you make "self.collected" a global att

make an attribute game.move

I tried..but to no avail! One thing I noticed was that the interpolate attribute was empty when I went to look over what could be wrong.

Interpolate Attribute: Self.Position.Y yo Self.Position.Y + 50 (50 is any number exact you want to move)

Interpolate Attribute: self.Position.Y To: 200

which wasn't necessary since I already had the Boolean attribute assigned.

Set up a Game attribute called TouchOrder that starts at 0.

i placed an attribute inside the coin called collected and set it to false

which wasn't necessary since I already had the Boolean attribute assigned.

OK, go it. This really hard to do, but definitely possible. You need to apply the principals found in CodeMonkey's joystick demo. Basically have small touch actors. One that constrains to touch1 anoth

Sure, I have 2 actors on 2 sides of the screen I have 2 people touching a device to move those actors but when I constrain it to axis 1.x for both actors it messes up and if I have 1 actor constrained

Another way is to use timers and Change Attribute.

Have it change attribute 'self.opacity' to 1 over 2 seconds say.

But with this case, how do I add the "+ game.CameraX" and "+ game.CameraY" (as per FMG's instructions) to a simple: if touch is pressed, change attribute game.actor

Add a display text behavior and put the OnTheGround attribute in it (Just stick it in the main ghost guy). Try to figure out where it is not triggering. Try pulling out the current ground actor in tha

How would one force an actor to do something, in this case jump, if it's constrained? I have an actor moving on the X but after it gets past a certain x value point it's constrained. I'm taking bits o

Add a display text behavior and put the OnTheGround attribute in it (Just stick it in the main ghost guy). Try to figure out where it is not triggering. Try pulling out the current ground actor in tha

Yes, you have to put save behavior for every attribute you want to save. You don't have so many attributes to save - in my game, I'm saving about 200 attributes - it took me almost two days to finish

I would like to save each time the level ends so my question is do I need to manually put a save attribute for each attribute I want save?