By the way: when i should use constrain and change att. in order to track attributes?

You want to display the linear velocity of an actor: a linear velocity is a fixed value and so you don't need a Constrain Behaviour at all in this....

No, im using Y and prueba like examples, and yes, im replacing the names jijiji, sometimes you create a new attribute, you delete it, create new one.. that's why i change the name, sorry for the mess

Change attribute self.Shooting to false

OK, your game attribute you've called Y: make sure this is a real attribute. This is like an integer but unlike integer, which is for whole numbers only, a real attribute shows fractions too.

I was also trying to track self.shoothingGround (the trigger to shoot) in order to detect if the status changes from false to true, but or the tracker does not work, or the value does not change. The

Gyroscope, i did what you tell me about unlocking the actor, constrain attribute and so, but the result its that the attribute who have to been updated it is not and its weird because its motion.line

Constrain Attribute:

Constrain self.motion.linear. X= 0 and the same for y...

You can't just choose accelerometer, you have to choose from the accelerometer submenu which is X, Y, and Z. Which one would I constrain from the 3?

Constrain attribute > self rotation > devices / accelerometer.

To which accelerometer attribute? There is no rotation attribute for accelerometer.

Constrain the actor's rotation to the accelerometer.

On every tap add + 1 to an attribute. same with timer, every second increase another attribute. When game over save these using save attribute as score timer And score tap. Make another 2 attributes

I can't see to get the visibility to function correctly with a change attribute. I can get it to work when I physically change the boolean, but not with the change attrib.

I haven't used that method but I'm guessing you would make the 3 an attribute and then randomize it by doing Change Attribute self.randomMod to random(3,6) and then checking to see if .05 > sel

Sounds like you solved it, but I thought I'd offer one suggestion: instead of counting the bricks and then assigning that value to the attribute, have each brick count itself as follows:

Yes -- in the examples I gave above, 'myDistance' was an attribute that you would make. It can be either an integer or a real -- depending on if you need whole numbers or if you need numbers down to

I'm working on a platformer and need to know how to keep a constrain on an actor while it can still collide. Meaning, its constrained on to an image but it is not following it's collide rule, how do I

I don't know if its me, but New Zealand apps take MINIMUM 12 days to approve, so I need this app out before Apple shuts its doors. I recently found a bug where 'every' timers get screwed up after Play