The ball rolling setup doesn't do what we're needing. Trying to constrain attributes as the person goes up or down a ramp but I'm still debugging. If I get a good solution I'll take a screen shot and

Opps, I missed the double dot after my attribute name, I suppose it was just a sort of placeholder.

from the larger and placing it is a number attribute that I then check to see if it has altered and is greater or lesser and that to a boolean the fires the scale up or down. The timing seems to be

Create an boolean game attribute game.spawn

----------change attribute game.jump to 0

you can have a boolean attribute called pause and have it set to false. On all your rules to shoot and stuff have when touch is pressed and pause is false. Then in the pause button have when touch is

I have a totalnumbers attribute that makes sure the amount of numbers on the screen doesnt exceed three, i have three integer attributes that control the three numbers, and ih ave a system set up that

I wanted my game to make a sound every time the score goes up. Instead of putting a rule to make this happens in every instance (102 instance per scene) I created an attribute and called Comparescore.

the higher the layer to better it keeps its constrain

first your gonna need to make a actor, change its alpha to 0, and stretch it to cover the whole scene. Thats gonna be your touch area. Next make 2 real attributes playermotionx and playermotiony, and

ITshould be using the built in pause behavior and the built in unpause behavior. no attribute needed.

(Optional. Rule: if touch is outside) Constrain attribute (self.rotation) to VectortoAngle((game.touches.touch1x-self.positionx),(game.touches.touch1y-self.positiony))

Interpolate is a attribute to an attribute over time.

Interesting that you're seeing good sales for your other apps - you attribute this to your url link.... I don't have the url link (don't ask.... I left it too late to purchase the $100 bargain upgrade

Create two attributes. Touchx and touchy

When self.positionX < or = to -240, change attribute self.positionX to 720 + 240 + self.positionX

Why do you have a release attribute? it you use when touch is pressed to trigger your move attributes and the otherwise for that rule to reverse it you should be good.

If you press down, and then SLIDE your finger off the button, it 'locks' down that attribute and doesn't register it as a release, so the character just keeps accelerating.

Like, if you want it to be at 50 pixel more of the camera, you do constrain self.x to scene.camera.x+50, and that's true for the y as well (Image)

ButterBeans, yeah that's what I usually do, though I NEED to use the built-in attribute since it needs to affect particles, and that can only be done with that attribute, but thanks for the reply anyw