I have a tiny issue with the idea of show on screen the values of certain attributes, just to log and test some functions.

Learning to draw a line in GameSalad is not a trivial thing. But it is a great way to learn many of the fundamentals. When developers can do a simple line (and understand why it is done the way it

I'm trying to create a turn based game, which I've heard is difficult with gamesalad, and I've encounter a problem. My main actor is shared by two players, so I have created a Boolean attribute called

Sounds like camera control doesn't work for spawned actors? If true, then you could try having the spawned actor constrain its X and Y positions to Game Attributes, and then constrain the camera orig

Indeed 'change attribute' is used.I changed it to 'constrain attribute' but it doesn't work.The line does not appear in the screen anymore.

use 'constrain attributes' while touch is pressed.... I'm assuming 'change attribute' is used at the moment. . . if not hopefully someone who is familiar with the tutorial will help.

For each level you could make and attribute, for example "level1stars" "level2stars" "level3stars" etc etc.

Constrain Attribute: mydistance To: magnitude(game.Mouse.Position.X-self.Position.X, game.Mouse.Position.Y-self.Position.Y)

---make real attribute called Mag

Change Attribute Power to (300-(magnitude(game.Mouse.Position.X-self.Position.X, game.Mouse.Position.Y-self.Position.Y))*2)

Basically on one scene, 3 items fit. I have 9 in total. The bar position is constrained to an integer going from min 30 to max 130. I am trying to come up with a exponential formula that works. Becaus

@tatiang -- Thanks for posting a completed demo. You mentioned that there were issues with quickly flicking or tapping the number actor. If you turn on the >625 and <205 rules, that wi

Was trying to avoid constraints due to reading about performance hits with too many off them. So was trying to solve the problem by not using them if possible

-- Change Attribute: self.Position.Y To: 205

-- Change Attribute: self.Position.Y To: 205

Simple add to the attribute you're using for the health total.

-- Change Attribute: self.myLinearVelocityY To:0

Set attributes for each level (BOOLEANS are useful) and then when the level is complete change that boolean to true and save the attribute. When your game starts have an actor that loads all of those

Change Attribute AttackAnim to false

Make three attributes (type = real): myLinearVelocityY, oldY, offsetY