well, that would work, but what i think the best course of action, would be to create an attribute that every say five seconds or so, changes itself to the say x axis of the gyroscope, then if there i

Alrighty, this is what i need help with, i need to change the volume of something based on how hard the ipad is hit, and to do this, i want to use the accelerometer to first measure the jump in positi

Once an actor is placed in the scene (and unlocked) it can have direct access to all the events and variables (attributes in GS) of the scene/game/whole shooting match!!

yes, I think you're right, but in my iphone game there isn't an otion to constrain directly to another actor, you need a game attribute which the target actor changes and the child actor is constraine

You need to set up a "change attribute" to set self.sizeX to self.Size.Width at the start

you could set a start x and start y for your character and then constrain camera origin x and camera origin y to player.x-start.x and player.y-Start.y.

you need to setup a game or self attribute and have a second timer

Ok now i totally fixed this one out. I should have use integer in the first place in the self attribute of the actor as it is much cleaner to execute.

Make an attribute called CameraPosY (make this real otherwise the movement can be jerky if its an integer)

If actor overlaps or collides with actor with tag "Stack" then change attribute CanMove to false.

Only 2 game attributes, both integer: FirstX, being the first actor's X pos; and SecondX being the second actor's X. The Rules in the pressed actor (unlocked, i.e an instance, so you can access the ot

youll need to use sin and cos. Youll also need to make 2 real attributes call them planetx and planety and in the planet you want to orbit around change attriubtes planet x and y to self position x an

(based on a every whatever seconds fire the sync attribute) and then used counters of the attribute being fired to lock things in to quarter, half, beats and every other or bar. It works pretty well

You could try some Magnitude features. However, you have to constrain them and it eats a lot of processor. If you have a ton of coins (like over 50 or so) then it might eat a lot of processor. If it's

Maybe you could try use an attribute that tracks which coin is the current target so that the computer-controlled player only has 1 target at any given time. For example, you have an attribute called

For some reason my attribute wont update.

For some reason my attribute wont update.

You will need to make a startX and startY real attribute in the platform actor then do a change attribute startX and startY to self.Position X and same for Y

make an attribute called "random scene" then on each actor that has a different question put-

I am working on a game where I need to build a rule that looks at the attribute of the item it is colliding with and compare it to it's own attribute. I tried working with tags, but tags are not modi