thanks Sous Chef however I have just updated my original post as I realised that the "movable" attribute does the job. The problem is that the constrain attribute setting doesn't see

You have to create that attribute yourself by clicking the plus button [+] in the Attributes pane of the Actor.

The "Movable' event triggers correctly but setting the Constrain Attribute of self.Position.X to "game.mouse.position.X" doesn't seem to work.

Create a button actor fot this propose. Create a boolean game attribute called "jump". When button touch is pressed, the boolean attribute is true. When is released boolean is false.

Make an integer game attribute called like "character_select". Assign a value to every character. Add a rule to every character:

if the joystick is "dragged", your could constrain the position.y attribute.

turns the alpha back to 1 through a global attribute. Obviously the rules for the colours could only allow touch pressed when alpha =1. the items on the coloring page would also need

- When a swatch is clicked, it saves its RGB values to global attributes named colorR, colorG, and colorB.

When you are doing something on scene editor, you have actors and behaviors at the left side of the screen. I think it will be great if GS have at the right side of the screen the actor attributes fro

You can explore using Touch Count perhaps? It's the global attribute that counts how many touches are current on the screen, regardless of position. Or a combination of Touch Count and something else.

to make clear: the problem occurs when these constrained collisions are stoped too. All others collisions that are not constrained works flawlessly and the problem don't occurs if I have only one ima

-That the background has a whole load of rectangular invisible actors to respond to touches and change the colour of the item through an attribute. These invisible actors fill the space as well as pos

Have a boolean attribute called 'no fire'.

And you can make 3 attribute text, first name, second name, full name.

\r also works but it might not if you integrate attribute calls.

with an image (non collidable). The collision is constrained to the same position of the flipper and rotate to the same angle at the sme speed when a button is pressed. What happens is that the ball

Health is an attribute on the actor. The actor is spawned every n'th second from another actor and moves to the end of the level. The five or so first enemies updates correctly (from 10 to 8 to 6 etc)

Is the health a global or character based attribute?

I've made a simple tower defense game. A box at the start of the level spawns enemies that have an attribute (health) set to 10. The health value is displayed on the enemy with DisplayText. After the

CONSTRAIN "CIRCLE" ATRIBUTE