screen and you would know the exact number of attributes to have ex. for a scene of 320x480 using 32x32 grid you would need 10x15=150 attributes for each x,y position and an attribute that relates to

Ok I understood... I goy confused there because I did not create a random exit attribute.

how I end up with a game exit attribute without x or y to make the random thing.

ok I thing that part is like I described but how do I do the change attribute game exit to random 1,6

I got confused... When you tell me to set up the x and y. is that creating an real attribute like exit1x then another exit1y and so on... then constraining each exit self position x and y to them?

[Attribute] section--you can change things too.

You can set the ball actor's Max Speed attribute to a number that wont exceed infinitely. its in the motion tab in you ball actor's editor.

You'll then have the attribute window open - at the bottom there's 'insert function'. Click on the button next to that and a drop down menu will appear.

to specific values. I did not have to add a constraint. Thanks everyone.

Hello, is there a way to copy instances in GS? I'm asking because I made a very complicated instance and I have to copy it 9 times. Every rule in that instance contains self attribute, so I would have

Constrain color = (accelerometer + 1) / 2

add the variable in the answerActor's Attributes Section

Can you just put an attribute called device and if you press Iphone it stays normal but if you press ipad It will change the scene size to the ipad size and in every actor put the rule but to make th

Constrain - self.Rotatio to vectorToAngle(-game.Accelerometer.Y,-game.Accelerometer.X)-90

I need your help. I have an app with more than 90 scenes. I have a boolean game attribute related to every scene, like game.1, game.2, game.3, etc. etc. In every scene I have an invisible actor that s

I tried changing the attribute and still nothing could it be that since I used 1 image and not 2 separate images thats causing the problem?

change attribute self.gravityCoefficient = gravityCoefficient * -1

I've tried it by making an attribute called 'self gravity' and setting it up like this:

I had drag-able actors that always overlap...(where is our Z position attribute?)

Booleans are very useful (I probably use them more than anything else). If I want to "switch on" a set of rules at certain times I use a boolean. Because booleans have only two possi