The three constrain behaviours in the main actor are what make it rotate.

You can constrain the object to the cos and sin of an angle instead, which will be very smooth.

It's really straightforward, just put an actor into your scene, unlock it, and the wobble the camera around using whatever you want (rotate, move, constrain . . . etc etc).

Let me rephrase that, i don't think it's changing the column to 0 but it changes the game.head attribute to 0.

Constrain three actors together to form a triangle.

Unless I'm missing something, you would just spawn an actor with the image of the pop out you want and use a Display Text behavior to display the attribute (e.g. game.damage). Then use something like

Another thing I noticed is that you're constraining self.Image to game.pageNumber, which is exactly what my demo does, but your image filenames are called "1car", "2car&

The problem is that you are constraining the page number attribute in the Next and Prev actors. Those should both be Change Attribute behaviors. For future reference, if you constrain an attribute t

Are you sure you used the "Constrain Attribute" behavior and not "Change Attribute"?

(Quote)

To constrain 3 actors together where each has a 'collision' rule that affect the whole group is as simple as constraining them together and having a global attribute that is triggered if any of the 3

.....Change attribute self.whichActor (integer) to random(1,3)

It's a text attribute, not an integer. If you have a button actor that changes the category to cars then you would change that attribute to "cars". Or for trucks, another button mi

1) I create an integer attribute, name it "category" and give it a value of 1.

Is it possible to constrain 3 actors (A, B & C) together where each has 'collision' rules that affect the whole group?

The way my health bar demo works is that right before the constrained actor spawns, I change an index value (1, 2, 3, ...). When the actor spawns, it changes a self attribute to match that value. So

@tatiang Thank you for the demo! Although I am very confused on the whole idea of tables and the constrain attributes. I have attached a screenshot as to what i want the fish to look like once it come

could concatenate a word onto the image name: Constrain Attribute self.Image to "truck"..game.pageNumber, and then name those images truck1.png, truck2.png, etc.

With a single fish, it's pretty easy to constrain a spawned actor to another spawned actor through the use of two game attributes (e.g. game.fishX and game.fishY) With multiple fish, it's not as easy

TABLES. You can store character specific attributes inside the tables that are trigger by an event in game. I would store global boolean as well as Integer attributes.