For a future reference if you want it to turn back to false if pressed again (not sure what your using it for) You create a rule when touch is pressed then throw another another rule in there that say

@uptimistik That's interesting. I've had mixed results. I just created a test project and set the actor's Move speed to 5000 and set "walls" to destroy if colliding with it and onl

.....change attribute self.AlreadySpawned to true

You're almost there. You don't have to do this, but I have a habit of always naming save/load keys the same as the attribute they are using.

Make a boolean called box3? and say when box1 and box2 collide and box 3 is false, spawn box3. Edit: then in box3 say change attribute box3 to true.

Constrain attribute constantly updates the variables whereas change attribute only updates (changes) it once. So it you were to drag a ship around with your mouse you would do:

So I am reading the Gamesalad manual where you recreate the basic shoot em' up and they say that I need to create a constrain attribute to constantly update the x and y position of the player ship. Wh

(Quote)

I can't think of any simple solution. It would require a lot of attribute changes back and forth between the arrows, actor, and points. Tables would make it so much simpler.

1 - I create a Game Attribute as boolean called Started.

left or right arrows, add or subtract from an attribute, and then use that to reference the correct row to pick the x and y values.

and an integer attribute called "Device"

Even if I create a duplicate with the exact same actions...

Change a text attribute to the tableCellValue and use that for the left side of the rule condition?

Constrain Attribute game.speed to 100*abs(self.positionX-game.X)/game.MaxPossibleDistanceBetweenTheTwo

For example, are you doing Change Attribute self.position.x to self.position.x*cos(self.rotation)? You listed the operators +* which isn't making sense to me.

Yes, you can have When Touch is Pressed rule with Change Attribute and Save Attribute behaviors within the rule. The Load Attribute behavior would go on your first scene in any actor and should not

@tatiang I'm a little slow, I need create a Game Attribute as boolean called Started, and where I put the Save Attribute behavior ? on new game button?

are great for storing large amounts of values/attributes.

thank you @pierrenilsson , but, how can I use without table? because I don't know alot about tables. I tried put a load attribute on first scene, and when I press the button "new game&quo