Think that's what you are looking for. In that demo you can have an unlimited number of the same actor and only control the one on the top using only one (i think, can't remember) global attribute and

The way I manage lots of different states of animation, images, and motion is to have an actor attribute (an integer) called 'self state'. Put rules in the actor that play animation, images and apply

I made an attribute so that the actor jumps 3 times while in air and after the attribute number is more than 3 the character moves down...until he collides with the ground...also if the user continues

I use a smaller mask actor if i want the collision area smaller and constrain it to X Y of the bigger actor.

You need 2 real attributes charX charY (call these what you want)

You could make a new attribute and give it the value time/score

unless you changed the attribute key names between versions?

I may be wrong here, but for johnny, you would calculate the angle that the player flicks or drags using VectorToAngle with the correct offsets, constrain an attribute to that, and then add that to th

But this glitches and the attribute changed rises extremely fast. Note that score is default 1 so it is not dividing by 0.

try creating a boolean attribute like "animate"

If the free version had no "change attribute behavior" or no "animate behavior" or no "move behavior" okey then you can complain. Because it would

I know what you're trying for. I posted a similar question a month ago (but was xy coords rather than angle) and got no answer - it's a hard one to describe. I had a map that I wanted the player to be

You're going to need a lot of attributes to track which actors are in what scenes and where they are positioned in those scenes and a lot of loading/saving to the attributes to make sure the custom sc

Figured it out! It wasn't an x value or y value issue. Had to use interpolate instead of change attribute (different than Darren's video on recycling)! Not sure why the difference but works great n

I believe tenrdrmer is indicating that you should use an attribute, not an "actor receives event", to control what you want to do. This is done by counting how many touches are down

It is not in a rule. I have it at the very bottom of the list (not the top because it seemed to cause the change velocity attribute to malfunction).

you said when attribute "harm" equals 1 -> Change attribute "health" to -1

Change attribute game.attribute to game.attribute+1

How do you add/subtract to an attribute?

Would the Y being calculated from the bottom of the screen apply if I constrain the X and Y values to the actor?