--->add a timer attribute

Create a boolean attribute called collision at false

pixel data? what exactly do you mean? are you meaning for collisions?

change attribute - game.platform - to: 1

5) If platform attribute is greater than 1, change opacity to 0 (to make it invisible) or destroy/move actor (if you want the platform entirely gone). This is for the first platform. The second plat

I have a bunch of scenes labeled Level1, Level2, Level3, Level4, etc. In my menu, I'd like to make a self.attribute in a button actor, say an integer, 4, and then, when it's tapped, it goes to Level4.

4) If player actor collides with platform actor AND platform attribute is equal to 0, change platform attribute to be 1. This is for the first platform. The second platform would use 1 and 2, the thi

1) Create a game attribute called "platform" (or whatever you'd like) using the boolean type. (Minus the quotations, of course.)

1) Create a game attribute called "platform" (or whatever you'd like) using the boolean type. (Minus the quotations, of course.)

hi is it possable to draw a wiggly line import it as a png and then constrain an actor to it so that the actor would follow the path i want it to be a smooth fluid cured movment not just a zig zag or

No worries; if you're using a change image behavior without a change attribute size behavior, the image will always appear and display to the size of the image that you've imported. There's no restric

I'm not sure if it's stuck on the first value or not. You could try constraining the attribute instead of changing it.

rule that adds 10 every second to a self number attribute in the spawning actor and having that referenced in the 'number of particles' in the particle behaviour. It doesn't have any effect, and I ha

for zooming and such. You should be able to constrain the width/height of the actor to the pinching magnitude.

Constraining will hold it in place if you have done the rules correctly. You can also throw in a constrain on the velocities to 0 but really that should not be needed.

Ok, so if I constrain self.position.x to 512 and self.position.y to 384, (ipad center) that should hold it still? I tried and it didn't work. I also tried constraining to the scene.background.position

You have to un check moveable in the prototype. that is one attribute that cannot be changed in game. If you must have it movable until that point then after your size increase you can add a constrain

I have an actor that I interpolate from small in size to fill the screen. At that point I want to make it non-moveable. I added a change attribute at the end of the rule to change self.physics.moveabl

Make a real-attribute (or an angle attribute) - game.PlanetRot

constrain self.X to ( game.PlanetRadius + game.ActorRadius )*cos( game.PlanetRotation )+ game.PlanetX