(Quote)

You need an Attribute, not an Actor.

I'm not sure i understand the question, are you trying to get them to continue the parallax effect when clicking on the blue object? I would just use when touch is pressed interpolate camera origin x

I'm still trying to wrap my head around terminology and how this software works and organizes things esp when placed in the game area. Coming from an OOP background I assume my master Trigger Actor h

You could also set the hero's acceleration attribute to be extremely high, but limit it with the 'max speed' attribute within the actor. That way, it would go from stationary to moving pretty much ins

Another option instead of Velocity that you can try is to Change Attribute Actors Motion Linear Velocity X to a number. You will also have to set your jump to a number on Motion Linear Velocity Y so t

For the score, you need a 'load attribute' in the beginning of the game for the high score to load from the last save.

Secondly, I closed the app then when I open it again the score is lost and went back to 0 but I did put save attribute in the score, did I forget to add something?

it's a bug the 10.3 builds I think I've seen similar issues when working with attribute values. it seems it's always the second thing I work with (attribute or expression).

I'm having some issues with Gamesalad for mac (the newest version). It seems that expressions at random times gets removed from building blocks, its giving me a bad headache when something that has be

http://forums.gamesalad.com/discussion/24219/can-you-make-an-actor-reference-another-actor-s-attribute

I set up an attribute linked to the position of the body, then linked a constrain attribute behavior to the position of the part. It only constrains it once. I can't see how you got it to constantly u

integer attribute = full numbers

It works just as intended since integers are whole numbers. You need to use real attribute instead.

I've been using gamesalad perfectly for about a month now, and starting today whenever I make new integer attributes, it rounds off to whole numbers. For example, I'm trying to make a game attribute c

1.) Actions on the Trigger that says if it collides with the Hero, set a boolean attribute I created within that Trigger to "true".

However, I have no clue how to do that short of constraining his X position on the platform, but that makes no sense...

In 10.3 you have to send the condition to a self attribute first but in the nightly build one can do it straight from a rule condition now.

9. "Don't save more than 3 attributes at once." Why? What kind of diminishing returns would I be looking at?

✓ 5. Turn every attribute under the physics tab in the actor editor to 0 on actors who do not need it." Is this really worth it? It'll take a long time but I can't see why it would affect pe