i have a jump boolean which which I have used in the runcycle. ( when attribute game.jump is true, change attribute self.motion.linearvelocityY to 500) (so that jumps while he runs)

---change attribute self.positionX to game.teleportTwoX

You could have an attribute that's a boolean called Jump, in the original animate rule, add 'if Jump is false' then animate. When you jump, turn the jump to on and then change the animation again.

so do I make 4 attribute integers?

---change attribute self.positionX to game.teleportTwoX

Have an attribute called 'Level' and make it an integer. After you complete a level (for example, level 9), change the 'Level' attribute to 9 then save the attribute (call the key whatever you want).

Unless somebody here has figured something out every icon will need at least a minimum script of either go to next scene when global attribute equals let's say 2 or 3 and so on when touch is pressed.

Each box actor should have an attribute called something like "contents"

Hi Saladfans!

Some more infos: at the moment I have only two constrain behaviours and not a single spawn behaviour. So I really try to use actor recycling. But I really do have a lot of instances of a single actor

So the way you have that set up if touched is pressed AND attribute = 1 AND attribute =5 spawn ball. So its only set up to spawn when that attribut =1. THis is how you want to set it up. First delete

I made an attribute integer with the value of one.

a hard time grasping the concept of using the attributes. I would really appreciate a brief definition or sample of when each type of attribute (integer, boolean, etc.) would be used.

how do I make it so when actor "player" colides with actor "finish" it destroys actor "player" and changes to the next scene.

which type of attribute do I make?

the reason constrain is one of the worst is it is a condition that is constantly firing or checking itself which means constant memory usage. Interpolate is actually one of the best and most precise w

interpolate is far less resource intensive than constrain. constrain is prob one of the most resource intensive.

I have a bunch of actors bobbing up and down at the same time. I've heard both interpolate and constrain can be expensive. Does anyone know if it would be worth having one actor interpolate, while t

Make the head of the arrow the game object and Constrain Attribute the shaft/feathers to the head. That way, the head will fall normally (based on your gravity settings) and the shaft/feathers will ha

you should include the original attribute of score to the computation.