Also, I had some problem with collision detection in my pinball games. I used the "Collide" attribute for bounces, as the rules appear to be skipped sometimes.

you need to make the "drop" attribute an actor attribute, not a game attribute.

2. Does it change the scene sizes, actor sizes (even sizes like that: 134.466?), positions and math in the behaviors (f.e. if attribute game.xxx is 1, then change the position to: xxxx), and what abou

There is a random function where you can set a min and max to select and for selecting between three attributes I would make an integer attribute call selector and set the random to be 1 to 3 and then

Create a real game attribute called screenRatio or something and set it to 1 for iPhone. Multiple all your X and Y coordinates by this attribute. Then after using your tool set it to 2.4 in the iPad p

Test 2) Then got rid of all on-screen 52 cards and just used 1 card and did a change image attribute based

Just a notice: there's no need to constrain the controls actor to the camera origin.x

Make a boolean attribute called 'Bomb dropped'

you could probably save different values for the same attribute using different keys but you would only be able to access one of the saved attributes at a time. I don't think it would be any less rule

oh, but i need to save the attribute about 300 times, so the problem is that when i save it once, i want it to reset the scene, and save it again, and i want to diffrent saves, but im worried its gonn

yes, the save attribute will save your attribute and then to load just use the load attribute. I think the reason that it is not working is saving attribute does not really save them in the editor...

i need to save 2 attributes, called x01 and y01, then i want to be able to somehow reset the game, and save the atributes again, but still have my old ones, i then want to call those back later, what

Constrain attribute "self.position.X" to "game.mouse.position.X"

Change 'player2' attribute to random (1,10)

change attribute game.score to game.score+1

change attribute game.score to game.score+1

change attribute: self.X to 200 (if you want it to be respawned at the X 200)

Then I had a self attribute "current aov", which I constrained to

Use interpolate or change attribute X instead.

You can count them by setting up a game attribute (i.e. "counter") and adding the actor a rule, like: