1. Added a game attribute called LEVEL

Constrain: self.Rotation To: min(60,max(-60,Rotation)

Called: "Using min and max in one Constrain?"

I have an actor whose rotation I need to constrain between -60 and 60.

3 self attributes (integer) startRotation, startAngle, newAngle.

Made a new attribute to use.

actor1 just sits there and actor2 is constrained to actor1

and also put a change attribute to it with change self.position.y to random(10,50) <- or something

I was using the alternative to timers in order to move between scenes (using a self attribute and the self time. I learned it from another post of these forums...good stuff!)

The modes are locked by checking a boolean attribute, "game purchased". By default, it is false. If the player tries to access it without having purchased the game, a notification po

What's weird is that, every time you die, it does increment the attribute CurrentMusic, so it's obviously passing through the rules properly. But the PlayMusic behaviours don't seem to trigger at the

You said that if you die a second time the music starts again, that sounds like it could be something wrong in the code. Look at the code that switches the attribute, that's where I'd start.

When my player dies, it switches to a new track (using an attribute) and then does a Play Music.

Actually.....maybe I could say if the Scene's 'Level' attribute is 1, use the original table and if the 'Level' attribute is 2, then use the copied table. Right?

Because the rules are programmed in a way that won't let you say if table cell = expression you'll probably need to store the table cell in an attribute and then in your rule say if attribute = expres

I've tried adding a rule where I drag an attribute condition, so that I can say if tablecell row 1 column is false do so and so, but it doesn't let me. I suppose this must be a limitation in GameSalad

I've not really looked at tables yet as I only started to look at GameSalad again a week or so ago, but yes that's what I mean, a true or false/boolean attribute.

(Quote)

One way I have made this a bit smoother is by calling an attribute lets say 'Gravity'.

Constrain attribute Game.Rotation to self.rotation