e.g. joints would help because you wouldn't need all the constrain attribute behaviors and the game attributes.

Scene attributes only show up in unlocked instances. This is because it would break the prototype if you tried to access a scene attribute that did not exist in the scene.

Constrain its X position to AAA*sin(self.Time*BBB)+CCC

I recently got a template (for windows) and I saw on there that when he put the behavior "constrain attribute" in an actor. and inside "constrain attribute" he had

To communicate between actors, you can use a game attribute.

Hi Guys! I am new to Gamesalad so this is prolly a newbie question, but I am having an issue with trying to get a virtual on screen button to rotate another actor. I set up a real attribute for the

Create two game attributes (type real) called game.doorX and game.doorY.

and sometimes disappears i tried the change attribute too but did not work, i think the error is in the physics of the ball, maybe i did the density and bounciness with the wrong value, what you guy

@BenMakesGames @Rthurman , ow it is possible, You just need a spawner and relate an attribute that gives every actor an ID tag.

So would I do this in the same rule? For example I created a rule that when enemy overlaps or collides with the bullet - minus enemy health attribute. Then the next rule is when enemy health is equal

You use the change attribute behaviour. After your enemy is destroyed and when you are spawning another enemy, use the change attribute behaviour to set the attribute back to its original/starting num

The table it looks at has seven rows. The row each actor looks at is determined by a local attribute (self.row). I have tested the one actor that works by cycling its self.row up to seven when I click

change attribute linear velocity.Y to 300 (or whatever) whenever it bounces off a surface.

Another nice feature would be an index attribute added to each instance automatically, whether it was spawned or placed in the scene manually it would be great to have a built-in way to talk to each i

.....Change Attribute game.killStreak to 0

Yep, you can of course use DisplayText. But it gets tedious when you're trying to track 30 different attribute values. And sometimes you want to track values across scenes so you have to add the act

Have 3 attributes recording the millisecond that a guy is killed (Kill1, Kill2, Kill3).

For instance, if you want to track whether an attribute is changing or not- Make a new actor. Put a Display Text behavior in there. Have it point to the attribute you want to watch.

Curious. Are you using change velocity with the direction set up as 'random' and then a value for speed - something like 300? This should work. You can also go into the actor attribute and under 'moti

I'm new to GameSalad and have been messing around with it for a little while, but I don't quite understand the Attribute Condition. When exactly does it run? I kind of thought it would be listening al