True, oh and of course the logic to actually trigger the constrains as well.

The only thing you'd also need in there would be an offset for the PlanetRotation . . . . so for instance if you have an incoming missile fired at the earth - it will hit in some arbitrary location .

Your questions aren't particularly clear, interchangeable terms aren't helpful (what is a 'constrain attribute' or a 'constraint' or a 'radius constrain behaviour' ?? etc etc).(Quote)

True, but not knowing how attributes behave and then jumping into trig can be daunting!

How do I let Gamesalad detect what I type in the "Save attribute" section as a "Custom key" ?

I *understand* what "constrain" means. I get that. But there is no built in "radius" attribute to constrain to something. And so as I said, my assumption was theref

I don't know !? Sorry, I feel like I'm being difficult now ! Lol, honestly I'm not, I guess I'm a little thrown by your questions . . . I don't know what the radius constrain behaviour is, nor where y

Behaviors are essentially predefined code that can serve multiple purposes. A constrain does exactly what it says. It constrains an attribute to a value (or another attribute, so any given variable).

When you save an attribute, you type in a "custom" name for the key. It can be anything you like but I always name it the same as the attribute I'm saving. So if I'm saving game.hi

I've looked up a video tutorial doing this with "Save and Load" Attributes by storing data in a custom key name.

. . . . you can convert those values to particle offsets, they don't need to be constrain behaviours, they are basically X and Y coordinates (and you won't need the third constrain rotation behaviour,

What is the "radius" constrain behavior? I have looked at the "Constrain Attribute" behavior built into GameSalad, and I see nothing that maps to "radius&a

Change attribute game.score to game.score + 117

(Quote)

Text attributes are for... text (words). For a score, you usually want an integer attribute. You cannot change an attribute's type so you'll need to delete it and create it again.

But this seems to say that the key is the "three constrain behaviors", which I *think* you created, right?

I found that, and added the attribute score as a text. Is that what I should have done? Sorry for the questions, I am absolutely new at this.

The feature is . . . . . . 'constrain', read through the instructions provided:(Quote)

There are three types of attributes in GameSalad: game, scene, and actor (aka self) attributes. The reasoning you are seeing "score" in the attributes menu is because that is the na

the trouble I am having is coming up with the attribute game.score - I initially created the actor for score and pulled it onto upper left corner of scene. Then under rules for "score&quo