1. Behavior: change attribute 1

You would need to Constrain the Actor's self.Position.X to a value, like 160.

With the Constrain Attribute?

you need to Constrain the X or Y value of an Actor if you don't want them to move freely.

This is my guess off the top of my head, but if you have your healthbars under a global game attribute, and you reset scene, it only resets self attributes, not globals, so you might have to put under

I have a clock dial of sorts that I want to rotate continually during the course of a game. Currently I have a timer within the clock actor that sets its own rotation every 0.05 seconds. It works fi

I had a similar thing going on with my game Food Fight!. I have an actor that jumps and when you push a button, he throws (spawns) a pot. I think I may have tried what you did, and had similar problem

main actor, (the one that moves back and forth) constrain attribute game.maincharacter x to self.position x (same for y value)

You'll need to keep track of the Camera.Origin.X and Camera.Origin.Y (the lower-left corner of the screen). Create two global integer attributes, cameraX and cameraY. Create a camera tracker actor and

Assume that there are three objects in a scene and one object wants to set the position of the other two objects. Three game attributes exists, named OBJ_ID, OBJ_X, and OBJ_Y.

integer (or real, your choice) attribute pair that then gets copied over into the actor's X and Y position values in the initialize area and I manually set those attributes ("InitX"

That attribute doesn't really matter to your project.

- Change Attribute, self.Physics.Moveable To true

-Interpolate attribute: (self.Color.Alpha) To: 0

Each would need a game attribute pair for sharing the constrains between the cup and saucer (lack of array/indexing). You could then manually place each cup and saucer and adjust the constrain refere

Suppose you had a lot of cups and saucers, and you wanted that when a saucer was moved, its cup stayed locked in its relative position, how would you do that? I can see that you could constrain one ac

on. The idea was that within one actor the real attribute that I was using in the timer started as one value but then needed to change. Eventually someone figured it out for me. In the shared project

The game attribute is being driven by the user via the SHOOT button. Then the self attribute is used to "switch" the game ball interior rules. The functionality seems to function c

It's for projectile purposes, so maybe i'm best to stick with 1 of's and spawn them? Can the particles be used in collisions?

Change Attribute self.Rotation To: 0