If you have multiple characters, and perhaps other unlocks in the game, I'd suggest using a table, not save attributes.

Yes, you can number your images like this: cutscene1.png, cutscene2.png, cutscene3.png, etc. and create an integer attribute called something like game.frame with a starting value of 1 and then each t

The width of the platforms is different, i want to know how i can set or constrain the distance between the right side of the current platform on the screen to the left side of the next random platfor

(Quote)

When Touch is Pressed and attribute game.coins ≥ 500 and attribute game.unlockedMario is false

Also how would I use the save attribute so my game knows its unlocked every time the user launches the game?

(Quote)

Aha! So that way, the game.text attribute is just a bridge from user to table, very nice. And use my integer attribute+1 to control which row to insert, is that correct?

     Change attribute game.input to ""

I want the user to be able to keyboard input multiple text attributes (up to 20), and then have the text stored in one col or row of my table, and then have them each displayed in an actor, before lat

Nice, could be useful for constantly changing colors. I mainly use the text attribute method to change an actors color at specific times, when colliding with another actor, or when reaching a certain

On a side note, you can do the same rainbow changing effect as in your demo file with just these three constrains . . .

I came up with a simple, reliable way to change or interpolate an actors color, without having to create 3 'change attribute' or 3 'interpolate' behaviors for Red, Green and Blue. I've found this tric

Say I want to put a variable in the middle of an attribute

I think Gamesalad is the only game engine that doesn't allow you to access scene attributes without unlocking the actor. It would be great and we wouldn't have to constrain actor's position to game a

That's - no bracket after Earth.Y / second constrain should be Y rather than X.

Constrain - Self.pos.x to 100cos(self.time75%360)+game.EarthX

(for example a new blank actor) and use that to constrain a couple of game.attributes to camera.origin X and Y . . your actor (the one you want to rotate) can then access the camera.origin via these

saved. Yes I have tried save table and save attribute and I have followed other simpler tutorials I saw on Youtube. I am using gamesalad on a pc and have a pro membership.

(Quote)