If you're saving a single attribute, you really don't need a table. Just do a Save Attribute and give it a key such as highscore. Then, on an actor on your first scene do a Load Attribute with that

i played it a bit and its creative. it has alot of potential. you should change the scene around on each level to make it different terrain maybe some floating terrain/platforms and horizontal moveme

basically add a constrain rule for your actor so if your actor is the bigger image constrain its height and width to the size you wish, and the same with the smaller image.

@alarm656 did you intend to run the save attributes every second? Did you not want after 1 second?

Have one game attribute for players weapon, either as a number or string.

(Quote)

If attribute/table data could be read/written to/from a web server... wow... that opens up a lot of possibilities with GameSalad — even beyond gaming!

Change Attribute BoolLoop to true

You need to use a couple of math expressions and then compare the sums. You would need to store the sums in self attributes in the actor that computes the score.

     Change attribute game.anInteger to 1-game.anInteger

Sure. Create two game attributes called game.character and game.scene (although I'd be tempted to call it game.level since "scene" is already a built-in GameSalad term). These can

Without seeing it, I would guess that once you constrain the main actor's Y position to the legs actor's Y position, it should move up when the legs move up.

I think you misunderstand my question. I'd like it to turn on a bolean attribute when pressed, then turn off a bolean attribute when pressed again. how do i do that?

P.S . . . on a side note . . . . in the main actor switch off the bottom constrain behaviour - and switch on the two rules in the middle that are currently switched off (a change attribute action and

From what it sounds like, you need to turn off scene gravity and any gravity effects (usually accelerate) on the main actor and turn on gravity effects on the legs actor. Then, constrain the main act

2) You then tell the actor to constrain its X position to this variable.

2) You then tell an actor to constrain itself to move left and right about this variable.

but my guess is that its got something to do with the attribute??

1) You create a variable, it's called constrainingXposition with a default value of zero.

created a self integer attribute called constrainingXposition