You need to keep track of the main player's X and Y positions in global game Attributes.

change attribute can be anything, it just depends on the attribute type you're using. If it's a boolean, you'll use true/false. If it's an integer, use 0 or 1.

I have several animations that I'm switching between. I've looked at the platformer template demo and the entries in the forum here about change attribute behaviors and Boolean attributes. Well it see

Is there no way I can constrain the rotation to simply a 'direction' attribute? (though there isn't one)

When I say to constrain the self.Position.X/self.Position.Y to the touches, it asks which touch to constrain to (Touches 1, 2, 3, 4 etc)

I believe there is also a visible boolean attribute switch in the actor's graphics attributes...haven't used it yet myself. I assume it makes it visible or not visible. Not sure if it makes the rule

Control Music Audio in the Attribute Browser under:

If FMG is storing the letters as a single string, there is likely a game attribute he is storing it in that you can use.

I think FMG was joining the letters entered to make a string (since he mentioned some issues with the spacebar), so if so, he probably is storing it in a game attribute.

If you alter the velocities as above, you probably won't even need to mess with the X position (i.e. no need to constrain it).

what you could do is create about 10 attributes

I want to have zombies spawning around the map, but I want my timer rule, which says every 3 seconds, spawn "Zombie" actor. Can i have that every minute or when a attribute gets to a

this is what I am currently using, but I want this game to be "endless" at least in theory. If I can have a timer with an attribute that changes then I can have a system that makes t

Well, create an actor attribute (call it "LastXBeforeCollision" or something) that is integer (or real) and you use the "Change Attribute" behavior to save the &

OK, thank you but could you go more in debt on the save it to an attribute part? sorry i just started yesterday

In that rule (which fires upon collision), add a "Constrain" behavior to constrain the actors "X" position (i.e. self.Position.X) to the current value from the same

Constrain the X position of the colliding actor(s) to their last known X position upon collision?

Sounds like you may need to move the "Load Att" behavior for "UnlockedLevels" attribute to like the title screen so it is ready well before the level select screen

I have tried everything i know how to do with collisions, but no matter what it shoots the actor in off the way where the collision happened. Any help anyone could provide would be nice! (Image)

There is an unlockLevels integer game attribute.